in reply to win32::process - "child" perl script never receives cgi parameters

When you create a DETATCHED_PROCESS, the process does not have the standard io handles STDIN, STDOUT and STDERR. As cgi parameters are supplied to the script via STDIN (and output to the browser via STDOUT) there is nowhere for a detached process to read from or write to.

Okay you lot, get your wings on the left, halos on the right. It's one size fits all, and "No!", you can't have a different color.
Pick up your cloud down the end and "Yes" if you get allocated a grey one they are a bit damp under foot, but someone has to get them.
Get used to the wings fast cos its an 8 hour day...unless the Govenor calls for a cyclone or hurricane, in which case 16 hour shifts are mandatory.
Just be grateful that you arrived just as the tornado season finished. Them buggers are real work.

  • Comment on Re: win32::process - "child" perl script never receives cgi parameters

Replies are listed 'Best First'.
Re: Re: win32::process - "child" perl script never receives cgi parameters
by Anonymous Monk on Jan 06, 2003 at 12:33 UTC
    Hi BrowserUk,
    Thanks for your reply,- So how come this works fine when run from DOS command or e.g. via the Task Scheduler?

    I have a different script for scheduled report execution which calls it self a number of times in detached processes and in turn executes other Perl scripts depending on which parameters is passed to it.
    This works great!

    So thís problem only appears when run via the web interface.
    I can work around this by executing the detached script via a system command from the CGI script, but this isn't nearly as elegant.

    Cheers, Kristian
[reply]

In Section Seekers of Perl Wisdom