Re: Solaris and running out of file descriptors

Peter K schrieb:

> On Fri, 28 Jan 2000, Jens-S. Voeckler wrote:
> > What did configure have to say about the FD limits?
> Same warning about less than 512 FDs

So, it does not see the new hard limit for some reason.
Are you sure that not some thingies in /etc/profile or
.profile or .yourshellrc are setting different limits? No
misspellings in /etc/system, and no superflous whitespaces
alongside the equals sign (just one between set and rlim)?

> > 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 ...)

Not mine, my shell reports the number of open(able) FDs with parameter -n.
But then, I am notoriously using a bash even as root. Try a ksh.

> 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

Come to think of, what version of Solaris are we talking about?

> Anyway, /var/log/* indicate that the system never complained about <
> 1024 FDs before the insertion of the directive in /etc/system.

Because 1024 FDs should be the default hard-limit.
Do you have a "special" configuration, like having a meta-device (md)
root partition, but booting from a different partition, or one of the
special boot prom parameters which selects a different /etc/system?

Ciao, Jens
Received on Fri Jan 28 2000 - 14:56:49 MST