Hello. Martin, I'm waiting for your response since spring, I'll NMU sysklogd soon ... ----- for policy: system-log-daemon: Reads messages from /dev/log and provides syslog-facility. Conflicts with other system-log-daemons. kernel-log-daemon: Reads messages from /proc/kmsg or per ioctl and writes them to /dev/log. Conflicts with kernel-log-daemon. ----- They need to conflict with themselfes, because: o Many provide identical files (/etc/syslog.conf, /sbin/syslog-facility), alternatives are not applicable because of the fast differences in formats and interfaces. o More than one instance of a daemon can only be run with special configuration (and can be avoided), else they would read or write the same sockets, which would lead to chaos. May be the interface of syslog-facility should get formalized, or at least frozen. A nice thing to do would be to split the sysklogd package into a syslogd and a klogd part. This would allow syslog-ng to use klogd without a Replaces: (I consider the current situation a cludge). ciao, 2ri -- Der beste Beweis für die Existenz ausserirdischer _Intelligenz_ ist der, dass noch niemand versucht hat, Kontakt mit uns aufzunehmen. -- Bill Watterson
Attachment:
pgpjFJSQob7pT.pgp
Description: PGP signature