From owner-cvs-all@FreeBSD.ORG Mon Jun 7 02:26:09 2004 Return-Path: Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A2AEA16A4CE; Mon, 7 Jun 2004 02:26:09 +0000 (GMT) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44A2743D39; Sun, 6 Jun 2004 19:26:09 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.12.8/8.12.8) with ESMTP id i572PlIX008069; Sun, 6 Jun 2004 22:25:47 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <200406070210.i572AAP1045726@repoman.freebsd.org> References: <200406070210.i572AAP1045726@repoman.freebsd.org> Date: Sun, 6 Jun 2004 22:25:46 -0400 To: Garance A Drosehn , src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) Subject: Re: cvs commit: src/usr.sbin/newsyslog newsyslog.c X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jun 2004 02:26:09 -0000 At 2:10 AM +0000 6/7/04, Garance A Drosehn wrote: > NOTE: > This commit does define NEWORDER (which you could get rid of if > you really don't trust this), but it does not flip the "-D neworder" > switch. So, at the moment none of these changes happen unless you > request them (perhaps by adding ' neworder' in newsyslog.conf). I have been running with this "neworder" code for a few days, and it seems to be doing all the right things for me. I've also tested various other configurations, so I am "cautiously optimistic" that it should work right for everyone. But it is a pretty major change, so I wanted to ease it into place and provide people an easy way of dropping back to the previous behavior if they suspect something wrong with it. I also have a testing-script which is what I have crontab execute instead of running newsyslog directly, and that goes through a bunch of extra work such that I can compare the results of "oldorder" vs "neworder" for every run of newsyslog on my system. It results in a lot of extra work, of course, but I can make that script available if someone else wants to do extensive comparisons of the "neworder" vs the "oldorder". -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu