PROBLEM WITH EVENT MONITORING USING REPLACEMENT SYSLOGD

mark newnham at HZBNO05A MAN - GBGMT000 (mark.newnham@grandmet.co.uk)
Fri, 19 Apr 1996 09:18:05 EDT

===============================================================================

System: tkined/scotty on Linux.
Software. syslogd 0.4
I have noticed that if the 8567 port is used to connect to the syslogd
daemon, the event monitor fails to report certain events. The same
does not happen if the syslog file is monitored directly. Examples of
failures are
1) syslog reporting from HP Laserjet Printers
2) user login entries from remote machines.

I tried to use a syslogd with the debug option enabled, but this
refused to accept any entries at all.

Has anyone any experience with this problem, or noticed anything
similar?

Mark Newnham
Haagen Dazs
Paris