Search Results

I think you missed my point. I was suggesting something like:

ls -tr $tbtsftp > listoffiles.txt

for FILE in `cat listoffiles.txt`; do
echo "cd "$remotepath_VAN >> $commandlist
echo...

Do you need to?

You already know which files you're attempting to transfer (ls -tr $tbtsftp > listoffiles.txt). Can you check which files actually transferred via increasing sftp's log level and...

I think that's expected behaviour - the built-ins abort, but shell can do whatever.

Your issue then is just that you don't know what (local) unlinks failed? Couldn't you create a list of the files...

Just to clarify, sftp -b isn't aborting on a failed put either?

As I mentioned in an edit above, can you do a pull rather than a push? Then you could use sftp's internal rm, and it would abort on fail.

Yes - I was confusing my local and remotes...

EDIT: Although it would work (abort) if you ran it the other way :).

!rm is excuting a shell command though, is it not? As opposed to sftp's builtin.

Theory only, haven't tried it myself :).

sftp rm should abort on fail, according to the man page: