This is good advice overall!

For the OP, I just wanted to add that there are "better" alternatives to system and backticks. In this particular case, if there are no variables being interpolated into the command string, meaning it's safe enough to call the shell, IPC::System::Simple's run would probably be easiest, since it's just a replacement for system with better error handling.

use IPC::System::Simple qw/run/;
run q{ find /path/to/files -name '*.csv' | cpio -pdm /target };

[download]

Otherwise, e.g. if variables are being interpolated into the command, things can get more complicated - I wrote about the whole topic at length here.

In reply to Re^2: How to write the perl script for the following linux command? by haukex
in thread How to write the perl script for the following linux command? by finddata

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.