[systemd-bugs] [Bug 87603] systemd pid 1 breaks after receiving sigquit

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=87603

--- Comment #4 from Lennart Poettering <lennart at poettering.net> ---
(In reply to Konstantin Gribov from comment #3)
> 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?

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.

-- 
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/20141223/6d95b12f/attachment.html>