➜ sudo sysctl -a|grep file

fs.file-max = 2037581
fs.file-nr = 2784   0   2037581

➜ ~ cat /proc/sys/fs/file-max

➜ ~ cat /proc/sys/fs/file-nr
2720    0   2037581


* hard nofile 2037581
* soft nofile 2037581
root hard nofile 2037581
root soft nofile 2037581


session required pam_limits.so


session required pam_limits.so

then reboot.

but ulimit -n got 1024 again.

only can ulimit -n 4096 as max value

or got error

 ulimit: value exceeds hard limit
  • Did you try setting a minimally changed limit instead? – Josip Rodin Jul 9 '16 at 22:32

If u set root hard nofile 65535 it will only change root users limit. If you want to change another users limit add that users username for example,

sharewind hard nofile 65535 Or add * for username which will change all users limit. But it is not recommended.

  • 1
    It doesn't work – sharewind May 8 '14 at 1:54
  • Did you change both soft and hard file limits. If not add the soft file limit too. I used hard limit only as an example – Manula Waidyanatha May 11 '14 at 9:17
  • I have the same experience as @ManulaWaidyanatha – Jeune Jan 27 '15 at 7:47

I found that if the service is launched under an upstart init script you must use the stanza limit to control this!

See: http://bryanmarty.com/2012/02/10/setting-nofile-limit-upstart/

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.