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 > > echo 1024 32768 > /proc/sys/net/ipv4/ip_local_port_range > > Actually, I'll just post the whole limits raising part of my Squid init > file--it might be useful: > > # More file descriptors > ulimit -HSn 8192 > echo 8192 > /proc/sys/fs/file-max > > # More user ports for squid to use > echo 1024 32768 > /proc/sys/net/ipv4/ip_local_port_range > > echo 3072 > /proc/sys/net/ipv4/tcp_max_syn_backlog > > Let us know what you find out, Edward. > > Actually, now that I'm thinking of it, Oops might look very different to > the OS than Squid. Because the file descriptor limit is a per-process > limit, it may not hit Oops at all--because each thread is a 'Light > Weight Process'...I don't know if a thread is limited by it's parent > file descriptor limits. Most probably, as threads share the same address space as the "parent", thus the limit would be for that process. > > Vladimir Ivaschenko wrote: > > Probably it is a problem not with threads, but with sockets. You need to > > increase number of maximum sockets (__FD_SETSIZE) in glibc (types.h) and > > in kernel. > > > > Edward Millington wrote: > > > > > >>HI there! Does anyone knows how I can increase the number of thread > >>linux can handle for oops? I find that linux could handle up to 950+ > >>thread fairly well. At around 980 threads, oops stops working. Is > >>there a way to solve this? With this big problem, I am thing of going > >>back to squid. > >>Thank you very much. > >> > >>Best regards, > >> > >>Edward Millington. BSc, Network+ > >>Systems Administrator > >>Cariaccess Communications Ltd. > >>Palm Plaza > >>Wildey > >>St. Michael > >>Barbados > >>1-246-430-7435 > >>Fax : 1-246-431-0170 > >>[EMAIL PROTECTED] > >>www.cariaccess.com > >> > > > > -- > > Best Regards > > Vladimir Ivaschenko > > Certified Linux Engineer (RHCE) > > > > > > > > ===================================================================== > > 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/ > > > > > > > > > > -- > 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/ ===================================================================== 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/
