Package: dsyslog Version: 0.5.0 Severity: normal If you fail, as I usually do, and create a dsyslog.conf that doesn't parse correctly, dsyslog will just fail to start, but not provide you with any information about why. This is because it logs its config errors to syslog, which is itself! :)
It would be good if these types of errors were spit out to STDERR so you had a chance of knowing what was up. Another option would be to add a --conftest/--configtest option which would parse the config and give you some clues about your failure. micah -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-vserver-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages dsyslog depends on: ii libc6 2.9-7 GNU C Library: Shared libraries ii libglib2.0-0 2.20.1-1 The GLib library of C routines ii libgnutls26 2.6.5-1 the GNU TLS library - runtime libr Versions of packages dsyslog recommends: ii logrotate 3.7.7-3 Log rotation utility Versions of packages dsyslog suggests: pn dsyslog-module-gnutls <none> (no description available) pn dsyslog-module-mysql <none> (no description available) pn dsyslog-module-postgresql <none> (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
