On Fri, 01 Jan 2016 19:05:50 +0100 Kamil Cholewiński <[email protected]> wrote:
> > sat will create a PID file in $XDG_RUNTIME_DIR. > > PID files are a flawed concept, race conditions and > everything. Well. But they are standard. satd does not use the PID file to determine whether it is running, it uses flock. There is still a possible, less important, race condition, but this can be fixed if one thought it was worth it. > > > How could supervision be made mandatory without making > > it tied into one solution. > > Simple: just don't fork, don't write PID files, don't do > anything. You can turn /bin/cat into a daemon under > supervisord, runit, svscan, systemd, nohup &, or any > other of the million solutions, as long as you don't try > to outsmart it. Would this not require that the user configures satd to be started by the supervisor? I would not want this because I would almost never it. 'satd -f' will cause it not to fork, or do other things that a traditional daemon would do. > > K.
pgpPM7MgHWm1x.pgp
Description: OpenPGP digital signature
