From owner-freebsd-arch Sun Feb 23 19:41:59 2003 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F77737B401 for ; Sun, 23 Feb 2003 19:41:58 -0800 (PST) Received: from smtp4.server.rpi.edu (smtp4.server.rpi.edu [128.113.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C66943F85 for ; Sun, 23 Feb 2003 19:41:57 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp4.server.rpi.edu (8.12.7/8.12.7) with ESMTP id h1O3ftqX011660; Sun, 23 Feb 2003 22:41:55 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <200302231911.14264.wes@softweyr.com> References: <20030210114930.GB90800@melusine.cuivre.fr.eu.org> <200302231911.14264.wes@softweyr.com> Date: Sun, 23 Feb 2003 22:41:54 -0500 To: Wes Peters From: Garance A Drosihn Subject: Re: NEWSYSLOG changes Cc: arch@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-RPI-Spam-Score: -0.8 () IN_REP_TO,REFERENCES,SIGNATURE_SHORT_DENSE,SPAM_PHRASE_00_01 X-Scanned-By: MIMEDefang 2.28 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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