Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 24590 invoked from network); 29 Apr 2002 16:17:06 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 29 Apr 2002 16:17:06 -0000 Received: (qmail 26978 invoked by uid 97); 29 Apr 2002 16:17:03 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 26961 invoked by uid 97); 29 Apr 2002 16:17:02 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 26945 invoked from network); 29 Apr 2002 16:17:02 -0000 X-Authentication-Warning: costinm.sfo.covalent.net: costinm owned process doing -bs Date: Mon, 29 Apr 2002 09:15:40 -0700 (PDT) From: X-X-Sender: To: Tomcat Developers List Subject: Re: logrotate and tomcat 3.3/4.0/4.1 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On the java side ? I think we should just use commons-logging, and the admin/ or manager/ or some other ( java-based code ) to control the underlying logger ( which should probably default to log4j when somebody has the time to do this ). There is no need to complicate things with -HUP and java - it isn't difficult ( I even started to work on that in the jk jni code ), but it would be much cleaner/portable/etc to just use java mechanisms. ( of course, JMX is a good choice - and log4j does support JMX ) Costin On Mon, 29 Apr 2002, GOMEZ Henri wrote: > Hi to all, > > Did there is plan to help implement logrotate > for Tomcat 3.3/4.0/4.1 ? > > On production the logs could became very important > after weeks of use and should be cleanup. > > The usual way under Unix is to use logrotate which > generally send a KILL -HUP/USR1 to the process which in > turn close its open logs files, and create new one. > > The logrotate daemon then do the cleanup, renaming, > compression and so on. > > What's the perspective for tomcat's ? > > - Use log4j in cycle mode and avoid use > of System.out / System.err ? > > - Team up with jakarta-service to be able to > catch up the signal and do what's needed ? > > Regards > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > > -- To unsubscribe, e-mail: For additional commands, e-mail: