Do your file names have characters that need escaping or quoting, e.g. $cmd = "perl script.pl < '$file'";? Have you actually tested that the code as posted fails in your context? It works for me for some simple test systems.

The simplest solution from my perspective would be to avoid shelling and modify script.pl to process multiple files. That will give you access to the actual diagnostics and remove a layer of misdirection.

Update: If you can't modify script.pl for whatever reason, you can handle the file opens and piping yourself with something like:

#!/usr/bin/perl -w use strict; my @files = glob("*.msg"); foreach my $file(@files) { open my $in, '<', $file or die "Open fail on $file: $!\n"; my @lines = <$in>; open my $out, '|-', 'perl script.pl' or die "Piping fail: $!\n"; print $out @lines; }
Note that making those variables lexical to the loop (my) is significant, and you will likely need to explicitly close the filehandles otherwise. See |- in open or Safe Pipe Opens for some background.

#11929 First ask yourself `How would I do this without a computer?' Then have the computer do it the same way.


In reply to Re: Using wildcards to open files. by kennethk
in thread Using wildcards to open files. by starface245

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.