Hi Ken,
we´ve had the same problem with a samba fileserver, which regularly
choked with a "too many open filehandles" message. We found out that
the value 8192 is nowadays the standard for /proc/sys/fs/file-max and
you can set it to much higher values. For example, the SuSE people say,
that for their Email-Server it should be set to 65536. There might also
be a value /proc/sys/fs/inode-max (may be only for certain file
systems), which according to SuSE might also be risen to 131072.
Maybe it helps.
mfg Frank Finner
On 07-Dec-01 Ken sat down, thought for a long time and then wrote:
> During busy hours, Postgres and Apache are reporting
> errors that there are too many open files, and sometimes
> Postgres will crash. I've searched all over for a way
> to increase this resource limit.
> I have tried:
>
> ulimit -n 8192
> (seems only to work for the current shell session)
>
> echo "8192" > /proc/sys/fs/file-max
> (did not seem to make a difference)
>
> adding this entry to /etc/security/limits.conf:
> postgres hard nofile 4096
> (did not seem to make a difference)
--
Frank Finner
And now there is no turning back at all.
(M. Moorcock, "Elric Of Melnibone")"
