The type should have the ability to only apply to the running system and bypass persisting to disk #14
Comments
trevor-vaughan
added a commit
to trevor-vaughan/augeasproviders_sysctl
that referenced
this issue
May 12, 2017
There are some sysctl values which, when set in /etc/sysctl.conf, may cause operational harm to a system. This patch provides the ability to only update the live value and make the disk persistence optional. Additionally: - Now use prefetching to get the sysctl values - Updated self.instances to obtain information about all sysctl values which provides a more accurate representation of the system when using `puppet resource` - Fail if the user attempts to set a value that is not valid on the system unless `silent` is set. - Updated all tests Closes voxpupuli#14
trevor-vaughan
added a commit
that referenced
this issue
May 31, 2017
There are some sysctl values which, when set in /etc/sysctl.conf, may cause operational harm to a system. This patch provides the ability to only update the live value and make the disk persistence optional. Additionally: - Now use prefetching to get the sysctl values - Updated self.instances to obtain information about all sysctl values which provides a more accurate representation of the system when using `puppet resource` - Fail if the user attempts to set a value that is not valid on the system unless `silent` is set. - Updated all tests - Refactored Travis CI Tests - Added OpenSUSE support Closes #14
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are a few sysctl values that require a reboot to be changed. In these cases, you can find that you've locked yourself out of your system because the value has persisted in
sysctl.conf.PR Forthcoming
The text was updated successfully, but these errors were encountered: