On Fri, 03.04.15 19:37, Andrei Borzenkov ([email protected]) wrote: > В Fri, 3 Apr 2015 14:04:10 +0200 > Lennart Poettering <[email protected]> пишет: > > > On Thu, 02.04.15 16:28, Martin Pitt ([email protected]) wrote: > > > > > Lennart Poettering [2015-04-02 13:03 +0200]: > > > > Yeah, and rightfully so. I mean, a service really should be able to > > > > shutdown if dbus is dead. In fact, it should be able to shutdown in > > > > pretty much any situation... > > > > > > They do, but that's irrelevant here. The problem is that dbus.service > > > shuts down very early as nothing prevents it from that. All > > > dependencies just refer to dbus.socket, but TBH socket (re-)activation > > > totally doesn't work for dbus. > > > > systemd will not reactivate services when shutting down, we refuse to > > go in circles... > > > > Could you elaborate? systemd will obviously start services when > starting shutdown.target. How does systemd differentiate between > services that can and can not be started?
Socket units for which a stop job is queued will suppress activations until the stop job is cancelled (ot it is stopped). Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
