On Aug 2, 2013, at 1:39, fuzzy186 wrote:
> Hi,
> Recently i've studying puppet by reading and doing the examples from this
> book: "Pro puppet".
> books.sysadmins.su/system/files/Pro.Puppet.pdf
...
> What should I do to make it work ?
The problem is you're using a pirated copy of that bo
> 3.2.3 is a bugfix release of the Puppet 3.2 series. It fixes some
> Windows bugs introduced in 3.2.0, as well as a few performance
> problems and miscellaneous bugs.
>
> ===
> ## Puppet 3.2.3 Downloads ##
> ===
>
> Source: https://downloads.puppetlabs.com
> As far as the large time differences, there are multiple references "out
> there" to a
> line at the top of ntp.conf as follows:
>
> tinker panic 0
>
> This tells the system to accept any offset that is handed to it.
By "large time differences" I meant between different servers on the network
> http://www.nsa.gov/ia/_files/os/redhat/NSA_RHEL_5_GUIDE_v4.2.pdf
>
> In general, they recommend running a daemon only when absolutely necessary.
Thanks for the reference! The security risk of ntpd listening by default is a
good reason for wanting to run it out of cron.
>> In general, that's
What's the use case for running NTP from cron? In general, that's considered
bad practice, and unnecessary because of ntpd's maturity. A few years ago we
were bitten by NTP running out of cron on RedHat Enterprise Linux 6.0 systems
because of the "tickless kernel."
On Jul 10, 2013, at 15:52,
