control: tags -1 wontfix

So, the krb5 packages as installed log to syslogd/journald and do not
log to kdc.log.

debian edu is doing something to change that, which is probably a debian
edu bug.  Also, it seems likely that if debian edu is messing with the
config files of krb5, it's a serious bug under policy because debian edu
is messing with the configuration of a package not its own.

If you are going to change the logging, then you can also add a systemd
fragment that gives the kdc permission to write to that log.
But another package in Debian should not make this change and override
krb5's decisions about where its logs go.

--Sam

Reply via email to