Hendrik Visage wrote: > On Fri, Mar 08, 2002 at 07:02:08AM -0600, Joe Cooper wrote: > >>Actually, modern glibc and the Linux kernel imposes no hard FD_SETSIZE >>limits. They can be raised from the shell using ulimit. >> >>But you might be right about that being Edwards problem--Linux defaults >>to 1024. Try adding a line like this to your Oops startup script: >> >>ulimit -HSn 8192 >> >>BTW-FD is file descriptors, not sockets--related but not the same thing. >> Network sockets (user ports actually) are increased by modifying the >>values in /proc/sys/net/ipv4/ip_local_port_range. I use the following >>to set this on all of my Squid boxes: >> > > In Unix, "everything is a file", and sockets uses filedescriptors, > ie. using the same read/write/close on but an FD (which is but a number) > as the index into the FD structure array. > > Do you tell me now that they are TOTALLY different in Linux, or do you > say that you have to up BOTH the allowed number of FDs and the allowed number > of sockets that may be open?? > > Hendrik
No. they aren't totally unrelated (which is why I said "related but not the same thing" ;-). But for heavily loaded servers, the user ports also need to be increased, as I indicated, in addition to the max file descriptors. In most things, Linux==Unix, and this is no different. My intention was to point out that FD stands for file descriptors which doesn't necessarily mean sockets--though a socket does associate to an FD (as you say, everything is a file--but not everything that is a file is a socket, you can't use socket semantics on a disk file, for example). -- Joe Cooper <[EMAIL PROTECTED]> http://www.swelltech.com Web Caching Appliances and Support ===================================================================== If you would like to unsubscribe from this list send message to [EMAIL PROTECTED] with "unsubscribe oops-eng" in message body. Archive is accessible on http://lists.paco.net/oops-eng/
