Why don't you do it like RHEL, CentOS and Fedora with logrotate?
http://pkgs.fedoraproject.org/gitweb/?p=tomcat.git;a=blob;f=tomcat-7.0.logrotate;h=a87b4c005cce267f7ffc6625a44b4a8ff3fad77b;hb=HEAD
Chris
__
This is the maintainer address of Debian's Java team
Thank you for the links. I'm preparing an upload of tomcat 6.0.32 and
will try to address this bug either in the -1 or -2 release of the new
version.
tony
On 12/20/2010 01:09 PM, Ludovic Claude wrote:
Logback and slf4j can provide a solution here as well, by redirecting
all System.out and
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.
I would not expect that to help.
Logback and slf4j can provide a solution here as well, by redirecting
all System.out and System.err to a log file managed by logback.
See:
http://blog.lidalia.org.uk/2010/04/system-out-over-slf4j-code-complete.html
https://github.com/Mahoney/sysout-over-slf4j
Ludovic
On 12/20/2010 10:13 AM,
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
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
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.
-- System Information:
Debian
7 matches
Mail list logo
