> Yeah, most daemons that write external PID files have issues with external
> PID files left from other running instances of the same daemon. (I assume
> that's what you're talking about.) It's probably possible to avoid that
> with judicious use of file locking, but that's not common and is mor
Ian Jackson writes:
> Russ Allbery writes:
>> Yeah, this is a good point. Since systemd uses the daemon-written PID
>> file for tracking forking daemons, it doesn't have the same issues as
>> the upstart expect fork or expect daemon protocols. Obviously, an
>> external PID file is not ideal, bu
On Thu, Jan 02, 2014 at 10:04:12PM +, Ian Jackson wrote:
> Zbigniew Jędrzejewski-Szmek writes ("Bug#727708: requirement of non-forking
> startup protocol"):
> > | 8. Policy rules for support for init systems must:
> > |
> > |(a) Specify the use of a
Russ Allbery writes ("Bug#727708: requirement of non-forking startup protocol"):
> Zbigniew Jędrzejewski-Szmek writes:
> > I think this should be changed to:
> > | 8. Policy rules for support for init systems must:
> > |
> > |(a) Encourage the use o
Zbigniew Jędrzejewski-Szmek writes:
> | 8. Policy rules for support for init systems must:
> |
> |(a) Specify the use of a non-forking startup protocol (for
> |upstart and systemd),
> I'm not sure about upstart, but systemd is perfectly happy with daemons
> which double fork (Type=f
Zbigniew Jędrzejewski-Szmek writes ("Bug#727708: requirement of non-forking
startup protocol"):
> | 8. Policy rules for support for init systems must:
> |
> |(a) Specify the use of a non-forking startup protocol (for
> |upstart and systemd),
[ Replying to thi
| 8. Policy rules for support for init systems must:
|
|(a) Specify the use of a non-forking startup protocol (for
|upstart and systemd),
I'm not sure about upstart, but systemd is perfectly happy with
daemons which double fork (Type=forking in systemd parlance).
It is mildly discoura
7 matches
Mail list logo
