On Sat, 13 Jun 2015 20:48:15 +0200 Laurent Bercot <[email protected]> wrote:
> > Hello, > > A part of systemd's Embrace And Extend strategy is to entice > daemon authors to link against the systemd library (and thus make > every possible daemon systemd-dependent) by pretending it is the > only way for them to notify readiness. > > As a step to obstruct that, I have written "sdnotify-wrapper". It's > a wrapper for daemons using the simple "write a newline" readiness > notification mechanism advertised by s6, which converts that > notification to the sd_notify format. So, it makes it possible for > daemons to *not* use the sd_notify() interface and still be properly > managed under systemd. > > http://skarnet.org/software/sdnotify-wrapper.c And now the questions begin :-) When I write my own daemons (for use with daemontools, daemontools-encore, runit, and soon to be S6), I use stdout to write to the log. Wouldn't the writenewline/close interfere with that? How do I take advantage of sdnotify-wrapper if I'm using S6? How do I take advantage of sdnotify-wrapper if I'm using daemontools-encore? I really like the fact that you've taken the fight to systemd. By all means, let *them* add the extra word in their unit files. SteveT Steve Litt June 2015 featured book: The Key to Everyday Excellence http://www.troubleshooters.com/key
