On Tue 2016-08-09 08:36:02 -0400, Christoph Anton Mitterer wrote: > It seems that, probably since the systemd unit files were added, > sks no longer logs to /var/log/sks/ > Either that should be restored, or that dir and it's contents > cleaned up.
Some systems don't have systemd. On those systems, /var/log/sks is
still needed.
On systems with systemd, the logs will be handled directly by journald,
and can be accessed with:
journalctl -u sks
journalctl -u sks-recon
What do you suggest we do concretely about /var/log/sks for the systems
that don't have this facility?
I suppose one option would be to split out a separate package
sks-sysvinit, which would Depend: sks and contain:
* /var/log/sks
* /etc/init.d/sks
* the maintscripts that manage ownership of /var/log/sks
* /etc/logrotate.d/sks
* /etc/default/sks
* /etc/cron.daily/sks (? maybe we can drop this entirely)
That doesn't cover "cleaning up" the contents of /var/log/sks on
upgraded systems -- but i don't actually think that should be done by
the package. local administrators of upgraded systems can do that
clean up themselves.
it would certainly make newer sks installations on systems with systemd
cleaner and simpler!
what do you think?
--dkg
signature.asc
Description: PGP signature
