>    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.

OK now I got you.
Comparing the behaviour to another programm, let's say Photoshop, you
expect the programm still to work if you delete the XYZ.jpg while doing
some changes to the resolution or something.

Correct behaviour should be to lock the file, so that you aren't able to
delete it whil log4j writes to it...


>    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.

Try using the RollingFileAppender!
You may set the number of backups that will be kept
#setMaxBackupIndex(int maxBackups) 

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to