<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - systemd pid 1 breaks after receiving sigquit" href="https://bugs.freedesktop.org/show_bug.cgi?id=87603#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - systemd pid 1 breaks after receiving sigquit" href="https://bugs.freedesktop.org/show_bug.cgi?id=87603">bug 87603</a> from <a class="email" href="mailto:lennart@poettering.net" title="Lennart Poettering <lennart@poettering.net>"> Lennart Poettering</a> <pre>(In reply to Konstantin Gribov from <a href="show_bug.cgi?id=87603#c3">comment #3</a>) > As I see in > <a href="http://svn.savannah.nongnu.org/viewvc/sysvinit/trunk/src/init">http://svn.savannah.nongnu.org/viewvc/sysvinit/trunk/src/init</a>. > 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? Usability? I really don't see that. The usual expection on Unix is that SIGQUIT results in an abnormal process exit with a coredump. I really don't see why PID 1 should not support that too. It's not user-friendly to add different logic here to PID 1 without a really good reason for it.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>