Change kernel runtime parameters persistent and non persistent
This article explains how to adjust Linux kernel runtime parameters, including non-persistent and persistent changes for system management.
In this article, we explain how to adjust Linux kernel runtime parameters, covering both non-persistent and persistent changes. Kernel runtime parameters control how the Linux kernel manages core functions such as memory allocation, network traffic, and file system operations. Typically, these parameters follow a naming convention where networking parameters start with “net”, memory settings with “vm”, and file system configurations with “fs”.
To view all active kernel runtime parameters, use the sysctl command with the -a flag. Note that not all parameters are accessible to a normal user; some lines might display “permission denied”. Using sudo will grant root privileges to read all parameters.Below are example outputs demonstrating the difference:
Copy
Ask AI
$ sysctl -afs.pipe-user-pages-hard = 0fs.pipe-user-pages-soft = 16384sysctl: permission denied on key 'fs.protected_fifos'sysctl: permission denied on key 'fs.protected_hardlinks'sysctl: permission denied on key 'fs.protected_regular'
For example, the parameter net.ipv6.conf.default.disable_ipv6 controls the status of IPv6 within the network category. A value of 0 (false) means IPv6 is enabled, while 1 (true) disables IPv6. To change this parameter non-persistently—meaning the change lasts only until the next system reboot—use the command below. The -w flag is used to write a new value, and be sure not to include spaces before or after the equals sign.
Non-persistent changes are effective immediately but will revert to their default settings after a reboot.
To verify a parameter’s current value, execute sysctl followed by the exact parameter name. If you receive a “permission denied” message, prepend the command with sudo to run it as root.
Persistent changes require modifying configuration files in the /etc/sysctl.d/ directory. These files must have a .conf extension. Persistent settings ensure that your changes are maintained across reboots.For example, consider the memory-related parameter vm.swappiness, which determines how aggressively the kernel uses disk swap space as an extension of physical memory. The parameter can take a value between 0 and 100: a higher value causes the kernel to use swap sooner, while a lower value delays swapping.Begin by referencing the man page for the sysctl.d directory to confirm the file extension requirement:
Copy
Ask AI
$ man sysctl.dSYNOPSIS /etc/sysctl.d/*.conf
Next, check the current value of memory-related parameters, including vm.swappiness:
Suppose you want to change vm.swappiness from 30 to 29. Create a new configuration file in the /etc/sysctl.d directory. In our example, we use the filename swap-less.conf to indicate that the setting will result in less frequent swapping.
Copy
Ask AI
$ sudo vim /etc/sysctl.d/swap-less.conf
Within the file, add the following line:
Copy
Ask AI
vm.swappiness = 29
Save and exit the editor. Although the change will be applied at the next boot, the current running kernel will still use the old value (30). To enforce the new setting immediately, reload the configuration using:
Copy
Ask AI
$ sudo sysctl -p /etc/sysctl.d/swap-less.conf
The output should confirm the updated value:
Copy
Ask AI
vm.swappiness=29
Remember, non-persistent changes made with sysctl -w will be lost after reboot, while persistent changes require adding a configuration file in /etc/sysctl.d/ and can be activated immediately using sysctl -p.
