Forge Home


A SIMP puppet module for managing upstart


238 latest version

5.0 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

  • 6.3.0 (latest)
  • 6.2.0
  • 6.1.2
  • 6.1.1
  • 6.1.0
  • 6.0.5
  • 6.0.4
  • 6.0.3
  • 6.0.2
  • 6.0.1
  • 6.0.0
  • 4.1.3
  • 4.1.2
released Aug 1st 2023
This version is compatible with:
  • Puppet Enterprise 2023.2.x, 2023.1.x, 2023.0.x, 2021.7.x, 2021.6.x, 2021.5.x, 2021.4.x, 2021.3.x, 2021.2.x, 2021.1.x, 2021.0.x, 2019.8.x
  • Puppet >= 6.22.1 < 8.0.0
  • , , ,

Start using this module

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

Add this module to your Puppetfile:

mod 'simp-upstart', '6.3.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add simp-upstart
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install simp-upstart --version 6.3.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.

Tags: init, initd, simp


simp/upstart — version 6.3.0 Aug 1st 2023

License CII Best Practices Puppet Forge Puppet Forge Downloads Build Status


Table of Contents

  1. Module Description - What the module does and why it is useful
  2. Setup - The basics of getting started with upstart
  3. Usage - Configuration options and additional functionality
  4. Reference
  5. Limitations - OS compatibility, etc.
  6. Development - Guide for contributing to the module
  7. Acceptance Tests

Module Description

Upstart is an event-based replacement for the /sbin/init daemon which handles starting of tasks and services during boot, stopping them during shutdown and supervising them while the system is running.

This class allows for configuration of upstart init files. The main class will ensure that /etc/init has proper permissions and disable ctrl+alt+del restarts by default.

upstart::job allows you to manage upstart jobs in /etc/init.


Include SIMP/upstart in your modulepath.

What upstart affects

This module will manage the /etc/init directory, and any additional jobs created by upstart::job

Begging with upstart

To ensure the proper permissions on /etc/init and disable ctrl+alt+delete restart, just include the main class in your manifest.

include upstart


I want to re-enable ctrl+alt+delete restarts

  disable_ctrl_alt_del => false,

I want to run a script at restart on any run-level

upstart::job { 'myjob':
  main_process_type => 'script',
  main_process      => template('myprofile/script'),
  start_on          => 'runlevel [0123456]',
  description       => 'Used to run my process'

I have a simple command I want to run on runlevel 5

upstart::job { 'myjob':
  main_process_type => 'script',
  main_process      => '/bin/foo --opt -xyz foo bar',
  start_on          => 'runlevel [5]',
  description       => 'Used to foo xyz options on foo and bar',


Public Classes

  • upstart: Manages /etc/init and controls the ctrl+alt+delete job.

Defined Types


SIMP Puppet modules are generally intended to be used on a Red Hat Enterprise Linux-compatible distribution.


Please read our Contribution Guide.

If you find any issues, they can be submitted to our JIRA.

Acceptance tests

To run the system tests, you need Vagrant installed.

You can then run the following to execute the acceptance tests:

   bundle exec rake beaker:suites

Some environment variables may be useful:

  • BEAKER_debug: show the commands being run on the STU and their output.
  • BEAKER_destroy=no: prevent the machine destruction after the tests finish so you can inspect the state.
  • BEAKER_provision=no: prevent the machine from being recreated. This can save a lot of time while you're writing the tests.
  • BEAKER_use_fixtures_dir_for_modules=yes: cause all module dependencies to be loaded from the spec/fixtures/modules directory, based on the contents of .fixtures.yml. The contents of this directory are usually populated by bundle exec rake spec_prep. This can be used to run acceptance tests to run on isolated networks.