Re: How to deal with a forked proces that is waiting for user input?

in reply to How to deal with a forked proces that is waiting for user input?

Since this is an issue, I assume that the program will be run without a person sitting there watching it, correct?

Also, I'm guessing that the forked processes will sometimes be run by a human directly and may then require user input, but sometimes will be run by your program, and for whatever reason will be able to function properly without receiving any input in that case.

If my assumption and my guess are correct, then why not add a command line argument to the program that gets forked? Wrap the sections that get user input in an 'if' and just skip over that section if the command line argument has been set. That way you can fork it without having it hang by passing the correct argument, and it will still work as usual if invoked directly from the command line.

It's not particularly fancy or elegant, but it's simple and should work unless there's constraints I'm not aware of

Comment on Re: How to deal with a forked proces that is waiting for user input?

Replies are listed 'Best First'.
Re^2: How to deal with a forked proces that is waiting for user input? by gepapa (Acolyte) on Oct 21, 2008 at 19:35 UTC
This will always be run via automation, so no user input.	[reply]
Re^3: How to deal with a forked proces that is waiting for user input? by eighty-one (Curate) on Oct 21, 2008 at 19:47 UTC
Ohhh, I get it now. For some reason I thought that by 'processes' you were referring to stuff you had developed and were calling; upon re-reading your node I see that I was mistaken.	[reply]

In Section Seekers of Perl Wisdom