Before compiling squid, try changing the value of the __FD_SETSIZE in the /usr/include/bits/typesizes.h file as #define __FD_SETSIZE 8192 and then in the shell prompt ulimit -HSn 8192 and try echo 1024 32768 > /proc/sys/net/ipv4/ip_local_port_range then compile and install squid This should help you out with the file descriptor problem. Thanks, -Squid Runner Support On 2/23/06, Gix, Lilian (CI/OSR) * <Lilian.Gix@xxxxxxxxxxxxxxx> wrote: > Hello, > > > I always had some problems with Filedescriptor. > One day, U changed my Linux version to a Debian (I don't now if it's the > reason) and I update Squid. And since, I got a configuration file under: > /etc/default/squid > On this file, there is: > > # > # /etc/default/squid Configuration settings for the Squid > proxy server. > # > > # Max. number of filedescriptors to use. You can increase this > on a busy > # cache to a maximum of (currently) 4096 filedescriptors. > Default is 1024. > SQUID_MAXFD=4096 > > I don't know if this can help.... > > Gix Lilian > > > -----Original Message----- > From: Mark Elsen [mailto:mark.elsen@xxxxxxxxx] > Sent: Donnerstag, 23. Februar 2006 09:26 > To: Gregori Parker > Cc: squid-users@xxxxxxxxxxxxxxx > Subject: Re: FILE DESCRIPTORS > > > Sorry to be pounding the list lately, but I'm about to lose it with > > these file descriptors... > > > > I've done everything I have read about to increase file descriptors on > > my caching box, and now I just rebuilt a fresh clean squid. Before I > > ran configure, I did ulimit -HSn 8192, and I noticed that while > > configuring it said "Checking File Descriptors... 8192". I even > > double-checked autoconf.h and saw #define SQUID_MAXFD 8192. I thought > > everything was good, even ran a "ulimit -n" right before starting > squid > > and saw 8192! So I start her up, and in cache.log I see... > > > > 2006/02/22 19:05:08| Starting Squid Cache version 2.5.STABLE12 for > > x86_64-unknown-linux-gnu... > > 2006/02/22 19:05:08| Process ID 3657 > > 2006/02/22 19:05:08| With 1024 file descriptors available > > > > To make sure that this is not bogus w.r.t. the real available amount of > FD's : do you still get warnings in cache.log about FD-shortage when > reaching the 1024 (bogus-reported ?) limit. > > The reason I ask is, that I have been playing with the FAQ guidelines > too, > ultimately getting the same result (stuck?) as you did. > > M. > >
