[syslog-ng]file() versus pipe() for kernel logging

Amodiovalerio Verde syslog-ng@lists.balabit.hu
Mon, 1 Mar 2004 16:09:37 +0100


It seems the only difference between file() and pipe() is the way files a=
re opened.

file() open files in read only , while pipe() open them in =
read-write.

There's also defined a source and a destination fifo() tha=
t is just another name for pipe().



Amodiovalerio [Hypo] Verde
=0D
=
---------- Initial Header -----------

>From      : syslog-ng-admin@list=
s.balabit.hu
To          : syslog-ng@lists.balabit.hu
Cc          : =0D
=
Date      : Sun, 29 Feb 2004 12:11:34 +1100
Subject : [syslog-ng]file() =
versus pipe() for kernel logging

> I was just wondering if anyone coul=
d explain the differences between pip()
> and file() when used as kernel=
 log sources.
> 
> For example the documentation suggests you would use=
 the following statement
> to collect kernel logs:
> 
> source s_file =
{ file("/proc/kmsg"); };
> 
> Most examples of syslog-ng.conf files I h=
ave seen have the following
> statement:
> 
> source s_pipe { pipe("/p=
roc/kmsg"); };
> 
> Is there any difference between the two?  Is one be=
tter than the other?
> 
> Any help much appreciated.
> 
> Thanks
> =0D
=
> James Turnbull
> 
> _______________________________________________=0D
=
> syslog-ng maillist  -  syslog-ng@lists.balabit.hu
> https://lists.bala=
bit.hu/mailman/listinfo/syslog-ng
> Frequently asked questions at http:/=
/www.campin.net/syslog-ng/faq.html
> 
>