You did not mention the platform, but if you are on unix, you can use
cp /dev/null tomcat.log
to 'null' out the logfile. This sets the file to be 0 bytes without interrupting the process using it.
Most processes do not have a problem with this. But some will just fill the 'null'ed bytes with garbage. I beleive Tomcat allows the file to be 'null'ed - though definately try on a development machine first.
(I am currently using NT, so I can't test it for you)
Charlie
-----Original Message-----
From: David Brewster [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 12, 2001 9:44 AM
To: [EMAIL PROTECTED]
Subject: Re: refresh/flush logs question
On Mon, Feb 12, 2001 at 01:28:13PM -0300, [EMAIL PROTECTED] wrote:
>
>
> Hi David.
>
> I had this problem........
>
> My solution was edit server.xml and change the verbosityLevel of
> jasper.log. See:
>
> In the FATAL mode, jasper.log only records the fatal errors and no
> more causes it problems.
Hi
Unfortunately we want to keep the log files (and all the verbose information)
however we want to rotate the logs, compressing the old ones, and keeping the
main log files from getting too large.
Thanks
David
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
