2.2. Setting Persistent Tuning Parameters
This book contains many examples on how to specify kernel tuning parameters. Unless stated otherwise, the instructions will cause the parameters to remain in effect until the system reboots or they are explicitly changed. This approach is effective for establishing the initial tuning configuration.
Once you have decided what tuning configuration works for your system, you can make them persistent across reboots. The method you choose depends on the type of parameter you are setting.
Procedure 2.1. Editing the /etc/sysctl.conf File
For any parameter that begins with
/proc/sys/, including it in the /etc/sysctl.conf file will make the parameter persistent.
- Open the
/etc/sysctl.conffile in your chosen text editor. - Remove the
/proc/sys/prefix from the command and replace the central/character with a.character.For example: the commandecho 0 > /proc/sys/kernel/hung_task_panicwill becomekernel.hung_task_panic. - Insert the new entry into the
/etc/sysctl.conffile with the required parameter.# Enable gettimeofday(2) kernel.hung_task_panic = 0
- Run
# sysctl -pto refresh with the new configuration.~]#
sysctl -p...[output truncated]... kernel.hung_task_panic = 0
Procedure 2.2. Editing the /etc/rc.d/rc.local File
Warning
The
/etc/rc.d/rc.local mechanism should not be used for production startup code. It is a holdover from the SysV Init days of startup scripts and is executed now by the systemd service. It should only be used for testing of startup code, since there is no way to control ordering or dependencies.
- Adjust the command as per the Procedure 2.1, “Editing the
/etc/sysctl.confFile” instructions. - Insert the new entry into the
/etc/rc.d/rc.localfile with the required parameter.
