"initctl status" no longer works as a non-privileged user

Bug #767053 reported by James Hunt on 2011-04-20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upstart (Ubuntu)
James Hunt
James Hunt

Bug Description

Binary package hint: upstart

In Maverick, the following command, run as a non-privileged user would

$ initctl status <job>

However, under the version of Upstart in Natty, this will fail:

$ initctl status cron
initctl: Unknown job: cron

... Whilst running the same command as root will succeed:

# initctl status cron
cron start/running, process 858

This problem is confined to non-priv users, but is a regression. The problem also affects the show-config and check-config commands. The problem does not affect the list command, so a work-around is:

$ initctl list|grep "^<job>"

For example,

$ initctl list|grep "^cron"
cron start/running, process 858

Related branches

James Hunt (jamesodhunt) on 2011-04-20
Changed in upstart (Ubuntu):
assignee: nobody → James Hunt (jamesodhunt)
status: New → In Progress
Colin Watson (cjwatson) on 2011-04-20
tags: added: regression-potential
Changed in upstart (Ubuntu Natty):
importance: Undecided → High
milestone: none → ubuntu-11.04
James Hunt (jamesodhunt) on 2011-04-20
Changed in upstart (Ubuntu Natty):
status: In Progress → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package upstart - 0.9.7-1

upstart (0.9.7-1) natty; urgency=low

  * New upstream release 0.9.7: Important session fix (LP: #767053).
 -- James Hunt <email address hidden> Wed, 20 Apr 2011 17:44:41 +0100

Changed in upstart (Ubuntu Natty):
status: Fix Committed → Fix Released
Chuck Smith (ccsmith) wrote :

I have package upstart - 0.9.7-1 installed but I still cannot start cron and it does not start on boot.

chuck@natty-chimera:~$ initctl grep cron

Warning: Fake initctl called, doing nothing.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers