Message 201436 - Python tracker

Message201436

Author	neologix
Recipients	Arfrever, benjamin.peterson, christian.heimes, georg.brandl, larry, neologix, pitrou, python-dev, r.david.murray, sbt, vstinner
Date	2013-10-27.08:57:11
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<CAH_1eM01859de=n1V3G5JVW7bWTbLfUq49cO4qu2obY7fu6+XA@mail.gmail.com>
In-reply-to	<3d6qby35WXz7Ln2@mail.python.org>

Content
Note that no matter where the atfork-hook is executed (prepare, parent, child), it will still be deadlock-prone in case of double-fork, since the hook will effectively be called after the first fork (and before the second one). And double-fork is common, e.g. when creating daemon processes.

Content

Note that no matter where the atfork-hook is executed (prepare,
parent, child), it will still be deadlock-prone in case of
double-fork, since the hook will effectively be called after the first
fork (and before the second one). And double-fork is common, e.g. when
creating daemon processes.

History
Date	User	Action	Args
2013-10-27 08:57:12	neologix	set	recipients: + neologix, georg.brandl, pitrou, vstinner, larry, christian.heimes, benjamin.peterson, Arfrever, r.david.murray, python-dev, sbt
2013-10-27 08:57:12	neologix	link	issue19227 messages
2013-10-27 08:57:11	neologix	create