in reply to Re: Re: FTP automation
in thread FTP automation

stange indeed. Have you tried setting the debug flag to see if anything odd pops up (need for passive mode? timeout? etc?)

my $FTP=Net::FTP->new($mvp, Timeout=>20, Debug => 1);

-derby

Replies are listed 'Best First'.
Re: Re: Re: Re: FTP automation
by TStanley (Canon) on Jul 01, 2003 at 16:21 UTC
    Setting the debug in my above test code shows the following:
    Net::FTP: Net::FTP(2.65) Net::FTP: Exporter(5.566) Net::FTP: Net::Cmd(2.21) Net::FTP: IO::Socket::INET(1.26) Net::FTP: IO::Socket(1.27) Net::FTP: IO::Handle(1.21) Net::FTP=GLOB(0x15de3b4)<<< 220 Service ready Net::FTP=GLOB(0x15de3b4)>>> user mvpadmin Net::FTP=GLOB(0x15de3b4)<<< 500 Unsupported command Connected to 128.1.198.22 Net::FTP=GLOB(0x15de3b4)>>> TYPE I Net::FTP: Unexpected EOF on command channel at ftptest.pl line 17 getsockname() on closed socket GEN0 at D:/Perl/lib/IO/Socket.pm line 1 +92.

    TStanley
    --------
      Hmm ... I wonder if your FTP server can only handle an uppercase "user" command. I would try to issue the lowercase user command from your manual ftp client to see what happens. If you can only use uppercase your either going to need to hack the FTP.pm module (since it explicitly uses lower case even though the rest of the commands are uppercase) or subclass it and override the _USER method.

      -derby