Thanks -- I'll strip this in to the draft. Please CC to me on any further syslog/syslogd gripes. How about expanding the list of strategies for dealing with syslog? Alex Brown <[EMAIL PROTECTED]> +1 508 323 2283 Please respond to [EMAIL PROTECTED] Sent by: Martin Hamilton <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: (Alex Brown/US/3Com) Subject: Re: So, what's wrong with syslog ? :-) I said: | I'm happy to do this - if people want to send me their syslog gripes | by personal email, I'll summarise to the list in ~24 hours or so. Well, it's a bit later than that :-) But here goes... I've tried to categorise the comments I received, and list (the number in brackets) how many people raised each point. Since I got a few directly implementation related comments too, I've included them for good measure. Hope this helps to concentrate people's minds! Thanks again to those who responded. Cheers, Martin
Re: So, what's wrong with syslog ? :-)
by way of "Chris M. Lonvick" <[EMAIL PROTECTED]> Mon, 10 Apr 2000 10:38:53 -0700
