RE: logrotate and tomcat 3.3/4.0/4.1

Quoting GOMEZ Henri <[EMAIL PROTECTED]>: > Whaou. > > Didn't now about copytruncate option of logrotate. It has some downsides too. But it's documented in the manual page, so everyone should know what to expect. > Under Linux there is truncate and ftruncate calls > but I wonder how it works r

RE: logrotate and tomcat 3.3/4.0/4.1

>And surprise!!, 3.3 it's suppoussed to have another logrotate inside, >broken, but the code is there.. just need that someones have spare >cycles to fix it.. I started take a look a log stuff in 3.3.2 and will see how to fix the logrotate support or better add log4j support ? -- To unsubscribe

RE: logrotate and tomcat 3.3/4.0/4.1

PROTECTED](. .) PGP KEY : 697ECEDD...oOOo..(_)..oOOo... PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 >-Original Message- >From: Bojan Smojver [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, April 30, 2002 12:40 AM >To: Tomcat Dev List >Subject: RE: logrota

RE: logrotate and tomcat 3.3/4.0/4.1

>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 ). commons-logging seems a good way to hide log4j

RE: logrotate and tomcat 3.3/4.0/4.1

This works (TC 3.3.x): /var/tomcat/logs/*.log { copytruncate weekly rotate 52 compress missingok } Bojan -- To unsubscribe, e-mail: For additional commands, e-mail:

Re: logrotate and tomcat 3.3/4.0/4.1

"Ignacio J. Ortega" <[EMAIL PROTECTED]> wrote: >> that those are not open by the JVM process... Therefore the >> best course of >> action is doing like catalina does... Which already has a some-sort of >> logrotate built in... > > And surprise!!, 3.3 it's suppoussed to have another logrotate in

RE: logrotate and tomcat 3.3/4.0/4.1

> that those are not open by the JVM process... Therefore the > best course of > action is doing like catalina does... Which already has a some-sort of > logrotate built in... > And surprise!!, 3.3 it's suppoussed to have another logrotate inside, broken, but the code is there.. just need tha

Re: logrotate and tomcat 3.3/4.0/4.1

"GOMEZ Henri" <[EMAIL PROTECTED]> 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 > general

Re: logrotate and tomcat 3.3/4.0/4.1

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 j

RE: logrotate and tomcat 3.3/4.0/4.1

>I don't really know much about log4j, so I can't comment on >that particular methodology, but I'd been looking at >implementing a logrotate for tomcat on my systems. I was >thinking something like this for tomcat 3.3 (haven't looked at >4.x yet): > >/var/log/tomcat3/jasper-*.log /var/log/tom

RE: logrotate and tomcat 3.3/4.0/4.1

.1). Would this be what you're looking for (and would it even work :-)? Jason -Original Message- From: GOMEZ Henri [mailto:[EMAIL PROTECTED]] Sent: Monday, April 29, 2002 11:47 AM To: Tomcat Developers List Subject: logrotate and tomcat 3.3/4.0/4.1 Hi to all, Did there is plan t

logrotate and tomcat 3.3/4.0/4.1

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 it