On Mon, 20 Aug 2012 15:12:57 -0400 Chris Knadle <[email protected]> put fingers to keyboard and said:
>On Monday, August 20, 2012 11:36:09, Bruce Bowler wrote: >> I have set up my .forward file to look like this... >> >> # exim filter >> unseen pipe "/path/to/command" >> >> And when I receive a message, the bash file 'command' is run, as >> expected. However, somewhere deep within the bowels of 'command', I >> have an error and not everything is completing as expected. I >> suspect it's a path problem, but don't know that for sure. Is there >> a way to get any output from 'command' either saved as a file on >> disk (I tried appending &> file.txt, to no avail) > >Just to double-check -- do you mean you did: > > command > file.txt 2>&1 > >i.e. you also redirected the error output to file.txt? > > -- Chris 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 there's output from the script as there are some echo commands that I put in to help figure out where it's mucking up... Bruce -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
