'telinit u' relies on the dbus system bus

Reported by Steve Langasek on 2012-12-08
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upstart
Medium
Unassigned

Bug Description

Unlike most initctl commands, 'telinit u' is implemented in such a way that it only works over the dbus system bus. Since this is a root-only command, this should not require dbus for operation, but should support connecting directly to upstart.

I discovered this issue when packaging 1.6.1 for inclusion in Debian, where the dbus package does not yet have upstart integration and so upstart is never signalled to reconnect to the system bus.

James Hunt (jamesodhunt) on 2012-12-10
Changed in upstart:
status: New → Confirmed
importance: Undecided → Medium
James Hunt (jamesodhunt) wrote :

Also, telinit needs to be able to use UPSTART_SESSION [1], to allow Session Inits to be restarted.

[1] - see https://wiki.ubuntu.com/FoundationsTeam/Specs/RaringUpstartUserSessions

On Fri, Jan 18, 2013 at 04:54:16PM -0000, James Hunt wrote:
> Also, telinit needs to be able to use UPSTART_SESSION [1], to allow
> Session Inits to be restarted.

I think that's conflating issues. The 'telinit' command is a standard
interface for init; user sessions would preferably be managed via initctl,
rather than changing the behavior of telinit in surprising ways.

James Hunt (jamesodhunt) wrote :

Technically it would only be surprising for the root user running a Session Init since that user would need to unset UPSTART_SESSION from within a session (or provide some new option to telinit) to manipulate the system as opposed to their own session. But that is indeed ugly behaviour. So yes, we'll have to introduce a secondary command interface to trigger a re-exec.

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

Other bug subscribers