Bug#770644: systemd: can't start dbus if dbus is not running

[brian m. carlson]

On Fri, Mar 20, 2015 at 03:45:30AM +0100, Michael Biebl wrote:
> That systemd freezes when it dies is expected behaviour and the only
> real sensible thing to do. At this point, you can only reboot, to get
> back into a defined state. You'll need reboot -f here, which bypasses init.

sysvinit doesn't have this problem.  An init system needs to be reliable
all the time; if it receives a fatal signal, it needs to re-exec and be
completely functional again.  Anything else is unacceptable from init.

Since systemd replaces sysvinit, it should be as reliable and functional
as sysvinit.

> What I was interested in, when I was asking about steps to reproduce
> this issue, is how the crash was triggered.
> I know that I can kill systemd via "kill -s ABRT 1", but that was not
> the point of my question.
> 
> I'm interested the cause for the crash.

I don't know why it happened.  All I know is that systemd stopped
working on my server and my laptop, once each, randomly.  I've provided
you with everything I know about the problem.
-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150324/25006efe/attachment-0002.sig>