Am 26.03.2014 17:39, schrieb Andreas Cadhalpun: > Hi, > > I build systemd with debugging symbols and extracted a backtrace from > the core dump:
Thanks a lot for the back trace! This helped me to reproduce the sequence of events which need to happen to trigger the abort. So this is good news (well sort of). The sequence of events is a/ make sure cups.socket is running and correctly setup b/ make sure cups.service is not running c/ make /etc/systemd/system/cups.socket.d/cupsd-listen.conf a dangling symlink d/ trigger a daemon-reload e/ trigger activity on the cups socket, e.g. via lpq → You get the abort At this point, systemd catches the SIGABRT and freezes, i.e. no longer responds to any requests. Andreas, you mentioned: > 'Freezing execution' sounds as bad as crashing. Actually it isn't. Would systemd symply crash, your kernel would freeze. With systemd catching the SIGABRT you can at least still stop your service (even if you need to do that via kill), you can sync and unmount your fs besides / and do a half-way decent reboot. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
