in reply to Re: Re: Forking in a CGI program on Windows systems
in thread Forking in a CGI program on Windows systems

Something like this should work:

@args = ("command", "arg1", "arg2");
system(@args) == 0 or die "system @args failed: $?";

[download]

Update: Or maybe this is better since exec() doesn't return to the current script:

@args = ("command", "arg1", "arg2");
exec { $args[0] } @args or print STDERR "couldn't exec $args[0]: $!";

[download]

Replies are listed 'Best First'.
Re: Re: Re: Re: Forking in a CGI program on Windows systems
by relax99 (Monk) on Nov 08, 2002 at 19:37 UTC

    I do appreciate that you were trying to help... Unfortunately, the above would not work. Just for the notes - quote from the Camel Book (3rd edition, p. 811) - "The system function works exactly like exec, except that system does a fork first and then, after the exec, waits for the executed program to complete." That's exactly what prevents me from envoking an external program using exec or system - I need my CGI program to completely finish and exit BEFORE the child process finishes.

    There's a similar post "Understanding fork" by neiwatson. I'll try some of the suggestions offered there, even though I'm not sure to what extent they are applicable to Windows systems. I was just wondering if anyone had experience forking on Windows systems from a CGI program (it's important for it to be a CGI program, i.e. run on a web server)

[reply]

      From perlfaq8:

      How come exec() doesn't return?
      Because that's what it does: it replaces your currently running program with a different one. If you want to keep going (as is probably the case if you're asking this question) use system() instead.

      So your current program would completely finish if you put the exec() at the end...

[reply]

In Section Seekers of Perl Wisdom