One thing I do to read all my Perl code errors is to create a simple log file at the begining of the code. (STDERR, ">err_log.txt"); Plus a one for the standard good out put. (STDOUT, ">log.txt"); I need log files for all my transmissions since I work with mortgage companies and need to keep records of all transmissions. This was real helpful in troubleshooting FTP problems for me. The error log normally will not have any thing in it unless there is a fatal error in the FTP logic or Perl code. I'm by no means even close to an expert so my solutions are simple. Hope is helps. Ski

In reply to Re^4: multiftp.pl by skiboy
in thread multiftp.pl by ergowolf

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.