Forge Home


Installs, configures, and manages the NTP service


1,454 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

  • 0.1.15 (latest)
released May 27th 2020
This version is compatible with:
  • Puppet Enterprise 2023.7.x, 2023.6.x, 2023.5.x, 2023.4.x, 2023.3.x, 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, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet >= 3.0.0
  • , , , , , ,
  • forcesync

Start using this module

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

Add this module to your Puppetfile:

mod 'eyp-ntp', '0.1.15'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

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

Manually install this module globally with Puppet module tool:

puppet module install eyp-ntp --version 0.1.15

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.



eyp/ntp — version 0.1.15 May 27th 2020


Table of Contents

  1. Overview
  2. Module Description
  3. Setup
  4. Usage
  5. Reference
  6. Limitations
  7. Development


Installs, configures, and manages the NTP service.

Module Description

The ntp module handles installing, configuring, and running NTP. For Ubuntu 18.04 by default uses systemd-timesync. To use NTPD instead, just set force_ntpd to true


What ntp affects

  • NTP config file: /etc/ntp.conf
  • ntp package
  • ntp service

Setup Requirements

This module requires pluginsync enabled

Beginning with ntp

This module setups NTP to use a given set of servers (it also has some default servers).

If this module is used on a VM, by default, it will set tinker panic to 0


basic usage:

    class { 'ntp':
    servers = [




  • driftfile: File to use to record the frequency offset of the local clock oscillator
  • tinker: Enables or disables system variables used by the clock discipline algorithm.
  • tinker_panic: Specifies the panic threshold in seconds. If set to zero, the panic sanity check is disabled and a clock offset of any value will be accepted.
  • servers:: List of servers to use
  • iburst: When the server is unreachable, send a burst of eight packets instead of the usual one (default: true)
  • management options:
    • manage_package: Package management (default: true)
    • package_ensure: Package status: (default: installed)
    • manage_service: Service management (default: true)
    • manage_docker_service: Service management on docker containers (default: true)
    • service_ensure: Service status: (default: running)
    • service_enable: Service enabled on startup: (default: true)


Tested on:

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


We are pushing to have acceptance testing in place, so any new feature should have some test to check both presence and absence of any feature


Nothing yet


  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request