➜

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 gregory.p.smith
Recipients bobbyi, gregory.p.smith, neologix, pitrou
Date 2011-02-10.16:56:33
SpamBayes Score 0.00029179535
Marked as misclassified No
Message-id <1297356994.09.0.639401119445.issue6721@psf.upfronthosting.co.za>
In-reply-to
Content 
fwiw http://bugs.python.org/issue6643 recently fixed on issue where a mutex was being closed instead of reinitialized after a fork.  more are likely needed.

Are you suggesting to use pthread_atfork to call pthread_mutex_init on all mutexes created by Python in the child after a fork?  I'll have to ponder that some more.  Given the mutexes are all useless post fork it does not strike me as a bad idea.
History
Date User Action Args
2011-02-10 16:56:34gregory.p.smithsetrecipients: + gregory.p.smith, pitrou, bobbyi, neologix
2011-02-10 16:56:34gregory.p.smithsetmessageid: <1297356994.09.0.639401119445.issue6721@psf.upfronthosting.co.za>
2011-02-10 16:56:33gregory.p.smithlinkissue6721 messages
2011-02-10 16:56:33gregory.p.smithcreate