Am 20.08.2012 22:24, schrieb Todd Lyons: > On Mon, Aug 20, 2012 at 12:47 PM, Bruce Bowler <bbowler@???> wrote:
>> command &> file.txt
>> which in bash should send both stdout and stderr to file.txt
>> file.txt never appears, even when given a complete path. I know
> You're using a bash feature when you test it, but your script is
> likely being run under the Bourne shell. Change "&>" to "> file.txt
> 2>&1" or change the shell your script is using.
>
> ...Todd
the docs say, no shell is involved in executing pipes.. which is correct
as i found the hard way ;)
You can debug pipes only this way :
|/path/to/script
whilst outputing the messages to stdout.
The result is a deliverymsg to the sender of the mail you reacted to,
which tells him, "something went wrong heres the output:"
This means, you send mails all the time OR you wrap the script executed
inside a shellscript, which redirects the messagesto a file instead.
