severity 704950 minor retitle 704950 logrotate: Error and forced rotation if timezone change moves localtime date backwards a day thanks
On Mon, Apr 08, 2013 at 08:20:49PM +0200, Vincent Lefevre wrote: > severity 704950 grave > done > > because obvious critical data loss (though the case is not common). > One part of the bug is that logrotate rotates the log files instead > of not changing anything if it incorrectly guesses that a file has > been written in the future. So, if the timezone changes several > times (e.g. during a travel), some logs may be lost, even recent > ones, while they would normally be kept e.g. for several weeks! > Logs are important data. Losing logs is not acceptable. It's not the intention to protect system administrators against the consequences of their own policies. Severity minor because it only affects a minority of users. This is not a grave bug as it is the system administrator's choice to change local timezone, and they should be aware of the consequences of how that affects cron jobs. It's also telling you that it's doing what it's doing, rather than silently losing data. The "time in future" warning is there to advise of a broken system clock, not against a system administrator intentionally breaking that clock. The alternative is a system that potentially never rotates its log files. cron runs in the system's local timezone, hence logrotate follows what cron does. I've given you a workaround that will help you. I will not be closing this bug as it provides a helpful reference for others in your situation. Alternatively, if you find yourself changing timezones regularly, run the system in UTC (or your home timezone) and have your own login set an appropriate timezone as part of its ~/.profile -- Paul Martin <p...@debian.org> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
