i've used IPC::Open3 because i needed to capture STDIN, STDERR, return code, and pid at once, and it's the only way to do it. you can find a summary on my implementation at once again: program output and return code

this code is running on a production system that synchronizes code between PVCS repositories. it's been running for over a year, and there's only ever been one problem: sporadic failures with IO::Pipe. see my question here: intermittent problem with IPC::Open3. finding no other resolution, i used a short sleep command.

perhaps you'll get some mileage from this.

~Particle

---

---

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

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, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

Outside of code tags, you may need to use entities for some characters:

	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.