<div dir="ltr">On Mon, Oct 15, 2012 at 12:30 PM, Joey Hess <span dir="ltr"><<a href="mailto:joey@kitenet.net" target="_blank">joey@kitenet.net</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"> forkProcess comes with a giant warning: since any other running threads</div>
are not copied into the child process, it's easy to go wrong: e.g. by<br>
accessing some shared resource that was held by another thread in the<br>
parent.<br>
<br>
In my experience, forkProcess often behaves incomprehensibly (to me)<br>
with -threaded, typically resulting in a forked process hanging, and<br>
quite often only some small percentage of the time, which makes it<br>
really hard to track down and try to diagnose what thunk might not be<br>
getting forced until after the fork, or whatever.<br></blockquote><div><br></div><div>The forkProcess MissingH discussion recently left me feeling like this is going to be triggered in all cases, because it sounds like one of the problematic threads is the I/O manager's thread?</div>
<div><br></div></div>-- <br><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div>
<div>unix/linux, openafs, kerberos, infrastructure <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div><br>
</div>