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

Dependency on pinned, old version of sysctl #192

Closed
bablakely opened this issue Feb 8, 2018 · 1 comment · Fixed by #195
Closed

Dependency on pinned, old version of sysctl #192

bablakely opened this issue Feb 8, 2018 · 1 comment · Fixed by #195
Assignees

Comments

@bablakely
Copy link
Contributor

Currently this cookbook depends on sysctl 0.9.0, due to this issue: Sous-Chefs-Boneyard/sysctl#100.

If I understand the issue correctly:

The sysctl cookbook now creates individual sysctl.d files for various items, instead of merging them all into /etc/sysctl.conf. @artem-sidorenko 's suggested workaround, since the upstream PR is not getting any attention, is to remove any files or changes made by os-hardening to sysctl's configuration that were in the old scheme, and then allow it to update with the new scheme. However, the challenge is that sysctl.conf (which may exist otherwise and have unrelated items in it) cannot simply be removed, and thus any os-hardening-created modifications must be stripped out.

@bablakely
Copy link
Contributor Author

Upon further inspection, sysctl.conf is uninvolved, and all that was needed is to remove the file in node['sysctl']['conf_file'] since this attribute is no longer used by sysctl and the necessary configuration should already be re-created in the new location. Sanity check on that would be appreciated, but I believe it's that simple.

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

Successfully merging a pull request may close this issue.

3 participants