Subject: FW: Broken Syslog
From: Christopher Svenstedt (Christopher.Svenstedt@framfab.se)
Date: Fri Dec 01 2000 - 12:34:26 CET
Hi,
I solved my problem (at least for now). Syslogd wants the link
/lib/libnss_files.so.2 (and lib) to be in place. This is not dissclosed with
ldd so I had to do a strace on a working system to find out. The other
minimal requirement (apart from /etc/syslog.conf, libc, ld-linux) is that
/etc/services and the entry "syslog 514/udp" is in place.
Regards,
Christopher
-----Original Message-----
From: R. W. Rodolico [mailto:rodo@dailydatainc.com]
Sent: den 20 november 2000 07:41
To: sysklogd@infodrom.north.de
Subject: Broken Syslog
I'm having a problem with syslog. I am using syslogd 1.3-3#33.1. For
some reason it can not create /dev/log. The result is all of my logging
is going to the console instead of to the log files. I have tried
sending a message to the logs using the logger program, but have the
same result.
I know very little about syslog, and have tried the debian isp mailing
list, but everyone there is as lost as I am. My only option if no one
can help me is to take down a working system and re-install as I am
very lost here.
FYI, I am using the 2.2.17 kernel, with RAID support patched in. I have
installed from the Debian potato distribution.
Any help would be greatly appreciated.
Rod
R. W. Rodolico
Daily Data, Inc.
POB 140465
Dallas TX 75214-0465
214.827.2170
It appears I could be pursuing an untamed ornithoid to no purpose.
--Brent Spiner as Data, Star Trek: The Next Generation
This archive was generated by hypermail 2b25 : Fri Dec 01 2000 - 12:37:58 CET