On 12 Feb 2001, Mark Delany wrote:
> On Mon, Feb 12, 2001 at 12:17:47PM -0500, Paul Farber wrote:
> > > > We've heard this again and again. Any specifics?
> > >
> > > I've seen the syslog daemon simply die. With no explanation. Several times
> > > on different boxes. I think this qualifies as being unreliable.
>
> Indeed syslogd notoriously dies on Solaris 2.5 and 2.6 especially when
> hit with multiple HUPqs at around the same time (which of course
> happens quite a lot if you use multiple log rolling scripts as one is
> almost forced to do on Solaris with that /usr/lib/newsyslog
> abomination).
>
Ok, finally a mention of WHICH syslog. Is that most people's experience, a
problem with syslog on Solaris 2.x? I've run mostly Linux boxen over the
years and have had little trouble with sysklogd, the daemon included with
Redhat installations. But then, I tend to use a log host that is on an
isolated, private LAN; UDP doesn't really bother me.
I guess I'll include looking at syslog as part of my performance research
when that time comes.
Later,
Bill Carlson
--
Systems Programmer [EMAIL PROTECTED] | Opinions are mine,
Virtual Hospital http://www.vh.org/ | not my employer's.
University of Iowa Hospitals and Clinics |
