None of those seemed to have the easiest solution that I know of -- add two dashes at the end of the shebang line:

#!/usr/bin/perl --

This tells the system to ignore anything after that point, so even if you accidentally upload a file from windows to unix in binary mode, it'll run just fine. (although, I don't have a windows machine on the network right now, and I've never tested it with pod, <<EOF blocks, or other multiline strings, which are the only parts of Perl code that might depend on lines being read correctly.)

It should, at the very least, result in better error messages, though, even if it doesn't fix the problem.

In reply to Re^2: ftp script problem .. bad interpreter? by jhourcle
in thread ftp script problem .. bad interpreter? 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.