I redirect standard out to /dev/null in my cron jobs. s3cmd sends errors to
standard error, so I only get emails on error.
On Mon, Feb 10, 2014 at 5:24 PM, Florin Andrei wrote:
> The --no-progress option is great, but when running s3cmd from a cron
> job, it would be great if it had a quiet mode
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
nload everything.
Do those options only apply when syncing to an s3 bucket?
--
Scott Jacobsen
303-800-2711
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat lan