On Tue 2016-11-22 12:21:57 -0500, Andrew Gallagher wrote: > It appears sks no longer (since 1.1.6) creates a pidfile. This means that a > standard > cron job such as 'kill -USR2 $(</var/run/sks/sksdb.pid)' no longer works. The > init > script still contains the arguments '--pidfile $SKSDBPID' and '--pidfile > $SKSRECONPID' > but these appear to have no effect. […] > Init: systemd (via /run/systemd/system)
pidfiles are a (traditional) gross hack and are sloppy and insecure.
For example, a process ID can be easily accidentally reused if the
process dies for some reason, and the pidfile remains. then you'd be
sending a signal to who-knows-what process!
That said, what you want to do is reasonable; it's just that pidfiles
aren't a great way to do it.
You're using systemd, and sks should be running under the control of
systemd. If you want to send a signal to the "sks db" process
supervised by systemd, you should do:
systemctl kill --signal=SIGUSR2 sks
That avoids all possible problems with pidfiles, and it doesn't clutter
the filesystem.
I'm closing this bug report because i consider it not a bug that no
pidfile is created.
If you have other concerns, feel free to reopen this report with an
explanation, or just open a different report.
Regards,
--dkg
signature.asc
Description: PGP signature
