Forge Home


Manage Ubuntu rCS boot script behaviour using Puppet.


8,747 latest version

2.3 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 (deleted)
released Jun 20th 2015

Start using this module

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

Add this module to your Puppetfile:

mod 'ajlanghorn-rcs', '0.1.1'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add ajlanghorn-rcs
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install ajlanghorn-rcs --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.



ajlanghorn/rcs — version 0.1.1 Jun 20th 2015


A Puppet module for configuring /etc/default/rcS, a script to control the behaviour of boot-time scripts.



If you're using a Puppet package managment system such as r10k or librarian-puppet, you can include this module in your Puppetfile as such:

mod ajlanghorn/rcs


A number of options are available to be configured using this module, including:

  • UTC

Brief descriptions can be found in init.pp, or via your distro's help system.

To configure an option, you can either include this class inside a manifest and provide an option, or include it and provide options in Hiera. The latter is a more extensible way of using this module, so is recommended.


In your manifest, include the module:

include rcs

And then configure options in your Hiera backend, namespaced around rcs. For instance, to configure VERBOSE to yes, set:

rcs::verbose: 'yes'

Where an option takes a numerical value, the value can be passed without quoting it to transform it to a string. For instance, to set TMPTIME to 7, use:

rcs::tmptime: 7

Class inclusion

In your manifest, include the module as such:

class { 'rcs' :
 verbose => 'yes', 


Contributions are both appreciated and encouraged. To get started:

  1. Fork the module, then clone it (git clone
  2. Create a feature branch (git checkout -b feature-branch-name)
  3. Commit your changes to your branch (git commit -vm 'Add new feature')
  4. Push to your feature branch (git push -u origin HEAD)
  5. Create a new pull request

When adding a new feature, it would be very much appreciated if tests were bundled in to the same pull request. If you need help writing tests, please feel free to mention me in your pull request or raise an issue and we can look together.