Sponsored Content
Full Discussion: Automated FTP
Top Forums UNIX for Advanced & Expert Users Automated FTP Post 24396 by Saint Carlos on Thursday 11th of July 2002 02:08:16 AM
Old 07-11-2002
Lightbulb

In Unix if u r looking for a completely automated ftping process, i feel its not possible , not possible simply because the ftp process does not return a valid exit status, an exit can occur due to many reasons and if u r to monitor whats happening then u cannot call it an automated ftp session. The only way out that i found especially when ur ftping takes place for hours,was to use another software called ncftp,which worked wonderful for me.

These r the status codes returned from 0- 12
Success.
Could not connect to remote host.
Could not connect to remote host - timed out.
Transfer failed.
Transfer failed - timed out.
Directory change failed.
Directory change failed - timed out.
Malformed URL.
Usage error.
Error in login configuration file.
Library initialization failed.
Session initialization failed.

which the normal ftp application does not.

This will solve the problem

Carlos
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

FTP automated?

If I wanted a machine to put a specific file onto another OS far across the internet via FTP - and I wanted to do it automatically not user intervented, how would I do that? Use the PUT command? The file name and position never changes, it gets overwritten and the system on the other end... (6 Replies)
Discussion started by: n9ninchd
6 Replies

2. UNIX for Dummies Questions & Answers

one time automated ftp session

How can an automated script be setup to run at a later time in the day. cron runs recurring tasks. I am interested in a one time process. I want to back up a number of files whenever I make changes to an application and ftp for backup purposes. The script to automate the zipping of files has... (1 Reply)
Discussion started by: msmkeml
1 Replies

3. IP Networking

Automated ftp for Multiple files

I have seen the script posted yesterday for automated ftp Can we do some thing like ftp ing multiple files in one script Example input.txt has all files names to be ftped input.txt ------ a.tar b.ccp c.perl i need to ftp all the files present in input.txt i tried something like... (0 Replies)
Discussion started by: pbsrinivas
0 Replies

4. Shell Programming and Scripting

automated ftp.

Hi I am trying to delete some specific files ( files other than created today) from the server on a cron basis. I wrote a small script, but I am stuck up in how to delete only specific files. #!/usr/bin/expect -f set IP set timeout -1 spawn ftp $IP expect ): send "username\n"... (10 Replies)
Discussion started by: sangfroid
10 Replies

5. Shell Programming and Scripting

how to devlop automated FTP in UNIX

Automated FTP. hint : use 'atd' to schedule to run a specific script. An Env Variable should be created,say CONF_DIR which points to some dir. @ some time, create a TAR file of this and FTP it to some server. (3 Replies)
Discussion started by: vishalzone2002
3 Replies

6. Shell Programming and Scripting

Automated FTP

I want to do Automated FTP from linux client to LINUX server using a shell script after every one hour. And copies last most updated file from Linux server. OR You can say that whenever files get modified on LINUX server so it also copies on my LINUX client. Linux SERVER path=... (4 Replies)
Discussion started by: wakhan
4 Replies

7. IP Networking

Automated FTP task

Every day i ftp tar.gz a file from the production server to a back up machine.. This task creates way to much traffic on the network at the end of the day and puts and undo load on the production machine during operation hours. i would like to create a script that would automatically fire off the... (36 Replies)
Discussion started by: LowOrderBit
36 Replies

8. Shell Programming and Scripting

Automated FTP script using .netrc to multiple FTP servers

Hi all, I'm using the following script to automated ftp files to 1 ftp servers host=192.168.0.1 /usr/bin/ftp -vi >> $bkplog 2>&1 <<ftp open $host bin cd ${directory} put $files quit ftp and the .netrc file contain machine 192.168.0.1 login abc... (4 Replies)
Discussion started by: varu0612
4 Replies

9. Shell Programming and Scripting

Automated FTP

Hello,I just know the basics of scripting & I need a script to automate ftp since I use it quite often. I use ftp to transfer different kind of files and everytime the source & the destination directories are different for transferring files, so can anyone help me out on this urgently.. (2 Replies)
Discussion started by: mohit_02mar
2 Replies
ncftpput(1)						      General Commands Manual						       ncftpput(1)

