Scott is correct. The errors are handled properly in s3cmd and sent to the
stderr stream (device). So you can pipe the stdout stream to /dev/null and
still see errors on the console (or send them to your destination of
choice--a log or database or email).
On Wed, Dec 19, 2012 at 9:58 AM, Scott Jac
Assuming s3cmd handles errors correctly error messages will be sent to
stderror and it will exit with a non zero exit status. I would test that
that is the case and use the exit status to check for errors, direct stdout
to /dev/null and capture stderr to your log.
Most often for a properly written
Andi and others:
With other command line tools, there is usually a "warnings only"
switch, in which the output is suppressed when things are normal, but if
a problem occurs, then it will respond with the problem.
For example, ffmpeg has the -loglevel switch, which can be set to
'quiet' 'warnin
Hi John,
I'm not sure exactly what you're asking. I don't use put routinely but I
do use sync in a script to run in the middle of the night and there I
catch the output to log files. If you don't want output can you just
direct it to /dev/nul?
Kind Regards,
Andi
On 12/12/2012 16:34, John Birc
Hello:
(sorry if this is a duplicate message - I have not revived any messages
from this list since I joined, including my first message that I should
have seen echoed back.)
I am trying to use s3cmd from within perl using system.
What is the switch to suppress the response dialog that comes b
Hello:
I am trying to use s3cmd from within perl using system.
What is the switch to suppress the response dialog that comes back for
every put request?
I have tried:
--no-progress
but that doesn't seem to change anything.
Also I there is nothing to say exactly where to put it, though I trie
