Re: multiftp.pl

[cybear]

ergowolf, What is it that you are doing with the message() statements?
Are you assigning somthing to it, or calling something from it?

On another note...
I have a script that FTP's a file to a VAN (Value-added Network).
Once the file transfer is complete an ILOG number is returned
from the VAN. This number 99.99999999% certifies that the file
was received correctly.

Currently, in order to capture that number, I need to turn
the debug on Net::FTP to 1 and redirect STDERR to a file.
 my $ftpSession = Net::FTP-> new("$host", Debug => 1); open (STDERR, ">>/detaillogfile.log");

Can you think of a better way?

[Anonymous Monk]

$ftp->message() is mentioned in the documentation - it returns the last line that was received from the server, so it would fit your purpose very nicely, read up the Net::FTP POD :)

[Anonymous Monk]

$ftp->message() grabs the last line STDOUT, but not the previous lines, nor STDERR... I'm trying to do the same thing...debug a troublesome FTP connection, and I'd like everything Debug -> 1 can give me. any way to redirect STDOUT and STDERR to a hash? (or a pair of them?)

[Anonymous Monk]

Is there by any chance we can get the return value of the FTP requests that we send to an FTP server ? Eg: 1->Success and 0->Failure

[skiboy]

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