On 24 Jan 2000 05:38:20 -0800  Russ Allbery wrote:

> That's just for starters.  To be fair, current syslog on *most* Unix
> systems is now pretty solid except for occasionally losing messages.  But
> among the problems I've seen or heard of in different
> implementations:

Also, depending on the vendor and version, I have seen:

- syslogd hang
- syslogd stop forwarding messages to other hosts, when it is
  configured to do so
- become a CPU hog
- log incorrect internal diagnostics due to clobbering errno

syslogd is not quality software.  There are various efforts underway
to write replacements, including of course Dan's tools.  People
committed to syslog() style interfaces might want to look at:

http://www.ietf.org/ietf/99nov/syslog-agenda-99nov.txt

Regards,

Giles

Reply via email to