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
Hi! 👋 I want to persist a sysctl that does not exist on the running system.
This is because I want it to be enabled on next reboot before a kernel upgrade, so it gets enabled at boot before a subsequent Puppet run.
This would be something that, reading the docs, I thought would be doable using:
However, if the sysctl does not exist, it currently fails (as it checks for its presence from the list obtained by sysctl -a), and if the :silent=>true parameter is set, it just adds the comment, not the actual value.
Would this be a behavior that would make sense adding to the module?. I see there is some support implemented for non-existent sysctls already for absent but not for present.
The text was updated successfully, but these errors were encountered:
Hi! 👋 I want to persist a sysctl that does not exist on the running system.
This is because I want it to be enabled on next reboot before a kernel upgrade, so it gets enabled at boot before a subsequent Puppet run.
This would be something that, reading the docs, I thought would be doable using:
However, if the sysctl does not exist, it currently fails (as it checks for its presence from the list obtained by
sysctl -a
), and if the :silent=>true parameter is set, it just adds the comment, not the actual value.Would this be a behavior that would make sense adding to the module?. I see there is some support implemented for non-existent sysctls already for
absent
but not forpresent
.The text was updated successfully, but these errors were encountered: