[syslog-ng] [Bug 135] pipe() source missing follow_freq() option

Patrick H. syslogng at feystorm.net
Wed Sep 28 15:57:59 CEST 2011

I havent looked at the code, but whats the behavior that is used when 
reading from pipes? There's 2 ways of seeing if theres data on a pipe, 
doing a periodic non-blocking read, and doing a select. From the 
documentation it sounded like doing a non-blocking read was the default 
behavior to check if theres data on the pipe, and that setting 
follow-freq to 0 changed it to a select() call. So without having this 
option available, which does it use?


Sent: Wed Sep 28 2011 01:22:39 GMT-0600 (MST)
From: bugzilla at bugzilla.balabit.com
To: syslog-ng at lists.balabit.hu
Subject: [syslog-ng] [Bug 135] pipe() source missing follow_freq() option
> https://bugzilla.balabit.com/show_bug.cgi?id=135
> Balazs Scheidler<bazsi at balabit.hu>  changed:
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |frobert at balabit.hu
> --- Comment #1 from Balazs Scheidler<bazsi at balabit.hu>   2011-09-28 09:22:39 ---
> No point in allowing follow-freq() for pipe sources, so this is a documentation bug and should be removed from there.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20110928/c02a31b9/attachment.htm 

More information about the syslog-ng mailing list