Hey all,

So I'm using NET::Ftp to transfer files on demand from a remote server. However, despite all the checks for valid characters in filenames, I cant by the nature of the beast stop users giving my script filenames to retrieve that dont exist.

What I need to do is attempt to grab a file but trap if the server gives me a "file not found" error.

I thought about just checking if the file exists after the transfer has taken place - thus proving whether or not it was downloaded but that seems rather inelegant to me.

Anyone know how to check for errors with NET::Ftp? Perldoc doesn't seem to mention anything.

The code I'm using to grab the file is thus. 

	sub fetch_metar {
		$ftp = Net::FTP->new($hostname);
		$ftp->login("anonymous","metar\@speedfreak.com");		
		$ftp->get($path.$station.".TXT", $datapath.$station.".TXT");
		$ftp->quit;
	}
- Jed

In reply to Trapping errors from NET::Ftp by Speedfreak

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.