systemd (Was Re: tmpfs for strategic directories)
ssorce at redhat.com
Wed May 26 18:47:41 UTC 2010
On Wed, 26 May 2010 18:20:08 +0200
Lennart Poettering <mzerqung at 0pointer.de> wrote:
> Regarding the LISTEN_PID env var:
> environment variables are normally inherited when forking/execing. We
> want to make sure that only the process we actually start ourselves
> parses and handles LISTEN_FDS. We want to avoid that if this daemon
> might spawn some other process, it might get confused into handling
> LISTEN_FDS, although that env var wasn't actually intended for it.
> And hence we say that LISTEN_PID should be verified first, and only if
> it matches LISTEN_FDS should be handled.
If you are mandating behavior in daemons, wouldn't it be simpler to
mandate the daemon unsets LISTEN_FDS ?
If I replace the process with a script, or the dameon runs other
processes LISTEN_PID is going to be wrong anyway, not sure how useful
it really is.
You are assuming that the process you run is always going to be *the*
daemon. I think it is an unrealistic assumption to make.
Simo Sorce * Red Hat, Inc * New York
More information about the devel