Shell Programming and Scripting

I have a shell script where I am trying to ftp some files but I get the error message "EOF unclosed" every time the script reaches the ftp section. Here is how my script is written.


#more code up here
rm -f $object >> $LOG_FILE 2>&1
fi #end of if
done #end of for loop

#################################################
ftp -n -v -i << EOF >> $LOG 2>&1
open $HOST_ADDRESS
user $HOST_LOGIN $HOST_PASSWD
ascii
lcd $DIR
cd $FTPDIR
mput $REPORT.*
close
quit
EOF
#################################################

This same script works if I take the FTP part and put it in a separate script by itself. But I don't like the idea of having a separate script just for FTP and would like to keep all of the code in the same script, if possible.

Please help on this issue as I am not sure what is wrong here.

You could use functions in a shell script. I have a script where one function does the FTP and the rest is taken care by other functions. I suppose the same would work for you too.

HI,
Did u try eot_ in place of EOF

after ftp the file. bye is not closed

for example..
for i in `cat a`
do
ftp -i -n I.P <<EOF
user Login password
promp
hash
mput $i
bye
EOF
done

revert back whether ur prob solved or not
Narsing

I have found cURL (command-line URL) indispensable for writing scripts with FTP commands. It is available at http://curl.haxx.se/ (both compiled binaries and source code).

It takes the place of the FTP client allowing not only puts and gets but deletes and directory listings. It also returns a detailed exit code for conditional evaluations.

For example, your original post could be handled with:

cd $DIR
for FILE in $REPORT.*
do
if curl -T $FILE -u $HOST_LOGIN:$HOST_PASSWD ftp://$HOST_ADDRESS/$FTPDIR/
then
echo "$FILE transferred"
else
echo "FTP of $FILE failed" 1>&2
fi
done

This is a simple example. It supports numerous protocols and has more options than letters in the alphabet. The usefulness of this utility in scripts is without measure.

Thanks for all the help. I was finally able to resolve this issue. There was a bad character after EOF in my code that I could not view through vi. After hours of troubleshooting I found this issue and deleting the character after EOF resolved the issue.