Two basic rules that are generally true when dealing with commands is to always check the return values and to keep as much within perl as you can. Try using the File::Copy module (not certain if it comes with 5.005), it should make things easier as it will error to screen something useful (not always true of system commands).

For a command like cp perl will wait in my experience. If you are worried about this you can pause your script for a second (or whatever time it usually takes plus some seconds for good measure) to make certain the shell command is finished. But also check the return value (with the system call this is relatively easy), just in case.

HTH,
jynx

In reply to Re: Re: Re: Frustrated with system calls by jynx
in thread Frustrated with system calls by dorpus

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.