Comment 34 for bug 430224

I have setup where I put clients in chroots, each client has it's own chroot. has been running on jaunty, and everything was great.

Now I upgraded one chroot to lucid, and I can't start services in client chroot:

[chroot] # /etc/init.d/atd start
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service atd start

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the start(8) utility, e.g. start atd
start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused

[chroot] # start atd
start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused

While all talk about future enhancements is great - what I can do *now* to get the atd/crond/others to run in the chroot?