Comment 1 for bug 728531

I clearly didn't test this well enough ;-)

On Thu, Mar 3, 2011 at 8:22 AM, James Hunt <email address hidden> wrote:
> Public bug reported:
>
> Current natty chroot support does not seem to work reliably. Logging
> into a natty schroot as root and running "initctl list" shows:
>
> plymouth-upstart-bridge stop/waiting
> james stop/waiting
>
> Logging out of the chroot  and back in as root again, "initctl list"
> shows no output. There are 38 .conf files in my chroots /etc/init/ so we
> would always expect (atleast) 38 jobs being listed by "initctl list"
> (possibly more if user sessions enabled).
>
> ** Affects: upstart
>     Importance: Undecided
>         Status: New
>
> --
> You received this bug notification because you are a member of Upstart
> Developers, which is subscribed to upstart .
> https://bugs.launchpad.net/bugs/728531
>
> Title:
>  chroot support is not reliable
>
> Status in Upstart:
>  New
>
> Bug description:
>  Current natty chroot support does not seem to work reliably. Logging
>  into a natty schroot as root and running "initctl list" shows:
>
>  plymouth-upstart-bridge stop/waiting
>  james stop/waiting
>
>  Logging out of the chroot  and back in as root again, "initctl list"
>  shows no output. There are 38 .conf files in my chroots /etc/init/ so
>  we would always expect (atleast) 38 jobs being listed by "initctl
>  list" (possibly more if user sessions enabled).
>