Thanks for the help, I did a ktrace. I noticed this in the trace. The trace file has nothing in it until I echo something to the pipe. 14319 bash CALL close(0x3) 14319 bash RET close 0 14319 bash CALL ioctl(0,TIOCGETA,0xcfbfd350) 14319 bash RET ioctl -1 errno 45 Operation not supported 14319 bash CALL lseek(0,0,0,0,0x1) 14319 bash RET lseek -1 errno 29 Illegal seek 14319 bash CALL read(0,0xcfbfd427,0x1) 14319 bash GIO fd 0 read 1 bytes "P" Bobby On Tue, 18 Nov 2003 10:08:39 +0100 Balazs Scheidler <bazsi@balabit.hu> wrote:
The script probably exits because of an EOF read from named.pipe, at least this is the case when you echo something into the named pipe.
syslog-ng should never close the pipe though, so it should correctly send messages. Maybe you should try to strace|ktrace|truss the shell script to see what it exactly does.
-- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html