Re: Option for runsv/runsvdir to specify how many times to restart a service in a certain time period before giving up?

[Laurent Bercot <ska-supervision@skarnet.org>]

> The problem with pid files is race conditions. I don't see that as being a 
> problem here, as there is a single thread of execution between ./run and 
> ./finish. ./finish should be able to reliably store whatever state it 
> needs in the file system. Or do you see something which I don't?

 I haven't thought of the problem in much detail - and I probably won't
in the foreseeable future: until I've finished writing my own supervision
suite, which may take an indeterminate amount of time, Gerrit's the definite
authority on the subject and I'll trust his decision ;)

 However, I've written enough buggy code to know that devil is in the
details, and enough overall Unix code to know where danger resides. And
there's a warning sign going off in my head here: bzzzt! storing
short-lived data in the filesystem - potential problems ahead!

 Not saying it can't work, of course; but there might well be more than
meets the eye at first sight, and that implementation decision should not
be taken lightly and without caution.

-- 
 Laurent