Hi,
On 27.03.2014 02:29, Michael Biebl wrote:
Thanks a lot for the back trace!
I'm glad I could help.
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).
This is great news, at least for me, as I now can reboot this machine.
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.
You're right, I can still make a half-way decent reboot, and that's what
I'm going to do now.
Best regards,
Andreas
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
