On Sun, 22 Jan 2017 20:59:04 -0700 Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > It is possible to get a log of events following journald shutdown. See > the section under Shutdown Completes Eventually > > > https://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1 Thank you very much for this. It took a few reboots, but I think I now know what the problem is. [ 134.831290] systemd-shutdown[1]: Sending SIGKILL to remaining processes... [ 134.839939] systemd-shutdown[1]: Process 1708 (plymouthd) has been marked to be excluded from killing. It is running from the root file system, and thus likely to block re-mounting of the root file system to read-only. Please consider moving it into an initrd file system instead. I'm not sure this is the problem, because the system didn't stall at shutdown once I modified the kernel line with the added options, systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M enforcing=0 I might just leave them, since systemd is more chatty with them enabled, mentioning every problem it encounters. The only thing is I'll have to remember to setenforce 1 at start, and setenforce 0 before shutdown. Or just remove the enforcing=0, and remember setenforce 0 before shutdown. Is there anything I can do as a user to remedy this issue with plymouthd? _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
