My take-away from this and the related threads is that a daemon author would ideally provide options to have it: * Either write log messages to stderr or syslog, but write the same data regardless; * Either stay running in the foreground, or auto-background itself once it's ready to begin taking requests; * Write a PID file only at the user's request--that is, only if a path is given.
I figure it's up to the user to select the combination of options suitable to address the task at hand, and it's up to the distro to select the sensible defaults. -Jude On Sat, Jun 13, 2015 at 2:37 PM, Laurent Bercot <ska-de...@skarnet.org> wrote: > On 13/06/2015 08:40, Didier Kryn wrote: > >> Yes, daemon writers are good-willing developpers; they want their >> software to serve as many users as possible; and users install >> distros. This gives power to the distros. But if someone provides >> them with a KISS readyness-signaling method, along with a systemd >> wrapper, then they can satisfy RedHat's requests at no cost. >> > > And there you go: > http://skarnet.org/software/sdnotify-wrapper.c > > Untested with a real systemd, because I'm not going to install a > real systemd anywhere - but I've listened to a socket on the other > end of NOTIFY_SOCKET and it appears to work. Bug-reports welcome. > > > The question now is who will develop, maintain and package this >> wrapper? Will Devuan be the official developper of >> "Systemd-Readyness-Wrapper", or can anyone convince Openssh or who >> else to take the job? Or are the daemon's developper powerfull enough >> to tell RH "do it yourself."? >> > > I'm willing to maintain this for the time being; as long as systemd > does not gratuitously break compatibility with itself, it should not > be too hard. The goal is to encourage daemon developers to stop using > the sd_notify() interface and just write a newline somewhere; the > wrapper is just there to make this simple behaviour work with systemd, > nothing more. > > I firmly believe it should *not* be packaged by Devuan. The wrapper is > meant to only be used on systemd installations, which is exactly what > Devuan is not. Devuan can advertise such a wrapper, advocate its use, > but I don't think it makes sense for it to be a part of the Devuan > distribution. > > I'm providing a single C file for now. I can turn it into a complete > package tarball with configure/make/make install if there's interest. > I'm not going to make distribution-specific packages, though; that's > the job of distribution maintainers. > > Enjoy! > > -- > Laurent > > _______________________________________________ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng >
_______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
