Are you testing this via an ssh login?
If so, I also had a problem similar to this, and an ugly kludge that I used was to add the ulimit -n 16384 in the sshd initscript before the various functions() get defined.
As I said,... Kludgy, and hopefully someone here knows a cleaner way (that works). ;-)
On Thu, Feb 24, 2005 at 12:17:30AM -0500, Mike Obvious wrote:
I did it before:
- soft nofile 16384
- hard nofile 16384
in /etc/security/limits.conf, but it doesn't work at all - I still have #ulimit -n 1024 #ulimit -Hn 1024
Any other ideas?
Mike
On Wed, 23 Feb 2005 22:22:13 -0500, C. Linus Hicks lhicks@nc.rr.com wrote:
On Wed, 2005-02-23 at 21:50 -0500, Mike Obvious wrote:
Hi!
Question from the novice.
I have to permanently increase number of opened files ( ulimit -n 16384 and ulimit -Hn 16384) for some application. I did custom kernel based on
https://www.redhat.com/docs/manuals/enterprise/RHEL-3-Manual/sysadmin-guide/...
and application documentation ( written for RH 9), no error during all makes but I have panic during the boot. ( It's Dell SC1425, dual CPU, 2GB RAM, i686-based kernel).
Is there any other way to do it ?
Look in /etc/security/limits.conf
-- C. Linus Hicks <lhicks at nc dot rr dot com>
CentOS mailing list CentOS@caosity.org http://lists.caosity.org/mailman/listinfo/centos
CentOS mailing list CentOS@caosity.org http://lists.caosity.org/mailman/listinfo/centos