This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH 4/4] Mark nscd service as forking in systemd service file (#16639)


On Wed, Feb 26, 2014 at 07:39:51PM -0800, Russ Allbery wrote:
> The sd_notify(3) protocol uses an environment variable to signal whether
> to do startup notification and skips the notification if that variable
> isn't set, so a service that supports Type=notify can still be used in the
> other ways with no negative effects.  The notification will just be
> skipped.  Of course, nscd still has to have that code, and in the glibc
> context that probably means open-coding the sd_notify call in the nscd
> source, which is not horribly attractive.  (But the shared library
> dependency issues are probably even worse.)

systemd fans who responded to one of my rants about systemd replied
claiming the intended usage of sd_notify is to copy the code into your
program rather than using the library. However, I suspect there are
license/copyright assignment rule issues that would prevent glibc from
using this approach unless the file is public domain and properly
documented as such.

However, this does mean systemd is (or at least needs to be) promising
to keep the underlying mechanism used by sd_notify stable, so an
alternate approach would be re-implementing sd_notify and assigning
the copyright to the FSF so it could be used in glibc and other GNU
code. (Or, preferably, making it public domain with the proper legal
paperwork so non-[L]GPL projects could use it too.)

Rich


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]