[systemd-bugs] [Bug 87603] systemd pid 1 breaks after receiving sigquit
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Dec 22 11:11:13 PST 2014
https://bugs.freedesktop.org/show_bug.cgi?id=87603
--- Comment #3 from gross <grossws at gmail.com> ---
As I see in
http://svn.savannah.nongnu.org/viewvc/sysvinit/trunk/src/init.c?annotate=159&root=sysvinit
(around line 1146) sysvinit set SIG_IGN for SIGQUIT.
It seems that OpenRC isn't an init (it provides rc but not /sbin/init), so it's
behavior depends on underlying sysvinit/bsd-init.
I don't see any SIGQUIT handler in upstart (and libnih), so it should behave
like systemd, with pid 1 core dumped and broken system after `kill -SIGQUIT 1`.
It's not a security problem, of course. It's at most an usability problem. Is
default core dump required for debugging systemd? Is there any reason not to
ignore it?
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20141222/c109d106/attachment-0001.html>
More information about the systemd-bugs
mailing list