On Thu, Jun 13, 2013 at 1:58 PM, Cristian Rodríguez
El 13/06/13 04:28, Stefan Seyfried escribió:
Am 13.06.2013 03:55, schrieb Brian K. White:
At some point long before "hundreds of packages" don't do what you consider correct, maybe it's time to say "maybe it's me?".
Of course it's you.
NO it is not, you are shooting the messenger !
There is also daemon(3), and if this one is not doing what's necessary, maybe it is simply a bug in glibc.
glibc 's daemon(3) follows BSD semantics, you cannot just fix daemon(3) without also importing BSD 's pidfile API and modifing the function in a way that is not behavior-compatible (effectively requiring a new daemon2() or linux_daemon() )
But of course, the glibc guys do not really know how to daemon(), thus the manpage in section 7 telling them what to do is necessary...
No one has ever said that, but that it does not implement all the needed steps to daemonize a complex piece of software in a race-free fashion.
This is so moot. Of all those 15 points in daemon(7), I've faced each and every one of them. They're necessary at some point or another. Maybe not all daemons care for all issues, but it's no exaggeration that they are all points to ponder when writing a daemon. It's not a systemd thing at all. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org