| Age | Commit message (Collapse) | Author |
|---|
|
pulling 2 bytes from /dev/urandom, giving them to od which turns them into unsigned decimals, and then we bitshift the output, either by 5 or 6 depending on if we are replacing $RANDOM/1000*60 (right sift by 5 is the same as dividing by 2^N, or /32) or $RANDOM/2000*60 (range of [0,983])
Thanks to dkg for working through this with me, not only did he come up with it faster than a human brain should be able to function, he had the patience to explain all the individual pieces that I did not understand to me.
|
|
(^err:|^alert:|^emerg:|^crit:) in the output from the puppet run doesn't leave us with a '1' return code from grep.
On Debian Squeeze systems, this problem would result in cron reporting that the cron command failed with an exit status 1:
/USR/SBIN/CRON[24107]: (CRON) error (grandchild #24108 failed with exit status 1)
This was because grep returns a '1' if it fails to find a match. We don't want the failure to find failure messages to produce a failure, so this checks the return code of the grep and fixes it to be '0' if there were no such failure log messages.
This is a bit ugly, if you ask me. We are already, unfortunately, swallowing the puppetd return code with the grep. It seems like these sorts of log messages should be retrieved via reports, logcheck, or something other than this grep of the output of the cronjob.
|
|
done to set a flag so that squeeze has the service stopped, but lenny does not
|
|
$puppet_ensure_version to a backported version and your pinning was setup so
that you dont pull any packages unless explicit (I believe this is the default),
then you will end up seeing things like this:
The following packages have unmet dependencies:
puppet: Depends: puppet-common (= 2.6.2-4~bpo50+1) but 2.6.2-1~bpo50+1 is to be installed
E: Broken packages
at /etc/puppet/modules/puppet/manifests/linux.pp:6
this commit adds the $puppet_ensure_version test in debian.pp to make sure that
the puppet-common package is also following this request
|
|
|
|
have been a mistake in a merge commit
This reverts commit bb8ede5cfa0bdbdcc0244a590e6453f16d815cb6.
|
|
distinguish between different linux distros
|
|
|
|
using the filename puppetd.cron
|
|
/etc/cron.d/puppetd.cron file resource and move the override from manifests/debian.pp.
/etc/cron.d/puppetd.cron is not a valid cronjob according to the run-parts system that Debian uses to decide what is valid, as a result if you were to 'include puppet::cron' in your manifests on a debian/debian-derived system, then a cronjob would be created that would never be executed.
|
|
reports on a monthly basis (by default)
|
|
|
|
|
|
this is done by removing the hacky `if !defined` on the bc package by removing the package dependency altogether and replacing the places where it is used by shell built-in math functions.
this is a follow-up commit to 1455b1f9a55cdffc582fd93fa0bc5c016585760c
|
|
updating my previous commits with the fixes from LeLutin (closes: #2693)
|
|
/etc/default/puppetmaster file shipped with the debian package
|
|
add two new munin graphs for puppetmaster: one to graph the memory usage of the running puppetmasters; and one to graph the average compile time
|
|
Conflicts:
manifests/puppetmaster/checklastrun.pp
manifests/puppetmaster/checklastrun/disable.pp
|
|
passenger mode
|
|
|
|
|
|
this tidy is quite conservative, only cleaning files that are older than one
month. this seems long enough to be able to recover from a disaster, yet still
keep things from filling up the disk.
|
|
Conflicts:
manifests/cron/base.pp
manifests/debian.pp
|
|
|
|
installed.
It seems a little silly to have a hard-coded dependency on a module
that simply installs one package. I replaced it with a test to see if
the package has been defined elsewhere, and if not then it installs
it, allowing those who wish to continue to do this to have no
change.
I also provide a mechanism to specify the version, if desired.
Conflicts:
manifests/linux.pp
|
|
believe that this Closes #2353)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* don't use builtin splay, splay runs depending on the fqdn of a
host -> puppet isn't running until it really should
* fix various things for cron on openbsd
|
|
If we disable the cleanup of reports, actually remove the cron job.
|
|
|
|
We can now either disable reports cleanup or set the amount of days
reports should be kept.
By default we still cleanup reports after 30 days.
|
|
this is a bit hacky, but works.
|
|
A new variable $puppetmaster_mode have been introduced, which should
later be replaced by a class variable.
|
|
There is no need to notify the cron service after placing something
in /etc/cron.d. This means that we can also remove the dependency
to cron, as we don't refer to any managed resource of the cron
module anymore.
|
|
|
|
|
