My version of IPC::Run (0.78) has the following example in the documentation:

## First,a command to run:
   my @cat = qw( cat ) ;

## Using run() instead of system():
   use IPC::Run qw( run timeout ) ;

   run \@cmd, \$in, \$out, \$err, timeout( 10 ) or die "cat: $?"

   # Can do I/O to sub refs and filenames, too:
   run \@cmd, "in.txt", \&out, \&err or die "cat: $?"
   run \@cat, "in.txt", '>>', "out.txt", '2>>', "err.txt" ;

   # Redirecting using psuedo-terminals instad of pipes.
   run \@cat, '<pty<', \$in,  '>pty>', \$out_and_err ;

[download]

so, yes, @cat needs to be filled with the command and the arguments of the thing you want to run.

But if you're trying some basic things, why dabble with IPC::Run if the plain system() call or backticks can do your work already? What do you want to do?

In reply to Re: IPC::Run syntax question by Corion
in thread IPC::Run syntax question 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.