comment on

The problem is that when you call

`$myscript &`;
[download]

You are essentially calling

`sh -c '$myscript &'`;
[download]

In other words... you are waiting for the shell process to terminate... but the shell process (if it were interactive) would have returned a prompt imediately after firing off $myScript.

If you really want to fire off a background job from a perl process, and don't care about the output (btw: backticks imply that you do care about the output, but continuing imediately imply that you do not care about the output)... then you should do something more like this:

my $pid = fork;
die "Could not fork: $!" unless defined $pid;
if (!$pid) {
   exec $myScript;
}
[download]

Which is somewhat akin to what the shell does when you launch the program foo by typing:

[user@host]$ foo &
[download]

------------
:Wq
Not an editor command: Wq
[download]

In reply to Re: http waits on process by etcshadow
in thread http waits on process by hotshot

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


XP is just a number
	PerlMonks