On Tue 2016-08-09 11:10:12 -0400, Christoph Anton Mitterer wrote: > [ Unknown signature status ] > On Tue, 2016-08-09 at 10:47 -0400, Daniel Kahn Gillmor wrote: >> Some systems don't have systemd. On those systems, /var/log/sks is >> still needed. > hmm indeed... > > well actually I liked to have the logs in there so I'd have preferred > to get that for systemd systems as well...
You should be able to configure journald to forward to syslog (see
journald.conf(5)) and ask the syslog of your choice to craete whatever
log directories you prefer.
>> I suppose one option would be to split out a separate package
>> sks-sysvinit, which would Depend: sks and contain:
> I think that's overkill...
hm, it seemed like the closest thing to what you were asking for. i'm
open to other suggestions, but...
> A config switch where logging should go to, would be nice.
> Perhaps something in /etc/default/sks, that's sourced sysvinit script
> and unit files and that allows to configure even under systemd to use
> /var/log/sks?
the right place for that config switch is in the log handler, whether
that's journald or any other supervisor (e.g. runit's svlogd,
daemontools' multilog, etc).
I do *not* want to offer any options that make use of the explicit
logging code in sks; handling log rotation is a mess -- likely a cause
of bugs and hangs, esp. on systems under I/O contention. Having sks log
to stdout and then never have to think about it again is a major
engineering win, and one that i don't think we should give up where we
don't have to.
--dkg
signature.asc
Description: PGP signature
