log grow over the limit.
I also just answered this on the mailing list.
3.0.5 is a VERY old version (2003-09-13). I would strongly suggest upgrading to something newer.
The Wrapper will try to roll the log file for every line logged, but if it is being locked by another process it will not be able to do so. As soon as you clear the lock, the next line logged should cause the log file to be rolled.
We added some code in 3.5.6 to improve the way the Wrapper handles these cases
You should now see the following in your log when the Wrapper first fails to roll the log file:
wrapper | Unable to rename log file ..\logs\wrapper.log to ..\logs\wrapper.log.1. File is in use by another application.
Please let me know if you still have any questions getting it working.
Log in to post a comment.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.