Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent behavior for certain sysctl keys. #9

Open
obscured1975 opened this issue Jan 29, 2014 · 2 comments
Open

Inconsistent behavior for certain sysctl keys. #9

obscured1975 opened this issue Jan 29, 2014 · 2 comments

Comments

@obscured1975
Copy link

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,
}

@fiddyspence
Copy link
Owner

How do they behave inconsistently - what platform are you on, and what behaviour are you seeing?

@obscured1975
Copy link
Author

Hey Chris,

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.

John

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants