Re^3: Net::FTP usage

You never call chdir, so you never change your working directory for your Perl script.

Maybe you want to read about glob instead of shelling out to write the entries of a directory into a file?

Also, I still don't believe you that you do not have whitespace at the end of the elements of @array.

use File::Glob 'bsd_glob';
my @files = bsd_glob "$tempdir/sudolog*";
print "Found file [$_]\n"
    for @files;
[download]

... will read all the files named sudolog* from the directory given in the $tempdir variable.

Comment on Re^3: Net::FTP usage Select or Download Code

Replies are listed 'Best First'.
Re^4: Net::FTP usage by kafkaf55 (Acolyte) on Aug 13, 2010 at 14:47 UTC
Results: Found file /ccifas/tempifas/AU/sudolog_2010Jul_infodevl Found file /ccifas/tempifas/AU/sudolog_2010Jul_infoprod Found file /ccifas/tempifas/AU/sudolog_2010Jul_infoprodx Found file /ccifas/tempifas/AU/sudolog_2010Jul_infoqual Found file /ccifas/tempifas/AU/sudolog_2010Jul_infostag I guess I am confusing how Unix runs FTP versus Perl. In Unix before I run a FTP function, I can CD to the directory. In the code the FTP step with CWD, is that not changing the target directory location? Right. This is one of the things that I do not see explain at all in all the documentation about Net::FTP is how to process setting up the local and target directories. I am assuming I have done the change directory with the CD command and the FTP steps should work. Sorry for not grasping this as I am slow with Perl and some times simple commands to others do not make much sense to me. Takes me time to review answers and understand what others are saying with their code. It looks like the found results above is showing no endofline before the FTP step is even run. Ken	[reply]
Re^4: Net::FTP usage by kafkaf55 (Acolyte) on Aug 13, 2010 at 14:59 UTC
I updated the @array to @xfiles which is the new glob array. The FTP process worked! The files appeared at the right location. Results of the found command you coded: Found file /ccifas/tempifas/AU/sudolog_2010Jul_infodevl Found file /ccifas/tempifas/AU/sudolog_2010Jul_infoprod Found file /ccifas/tempifas/AU/sudolog_2010Jul_infoprodx Found file /ccifas/tempifas/AU/sudolog_2010Jul_infoqual Found file /ccifas/tempifas/AU/sudolog_2010Jul_infostag Is the $f =~ s/\s+$// ; statement doing the chomp function? Can you expand on the statement and tell me is it editing out whitespaces? Thank you, Corion for your help and understanding. I would probably never have solved this without you and the Perl Monks! Ken	[reply]
Re^5: Net::FTP usage by Corion (Patriarch) on Aug 13, 2010 at 15:02 UTC
For what `s/\s+$//` does, see perlop and perlre, and compare that with chomp.	[reply] [d/l]
Re: Net::FTP usage by jonadab (Parson) on Aug 13, 2010 at 18:48 UTC
Is the $f =~ s/\s+$// ; statement doing the chomp function? In this context, it's probably accomplishing more or less what the chomp would have been intended to accomplish. There are however technical differences, e.g., the + causes the substitution to remove as much trailing whitespace as it can find, so if the line ends with twenty-seven spaces in a row followed by three tab characters, a carriage return, and a line feed, they'll all be taken off; chomp would probably only take the CRLF, or maybe even just the linefeed, depending on the value of $/. For more details about the substitution, read the chapter on regular expressions in your favorite Perl book. Don't worry too much about chomp for now (until you have been using Perl for a while longer); if you know how to use s///, you can probably get by without chomp for the time being. (Regular expressions, on the other hand, are pretty much impossible to live without. The internet as we know it could more likely exist without integrated circuits than without regular expressions.)	[reply]