Sounds much as if you delete the /var/log files or set the wrong permissions, it wont log any information, but will continue to run. The other solution would be to d/l the services file or simply recreate it to allow syslogd to continue to run properly!
----- Original Message -----
From: Xuanzhou Dong
To: sysklogd@infodrom.north.de
Sent: Wednesday, July 18, 2001 5:28 PM
Subject: A Bug with syslogd in syslogd.c
For Version 1.3-33
The current syslogd daemon doesn't create the /dev/log unix domain socket if it
can't get the service port for syslog.
So if someone deletes the syslog service entry in /etc/sevices, syslogd will continue
to run. But since the /dev/log is not created, this makes no sense.
The fix seems to be very straightforward. A rearrangement of the code in init() in syslogd.c
should solve this problem.
This archive was generated by hypermail 2b30 : Thu Jul 19 2001 - 04:22:08 CEST