On Mon, Feb 1, 2016 at 6:28 PM, Justin Garrison <[email protected] > wrote:
> /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 > The signals are documented in `man systemd`. Not all `kill` implementations support all realtime signal names; note that /bin/kill is different from bash's built-in `kill` (the former recognizes "RTMIN+" as a generic prefix, the latter only has a static list of names so you need RTMAX-8 instead). > 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 > > > _______________________________________________ > systemd-devel mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/systemd-devel > > -- Mantas Mikulėnas <[email protected]>
_______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
