Re: cvs commit: httpd-2.0/docs/error README
* [EMAIL PROTECTED] wrote: Changes with Apache 2.0.49 + *) Add Polish translation of error messages. PR 25101. + [Tomasz Kepczynski tomek jot23.org] + iirc these made it never into the change log. nd
Re: cvs commit: httpd-2.0/docs/error README
On 06.01.2004, at 11:40, André Malo wrote: * [EMAIL PROTECTED] wrote: Changes with Apache 2.0.49 + *) Add Polish translation of error messages. PR 25101. + [Tomasz Kepczynski tomek jot23.org] + iirc these made it never into the change log. The Swedish and the Polish ones did, e.g.: Revision 1.1347 - Thu Dec 18 15:29:41 2003 UTC (2 weeks, 4 days ago) by trawick http://cvs.apache.org/viewcvs.cgi/httpd-2.0/CHANGES?r1=1.1346r2=1.1347 However, I think from a user POV the change warrants an entry in CHANGES, hmm... Cheers, Erik nd
FD_SETSIZE comparison
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
Re: FD_SETSIZE comparison
On Tue, Jan 06, 2004 at 09:53:47AM -0500, 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?
You can use file descriptors up to OPEN_MAX.
However, you can only select() on fds FD_SETSIZE.
That is a limitation of select() because of the memory size
of the fd_set typedef (based on FD_SETSIZE).
It is not a limitation of poll(), or other mechanisms like
kqueue, sys_epoll, or /dev/poll.
Cheers,
Glenn
Re: FD_SETSIZE comparison
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).
If APR uses select() to implement send/recv/connect timeouts, some code
some where needs to check for FD_SETSIZE to prevent that select() logic
from blowing up (it could even overlay storage).
But APR doesn't use select() on most boxes since poll() is pretty
standard nowadays. The plan is to yank these checks from Apache 2.1-dev
(which uses APR 1.0) and change APR 1.0 to implement the check only on
the dwindling set of platforms where select() is used.
Question about container directive, like location
Hi , I am new to this group as well as Apache development in general. I am writing a module and want to have some container directives. I looked at the source code for the directive location, directory in core module. But I could not find the source code for handling the closing tag like /location. How are the closing tags handled in code? Am I missing something here, I really dont know how to code the container directives. take care... Pawan. -- Pawan Deshpande, Alpha Software, Inc Ph: 800-451-1018 Ex : 23 Email: [EMAIL PROTECTED]
