linux - Settings in limits.conf can't affect process started by init.d script -


my host redhat, default fd limit 1024, , added following lines in /etc/security/limits.conf :

*       soft    nofile  8192 *       hard    nofile  65535 

after this, newly logged in shells have fd limit raised 8192 correctly, processes started init.d script doesn't have fd limit raised, i.e. still have fd limit 1024, after logged in , use service command restart them, fd limit raised 8192.

so how can make daemons started init.d script have fd limit set in limits.conf?

thanks.

the /etc/security/limits.conf configuration file pam authentication. sets limits logged in users not system processes:

from man limits.conf:

the pam_limits.so module applies ulimit limits, nice priority , number of simultaneous login sessions limit user login sessions. description of configuration file syntax applies /etc/security/limits.conf file , *.conf files in /etc/security/limits.d directory.


Comments

Popular posts from this blog

javascript - Jquery show_hide, what to add in order to make the page scroll to the bottom of the hidden field once button is clicked -

python - Django-cities exits with "killed" -

python - How to get a widget position inside it's layout in Kivy? -