In fairness, readiness notification does seem to require application-specific integration in general under current constraints of most Unixes.

Good work, nonetheless. sd_notify isn't complicated, to their credit.

On 06/13/2015 02:48 PM, Laurent Bercot 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

 Enjoy,
 Bug-reports welcome.


Reply via email to