Date: Sun, 23 Feb 2003 22:41:54 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: Wes Peters <wes@softweyr.com> Cc: arch@FreeBSD.ORG Subject: Re: NEWSYSLOG changes Message-ID: <p05200f1bba7f40fe23c0@[128.113.24.47]> In-Reply-To: <200302231911.14264.wes@softweyr.com> References: <20030210114930.GB90800@melusine.cuivre.fr.eu.org> <p05200f08ba7b59fffe0a@[128.113.24.47]> <p05200f0cba7b6990a408@[128.113.24.47]> <200302231911.14264.wes@softweyr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 7:11 PM -0800 2/23/03, Wes Peters wrote: > >I don't see where your patch addressed the concern Terry raised >about oversize files being rolled improperly on startup. I.e. >if newsyslog encounters a file that it is supposed to roll at >256K and the file is 40M long, what do you do? ... > >Were you going to look into that? Yes, I have an idea of what I want to do for that, but it will be done as a separate patch. I have several different changes in mind, and I'm trying to figure out the best order to make them. Note that the problem isn't the first roll (where the 40-meg file turns into /var/log/somelog.0), it's that later checking may see that /var/log/somelog is 0 bytes (particularly if /var/log is out of disk space), and thus the 40-meg logfile is *never* rotated after that first shot. Once I add the -R option, and once you add the improvements to syslogd itself, then the situation that Terry describes is less likely to happen. I do want to do something about it, though. -- 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?p05200f1bba7f40fe23c0>