You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed this while working with a prospect. sysctl { "namevar": ensure => absent, permanent => yes, } seems to generally remove the entry for the sysctl key from the configuration file on the filesystem. Tested with two different keys and 'net.ipv4.ip_forward' appears to get removed from the file whereas 'net.bridge.bridge-nf-call-iptables' doesn't get removed. Was testing this on a CentOS 6.4 agent.
Some of the sysctl keys do not behave consistently. For example:
Removes net.ipv4.ip_forward entry from /etc/sysctl.conf
sysctl { "net.ipv4.ip_forward":
ensure => absent,
permanent => yes,
}
Different key such as net.bridge.bridge-nf-call-iptables doesn't do the same
sysctl { "net.bridge.bridge-nf-call-iptables":
ensure => absent,
permanent => yes,
}
The text was updated successfully, but these errors were encountered: