Not presently, no.  One hacky way to do it, I suppose, would be to comment out the symlink cases.  I think they'd get treated like normal dirs then.

# of retries is settable. 

Some ppl have reported improved tx rates running several copies at once (on different dirs obviously)

There is probably a bug in the connection code where we should reset the connection more forcefully than currently does.

Lots of needed changes, no time lately to do them.

Must be a bug in the yml processing (which I don't use myself).

You could write a patch in a progress-stream-like fashion that runs an idle timer and aborts.  Someone else had a similar request, but I don't necessarily see doing that myself.

I don't yet know what the deal is but I have an idea.  I think that a recent change may have weakened the ability for the connection state to reset (somehow)

I don't have any idea what to do about it.  The char code stuff is all a black box ruby lib that I call into.

I am totally stumped.
If you want to temporarily grant me
<--------
access to your test bucket I can try and repro the problem here.

So you can list that bucket using s3cmd and the same creds?

I am greg13070

Patience

Try ./s3ync.rb -r --ssl /Drop1/ mybucket:Drop1

From a cron:
I have my commands send output to a log file, and if the result code was non-zero I 'cat' the log file so it will be emailed to me via the cron system.  This way I don't have to care about logs when the procedure worked fine.

OK so it sounds like for some reason there are items stuck and not able to be deleted, in 2 different tools too. Unless you want to give me access to your bucket I think you'll have to talk to AWS.

Why not just make the command say /usr/local/bin/ruby then?

More useful if you posted the command.  Even more if you posted -d output. 

EOF usually is a local issue such as trying to access an open named pipe or some other abnormal/open/locked file.