Tim Funk,
I tried it in 5.0.19 version it didn't work for me also
but document says it must work and the default value of timestamp is false and
my other problem
with logger I have already posted it & didn't hear from any one abt. it
problem for creating the separate log file by <Logger .....
/>for my application context in tomcat-5.0.19.
that is working fine in tomcat 5.0.27!!!!!
please help me what the settings are to be needed to make it
out on tomcat 5.0.19 .
is this bug ???? or AM I missing some thing
sample of my context file which is under
..conf\Catalina\localhost\
<Context displayName="SMART" debug="0" docBase="Smart" path="/Smart">
<Logger className="org.apache.catalina.logger.FileLogger"
directory="webapps/smartlogs"
prefix="Smart_log." suffix=".txt"
timestamp="true"/>
.....................
..................
<Context/>
any help regarding these pls.
thanx in advance
Manish
***********************************************************************************
In
-----Original Message-----
From: Tim Funk [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 23, 2004 7:59 PM
To: Tomcat Users List
Subject: Re: Logger without timestamp not working
The loggers doesn't support the timestamp attribute, only the accessvalve
loggers do.
-Tim
Faine, Mark wrote:
> Tomcat 4.1.27
>
> I can't get Tomcat to not timestamp log files. I've set the logger's
> timestamp attribute to false and still a timestamp is placed on the file.
> Is this a bug?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
***********************************************************************************
Information contained in this email message is intended only for use of the
individual or entity named above. If the reader of this message is not the
intended recipient, or the employee or agent responsible to deliver it to
the intended recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited. If you
have received this communication in error, please immediately notify the
[EMAIL PROTECTED] and destroy the original message.
**************************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
