Hello,
i fixed the following problem. The logrotate refresh the file statistic only once at the beginning. The timeout managment with thread restart refresh also the file statistic, but only after 10s timeout with no log activity on the file. So in case that a Application is logging without interruption to a destination file it will increase unlimited.
The fix is made by a simply activity counter, set actually to 5000 until to refresh the file statistic and initiate a rotate. This results, depending on print length, in my case at least a 500kB log file size overhead until the refresh is initiate, but better once then never.
Since version 0.3 is buggy i only made a patch but didn't run tests. Actually working and tested on version 0.1.
The patch is applied after an other patch fixing the windows line feed problem.
Best regards
Daniel Lehne
Hello,
I added you to admins of this project. Feel free to make next release.
Unfortunately, I haven't written anything for windows for last 3+ years.
Alexander.
2014-11-13 13:11 GMT+06:00 D. Lehne lehned@users.sf.net:
Related
Feature Requests:
#5fixed in revision 86
The size will marked by written bytes to file, but the verification is done after writing a coup of messages, so it could exceed the maximum size until fifo_cs is finished. So maximum overwrite depends on filled fifo size to process.
Need may a better solution, but for first test is usable and better than unlimited expanding of logfile.