DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=44036>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44036 [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From [EMAIL PROTECTED] 2007-12-30 22:39 ------- Until the parent process has fresh activity, yes it holds open it's last used log. This is what you are observing. " 3. Change Windows date " isn't quite a legitimate testing methodology, as it has unexpected side effects. An appropriate hack would be to have rotatelogs actually 'expire' its lock on the current file once a timeup occurs (mapping it to the number of seconds until the next valid file should be created). In fact this could avoid other side effects. But I'd offer that's a subject for another bug report (patches welcome!) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
