cvs commit: src/usr.sbin/newsyslog newsyslog.c

[Garance A Drosihn]

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 '<debug> 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 at gilead.netel.rpi.edu
Senior Systems Programmer           or  gad at freebsd.org
Rensselaer Polytechnic Institute    or  drosih at rpi.edu