[systemd-devel] systemctl isolate disconnects network

Justin Garrison justinleegarrison at gmail.com
Mon Feb 1 08:28:39 PST 2016


>
> /bin/kill -RTMIN+22 1
> systemctl islolate ...
> journalctl -b


-RTMIN+22 doesn't appear to be a valid kill flag and I couldn't find
documentation on which flags do what for systemd
I tried -RTMIN+2 and the system hung and told me it was going to shut down
but didn't. I switched ttys and tried to isolate multi-user again and
interestingly enough network didn't die this time. This is all I see in the
journal.

Feb 01 08:22:32 systemd[1]: Started /etc/rc.d/rc.local Compatibility.
Feb 01 08:22:32 systemd[1]: Starting Wait for Plymouth Boot Screen to
Quit...
Feb 01 08:22:32 systemd[1]: Starting Terminate Plymouth Boot Screen...
Feb 01 08:22:32 systemd[1]: Received SIGRTMIN+21 from PID 11533 (plymouthd).
Feb 01 08:22:32 systemd[1]: Started Terminate Plymouth Boot Screen.
Feb 01 08:22:32 systemd[1]: Started Wait for Plymouth Boot Screen to Quit.
Feb 01 08:22:32 systemd[1]: Started Getty on tty1.
Feb 01 08:22:32 systemd[1]: Starting Getty on tty1...
Feb 01 08:22:32 systemd[1]: Reached target Login Prompts.
Feb 01 08:22:32 systemd[1]: Starting Login Prompts.
Feb 01 08:22:32 systemd[1]: Reached target Multi-User System.
Feb 01 08:22:32 systemd[1]: Starting Multi-User System.

--
Justin Garrison
justingarrison.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20160201/608d4d3e/attachment.html>


More information about the systemd-devel mailing list