httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <wr...@rowe-clan.net>
Subject Re: FD_SETSIZE comparison
Date Tue, 13 Jan 2004 22:06:35 GMT
Perhaps this is none of Apache's business, but should be a very specific
result from the various apr_poll setup functions that invoke select()?

Bill

At 08:53 AM 1/6/2004, Brian Akins wrote:
>Call me stupid, put why in various places does Apache do things like this:
>if (csd >= FD_SETSIZE) {
>        ap_log_error(APLOG_MARK, APLOG_WARNING, 0, NULL,
>                     "new file descriptor %d is too large; you probably need "
>                     "to rebuild Apache with a larger FD_SETSIZE "
>                     "(currently %d)",
>                     csd, FD_SETSIZE);
>        apr_socket_close(sock);
>        return;
>    }
>
>On linux, at least, FD_SETSIZE is fairly low (1024), yet the actually max file descriptors
can be much, much higher (we have thousands per process with squid).
>
>
>Is this just not true elsewhere?  Can someone explain?
>
>-- 
>Brian Akins
>Senior Systems Engineer
>CNN Internet Technologies



Mime
View raw message