If you want to change the logging framework, you should consider logback which is the successor of log4j. It's faster, more configurable, and it's got even an adaptor for Tomcat juli (replace juli by juli-over-slf4j which will redirect the logs to logback and you're done) Logback can even take care of the access log of Tomcat, and of course rotate it as appropriate.
https://github.com/olamy/slf4j (contains the additional juli-over-slf4j jar) http://logback.qos.ch/access.html You cloud split tomcat-juli out of libtomcat-java, and allow an alternative tomcat-logback package to be used with Tomcat, and this package will feature log rolling with logback. Like that, people expecting a standard Tomcat installation won't be surprised (juli is explained in the Tomcat manual), and people using Tomcat over a long period of time can be told to install tomcat-logback instead. Ludovic On 12/19/2010 09:12 PM, tony mancill wrote: > On 12/14/2010 01:41 AM, Elmar Haneke wrote: >> Package: tomcat6 >> Version: 6.0.28-9 >> Severity: normal >> >> In /var/log/tomcat6 there is file "catalina.out" which does hold all console >> output. >> >> To allow cronjob remove old logging data there should be an new file started >> every day by usin cronolor or something similiar. > > Hello Elmar, > > Thank you for the bug report. I'm wondering if we could easily handle > this by using log4j instead of the juli logger as the default logging > subsystem. That would handle daily or sized-based rotations without > requiring the user to set up anything additional. > > Regards, > tony > > > > > __ > This is the maintainer address of Debian's Java team > <http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers>. > Please use > debian-j...@lists.debian.org for discussions and questions. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
