On Wed, 2008-08-20 at 09:10 -0500, midnight codder wrote:
Thanks for all of those alternatives. Allow me to rephrase my question (any idea): Does anyone have any idea as to why I am getting the broken pipe? The script I am using now is for the sake of simplifying things so I can pin point where troubles begin. We are not going to use such a script in production. The original java program that was supposed to be the destination is much more complicated, although in a sense it still reads the log messages off of std in, just like the script. (it is the handling of the logs afterwards that is complex). I shall investigate into using one of the alternatives, however - I will still be happy to know what might have went wrong.
<priC> <date 08-08-19T15:13:56.198-05:00> <host=oracle-test> <msg=syslog-ng[27971]: I/O error occurred while writing; fd='11', error='Broken pipe (32)'> <priF> <date 08-08-19T15:13:56.198-05:00> <host=oracle-test> <msg=syslog-ng[27971]: Sending child a TERM signal; child_pid='27972'>
Your script terminates for some reason, it's not syslog-ng that kills your process, it is your script that dies. please run syslog-ng under strace -f (to follow forks) and see why your shell script exits. -- Bazsi