1. Syslogd 1.3-3
Running Sysklogd 1.3-3 and Linux 2.0.36
Greg,
There is apparently a bug in syslogd 1.3-3 and earlier versions, which
fails to properly record kern.debug messages.
Some kern messages are logged, but others are not, in particular SCSI
error messages and logger messages, amongst others.
For example the following command was issued with the following
syslog.conf entries.
logger -p kern.debug This is a debug message
kern.debug /dev/console # Will not record it
kern.* /dev/console # Will not record it
*.debug /dev/console # Works properly
*.* /dev/console # Works properly
Of course I may be in complete error about how all this is supposed to
work, but if I am right, you can imagine that failing to properly get
kernel warnings and errors can be a severe security and system integrity
risk.
We discovered the problem because in fact SCSI error messages were
being missed and a disk drive crash did happen. The errors were being
logged in dmesg, but not in /var/log/kern with the following line in
syslogd.conf
kern.debug /var/log/kern
kern.debug /dev/console
There are also possible inconsistencies, sometimes NFS warnings
show up on some machines, and on others they don't with similar
syslog.confs.
As I have said, I am not an expert at this, but clarification on these
matters would oblige me greatly and set my mind to rest.
Thanks Homer
------------------------------------------------------------------------
Homer Wilson Smith The paths of lovers Art Matrix - Lightlink
(607) 277-0959 cross in Internet Access, Ithaca NY
2. COL 2.3 & MC
3. Syslogd 1.3 problem
4. ISDN + Fritz! Card PCI + AVM drivers
5. syslogd 1.3 dumps core, what's wrong ?
6. MySQL install barfs on m68k?
7. selection 1.3: patch for 3-button Mouse Systems devices
8. That Was Cool
9. NIS/YP patch for NCSA httpd 1.3, 1.4
10. Patch for ProxyPreserveHost feature in apache 1.3
11. 3c509 and 1.3.6x/1.3.7x
12. Patches fro Solaris2.51 and SunOS4.1.3
13. DOSEMU 0.60.4 + Linux 1.3.x: Need patch/help to compile EMUMODULES