Hello Thorsten, I'm working on a tomcat7 security-only update, and checking the pending bugs.
/etc/cron.daily/tomcat7 uses the "copytruncate" method, which normally should handle this situation, where it's not possible/wanted to restart the server, and there's "a very small time slice between copying the file and truncating it, so some logging data might be lost" (logrotate.conf(5)), so I assume the potentially missing write is a known compromise. Note: it also uses the "weekly" keyword which does not match this bug's mention of "not have been written to for a day". At first glance the situation looks OK to me. What would you recommend? Cheers! Sylvain
