On 09/07/2012 01:48 PM, Lennart Poettering wrote:
On Fri, 24.08.12 00:54, Gerardo Exequiel Pozzi ([email protected]) wrote:
Hello
Just for fun I am sending some signals to systemd (188) to see how
reacts compared to sysvinit. While sysvinit ignores them or restores
from "crash" after 30 seconds of sleep, systemd/journald just logs
the status them freezing execution.
Example
kill -SEGV 1 -> freeze
kill -QUIT 1 -> freeze
Sending other signal again result in a crash (attemped to kill init)
Is this intentional? There is a way to restore systemd again without
a forced reboot?
Yes, this is intentional. If we crash (or the user kills us) we print a
warning and freeze. If the user kills us again then we return control to
the kernel. Sounds like a really reasonable reaction to some really
pointless action by the user.
I mean, the user issued the kill commands, hence he probably has a
reason to, even if that reason is "I want to shoot myself in the
foot" -- and hence we do what we do.
Lennart
OK, so in case of and internal crash, there is no way, at least this
moment (maybe in a future?), to restore from "freeze" without doing a
forced reboot?
Thanks for your answer.
--
Gerardo Exequiel Pozzi
\cos^2\alpha + \sin^2\alpha = 1
_______________________________________________
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
