Bug#761576: systemd: fails to shutdown after changing to sysvinit

[Thorsten Glaser]

Michael Biebl dixit:

>This is not necessary. sysvinit's shutdown/reboot etc utility are able
>to talk to systemd and vice versa.

Hm okay.

>No, this seems wrong. Besides, we first need to know what went wrong.

Agreed.

>Please provide at least the versions that were installed.

Right; the system was rebooting at the time I wrote the report,
and we’ve debugged more things since. Now I can look at apt/term.log:

Removing libpam-systemd:amd64 (208-8) ...
Removing systemd-sysv (208-8) ...

>Also a debug log from the (failed) shutdown would be really helpful [1].

>[1] http://freedesktop.org/wiki/Software/systemd/Debugging/
>(/usr/lib/systemd/system-shutdown/debug.sh would be
>/lib/systemd/system-shutdown/debug.sh on Debian)

Hm, probably not after purging it…

I understand if you cannot work without the logs, but I wanted
to have this problem at least recorded somewhere…

bye,
//mirabilos
-- 
[...] if maybe ext3fs wasn't a better pick, or jfs, or maybe reiserfs, oh but
what about xfs, and if only i had waited until reiser4 was ready... in the be-
ginning, there was ffs, and in the middle, there was ffs, and at the end, there
was still ffs, and the sys admins knew it was good. :)  -- Ted Unangst über *fs