Age | Commit message (Collapse) | Author |
|
This simplifies the hierarchy and fixes the problem that going from
puppet::cron to puppet under debian doesn't remove the cron file.
Signed-off-by: Gabriel Filion <lelutin@gmail.com>
|
|
|
|
|
|
puppet::cron.
The module should make sure that the cron file is not there if you aren't using
the cron method, otherwise the daemon and the cronjob could both run.
Used suggested change from jcharaoui in #3513
|
|
|
|
|
|
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.
|
|
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
|
|
|
|
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)
|
|
|
|
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.
|
|
Only code style and whitespace formatting issues. Everything should
no be in ligne.
|
|
|
|
|
|
of present
|
|
|
|
|
|
'present'
|
|
|
|
/usr/local/bin rather than /opt/bin
|
|
|
|
|