On Tue, Oct 16, 2012 at 3:00 PM, Amos Jeffries <squid3@xxxxxxxxxxxxx> wrote: > On 17.10.2012 10:48, George Herbert wrote: >> >> I still find this behavior slightly bizarre, that the ulimit in the >> build environment can affect the prod envt. And it keeps biting other >> people... > > > It's not ulimit in the build environment particularly. Although the build > environment might need ulimit permissions to perform the setrlimit() tests. > > It is a basic default of N=1024 > ... altered by ./configure --with-filedescriptors=N > ... overridden on production by squid.conf max_filedescriptors (If, and > only if, setrlimit() RLIMIT_NOFILE is able to be built+used). > > Amos Right; it's the build environment setrlimit() test I think that causes the problem. I'd have configure'ed --with-filedescriptors=N (64k, say) and forget the ulimit in the build script wrapper and still get 1024, or whatever the current build hard limit was. I never bothered to look and see the details of what it was doing, but is there any situation where the build environment setrlimit test is actually helping? All the prod boxes had 16k, 32k, 64k hard limits; the build box often defaulted to a lower value. Having my own minimal script around make to ulimit unlimited first then configure and make worked, but.... -- -george william herbert george.herbert@xxxxxxxxx
