Better error reporting when user does not have permissions

Bug #1553051 reported by SudhirR
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upstart
New
Undecided
Unassigned

Bug Description

Running Upstart 1.11 on a Raspbian OS.

trying to run upstart commands e.g.

initctl list
initctl list-env

as a normal user: pi on Raspbian throws this generic error message:
initctl: Name "com.ubuntu.Upstart" does not exist

When I run as sudo things are all good.

I am filing this report to check if the message can also include run as root to make it very explicit.

Revision history for this message
Steve Langasek (vorlon) wrote :

This is a usage error, not a permissions error.

When you run 'initctl' as a non-root user, by default it will try to connect to an upstart session instance.

To connect to the system init as non-root, invoke it as 'initctl --system'.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.