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
- remote root qmail-pop with vpopmail advisory an... John Gonzalez/netMDC admin
- Re: remote root qmail-pop with vpopmail ad... Russell Nelson
- Re: remote root qmail-pop with vpopmai... Derek Callaway
- Re: remote root qmail-pop with vpo... Russell Nelson
- Re: remote root qmail-pop with... Russ Allbery
- Re: remote root qmail-pop... Giles Lean
- Re: remote root qmail... Russ Allbery
- Re: remote root qmail-pop with vpo... Derek Callaway
- Re: remote root qmail-pop with... Petr Novotny
- Re: remote root qmail-pop with... Russell Nelson
- Re: remote root qmail-pop... Pavel Kankovsky
- Re: remote root qmail... Russell Nelson
- Re: remote root q... Petr Novotny
- Re: remote root q... Pavel Kankovsky
- Re: remote root q... Peter Haworth
- Re: remote root qmail-pop with vpopmai... Adam McKenna
