4 ms·
https://www.freedesktop.org/software/systemd/man/systemd.html https://www.freedesktop.org/software/systemd/man/systemd.htm... - See signals It's init dependent
by abofh 9y ago
https://www.freedesktop.org/software/systemd/man/systemd.html https://www.freedesktop.org/software/systemd/man/systemd.htm... - See signals
It's init dependent (though I think SIGKILL is blocked at the kernel – I wouldn't swear to it) - sigrtmin+3 will likely kill your init process :)
- gerdesj 9y agoCor, the locals are a bit harsh here. I've just run # kill -L - there seem to me rather more signals available than I remember from the past. I'm pretty sure I have never even heard of the ones >16 let alone SIGRT{MIN|MAX}{|x}. I've only ever used SIGHUP or SIGKILL in general and SIGUSR1 for dd progress (which now has --progress at last) Time to dig out the manual 8)
- int0x80 9y agoIn Linux, from the manpage: "The only signals that can be sent to process ID 1, the init process, are those for which init has explicitly installed signal handlers. This is done to assure the system is not brought down accidentally." And SIGKILL can not be captured (enforced by the kernel): "The signals SIGKILL and SIGSTOP cannot be caught or ignored."