Author vinay.sajip
Recipients Poddster, vinay.sajip
Date 2017-01-25.19:00:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1485370851.02.0.631378523751.issue29372@psf.upfronthosting.co.za>
In-reply-to
Content
I don't see the point - your proposed solution only works if the log file is completely empty at rollover time, but if the file contains a few bytes from an earlier "short" log message, it might seem just as wasteful of a backup slot as if it had zero bytes. I think the understanding is that maxBytes should be large compared to the size of an average log message, and that if that isn't the case, the user will live with the consequences because it's a contrived scenario (for tests, etc.) rather than a real-life one. There's always the option of subclassing if a user really does need bespoke rollover behaviour.
History
Date User Action Args
2017-01-25 19:00:51vinay.sajipsetrecipients: + vinay.sajip, Poddster
2017-01-25 19:00:51vinay.sajipsetmessageid: <1485370851.02.0.631378523751.issue29372@psf.upfronthosting.co.za>
2017-01-25 19:00:51vinay.sajiplinkissue29372 messages
2017-01-25 19:00:50vinay.sajipcreate