This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mori-b
Recipients docs@python, mori-b, vinay.sajip
Date 2021-06-13.16:13:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1623600812.97.0.314646200143.issue44399@roundup.psfhosted.org>
In-reply-to
Content
Indeed this situation would rise only under misusage of the log, where multiple processes inherit by  mistake or by wrong design a file descriptor of a same log file (Regarding the threads case I unfortunately cannot reproduce).
While this kind of misusage doesn't have terrible consequences when not using the rotator, the growing used disk space which occurs when using the rotator is more serious, that's why I found appropriate to try and protect the programmer from his own mistake. But I understand if this is out of scope.
History
Date User Action Args
2021-06-13 16:13:33mori-bsetrecipients: + mori-b, vinay.sajip, docs@python
2021-06-13 16:13:32mori-bsetmessageid: <1623600812.97.0.314646200143.issue44399@roundup.psfhosted.org>
2021-06-13 16:13:32mori-blinkissue44399 messages
2021-06-13 16:13:32mori-bcreate