On 08/08/2012 11:14 PM, "Jóhann B. Guðmundsson" wrote: > On 08/08/2012 05:30 PM, Lennart Poettering wrote: >> On Tue, 07.08.12 16:01, David Strauss ([email protected]) wrote: >> >>> On Sat, Aug 4, 2012 at 4:46 AM, Lennart Poettering >>> <[email protected]> wrote: >>>> (But please, don't implement this bit just yet, let's wait for somebody >>>> actually needing this. Note though, that Upstart actually does have >>>> functionality like this). >>> There are broken daemons like the "cluster" support in node.js that >>> return non-zero on clean shutdowns. While this is broken behavior, it >>> seems the systemd standard is to support broken/non-standard behavior >>> with optional settings. (That is, the default in systemd is a >>> well-behaved application.) >> Hmm, I was kinda waiting for use cases like this. i.e. before we add an >> option to reconfigure what clean exits are I wanted an explicit request >> for it, so that we don't end up adding something that is actually >> unncessary. >> >> Added this to the TODO list now. > > Should not this be fixed in the daemon instead of worked around in systemd? In principle yes, but some of the daemons that are broken are pretty heavy-weight: sshd [1], java [2].
[1] http://lists.freedesktop.org/archives/systemd-devel/2011-March/001656.html [2] http://lists.freedesktop.org/archives/systemd-devel/2011-December/004069.html I'm all for fixing things upstream, but sometimes it's hard. Zbyszek _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
