thanks for the pointer on the potential race condition. I haven't seen that as a problem yet, but i can see where it could be.

I do have a waitpid, just lost it when copying. (i also have a lot of other things i've tried and commented out in that area).

when open2 does fail, i actually a message stuck into $out (i assume this is because my $cmd has stderr redirected to stdout).

this is what i am matching with:

$err = 1 if (/^thread failed/);
[download]

and in that case i exit from the loop and send myself the done message.

I had suspected that this (the open getting stuck) was the problem which is why i also put in the extra kill just to make sure, but at this point, all of my tests are actually finishing successfully, (i.e. all output coming out, and no spurious tests left on any of the severs).

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.