OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Subject: Re: qmgr logging breaks
From: Leif Nixon (nixonlysator.liu.se)
Date: Mon Feb 07 2000 - 03:33:23 CST

Dylan Griffiths <Dylan_Gbigfoot.com> writes:

> [Wietse writes:]

> > I suspect that the Linux syslog client does not maintain state from
> > openlog() (the logging tag and the logging class) so that when it
> > has to re-connect to syslogd it just invents a tag, which is wrong.
>
> Wieste points out that the state is somehow not saved, requiring the
> restart. He says the Linux implementation is broken because he assumes the
> admin understood syslogd hard restarts will drop token info (soft is a HUP,
> hard is a kill -9 or TERM).

No, I suspect he means that state should be maintained on the client
side, not the server side. This might be why he chose to use the words
"syslog client".

> Restarting syslogd is the culprit. I've had no problem with losing my
> "states" across many log rotations (daily, which involve HUPing any daemons
> that write to log files, such as syslogd). The Linux Syslogd is not at
> fault this time. I'll chock this one up to temporary insanity on the part
> of the sysadmin :-)

All right, I've read the man page for syslog(3) now. No need to be so
glib about it.

/Leif Nixon