NAME
ncftpput - Internet file transfer program for scripts SYNOPSIS
ncftpput [options] remote-host remote-directory local-files... ncftpput -f login.cfg [options] remote-directory local-files... ncftpput -c remote-host remote-path-name < stdin OPTIONS
Command line flags: -u XX Use username XX instead of anonymous. -p XX Use password XX with the username. -P XX Use port number XX instead of the default FTP service port (21). -j XX Use account XX in supplement to the username and password (deprecated). -d XX Use the file XX for debug logging. -a Use ASCII transfer type instead of binary. -m Attempt to make the remote destination directory before copying. -t XX Timeout after XX seconds. -U XX Use value XX for the umask. -v/-V 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 XX for host, user, and password information. -A Append to remote files, instead of overwriting them. -T XX Upload into temporary files prefixed by XX. -S XX Upload into temporary files suffixed by XX. -R Recursive mode; copy whole directory trees. -r XX Redial a maximum of XX times until connected to the remote FTP server. -z/-Z Do (do not) try to resume transfers. The default is to not try to resume (-Z). -E Use regular (PORT) data connections. -F Use passive (PASV) data connections. The default is to use passive, but to fallback to regular if the passive connection fails or times out. -DD Delete local file after successfully uploading it. -y Try using "SITE UTIME" to preserve timestamps on remote host. Not many remote FTP servers support this, so it may not work. -b Run in background (by submitting a batch job and then spawning ncftpbatch). -bb Similar to -b option, but only submits the batch job. You will need to run ncftpbatch for the batch job to be processed. This is useful if you already have a ncftpbatch process running, or wish to have better control of when batch jobs are processed. For example, if you wanted to do background processing of three files all on the same remote server, it is more polite to use just one ncftpbatch process to process the three jobs sequentially, rather than having three ncftpbatch processes open three simultane- ous FTP sessions to the same server. -B XX Try setting the TCP/IP socket buffer size to XX bytes. -W XX Send raw FTP command XX after logging in. -X XX Send raw FTP command XX after each file transferred. -Y XX Send raw FTP command XX before logging out. The -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. For the -X option, you can use the cookie %s to expand into the name of the file that was transferred. DESCRIPTION
The purpose of ncftpput 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 ncftp. By default the program tries to open the remote host and login anonymously, but you can specify a username and password information. The -u option is used to specify the username to login as, and the -p option is used to specify the password. If you are running the program from the shell, you may omit the -p option and the program will prompt you for the password. Using the -u and -p 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 ps program could see your password while the program runs. You may use the -f 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 account information. Nevertheless, if you choose to use the -f option the file should look something like this: host sphygmomanometer.ncftp.com user gleason pass mypassword Don't forget to change the permissions on this file so no one else can read them. The -d 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 stdout as the name of the debugging out- put 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 -a 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 using the -R flag. Example: $ ncftpput -R pikachu.nintendo.co.jp /incoming /tmp/stuff This would create a /incoming/stuff hierarchy on the remote host. The -T and -S 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 complete. Using these options, you will not destroy a remote file by the same name until your file is finished. 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 finished sending. Here is an example that uploads to the file /pub/incoming/README, using the filename /pub/incom- ing/README.tmp as a temporary filename: $ 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 -c option, which denotes that you're using stdin as input. 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 DIAGNOSTICS
ncftpput returns the following exit values: 0 Success. 1 Could not connect to remote host. 2 Could not connect to remote host - timed out. 3 Transfer failed. 4 Transfer failed - timed out. 5 Directory change failed. 6 Directory change failed - timed out. 7 Malformed URL. 8 Usage error. 9 Error in login configuration file. 10 Library initialization failed. 11 Session initialization failed. AUTHOR
Mike Gleason, NcFTP Software (mgleason@ncftp.com). SEE ALSO
ncftpget(1), ncftp(1), ftp(1), rcp(1), tftp(1). LibNcFTP (http://www.ncftp.com/libncftp/). Software NcFTP ncftpput(1)
All times are GMT -4. The time now is 05:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy