You can use s3cmd or some other sort of shell.

OK so try near line 376 of s3sync.rb

Code:

begin
   dNode.updateFrom(sourceNode) unless $S3syncOptions['--dryrun']
rescue Errno::ENOENT => e
   $stderr.puts "Skipped item: #{e}"
end

As you can see it's just wrapping the existing line with a begin/rescue/end that matches the error type thrown.  The reason I put it out at the comparator instead of *right* where the error occurs at like 638 is that we need to catch at a place where we're able to easily move on to the next item.

If you paste in the error out messages I can advise you about changes.

Most of the existing error handling is in s3try.rb (not that it's necessarily where you need error handling added).  Look for blocks like

Code:

begin
   ....
rescue Some::ErrorType => e
   ...
end

If you find where you are erroring out, and what error type(s) you have, you can wrap it in begin/rescue/end

What happened to your NAS?  HD bork?  I recommend spinrite for drive health (not affiliated, just a satisfied customer)
http://www.grc.com/sr/spinrite.htm
Depending on the problem, you might even get to recover the old drive.

When I add this, I want it to be compatible with the --no-md5 option, so that when a transfer is needed it will calculate the md5 anyway (but not bother for just comparing the two trees)

I agree about the switch.  I know I need to add this feature.

Is there any reason you have done

Base64.encode64(md5.digest)

rather than

md5.hexdigest

or maybe I don't understand the difference properly..?

Warning: the patch is backwards.

You could use 'find' to get only new files, and pipe that to s3cmd.  Not a one-click type solution, but if you're concerned about efficiency maybe that's ok.

Are you missing base64.rb in your ruby installation's "lib" area?  That's all I can think of; there's nothing s3sync adds or changes here, the b64 stuff is all straight from the AWS s3.rb file.

It's not even clear to me why I need to input a certificate, when the question is to determine the authenticity of the S3 server, not that of mine, but this is another question.

You have to specify the cert of the server *or* that of a trusted root; that is the way it determines authenticity of the server.  If you have a set of root certs on your system you may be able to point the program there instead of using the single approach.  Then it behaves more like a web browser like you expect.  This stuff is just non-trivial to use because it's not a complete interface.  Maybe you ought to try jungle disk?

Widely announced, including here:
http://s3sync.net/forum/index.php?topic=163.0

Other comments, check your system mails

There's not any facility for it to input your own URLs like that.  It can only be used to generate the signed requests.

The right way to do this would involve using the s3 copy functionality, which is not something I've had time to look into.

Good to know, thanks. Is it a bug that S3sync actually waits for way way more than 30 seconds sometimes?

It would be a bug, but I bet it's really just moving on and no other lines get printed.  You can also decrease the delay by setting a parameter (see readme)