Since breaking things up bypasses the shell (definitely a good thing), your "< /dev/null" bit will be passed as-is as an argument to ci, which is not what you want. The shell is what does your pipes and redirections for these types of things.

To simulate the same behavior, just close STDIN before calling system (assuming you don't need it):

close(STDIN); system($ci, '-u', '-zLT', $file);
If you do need STDIN, and still need your multiple-argument form of system, consider saving STDIN, closing it, and re-opening it when you're done:
open(STDSAVE, "<&STDIN"); close(STDIN); system(...); open(STDIN, "<&STDSAVE");
Incidentally, does the -q flag allow you to do this in a "batch"/non-interactive mode without worrying about this sort of thing?

In reply to Re: Input redirection by Fastolfe
in thread Input redirection by spaz

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.