Means that you created the s3 side with some other tool and expected s3sync to pull it back down to local.  But since the folder nodes were not stored by s3sync, it is horking now.

"$folder$" is a give away.. s3sync doesn't build nodes like that. 

You can try the option to force local folder creation and see if that helps.  You might also try including your command line and the -d output here.

Out now.

2008-01-06
Version 1.2.4
Run from any dir (search "here" for includes).
Search out s3config.yml in some likely places.
Reset connection (properly) on retry-able non-50x errors.
Fix calling format bug preventing it from working from yml.
Added http proxy support.
----------

Will be fixed today; see announce.

Is this a commonly needed feature?  It seems a bit fringe to me, but if you all need it I can include it in the future.

A nice fix for this will be coming today.  Watch announce.

See http://s3sync.net/forum/index.php?topic=133.msg589#msg589

I'm going to put a (hopefully) fix in for this today.  Check announce board.  Will need testers!

Nice touch. Thanks.

Attached is a mod I made to s3config.rb to look for s3config.yml in the .s3conf, $HOME/.s3conf, and /etc/s3conf directories. That way you can lock down your s3config.yml in an appropriate directory but still run the s3cmd/s3sync.rb scripts from anywhere.

... WkH

Will be added to main version today. Check announce.

If you add this line to the top of your s3cmd.rb, you can run the script from anywhere.

$LOAD_PATH << File.expand_path(File.dirname(__FILE__))

Will be added today in sync and cmd; watch announcements.

I have this problem also.

This works:
AWS_CALLING_FORMAT=SUBDOMAIN ./s3cmd.rb createbucket mybucket EU
but only if I remove
AWS_CALLING_FORMAT: SUBDOMAIN
from s3config.yml. Otherwise it fails with 403 Forbidden (SignatureDoesNotMatch)

This will be fixed today; watch announce.

Will be fixed today, watch announce board.

You'd have to hack on the list code.

Yes it is reported to be broken already.  You can only set that one with an env variable at the moment.

I wonder what occurred right *before* that.  It is as if the connection is being closed but we don't catch it.