Интерактивная система просмотра системных руководств (man-ов)
ncftpput (1) ( Solaris man: Команды и прикладные программы пользовательского уровня )>> ncftpput (1) ( Linux man: Команды и прикладные программы пользовательского уровня )
ncftpput - Internet file transfer program for scripts
remote-host remote-directory local-files...
Command line flags:
- -u XX
instead of anonymous.
- -p XX
with the username.
- -P XX
Use port number
instead of the default FTP service port (21).
- -j XX
in supplement to the username and password (deprecated).
- -d XX
Use the file
for debug logging.
Use ASCII transfer type instead of binary.
Attempt to make the remote destination directory
- -t XX
- -U XX
for the umask.
Do (do not) use progress meters.
The default is to use progress meters if the output stream is a TTY.
- -f XX
Read the file
for host, user, and password information.
Append to remote files, instead of overwriting them.
- -T XX
Upload into temporary files prefixed by
- -S XX
Upload into temporary files suffixed by
Recursive mode; copy whole directory trees.
- -r XX
Redial a maximum of
times until connected to the remote FTP server.
Do (do not) try to resume transfers.
The default is to
try to resume (-Z).
Use regular (PORT) data connections.
Use passive (PASV) data connections.
The default is to use passive, but to fallback to
regular if the passive connection fails or times out.
Delete local file after successfully uploading it.
Try using "SITE UTIME" to preserve timestamps on remote host.
Not many remote FTP servers support this, so it may not work.
Run in background (by submitting a batch job and then spawning
option, but only submits the batch job.
You will need to run
for the batch job to be processed.
This is useful if you already have a
process running, or wish to have better control of when batch
jobs are processed.
if you wanted to do background processing of three
files all on the same remote server, it is more polite
to use just one
process to process the three jobs sequentially, rather than
processes open three simultaneous FTP sessions to the same
- -B XX
Try setting the TCP/IP socket buffer size to
- -W XX
Send raw FTP command
after logging in.
- -X XX
Send raw FTP command
after each file transferred.
- -Y XX
Send raw FTP command
before logging out.
-W, -X, and -Y
options are useful for advanced users who need to tweak
behavior on some servers.
For example, users accessing mainframes might need to send
some special SITE commands to set blocksize and record format information.
For these options, you can use them multiple times each if you need
to send multiple commands.
option, you can use the cookie
to expand into the name of the file that was transferred.
is to do file transfers from the command-line
without entering an interactive shell.
This lets you write shell scripts or other unattended
processes that can do FTP.
It is also useful for advanced users who
want to send files from the shell command line without
entering an interactive FTP program such as
By default the program tries to open the remote host
and login anonymously, but you can specify a username
and password information.
option is used to specify the username to login as,
option is used to specify the password.
If you are running the program from the shell, you may
option and the program will prompt you for the password.
options are not recommended, because your account information
is exposed to anyone who can see your shell script or your
process information. For example, someone using the
program could see your password while the program runs.
You may use the
option instead to specify a file with the account information.
However, this is still not secure because anyone who
has read access to the information file can see the
Nevertheless, if you choose to use the
option the file should look something like this:
Don't forget to change the permissions on this file
so no one else can read them.
option is very useful when you are trying to diagnose
why a file transfer is failing.
It prints out the
entire FTP conversation to the file you specify, so
you can get an idea of what went wrong.
If you specify the special name
as the name of the debugging output file, the output
will instead print to the screen.
Using ASCII mode is helpful when the text format of your host
differs from that of the remote host.
For example, if you are sending a text file from
a UNIX system to a Windows-based host, you could use the
flag which would use ASCII transfer mode so that the file
created on the Windows machine would be in its native text
format instead of the UNIX text format.
You can upload an entire directory tree of files by
$ ncftpput -R pikachu.nintendo.co.jp /incoming /tmp/stuff
This would create a /incoming/stuff hierarchy on
the remote host.
options are useful when you want to upload file
to the remote host, but you don't want to use
the destination pathname until the file is
Using these options, you will not destroy a
remote file by the same name until your file
These options are also useful when a remote
process on the remote host polls a specific
filename, and you don't want that process to
see that file until you know the file is
Here is an example that uploads to the file
/pub/incoming/README, using the filename
/pub/incoming/README.tmp as a temporary
$ ncftpput -S .tmp bowser.nintendo.co.jp /pub/incoming /a/README
A neat way to pipe the output from any local command into
a remote file is to use the
option, which denotes that you're using
The following example shows how to make a backup and store
it on a remote machine:
$ tar cf - / | ncftpput -c sonic.sega.co.jp /usr/local/backup.tar
returns the following exit values:
Could not connect to remote host.
Could not connect to remote host - timed out.
Transfer failed - timed out.
Directory change failed.
Directory change failed - timed out.
Error in login configuration file.
Library initialization failed.
Session initialization failed.
Mike Gleason, NcFTP Software (email@example.com).
- Command line flags:
- SEE ALSO