Bug#607050: tomcat6: catalina.out grows
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 http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#607050: tomcat6: catalina.out grows
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 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, Elmar Haneke wrote: 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. File catalina.out is redirected stdout/stderr of tomcat java process it is not handled by any logging framework. The output should be piped through cronolog ore something similiar. Elmar signature.asc Description: OpenPGP digital signature __ 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.
Bug#607050: tomcat6: catalina.out grows
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. File catalina.out is redirected stdout/stderr of tomcat java process it is not handled by any logging framework. The output should be piped through cronolog ore something similiar. Elmar __ 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.
Bug#607050: tomcat6: catalina.out grows
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, Elmar Haneke wrote: 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. File catalina.out is redirected stdout/stderr of tomcat java process it is not handled by any logging framework. The output should be piped through cronolog ore something similiar. Elmar __ 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. __ 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.
Bug#607050: tomcat6: catalina.out grows
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 signature.asc Description: OpenPGP digital signature __ 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.
Bug#607050: tomcat6: catalina.out grows
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. __ 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.
Bug#607050: tomcat6: catalina.out grows
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 Release: squeeze/sid APT prefers unstable APT policy: (650, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.36-trunk-686 (SMP w/2 CPU cores) Locale: lang=de...@euro, lc_ctype=de...@euro (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages tomcat6 depends on: ii adduser 3.112+nmu2 add and remove users and groups ii debconf [debconf-2.0]1.5.37 Debian configuration management sy ii tomcat6-common 6.0.28-9Servlet and JSP engine -- common f ii ucf 3.0025+nmu1 Update Configuration File: preserv Versions of packages tomcat6 recommends: ii authbind 1.2.0 Allows non-root programs to bind() Versions of packages tomcat6 suggests: pn tomcat-native none (no description available) pn tomcat6-admin none (no description available) pn tomcat6-docs none (no description available) pn tomcat6-examples none (no description available) pn tomcat6-user none (no description available) -- Configuration Files: /etc/tomcat6/server.xml changed [not included] /etc/tomcat6/tomcat-users.xml [Errno 13] Keine Berechtigung: u'/etc/tomcat6/tomcat-users.xml' -- debconf information excluded __ 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.
