Since the Amazon-side algorithm is uncovered, the 's3cmd info' operation should be enhanced to return both the entire-file MD5 hash (as it now does) and the Amazon MD5 Etag.
Those who use 's3cmd' to archive huge backup volumes will want to retrieve the value and match it against the local calculation for it. The only other way to obtain an MD5 calculated by Amazon for an entire file is to 's3cmd mv' the file over itself. This could incur charges and/or take a long time for large files. Might be especially useful for multi-terabyte files migrated to Glacier. Perhaps this is worthy of an additional option off the 'list' command so that all of the MD5 Etags can be recovered in one operation. ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ S3tools-general mailing list S3tools-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/s3tools-general
