Package: sysklogd Version: 1.4.1-16 Severity: normal
Due to some human mistke, /etc/syslog.conf has been moved to /etc/syslog.conf.0 After next cron, syslog has been restarted, but with an empty conf file. Thus no logging were done AT ALL. I restarted manually the daemon several times: # /etc/init.d/sysklogd restart Restarting system log daemon: syslogd. loks ok, did not change anything -1- syslogd should shout/cry something when its defaulh conf file is empty, or invalid, so that restarting the daemon says something, even trying to keep the daemon alive, but at least mention an error. -2- when /etc/syslog.conf is broken, invalid, incompleet, it should still try to: -a- fill /var/log/syslog any way -b- complain about invalid conf file in both: current console, tty1, and the console from which it have been restarted. The problem is that syslogd is the key daemon to track all errors; if it does not complain itself about internal errors, then there is no way to track why there is no more logging. Logging everywhere any errors about parsing the conf file, or opening logging files/devices would in one shot solve side bugs like #2883 #59662 #100043 ( maybe not directly remove the bug, but would help a lot in tracking such bugs) -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages sysklogd depends on: ii klogd [linux-kernel-log-dae 1.4.1-16 Kernel Logging Daemon ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
