[rsyslog] Is '--enable-unlimited-select' in 5.5.1 consideredusable?
Rainer Gerhards
rgerhards at hq.adiscon.com
Tue Dec 8 16:44:42 CET 2009
> -----Original Message-----
> From: rsyslog-bounces at lists.adiscon.com [mailto:rsyslog-
> bounces at lists.adiscon.com] On Behalf Of Ryan Lynch
> Sent: Tuesday, December 08, 2009 4:42 PM
> To: rsyslog-users
> Subject: Re: [rsyslog] Is '--enable-unlimited-select' in 5.5.1
> consideredusable?
>
> On Tue, Dec 8, 2009 at 10:36, Rainer Gerhards
> <rgerhards at hq.adiscon.com> wrote:
> >> this mechanism is intended to provide for higher number of open
> files
> >> and network connections in branches that do not support epoll() (it
> is
> >> present in v4-devel, can be backported to v3 with ease). It is
> >> obsoleted
> >> in the most recent v5 builds.
> >
> > good point: it is not really obsoleted for *all* sources
> (unfortunately). So
> > far, I have only moved imudp and the plain tcp netstream driver to
> epoll. The
> > others use your patch, if enabled. Also, on systems where epoll is
> not
> > available, the patch is included for plain tcp as well (I will keep
> the
> > select() code because it is more portable, but disable it if I find
> epoll).
>
> So, if I understand you, correctly, epoll() is not supported for RELP,
> GSSAPI, and/or TLS connections?
correct
> Do you plan to support epoll() for
> those types of connections, in the future?
Yes, but I want to gain some experience with the current implementation
first. I needed to make quite some changes to the driver layer and would like
to see that used in practice first. That, btw, was a primary reason why I
selected plain tcp as the initial target -it is the most often used transport
of all these.
Rainer
>
> -Ryan
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog
> http://www.rsyslog.com
More information about the rsyslog
mailing list