https://bz.apache.org/bugzilla/show_bug.cgi?id=53930
--- Comment #4 from peterhansson...@yahoo.com --- As a workaround: Use a copy-and-truncate strategy instead. This doesn't require changes to catalina.sh script. On Linux: Use logrotate utility with 'copytruncate' option. On Solaris: Use logadm utility with '-c' option. (or on Solaris 11 and later you can install logrotate by doing 'pkg install file/logrotate' if you really, really want to use logrotate instead of logadm) The proposed change basically allows for a pipe strategy. This strategy is better than a copy-and-truncate strategy for the following reasons: - The copy-and-truncate strategy requires extra disk space when the operation is being executed. - The copy-and-truncate strategy has a small time gap between the copy and the truncate. During the gap messages may be lost. - The copy-and-truncate strategy requires changes to setup outside of the Tomcat configuration: it requires changes to logrotate/logadm tool and potentially a new entry in cron table. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
