exec command
ulimit -n 65535
when i relogin ,
ulimit -a
show default values 1024

how can i let tomcat server use max file num=65535 ,when start with /tomcat_install_dir/bin/startup.sh,why ulimit -n 65535 no effect!

configure in /etc/sercurity/limits.conf or /etc/sysctl.conf ? or
/etc/profile? or any other configure file ?

thx for your hint.....

Hi,

Running ulimit -n XXX, lasts only for the current session.
Depending on distro you can set it in /etc/sercurity/limits.conf or /etc/sysctl.conf, but sometimes it's not guaranteed it'll work after reboot. I had a RHEL4 box and to eliminate the problem, I had the ulimit command run through /etc/rc.local.

Anyway, you can try the methods above, but if you want to set it only for tomcat, I'd suggest to put it in /tomcat_install_dir/bin/startup.sh, so it's set only for the user that runs tomcat and only for running tomcat.

Regards

Not sure too, if it applies equally to OP's situation here, but maybe have a look over here:
http://www.linuxquestions.org/questi...e-size-822491/

The OP there needed to define the core pattern before a `ulimit -c` command would work. You may need to do the same. If you do this, make sure that somewhere in your boot scripts, `sysctl -p` is executed to make the values take effect.

EDIT: I think I misread the OP - you *do* have it working, but it is not persistent, right? Sorry about that (if that's the case), ignore this! It probably doesn't apply.

thx,i test right now,I do believe I can make it...

Hi xiutuo,
U have this above File Descriptor (FD) problem with SQUID as Proxy server. I don't know the kernel version of linux and squid ur using with this. One thing u must be clear that linux/CentOS/RHEL or other version of linux kernel has File Descriptor limit (makes real-time file but needs to be restricted which might hang up ur server as well with memory consumption. It get removed automatically from memory after jobs are done.) and has default limit to 1024 which is really enough for other services like smtp,ftp,imap,named etc. We can configure FD with various methods.
Following link also works,
=================
http://www.linuxquestions.org/questi...le-size-822491
=================
but problem is that FD is even used on every kernel level error and every services running on system which we really don't wan't. Gr8, what we really want? Then, specific limit for specific service for user.

Here we go for the best in my practice.Ok
=============
Check for ur current Maximum File descriptor limit in current session:
-------------
# ulimit -n
-------------
Squid only starts with a maximum of 1024 FD's
=============
#vi /etc/security/limits.conf
add the following lines ( if u have squid user u can even replace * with the squid user otherwise just leave it.)
#<domain> <type> <item> <value>
* soft nofile 65536
* hard nofile 65536
------Save N Quit--------------

#ulimit -HSn 65536 --->sets File descriptor limit for current session
# ulimit -n
---------------------
# vi /etc/sysctl.conf
-----------------
add the line at the end of the file and save it

fs.file-max = 65536
-----------------
# sysctl -a


================
then add the following line inside
#vi /etc/pam.d/login
#%PAM-1.0
auth [user_unknown=ignore success=ok ignore=ignore default=bad] pam_securetty.so
auth include system-auth
account required pam_nologin.so

session required pam_limits.so ---> add this line

======Save N Quit==========
# reboot your computer
===========================
#ulimit -n ====> to check after reboot and should return 65536
set ulimit for current session if not set to 65536
===============
Boss it works enjoy.
U can get this on
http://www.ispexperts.com.np/?p=535

os:centos5.4
kernel:2.6.18-194.el5

tomcat log show some msg like this:

too many open files


any way,"abhandari" 's work fine...

but kernel.core_pattern=core.%e.%p only for 'ulimit -c'

thx

======
[SOLVED]
This is just warning msg since we have by default 1024 FD set by squid but we set it soft/hard FD limit to 65536 which gets checked and display the message on log. Don't worry abt this, its fine to have warning then silent problem.
This might even happens if you have default installation with LVM file system. Just ignore it nothing happens with that warning. Sometimes we have to ignore little things to solve big problems. U got the point.

change your /etc/security/limits.conf file

add the line:

username soft nofile 65536
username hard nofile 65536

you have to set both hard and soft limits for it to work. reboot.
ulimit -a to check

Just wanted to add that finding this thread has resolved my Hyperion install problem, which was that I could change ulimit -n to 4096 in root, but it wouldn't allow it in the install user (oracle):
[bash: ulimit: open files: cannot modify limit: Operation not permitted].
Adding these lines in /etc/security/limits.conf did exactly what I wanted (I think!):
* soft nofile 4096
* hard nofile 4096
Big thank you for this forum!