On Wed 2016-11-23 05:59:19 -0500, Andrew Gallagher wrote: > On 22/11/16 17:54, Daniel Kahn Gillmor wrote: >> >> You're using systemd, and sks should be running under the control of >> systemd. > > That addresses my use case, but not the case of someone using > traditional init - is this not supported?
If you use sysvinit, then /etc/init.d/sks will be invoked, rather than
the sks daemons being managed by the sks.service and sks-recon.service
files. Unless someone else steps up, /etc/init.d/sks is not as
well-maintained as the .service files, as i personally have no systems
left running sysvinit.
I also believe the sysvinit system management mechanisms are not as good
as systemd's in this case, fwiw, and their use of a pidfile instead of
well-tracked state based on process tree and control group management is
just one example of that inferiority.
So in the case that someone is using sysvinit, i believe that the
pidfile will be created (though i haven't tested it). That doesn't mean
that i would recommend anyone actually relying on the pidfile for
anything, for the reasons i outlined in my earlier e-mail.
Regards,
--dkg
signature.asc
Description: PGP signature
