https://issues.apache.org/bugzilla/show_bug.cgi?id=51081
Thangaraj AntonyCrouse <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #3 from Thangaraj AntonyCrouse <[email protected]> 2011-04-19 13:27:44 EDT --- (In reply to comment #2) > (In reply to comment #1) > > I'd vote -1 on this patch. > > > > rotatelogs is designed to be nondestructive, and you propose to add > > destructive > > behavior to the log records. > this alarmed me as well, if you don't add reasonable granularity to the > filename, letting it grow until someone notices is better than truncating it > periodically. Appreciate your comments. This path provides the best of both worlds - non-destructive and destructive modes of operation. If users don't like destructive mode - they can use large file size option. If users like me don't want Server disk space to be exhausted and prefer log overwriting they can use small file size as option with less granular time format (as mentioned in docs: http://httpd.apache.org/docs/2.2/programs/rotatelogs.html). If Rotatelogs is meant to be non-destructive always - I'm trying to understand then why do we even have filesize option? -- 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]
