change setting but return to original

sub320 · 01-22-2016, 11:12 PM

deleted

Combinare · 01-23-2016, 12:40 AM

The ulimit command only sets the limit for the duration of that login session. To make the change permanent, you will need to update the configuration file that controls default limits on your system. On most distributions, the file is /etc/security/limits.conf. You can run "man limits.conf" to get more information on the format of the file and how to configure permanent limit changes.

sub320 · 01-23-2016, 03:02 AM

deleted

sub320 · 01-24-2016, 01:32 AM

deleted

TB0ne · 01-24-2016, 05:19 PM

Quote:

Originally Posted by sub320

Thanks reply ,
I would like to confirm what I need to do is add the following two lines to /etc/security/limits.conf , is it right ? if yes , I have to restart the server after update it , what can I do if I don't want to restart server ?

Code:

*               hard    nofile          65535
*               soft    nofile          4096

...and, less than 24 hours later:

Quote:

Originally Posted by sub320

May I know if I have to restart the server after add this line ?

Don't bump your own thread, unless you have new information to add...read the LQ Rules, Question Guidelines, and How to ask a smart question links.

Your question was answered very clearly in post #2...running that command sets it for THAT login session only. To set it system wide, you edit the file, and REBOOT. You were pointed to a man page for that file...did you read it?

And what you can do if you don't want to restart the server, is set the limit manually, and run whatever process you want from that session. That is your only option.

Combinare · 01-24-2016, 06:17 PM

The lines you have posted appear to be correct.

However, as far as I know, you do NOT need to reboot the server. You *will* need to log out and back in, however, for the settings to take effect.

If you are changing the limits for a process that starts on boot, you will need to restart the service.

sub320 · 01-24-2016, 08:44 PM

deleted

Combinare · 01-24-2016, 10:38 PM

Correct: the limits.conf file is read by PAM (pam_limits.so) when the user logs in. You do not need to reboot the server for the configuration change to take effect on an interactive user session - the user simply needs to log out and back in.

If you are trying to change the limits in effect for a daemon/service process (for example, if you are trying to increase the limits for the mysqld service processes), you will need to stop and restart the service after making the configuration change.

sub320 · 01-25-2016, 12:12 AM

deleted

Combinare · 01-25-2016, 08:19 AM

This is documented in the man page for limits.conf:

Quote:

All items support the values -1, unlimited or infinity indicating no limit, except for priority and nice.