m0nk3yza
asked on
Disable one update action of puppet agent -test
Hi Guys,
One of our customers are having an issue with the contents of /etc/cron.d/* not being processed correctly and have decided to use crontab instead (until the issue is resolved).
However, our PuppetMaster is set to enforce the usage of /etc/cron.d/* and delete any crons under /var/spool/cron/ (once puppet agent -t is run).
Is there a way (perhaps in site.pp) to prevent the deletion of /var/spool/cron/ ?
Thank you.
One of our customers are having an issue with the contents of /etc/cron.d/* not being processed correctly and have decided to use crontab instead (until the issue is resolved).
However, our PuppetMaster is set to enforce the usage of /etc/cron.d/* and delete any crons under /var/spool/cron/ (once puppet agent -t is run).
Is there a way (perhaps in site.pp) to prevent the deletion of /var/spool/cron/ ?
Thank you.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The issue remains unresolved.
Can you find somethiung in the Puppet "jobs" which might cause this cron.d reiterated clean-up?
ASKER
There is some corruption in the cron files under /etc/cron.d/
Our developers are trying to resolve this issue.
The customer has placed all their crons in the root crontab, and this seems to work, but each time they run puppet agent -t, it reverts these changes.
So I wanted a temporary work-around to disable just the enforcement of this one directory (/etc/cron.d).