From: | John R Pierce <pierce(at)hogranch(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: error messages not getting logged when running script from cron |
Date: | 2015-11-23 20:33:08 |
Message-ID: | 56537804.2050405@hogranch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 11/23/2015 12:21 PM, Tom Lane wrote:
>> >0 20 * * * db_backup.sh 1> /dev/null 2>&1 | mail -s "backup cron"
>> >myemail(at)comp(dot)com
>> >I am re-directing stderr to stdout and then sending that to email.
> Uh, read it again: you're redirecting stdout to /dev/null and then
> redirecting stderr to go where stdout goes. So all output is
> going to the bit bucket, not the pipe.
the 2>&1 notation is not completely intuitive.... if you want to
redirect stderr to the pipe and bitbucket stdout, do it in the opposite
order.
.... 2>&1 1> /dev/null | ...
that sends stderr to the file that stdout was assigned, and sends stdout
to the bit bucket... note specifically that redirecting stdout won't
affect the file stderr is being sent.
--
john r pierce, recycling bits in santa cruz
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2015-11-23 22:51:48 | Re: using a postgres table as a multi-writer multi-updater queue |
Previous Message | Melvin Davidson | 2015-11-23 20:29:35 | Re: error messages not getting logged when running script from cron |