[systemd-devel] [PATCH] dbus: fix --system handling

Lennart Poettering lennart at poettering.net
Mon Oct 25 15:26:04 PDT 2010


On Fri, 15.10.10 12:25, Robert Schwebel (r.schwebel at pengutronix.de) wrote:

> We currently only create the private D-Bus server when pid == 1, but
> this has also to be done if the user started us with --system.
> Otherwhise we get this error:
> 
>   systemd-cgroups-agent[164]: Failed to get D-Bus connection:
>   Failed to connect to socket /org/freedesktop/systemd1/private:
>   Connection refused

Sorry for the delayed reply. Needed to think a bit about this.

Your patch would break running "systemd --system --test" to verify the
systemd setup as normal user, since that second instance would fight for
the same socket as the main (PID 1) instance, and this hence would
break.

Note that we do not support booting a real system with systemd on PID !=
1. The primary reason for that is that we need the SIGCHLD signals
properly, and we only get those as PID 1. Early systemd versions
supported a mode where we didn't rely on those signals. However, we
removed that after a while, since I didn't see much benefit in this mode and
I was unable and unwilling to keep this mode working and do the
necessary testing.

Sorry,

Lennart

-- 
Lennart Poettering - Red Hat, Inc.


More information about the systemd-devel mailing list