[systemd-devel] [PATCH] analyze/run: Use bus_open_transport_systemd instead of bus_open_transport.

[Zbigniew Jędrzejewski-Szmek]

On Mon, Feb 24, 2014 at 07:35:12PM +0100, Thomas Bächler wrote:
> Am 24.02.2014 17:10, schrieb Lennart Poettering:
> > On Fri, 21.02.14 11:55, Thomas Bächler (thomas at archlinux.org) wrote:
> > 
> >> Both systemd-analyze and systemd-run only access org.freedesktop.systemd1
> >> on the bus. This patch allows using systemd-run --user and systemd-analyzeefau
> >> --user even if the user session's bus is not properly integrated with the
> >> systemd user unit.
> > 
> > I am not convinced this is really desirable. The private socket exists
> > solely to make sure we cann communicate during really early boot and
> > during late shutdown with it, but neither systemd-analyze nor
> > systemd-run really appears to be tools that need to support that?
> 
> I am not saying it is desirable (it is not). I am saying it may be
> necessary.
> 
> Short reason: We don't live in a perfect world yet.
> 
> Long reason (sorry, this is going to be really long):
tl;dr

> 3) (why not?)
> 
> It doesn't hurt anyone. Both tools only ever connect to
> org.freedesktop.systemd1, never to anything else. Whether we connect via
> the "normal" bus or the private one does not matter, the functionality
> provided will be the same.
Yeah, we have bigger fights to fight, and this seems to be something that
trips up a lot of people. This workaround may not be the nicest thing, but
it should work without causing additinal issues. Pushed patch now.

Zbyszek