On Thu, May 30, 2002 at 07:38:32AM -0400, Michael Earls wrote:
On this new ver does it fix the broken pipe on debian?
michael
bazsi@balabit.hu 05/30/02 02:32 AM >>> Hi,
I've released syslog-ng 1.5.18 with the folowing NEWS entry:
News for the 1.5.18 release Wed, 29 May 2002 12:23:45 +0200
Changes: * fixed a crash bug when an UDP destination was unreachable
In addition to this you can now specify log_prefix() for pipe sources.
It can be downloaded from the usual places:
I haven't touched the pipe support. However I think pipe() has no problems on Debian, as the following typescript shows: balabit:~/src/syslog-ng-1.5/src$ cat syslog-ng.conf source src { pipe("log.input"); unix-stream("log"); internal(); }; destination dst { pipe("log.output"); }; log { source(src); destination(dst); }; balabit:~/src/syslog-ng-1.5/src$ ls -l log.input log.output prw-r--r-- 1 bazsi bazsi 0 May 30 13:45 log.input| prw------- 1 bazsi bazsi 0 May 30 13:45 log.output| balabit:~/src/syslog-ng-1.5/src$ ./syslog-ng -dvf syslog-ng.conf & initialising nscache: 1007 entries, 3600/60 expiration. io.c: Preparing fd 3 for reading binding fd 4, unixaddr: log io.c: listening on fd 4 syslog-ng version 1.5.18 starting [1] 25160 balabit:~/src/syslog-ng-1.5/src$ logger -u log xxx io.c: Preparing fd 5 for reading io.c: Preparing fd 6 for writing Read EOF on fd 5. Marking fd 5 for closing. Closing fd 5. balabit:~/src/syslog-ng-1.5/src$ echo xxx2 > log.input balabit:~/src/syslog-ng-1.5/src$ cat log.output May 30 13:45:04 src@balabit <someone>: xxx May 30 13:45:12 src@balabit xxx2 balabit:~/src/syslog-ng-1.5/src$ exit As you can see both messages can be read from the output fifo. We're definitely using pipe() sources on production systems. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1