kamaldev,

itkamaraj has drawn you the skeleton of a solution. You will need to ftp one file at a time with the loop. If you test that the file has been delivered successfully, then you can remove it on the local server. If you try it how you have it at the moment, you will put every file every time you read a line from you input file, so one file will be put once (no worries there), but two will be put twice (hmmmm) or 10 files will be put ten times EACH. if the files are big then you could be thrashing things about repetitively quite a bit.

Do you really want to only put files with a dot in their name? From unix, an "mput *" is all that is required to state all files, but you are also sending every file with the mput so you may duplicate the FTP later on if you run the job again.

Capture the output from the FTP command and look for the success message in your script. The FTP command may still exit with return code zero (i.e. no error) even if the file fails to be written, because the error is remote and the FTP command itself works. If you schedule this with SFTP, then you would get a non-zero return code to test, but it depends on you having the SFTP client & server tools installed.


Something like this perhaps:-

Code:

while read filename
do
     ftp -i -n << EOF  > ftp_log.txt
        open 192.168.1.75
        user loguser PASSWORD
        prompt
        cd \logs_finacle
        put ${filename}
        EOF

     if [ `grep -c "^226 " ftp_log.txt` -eq 1 ]
     then
         rm ${filename}
     else
         echo "Failed to deliver file ${filename}"
         exit 99
     fi
done < /usr/ftprm.txt

Be careful to ensure that the EOF line is only indented with tab characters. Using a space will mean that the block of text passed to the FTP command will be incomplete and the FTP will fail with a strange message.

You will need to run an FTP manually to check what the success message you should get is. Mine is prefixed with the line starting "226", so that's what I've used. The ^ states that this is the beginning of the line.


I hope that this is helpful. It is a lot to take in at once, so ask if you need some clarification - or should if I've made an error. I would never profess to be perfect!



Robin
Liverpool/Blackburn
UK