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 sstewartgallus
Recipients sstewartgallus
Date 2014-06-02.00:56:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1401670618.4.0.67566797637.issue21627@psf.upfronthosting.co.za>
In-reply-to
Content
Gah, I had trouble figuring out mecurial.

Close files after reading open files and not concurrently

This commit removes the old behaviour of closing files concurrently
with reading the system's list of open files and instead closes the
files after the list has been read.

Because no memory can be allocated in that specific context the
approach of setting the CLOEXEC flag and letting the following exec
close the files has been used.

For consistency, the brute force approach to closing the files has
also been modified to set the CLOEXEC flag.
History
Date User Action Args
2014-06-02 00:56:58sstewartgallussetrecipients: + sstewartgallus
2014-06-02 00:56:58sstewartgallussetmessageid: <1401670618.4.0.67566797637.issue21627@psf.upfronthosting.co.za>
2014-06-02 00:56:58sstewartgalluslinkissue21627 messages
2014-06-02 00:56:57sstewartgalluscreate