I would be tempted to handle it this way: 
my $pid = fork();
if ($pid == 0) {
    # child process
    my $exit = system("whatever command you want");
    if ($exit != 0) {
        # handle error
    }
    exit;
}
# rest of the program that isn't waiting on the 'system'
.
.
.

[download]

This way you can handle any errors that might result from the system command, and not have to wait for it to finish.

If later in your code you need to make sure that the system has finished before you go on, you can use waitpid($pid,0) to have this process pause until the other has exited.

/\/\averick

In reply to Re: Don't want to wait by maverick
in thread Don't want to wait by Charlie

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.