Forge Home

limits_conf

UNKNOWN

Brian Hardy

bhardy

7,605 downloads

7,605 latest version

1.9 quality score

Version information

  • 0.0.1 (latest)
released Sep 25th 2015

Start using this module

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

Add this declaration to your Puppetfile:

mod 'bhardy-limits_conf', '0.0.1'
Learn more about managing modules with a Puppetfile

Add this module to a Bolt project:

bolt module add bhardy-limits_conf
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install bhardy-limits_conf --version 0.0.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.

Download

Documentation

bhardy/limits_conf — version 0.0.1 Sep 25th 2015

This template is designed to work with Foreman such that the following Global Parameters can be specified inside a Host Group:

limits_conf_nofile_soft limits_conf_nofile_hard limits_conf_nproc_soft limits_conf_nproc_hard

The names are pretty much self explanatory. They define various settings in /etc/security/limits.conf.

If you wanted to set the soft nofile limit for user "tom" to 2048, you would use the following Global Parameter in Foreman:

limits_conf_nofile_soft tom 2048

If you needed to the the soft nofile limit for multiple users, say "tom", "eric", and "barry", you would do the following:

limits_conf_nofile_soft tom 2048, eric 8192, barry 4096

A puppet agent run would then give you an /etc/security/limits.conf file like this:

cat /etc/security/limits.conf

This file is managed by Puppet

DO NOT EDIT BY HAND

tom soft nofile 2048 eric soft nofile 8192 barry soft nofile 4096

You need to use the correct corresponding Global Paramater to set the various domains/types/values in /etc/security/limits.conf. For now, only these 4 have been created. As demand for others arises, others will be added.