Summary: | config file '/etc/sysctl.conf' is used after parsing user settings in '/etc/sysctl.d/*.conf' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kai Peter <kp> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | tsmksubc |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://blog.dyndn.es/doku.php/blog/2015/02/20_config_file_sysctl.conf_overwrites_sysctl.d | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Kai Peter
2017-10-28 09:07:05 UTC
The settings are applied in the order documented in the sysctl man page. /etc/sysctl.conf is under the sysadmin's control, so I don't see the problem here. My intention is to prevent that (changes in) /etc/sysctl.conf will be overwritten accidently by an etc-update. Let me take the freedom to make two suggestions: 1. Add an 'include' statement at the bottom of the file (e.g. like in /etc/rsyslog.conf) 2. remove the option 'net.ipv4.ip_forward = 0' from the default config file (comment out). Maybe put it in a file in sysctl.d, outside of CONFIG_PROTECT. |