Am 21.01.2013 02:32, schrieb Andres Salomon: >>> A better approach imho would be to simply remove sysklogd from the >>> archive. It's dead upstream, apparently no longer properly >>> maintained in Debian, and there are enough more then suitable >>> alternatives. With rsyslog we even have a drop-in replacement. >>> >> I've added a hint to remove it from wheezy. > > Hm. Rather than simply remove it, can we actually provide an upgrade > path to rsyslog? I'd be happy to NMU a version of ksyslogd that > does this in unstable (for consideration in wheezy), as long as rsyslog > is truly a drop-in replacement. It was an explicit decision back then, to not remove sysklogd automatically on upgrades. If sysklogd/klogd are converted to transitional packages, which simply pull in rsyslog, then any configuration changes should be migrated over to then new config file, imo. sysklogd uses /etc/syslog.conf and rsyslog /etc/rsyslog.conf > It seems that new squeeze installs default to using rsyslog. However, > I still have several older systems that've been upgraded from earlier > Debian releases that are still using ksyslogd/klogd. There's been no > indication that ksyslogd had been deprecated in favor of something > else. Something like http://www.debian.org/releases/lenny/i386/release-notes/ch-whats-new#system-changes That said, a removal of the package is a clear indication that the package is no longer maintained and should be replaced, isn't it? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Attachment:
signature.asc
Description: OpenPGP digital signature