system LIST
system PROGRAM LIST

Does exactly the same thing as exec LIST, except that a fork is done first, and the parent process waits for the child process to complete. Note that argument processing varies depending on the number of arguments. If there is more than one argument in LIST, or if LIST is an array with more than one value, starts the program given by the first element of the list with arguments given by the rest of the list. If there is only one scalar argument, the argument is checked for shell metacharacters, and if there are any, the entire argument is passed to the system's command shell for parsing (this is /bin/sh -c on Unix platforms, but varies on other platforms). If there are no shell metacharacters in the argument, it is split into words and passed directly to execvp, which is more efficient.
Beginning with v5.6.0, Perl will attempt to flush all files opened for output before any operation that may do a fork, but this may not be supported on some platforms. To be safe, you may need to set $| ($AUTOFLUSH in English) or call the autoflush() method of IO::Handle on any open handles.
The return value is the exit status of the program as returned by the wait call. To get the actual exit value shift right by eight (see below). See also /exec. This is not what you want to use to capture the output from a command, for that you should use merely backticks or qx//, as described in perlop/"`STRING`". Return value of -1 indicates a failure to start the program (inspect $! for the reason).
Like exec, system allows you to lie to a program about its name if you use the system PROGRAM LIST syntax.
Because system and backticks block SIGINT and SIGQUIT, killing the program they're running doesn't actually interrupt your program. 


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

[download]


You can check all the failure possibilities by inspecting $? like this: 
    $exit_value  = $? >> 8;<br>
    $signal_num  = $? & 127;<br>
    $dumped_core = $? & 128;   <br>

[download]

or more portably by using the W*() calls of the POSIX extension.
When the arguments get executed via the system shell, results and return codes will be subject to its quirks and capabilities.

In reply to Re: using a set variable in system or exec by Mago
in thread using a set variable in system or exec by Anonymous Monk

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.