Hello Roberto, I can't reproduce your problem, logrotation is working normal for me with Bering-uClibc-2.1. There where no changes or patches regarding log-rotation between 2.1.0-rc2 and final. Can you give some more details about your specific setup (did you change anything in lrp.conf) and which packages are installed?
Regards, Eric Spakman > > I have noticed the following anomaly about the daily log rotation. If I > understand correctly, logs declared in the variable lrp_LOGS_DAILY in > lrp.conf are to be rotated daily. Well, what I have found is that some days > some logs get rotated while others don't. > > > lrp_LOGS_DAILY="daemon.log debug cron.log messages syslog user.log \ > ppp.log pslave.log shorewall.log" > > I have had the router up for 3 days 19 hours, so there should have been > three or four rotations, but this are the logs I have at this moment. > > cron.log: (ps -A shows cron running) > cron.log, cron.log.0, cron.log.1, cron.log.2.gz are EMPTY > cron.log.3.gz contains events up too March 16 6:42 AM (last log entry is CMD > (run-parts --report /etc/cron.daily)) > > (there seems that there have been 4 rotations but that logging has stopped > when the log was compressed, it is still probably logging to a unlinked > cron.log.3 o .2 file). > > > shorewall.log: > shorewall.log.0, shorewall.log.1, shorewall.log.2.gz, shorewall.log.3.gz are > EMPTY > shorewall.log contains every single event from startup (Mar 14 15:32 UTC - > Mar 18 11:27) > > messages.log, syslog, auth.log, sh-httpd.log: > Same as with shorewall.log > > > debug, daemon.log: > Same as with cron.log > > As I write this mail I notice that all the logs declared before cron behave > in one way, and after cron they behave in a different way. > > I was wondering if this problem is specific to rc2 and has been solved in > the release version (there are no notes about this in the changelog), or if > someone else has run into it. > > I am about to upgrade to the release version 2.1.0, and I was wondering if > there is a way to upgrade and keep the current configuration other than > finding out what files I have modified, save them manually, upgrade the > packages, and restore the saved files (hoping configuration settings remain > valid for all packages from one version to another). > > > Other than that, this is the only little problem I found, the firewall runs > perfectly, and cheers to all LEAF and Bering developers. > > Thanks in advance, > Roberto Lublinerman. > > PD: Forgive my awkward way of phrasing things, you have probably noticed > that English is not my native language. > > > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > ------------------------------------------------------------------------ > leaf-user mailing list: [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-user > SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html > ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
