subset of the RFC959 commands.
if you really know what you're doing).
This is the constructor for a new Net::FTP object.
instead be passed as the "Host" option described below.
also refered to as an ftp proxy.
every 1024 bytes.  This simply invokes the "hash()"
anonymous@ will be used for password.
If the connection is via a firewall then the "authorize"
method will be called with no arguments.
"Net::Netrc" to do a lookup.
transfer all files in binary mode.
Send a request to the server to delete "FILENAME".
cause a subsequent data transfer to fail.
Remove the directory with the name "DIR". If "RECURSE"
Create a new directory with the name "DIR". If "RECURSE"
directories in the given path.
ated with a normal file.
Get "REMOTE_FILE" from the server and store locally.
tory with the same leafname as the remote file.
will be appended to the local file if it already exists.
then "REMOTE_FILE" must be specified. If "REMOTE_FILE"
if "REMOTE_FILE" is not given.
transfered will not be remove automatically.
Same as put but uses the "STOU" command.
after transfer may be different.
to a "Net::FTP::dataconn" based object.
the name of the new file that should be created.
these methods to do so.
that do not require data connections.
another ftp server using the "port" method.
connect directly to each other.
name of "SRC_FILE" will be used.
server using the STOU command.
plete between a passive server and a non-passive server.
to the remote server and wait for a response.
timeout value from the command connection will be used.
also performing any <CRLF> translation necessary.
from the command connection will be used.
Returns the number of bytes read so far.
the server was a '2'.
the RFC says) on the commands it accepts.
for file to be transferred.
the problem as almost every setup is different.
from a run of your program which does yield the problem.
files via the FTP protocol in a non-interactive manner.