Hi, Probably the low limit on file descriptors came from /etc/security/limits.conf. But you can edit /etc/sysconfig/squid and add there the command ulimit -n 16384 So squid gets a higher number no matter what's in limits.conf []s, Fernando Lozano > There is an issue with that not related directly to squid. > You can try to add into the sysvinit script a strict declaration using > ulimit that will force a limit on the script at runtime. > > It can be caused due to malfunction or mis-configuration in RH and > that the FD limit at the time when squid starts up at boot is not yet > set. > > Regards, > Eliezer > > On 06/20/2014 04:05 PM, amaury@xxxxxx wrote: >> Hello >> we are testing squid-3.4.5-20140616-r13146 on >> - rh es 6 64 with >> kernel version 2.6.32-431.20.3.el6.x86_64 >> squid it's compiled with -- >> with-filedescriptors=16384 >> and we have found this strange behavior >> >> If >> I reboot the linux box we have this situation(wrong): >> >> squidclient mgr: >> info |grep file >> Sending HTTP request ... done. >> Maximum number >> of file descriptors: 1024 >> Largest file desc currently in >> use: 14 >> Number of file desc currently in use: 7 >> >> Available number of file descriptors: 1017 >> Reserved number of >> file descriptors: 100 >> Store Disk files >> open: 0 >> After this I restart the squid service and >> the situation(correct): >> >> squidclient mgr:info |grep file >> Sending HTTP >> request ... done. >> Maximum number of file descriptors: 16384 >> >> Largest file desc currently in use: 14 >> Number of >> file desc currently in use: 7 >> Available number of file >> descriptors: 16377 >> Reserved number of file descriptors: 100 >> >> Store Disk files open: 0 >> >> Regards, >> >> Maurizio >> >> >
