https://issues.apache.org/bugzilla/show_bug.cgi?id=51081
William A. Rowe Jr. <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #4 from William A. Rowe Jr. <[email protected]> 2011-04-19 13:36:01 EDT --- > If Rotatelogs is meant to be non-destructive always - I'm trying to understand > then why do we even have filesize option? rotatelogs file size option is intended to allow the user to roll over at a given limit, for archival purposes; not to destroy the log. I would suggest that if you want a destructive / sampling behavior as opposed to a record of operations, then a new utility would be more appropriate than modifying rotatelogs. Based on two committers negative feedback to destructive operation, I'm going to mark this INVALID for now as the documentation is very clear, but further httpd developer comments are welcome. "When using strftime(3) filename formatting, be sure the log file format has enough granularity to produce a different file name each time the logs are rotated. Otherwise rotation will overwrite the same file instead of starting a new one. For example, if logfile was /var/logs/errorlog.%Y-%m-%d with log rotation at 5 megabytes, but 5 megabytes was reached twice in the same day, the same log file name would be produced and log rotation would keep writing to the same file." -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
