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 sbt
Recipients christian.heimes, sbt
Date 2012-11-18.17:34:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1353260083.68.0.362226444185.issue16500@psf.upfronthosting.co.za>
In-reply-to
Content
pthread_atfork() allows the registering of three types of callbacks:

1) prepare callbacks which are called before the fork,
2) parent callbacks which are called in the parent after the fork
3) child callbacks which are called in the child after the fork.

I think all three should be supported.

I also think that a recursive "fork lock" should be introduced which is held during the fork.  This can be acquired around critical sections during which forks must not occur.

This is more or less a duplicate of #6923.  See also #6721.
History
Date User Action Args
2012-11-18 17:34:43sbtsetrecipients: + sbt, christian.heimes
2012-11-18 17:34:43sbtsetmessageid: <1353260083.68.0.362226444185.issue16500@psf.upfronthosting.co.za>
2012-11-18 17:34:43sbtlinkissue16500 messages
2012-11-18 17:34:43sbtcreate