On Fri, 28 Jan 2000, Jens-S. Voeckler wrote:
> Peter K wrote:
>
> > > DO USE poll with Solaris - though it should be selected by configure. The
> > > Solaris select() only allows for 1024 FDs, regardless of any higher
> > > limits.
> >
> > Hmmm. Wonder why it didn't. Yet squid limits itself to 128.
>
> --enable-poll
:) Done. BTW, it appears one has to specify --enable-poll=yes
> But you did reboot, after changing /etc/system?
Several times (though for unrelated reasons)
> And you did compile the
> squid on the machine it is ultimataly running on, with the extended
> limits?
Yep.
> What did configure have to say about the FD limits?
Same warning about less than 512 FDs
> What does "ulimit -Hn"
> say for (a) the user who is running the compile job, (b) the user who
> is starting squid, (c) the uid squid is running with?
User is root in all instances. /usr/bin/ulimit -Hn outputs 128 (but
ulimit pertains to _file_ size on _writes_, not number of open FDs ...)
> > I'd like to know how the hard limit of 1024 set in /etc/system will be
> > honoured by squid.
>
> During startup, squid determines the hard limit using a getrlimit()
> call. It expands the softlimit to the hardlimit, if the hardlimit is
> larger, and it will complain, if there are less than 1024 FDs.
Hmmmm. Prior to setting rlim_fd_max to 1024 ./configure reported
checking Default FD_SETSIZE value
as 128. The code in configure indicates that this is merely acquired
from the #define in /usr/include/sys/select.h
Anyway, /var/log/* indicate that the system never complained about <
1024 FDs before the insertion of the directive in /etc/system.
After reconfiguring with --enable-poll=yes, squid still records
With 128 file descriptors available
Oh, well, will see Monday around 13h00 local.
Any other suggestions ?
Peter Kooiman | Voice : +27-12-547-2846
| Cell : +27-82-321-3339
Box 81214, DOORNPOORT, 0017, RSA | e-mail : pko@paradigm-sa.com
Received on Fri Jan 28 2000 - 09:41:29 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:50:45 MST