Forge Home


Cross-distributions sysctl handling


9,683 latest version


Version information

  • 0.2.0 (latest)
  • 0.1.0
  • 0.0.2
  • 0.0.1
released Apr 10th 2013

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'Flameeyes-sysctl', '0.2.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add Flameeyes-sysctl
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install Flameeyes-sysctl --version 0.2.0

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



Flameeyes/sysctl — version 0.2.0 Apr 10th 2013

Sysctl variables handling for Puppet


This module provides cross-distribution support for handling sysctl variables. It doesn't only set the variables in the appropriate config file, but also makes sure that they're applied at runtime.

Usage example

Set the sysctl variable net.ipv4.conf.all.accept_redirects to 0:

include sysctl
sysctl::value { "net.ipv4.conf.all.accept_redirects": content => "0" }

If you want to manage your sysctl settings exclusively through Puppet, you need to declare the class instead of using the include shortcut to set the exclusive class parameter:

class {"sysctl": exclusive => true }
sysctl::value { "net.ipv4.conf.all.accept_redirects": content => "0" }

This will unset all custom sysctl variables set by the user/distribution first and only those defined through Puppet will remain to be actually applied.