Michal Ludvig wrote:
> Hi Jeff,
> 
>> Is it possible for s3cmd to read from stdin and write to stdout?
> 
> Yes, 'get' can be done to stdout, simply use 's3cmd get s3://... -' and
> it'll print the file content to stdout.
> 

Okay, that's good to know.  I could then pipe that directly to gunzip and then 
restore if needed.

> However 'put' can't read from stdin (yet), because Amazon has to know
> the input file size before upload and that's not known when reading from
> stdin. Indeed, s3cmd could save the input stream to a temporary file (or
> keep it in memory for small inputs) to find the size but that is not
> implemented yet.
> 

Ah, that makes sense.

>> I do level dumps that I save on a local disk.  Although I do not want to gzip
>> them here (just makes retrieving a file from the dump that much slower) I do
>> want to gzip -9 the file before I put it into my S3 bucket.
>>
>> Alternatively, can I use gzip as the encryption program, with the appropriate
>> flags in the encrypt and decrypt commands?  I tried this but got a python
>> error--I may not have had the python syntax correct in the s3cfg file.
> 
> It is probably possible to abuse --encrypt for compression, however I'll
> better add --compress option for that, what do you think? ;-)
> 

I think that sounds great! I look forward to trying this out.  I've only just 
begun with s3cmd but it is working as advertised--so far much better than 
using s3rsync.

  Michal

Jeff

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
S3tools-general mailing list
S3tools-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/s3tools-general

Reply via email to