On Mon, 2004-09-20 at 16:12, Dan Sugalski wrote: > My bet is you've got a version of perl that's built with safe > signals. If so, you're hosed -- signal delivery to your perl program > will be blocked until the child process exits. For that you'll need > Plan B, which likely involves spawning off the process to run > asynchronously and poll for its completion or the timeout, and > collect whatever data it's emitted. Since this looks to be Unix I > expect you can do a select on the filehandle to see if there's data > to be read from it, then read it with sysread in nonblocking mode or > something like that. I expect someone (like, say, uri) could fill you > in on the gory details.
Ah hah! That's very helpful. Sounds like I have some reading to do, here (and if you have a free moment, Uri or someone who is familiar with what Dan is talking about, pointers would be great!). Thanks a lot Dan! Mike - I tried what you had suggested and I get the same result, thank you for the help. Ben _______________________________________________ Boston-pm mailing list [EMAIL PROTECTED] http://mail.pm.org/mailman/listinfo/boston-pm
