From: Matt D. <ma...@do...> - 2014-03-13 02:13:07
|
There's a bug I see (and I created) in current upstream master, where --no-check-md5 will still do the file I/O on local files to get the md5sums for them, exactly to decide if it can do remote copying. That's annoying. This bug also means --no-check-md5 won't, as you might expect, disable remote copying. As no one has asked to be able to disable remote copying, I never coded for it. I'll think about this a bit. There's probably a cleaner way to solve both problems. On Wed, Mar 12, 2014 at 5:14 PM, WagnerOne <wa...@wa...> wrote: > While this feature is fantastic, I can't find a lot of detail on it in > general. I wonder how to disable it? > > During initial uploads at least, our DirectConnect link seems to be faster > in copying the files themselves than s3cmd is at telling S3 to "remote > copy" objects. > > Would that simply be using s3cmd switch --no-check-md5 ? > > This would seem likely to reduce the RAM required to enumerate the source > files too? > > Thanks, > Mike > > > > > > ------------------------------------------------------------------------------ > Learn Graph Databases - Download FREE O'Reilly Book > "Graph Databases" is the definitive new guide to graph databases and their > applications. Written by three acclaimed leaders in the field, > this first edition is now available. Download your free book today! > http://p.sf.net/sfu/13534_NeoTech > _______________________________________________ > S3tools-general mailing list > S3t...@li... > https://lists.sourceforge.net/lists/listinfo/s3tools-general > > |