Re: pid file security
]] Russell Coker
| > in other words, a service is _always_ run
| > in "foreground" mode. if it dies (i.e. a segfault signal is caught),
| > the service is restarted automatically - by depinit (based on the
| > signal alone). thus, the need for safe_mysql goes away entirely; the
| > need for "apache2ctl start" goes away (i.e. you use apache2 -c
| > FOREGROUND=True or whatever it is) and so on. in this way, there
| > simply _is_ no need for a PID file, period. the relevant state
| > information is contained within depinit itself, and you can guarantee
| > that depinit will catch the signal.
| systemd does all that.
More importantly: systemd _allows_ them to do that, it doesn't require
them. From the description of depinit, it sounds like it requires all
daemons to be modified.
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are