Forge Home

limits

manages /etc/security/limits.conf

11,642 downloads

7,390 latest version

4.8 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

  • 3.1.9 (latest)
  • 3.1.8
  • 0.1.8
  • 0.1.7
  • 0.1.6
  • 0.1.5
  • 0.1.4
  • 0.1.3
  • 0.1.2
  • 0.1.1
  • 0.1.0
released Jun 22nd 2016
This version is compatible with:
  • Puppet Enterprise >= 3.0.0
  • Puppet >= 3.0.0
  • , , , , , , ,

Start using this module

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

Add this module to your Puppetfile:

mod 'eyp-limits', '3.1.9'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add eyp-limits
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install eyp-limits --version 3.1.9

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

eyp/limits — version 3.1.9 Jun 22nd 2016

limits

PRs Welcome

NTTCom-MS/eyp-limits: Build Status

Table of Contents

  1. Overview
  2. Module Description
  3. Setup
  4. Usage
  5. Limitations

Overview

Control your /etc/security/limits.conf via puppet

Module Description

This module fully manages /etc/security/limits.conf so this will overwrite your existing file

Setup

What limits affects

  • /etc/security/limits.conf WILL BE overwritten

Setup Requirements

pluginsync must be enabled

Beginning with limits

Simple example

class { "limits": }

limits::limit { "nofile *":
  domain => "*",
  item => 'nofile',
  value => '123456',
}

limits::limit { "nproc *":
  domain => "*",
  item => 'nproc',
  value => '123456',
}

This will generate the following entries:

* - nofile 123456
* - nproc 123456

Usage

class limits

Without parameters, it just setups the limits.conf file with a header

define limits::limit

  • domain: user, %group or * (means all)
  • type: soft, hard or - (means both)
  • item: can be one of the following:
  • core - limits the core file size (KB)
  • data - max data size (KB)
  • fsize - maximum filesize (KB)
  • memlock - max locked-in-memory address space (KB)
  • nofile - max number of open files
  • rss - max resident set size (KB)
  • stack - max stack size (KB)
  • cpu - max CPU time (MIN)
  • nproc - max number of processes
  • as - address space limit (KB)
  • maxlogins - max number of logins for this user
  • maxsyslogins - max number of logins on the system
  • priority - the priority to run user process with
  • locks - max number of file locks the user can hold
  • sigpending - max number of pending signals
  • msgqueue - max memory used by POSIX message queues (bytes)
  • nice - max nice priority allowed to raise to values: [-20, 19]
  • rtprio - max realtime priority
  • chroot - change root to directory (Debian-specific)
  • value: value for item

Limitations

Tested on

  • Ubuntu 14.04
  • CentOS 5
  • CentOS 6
  • CentOS 7
  • SLES 11 SP3