It uses bucket list operations to pull status data.  By default it uses the md5 and file size to compare.

Try using some -v or something, figure out what it's doing.  Otherwise no one could help.

Actually the current program can only have one transfer operating at a time.  Multiple transfers is a feature that I plan to add to the new version. 

I don't really know how to help with your problem.  I don't have control over the buffering from ruby.  The only thing I can think of is to purposefully slow down the transfer speed.

iconv is the thing which converts between character encodings.  It is telling you that it found a character sequence that shouldn't exist.  Either your choice for system encoding is set wrong, or there's some really bogus filename it's hiccuping on.

There have been many feature requests that have been too tricky to add with the current design, and bugs that have been the fault of the crappy ruby runtime.  Now ruby 1.9 breaks the old APIs, and the 1.8 runtime has started crashing on my windows system.

So I'm going to redesign and rewrite s3sync, and it's going to be in java so we get a robust runtime.  (I tried running the existing code under jruby, but got errors.  Besides, code needs redesign).

I'm going through all the outstanding features and bugs, and I will try to design with an eye toward extensibility.

Just wanted to give everyone a heads up... if anyone still uses or cares about this old cruft.

I am so tired of ruby.  The language had such potential but the runtime is such a pile of crap.

I think I'm going to rewrite s3sync to use a java back end.  At least it'll *work* then.. Seriously, most of the sync complaints can be traced back to shoddy runtime issues.

Signing has always been black box to me.  Did they update the "example" ruby libraries?  Maybe I need to merge in changes.

I'm concerned about possibly breaking existing functionality.  Can anyone else comment on this change?  My own backups seem as fine as usual.  But I'm not setting x-amz-acl or anything like that..

FYI to anons: you have to log in to see the attachment.

Can you send me output of a run with debug enabled?

Sorry; as I understand the S3 spec, you can't just "send utf-8".  object names must be URL-encoded.

Scenario (B) sounds like the correct approach.  But I see you are getting errors, so maybe there is some bug in s3sync.  Can you make a tar of your test files and send it to me? (see README for contact)

-r means recursive.. What's the problem you're experiencing?

It just uses the basic ruby calls for that stuff.. it's not shocking that it's wrong on cygwin. 

It's a sync.. it syncs file name, contents, owner name, and permissions.  Of course if you don't have permission to change those things, then I guess it'd fail.  You could comment that part out I'm sure.

Yeah I think it's an OS-level thing. 

Wow, is that something you can even *do* in ruby I wonder?