On Sat, Jan 15, 2011 at 10:00:42AM +0300, Andrey Borzenkov wrote: > On Sat, Jan 15, 2011 at 12:15 AM, Michael Biebl <[email protected]> wrote: > > 2011/1/14 Eugeni Dodonov <[email protected]>: > >> I know that it is perhaps a simple newbie question, but is it something > >> that must be changed in our messagebus init script (attached), or some > >> systemd configuration which we could change to make it work? > > > > Why don't you use the native systemd services files that are shipped > > with dbus 1.4.x? > > > > But it is just another method of starting D-Bus. It is still started > as part of standard startup (i.e. Fedora installs > /lib/systemd/system/multi-user.target.wants/dbus.service) and should > be stopped when multi-user.target is stopped as well. There is no > magic in handling SPECIAL_DBUS_SERVICE except attempting to reconnect > to it when it is started. > > So may be it changes timing so this problem becomes less obvious, but > I do not see how it fixes it. > > I myself never experienced problems on shutdown due to d-bus (which > seems to hint this is a timing issue). Eugeni, could you get debug > output to console up to the moment shutdown hangs? I used > systemd.log_target=kmsg, systemd.log_level=debug and set LOGLEVEL=8 in > /etc/sysconfig/init so that everything is dumped on console.
I suspect that it was a timing problem indeed, and perhaps caused by some weird interaction with some other daemon. I could not reproduce it anymore today - everything is working as expected (14 seconds boot time and 3 seconds reboot time - looks like magic to me :)). If I manage to reproduce the problem again, I'll send the log. Thanks! -- Eugeni Dodonov _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
