Re: syslog.conf format (Re: SoC: Improve syslogd)

[christos%astron.com@localhost (Christos Zoulas)]

In article 
<dc67eef70806092240q78f0f155v99a75b04b27eb487%mail.gmail.com@localhost>,
Rainer Gerhards <rgerhards%gmail.com@localhost> wrote:
>On Mon, Jun 9, 2008 at 9:15 PM, Christos Zoulas 
><christos%astron.com@localhost> wrote:
>> In article 
>> <dc67eef70806090641o1d881b8la1351ce25493cfb6%mail.gmail.com@localhost>,
>> Rainer Gerhards <rgerhards%gmail.com@localhost> wrote:
>>>On Mon, Jun 9, 2008 at 12:53 PM, Martin Schütte 
>>><lists%mschuette.name@localhost> wrote:
>>>> Rainer Gerhards schrieb:
>>>>>
>>>[snip for now]
>>>> Also some implementations already made incompatible extensions. The most
>>>> important is probably the pipe action (|), which pipes to a fifo on Linux
>>>> (sysklogd and rsyslog) but to an exec()'d program on BSD.
>>>
>>>Good to know. Maybe I extend rsyslog so that it has a switch to change
>>>the meaning of that option. But it depends on whether or not that make
>>>real sense - I am undecided ;)
>>
>> Why not use > for fifo and | for program?
>
>The problem is backwards compatibility. If I change the syntax (from |
>to >), lots of configurations would be broken. So I can not do that.

Can't you just stat the destination and if it is a fifo and it has | warn
for a version or two?

christos