Re: Open3 and bad gut feeling

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

Comment on Re: Open3 and bad gut feeling

Replies are listed 'Best First'.
Re: Re: Open3 and bad gut feeling by coreolyn (Parson) on Feb 17, 2002 at 00:40 UTC
Thanks particle. Great node. It looks like you were going over the same nodes I was. Finishing that node really helps a lot. I think I can make a few changes and have it much more legible about what the hell is going on. I'm a bit worried about the resource error (maxed filehandles?). I guess should set a trap for that one right off the bat. How long did you sleep before the retry? coreolyn	[reply]
Re: Re: Re: Open3 and bad gut feeling by particle (Vicar) on Feb 17, 2002 at 00:47 UTC
`sleep(1);` ought to do it. it's quite sporatic (~1 per 1000 calls) and frustrating. the production server is a 180MHz pentiumpro w/256MB RAM, running NT 4 SP6, but it has ultra-fast-wide scsi, and a fat network pipe. i did not see this problem on my (then) desktop, a dual pIII 450. your mileage may vary. good luck! ~Particle	[reply] [d/l]