session support disallows user jobs with same name as system jobs

Hmm, interesting - I thought the current code allowed them to co-exist
and just "hid" the global one when in a session

On Thu, Mar 10, 2011 at 7:36 AM, James Hunt <email address hidden> wrote:
> Public bug reported:
>
> The session support added to Upstart for Natty disallows user jobs with
> the same name as system jobs. This seems like an artificial restriction.
>
> What is also missing is a D-Bus method which allows initctl to query the
> session+chroot details associated with each job. Thus, "initctl list"
> currently intermingles system jobs and user jobs with no indication as
> to which jobs are of which type.
>
> ** 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/732656
>
> Title:
>  session support disallows user jobs with same name as system jobs
>
> Status in Upstart:
>  New
>
> Bug description:
>  The session support added to Upstart for Natty disallows user jobs
>  with the same name as system jobs. This seems like an artificial
>  restriction.
>
>  What is also missing is a D-Bus method which allows initctl to query
>  the session+chroot details associated with each job. Thus, "initctl
>  list" currently intermingles system jobs and user jobs with no
>  indication as to which jobs are of which type.
>