Shell Programming and Scripting

Hi,

I am trying to figure out a ksh script that i have and i think i found it but not sure.

i am having to scp or sftp files from my remote server over 2 others to the destination.

i have the rsa keys setup for the servers on my end and the username and password for the final server.

i have to clean out the sftp server folders so i do not transfer duplicate files over.

basicaly i ssh to sftp1 server

Code:

cd to directory 
rm -f *

then i do a scp of the files i need to that folder.

my question is can i stick an exit command after the rm so that i quit the ssh connection before the scp?

i am running into an issue of i think i am still on the sftp1 server while i try and do the scp which results in no files being transfered.

Code:

ssh -T ${guser}@${gsftp} <<endscript >> ${debug_log} 2>&1
echo $HOSTNAME
cd ${draw_dir}
pwd
rm -f *.*
exit
#Transfer to 
scp ${draw}* ${guser}@${gsftp}:${draw_dir} >> ${debug_log}
endscript

would this work? thanks.
i couldn't find this on the forum.

Sure, or you could pipe the files down the stream using something like cpio or tar, continuing to use the original connection. I like 'cpio -oaH crc' and 'cpio -idmH crc' to pack and unpack, respectively. The more connections you make, the more ssh connection setup delay you eat, and the more chance the connection will fail or hit some system ssh limit. Use ssh compression, or put your choice of compression right on the pipe to speed the transfer and reduce the encrypt cost:

Code:

$ fgrep cpio mysrc/*
mysrc/bcpio:cpio -oaH crc $1 |bzip2 $2
mysrc/buncpio:bunzip2 <$2 |cpio -idmH crc $1

Code:

cd ${draw_dir} || exit

is safer, because it will exit if the cd would fail - and not empty the wrong directory.
*.* matches filenames with a dot.
The endscript terminates the remote code initiated by the ssh. Shouldn't that be directly after the rm *.*, replacing the exit?

The script makes no sense, as while on the remote host you scp remote host explicit to remote host implicit, so cp would do.