For one, you can pass a Debug => 1 to new() - debug messages will then be written to STDERR, which you can capture in whichever fashion your shell provides.

For another, if you transfer files using the get() method, then you can store this method's return value which will be the filename the requested file got stored as locally, and then stat this file, as per erasei's suggestion.

And finally, if you use the retr() method and do the transfer logistics manually, you can call bytes_read() on the Net::FTP::dataconn object it returns at any point to query the amount of data transferred so far.

All of this is mentioned in the Net::FTP POD page.

Makeshifts last the longest.

In reply to Re: FTP logs by Aristotle
in thread FTP logs by windy

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.