[Pkg-systemd-maintainers] Bug#732157: Bug#732157: Want SIGSTOP-style daemon/service readiness notification

[Vincent Bernat]

 ❦ 14 décembre 2013 23:17 CET, Ian Jackson <ijackson at chiark.greenend.org.uk> :

>> Another big problem with raise(SIGSTOP) is that if done on an init
>> system that can't handle it will result in a freeze. OTOH
>> sd_notify() handles this gracefully and just becomes a NOP.
>
> It seems to me that this would be handled by running the daemon with
> an argument so that it knows what to expect.  By default it will
> probably call daemon(3), after all, and there'll have to be a way to
> tell it not do that.  So I don't think this is a realistic problem.

I have implemented this raise(SIGSTOP) stuff by checking if I am running
under upstart by looking at UPSTART_JOB environment variable.
-- 
Don't just echo the code with comments - make every comment count.
            - The Elements of Programming Style (Kernighan & Plauger)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20131215/4f0ac7ad/attachment-0002.sig>