Re:Systemd has 6 service startup notification types, and the...
by bkor on Wednesday May 28, 2014 @09:32AM
(#7809780)
The code for that is stable, it is just that the recommended way is using that library. When people asked, the code was provided to do this without linking. Just that linking is way more reliable.
The comment should've stated something like "the way to do this is not documented". The way it is currently worded implies something totally different.
Re:Systemd has 6 service startup notification types, and the...
by rlpb on Wednesday May 28, 2014 @10:46AM
(#7810209)
> Just that linking is way more reliable.
Why? Is not linking somehow unreliable? You can't have it both ways. Either it is stable, or it is not.
Re:Systemd has 6 service startup notification types, and the...
by bkor on Wednesday May 28, 2014 @08:56PM
(#7813995)
Don't put words into my mouth to win an argument.
I'm saying that linking to a function is more reliable than copy/pasting that stuff into your program. If you want to argue that copy/pasting is totally fine, go ahead. I'm sure enough people will respond to that :-P
Edit: Interestingly, it looks like one of the other Wiki pages[1] does specificially call out the underlying $NOTIFY_SOCKET protocol as a stable interface. (Then points to an authoritive chart that doesn't, presumably because the implementation details of the other sd-daemon.h APIs aren't stable despite being documented in the same way?)
[1] http://www.freedesktop.org/wiki/Software/systemd/InterfaceSt...