Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 19957 invoked from network); 13 Jun 2008 19:37:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Jun 2008 19:37:20 -0000 Received: (qmail 13374 invoked by uid 500); 13 Jun 2008 19:37:10 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 13350 invoked by uid 500); 13 Jun 2008 19:37:10 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 13339 invoked by uid 99); 13 Jun 2008 19:37:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Jun 2008 12:37:10 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [212.85.38.174] (HELO popeye.combios.es) (212.85.38.174) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Jun 2008 19:36:20 +0000 Received: from [192.168.245.129] (p549EA55D.dip0.t-ipconnect.de [84.158.165.93]) (authenticated bits=0) by popeye.combios.es (8.13.8/8.13.8/Debian-3) with ESMTP id m5DJaRR6011570 for ; Fri, 13 Jun 2008 21:36:28 +0200 Message-ID: <4852CC39.6070905@ice-sa.com> Date: Fri, 13 Jun 2008 21:36:25 +0200 From: =?ISO-8859-1?Q?Andr=E9_Warnier?= User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Tomcat producing (near) duplicate Catalina logs References: <485281BA.5090209@xe.com> <485284FF.2060700@xe.com> <485287BE.8000804@ice-sa.com> <0AAE5AB84B013E45A7B61CB66943C1721384F9B9F5@USEA-EXCH7.na.uis.unisys.com> <4852955E.2030703@ice-sa.com> <48529B8D.4010309@kippdata.de> In-Reply-To: <48529B8D.4010309@kippdata.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on popeye.combios.es X-Virus-Scanned: ClamAV 0.92.1/7463/Fri Jun 13 12:38:49 2008 on popeye.combios.es X-Virus-Status: Clean X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No, score=-97.9 required=2.5 tests=RCVD_IN_PBL, RCVD_IN_SORBS_DUL,USER_IN_WHITELIST autolearn=no version=3.2.3 Rainer Jung wrote: > Andr� Warnier wrote: >> Caldarale, Charles R wrote: >> [...] Guys, I hate to admit it, but it very much looks like I will have to eat my words and be humble and deferential in the future to the "real Tomcat" school of thought. In just found this in the /etc/init.d/tomcat5.5 script of my Debian Linux system : su -p -s /bin/sh $TOMCAT5_USER \ -c "$ROTATELOGS \"$CATALINA_BASE/logs/catalina_%F.log\" 86400" \ < "$CATALINA_BASE/logs/catalina.out" & su -p -s /bin/sh $TOMCAT5_USER \ -c "\"$DAEMON\" start $STARTUP_OPTS" \ >> "$CATALINA_BASE/logs/catalina.out" 2>&1 Might that maybe be the reason for finding similar-but-not-quite-the-same logfiles for Tomcat ? - one named "catalina.2008-06-12.log" - one named "catalina_2008-06-12.log" The above would explain why we find "catalina_2008-06-12.log" like files in the /var/log/tomcatxx directory. It seems to me (but I'm not quite sure before I check the rotatelogs doc) - that it tells rotatelogs to take "catalina.out" on a daily base and archive it to e.g. "catalina_yyyy-mm-dd.log" - and then starts Tomcat, re-directing STDOUT and STDERR to catalina.out On the other hand, Tomcat itself creates another daily logfile, in the form of "catalina.yyyy-mm-dd.log". Now, as a separate follow-up question, to the "real Tomcat" gurus (to which I humbly tip my hat and genuflect in shame) : Is it possible to change this so that Tomcat5.5 would produce a single logfile e.g. per month (catalina.yyyy-mm.log), instead of one per day ? And if yes, where ? And, by the same token, for the files "host-manager.yyyy-mm-dd.log" and "manager.yyyy-mm-dd-log" and "localhost.yyyy-mm-dd.log", which are created everyday and often remain quite small ? Or is there a better way to manage this proliferation of logfiles ? (and please, if possible, do not tell me that I have to read and understand the log4j documentation for this, as I am a mere Tomcat user.) And, as a second question : do we really need the STDOUT/STDERR of Tomcat when it is running as a daemon ? Can I just replace some of the above to redirect Tomcat's STDOUT/STDERR > /dev/null ? Or would we then lose some essential information ? Thank you in advance, Andr� (And I am for now not even speaking to the wicked wicked Debian Linux Tomcat packagers anymore) --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org