Date: Fri, 14 Feb 2003 22:44:45 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: Terry Lambert <tlambert2@mindspring.com>, Gordon Tetlow <gordont@gnf.org> Cc: arch@FreeBSD.ORG Subject: Re: syslog.conf syntax change (multiple program/host specifications) Message-ID: <p05200f17ba736570c876@[128.113.24.47]> In-Reply-To: <3E4D7C2B.DDFC9DBE@mindspring.com> References: <20030210114930.GB90800@melusine.cuivre.fr.eu.org> <20030213174531.GZ83215@roark.gnf.org> <20030213184309.GA53098@melusine.cuivre.fr.eu.org> <200302141100.23529.wes@softweyr.com> <p05200f15ba72fb31e177@[128.113.24.47]> <20030214220145.GM83215@roark.gnf.org> <3E4D7C2B.DDFC9DBE@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 3:30 PM -0800 2/14/03, Terry Lambert wrote: >Gordon Tetlow wrote: >> From newsyslog(8): > > > > -F Force newsyslog to trim the logs, even if the trim > > conditions have not been met. This option is useful > > for diagnosing system problems by providing you with > > fresh logs that contain only the problems. > >Not really useful. > >For example, we had a system where cron would occasionally die, Note that what we are saying is that syslog would execute newsyslog, at the moment syslog notes the logfile has grown too large. Newsyslog would be told to "rotate this file now". So, it wouldn't matter if cron dies. And the log would be rotated right after the first syslog write which caused the file to pass the size limit. >Only newsyslog is stupid. > >No matter what options you gave it, the first thing it would do is >the moral equivalent of -F. > >So instead of a 60M Samba log file "/var/log/samba", you ended up >with a "/var/log/samba.1" that was 60M, and a "/var/log/samba" >that was empty. I still have some message squirrelled away where you describe this problem. I do agree this would be good to fix. It seems to me that would be separate from the Wes's syslog change. Ie, it's good to fix this whether or not Wes's change goes in, and it's good for Wes's change to go in whether or not this is fixed. >I would really object to rolling this same thing into syslog, >without fixing this first. Some people talked about (basically) moving all of newsyslog functions into syslog, but I don't think we are heading that way. We're now just talking about having syslog run newsyslog on a specific logfile. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05200f17ba736570c876>