Forge Home


Cross-distributions sysctl handling


12,664 latest version

2.2 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.1.1 (latest)
  • 0.1.0
released Apr 7th 2013

Start using this module

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

Add this module to your Puppetfile:

mod 'eliasp-sysctl', '0.1.1'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

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

Manually install this module globally with Puppet module tool:

puppet module install eliasp-sysctl --version 0.1.1

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.



eliasp/sysctl — version 0.1.1 Apr 7th 2013

Sysctl variables handling for Puppet

This module is a fork of "Flameeyes/sysctl" and should only be used as long as the pull-requests (e.g. for Ubuntu support) haven't been applied yet.

The goal of this module is: to be obsolete as soon as possible :)


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.