Nuno,
it seems to me that the "ExternallyRolledFileAppender" should provide the type of
behaviour you want. I personally have not used it yet, but according to the
description,
it looks like it could do the job.
Serge A.
Nuno Carvalho <[EMAIL PROTECTED]> on 2002-12-20 09:31:07
Veuillez r�pondre � "Log4J Users List" <[EMAIL PROTECTED]>
Pour : Log4J Users List <[EMAIL PROTECTED]>
cc :
Objet : Re: Not logging to file when it no more exists
Thimo K�nig wrote:
>> When logging for a single file, the Log4J works fine. If the
>>application is running, the log file is created (if it don't
>>exist) and
>>logged properly. However, if I delete the log file, at
>>runtime, and some
>>log messages are generated then the log file won't be created
>>again and
>>the log messages are lost forever. Am I doing something wrong ?
>
>
> I think this is behaviour as expected!
>
> Why do you want do delete the log file at runtime?
Usually the log files are not deleted.
If you are running a platform on a production system which do not
should be restarted and for some unexpected reason the log file is
removed, then the logging won't work anymore. In my opinion, this is
wrong. It will require a restart to the platform in order to get the
logging system to work.
On a pontual situation, I may want to backup that log file for some
reason. In that case, I will move the file to other name.
Anyway, thanks to the development team by the great job. Maybe
there's a good reason for that...
Regards,
Nuno
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
