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=44427>. 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=44427 ------- Additional Comments From [EMAIL PROTECTED] 2008-02-15 13:03 ------- Caution: the proposed change doesn not close the file unconditionally. It closes the file only, if the rules about size or time interval given when starting up rotatelogs are fulfilled. The only difference to standard rotatelogs is, that a standard version does only check the rules, when a new log line is received. If the logger is idle, then it keeps the file open indefinitly. For your use case I would suggest a trivial enhancement: use a different signal to unconditionally close the file. There's a caveat then: in case we use the common interval based log rotation and we force a log rotation at some point in time, we need to calculate the file name for the new log file in a different way. Otherwise we would very likely overwrite the most recent file. In this case we should use the actual timestamp instead of the beginning of the interval for the name. That would be OK, if the two uses were seperated by using different signals, so that the admin knows, what the result of his action would be. -- 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]
