On Tue, Jul 10, 2012 at 10:41 PM, Kmbu <yum...@hotmail.com> wrote: > Hi, > > Thanks for supporting. We've been running this environment of around 1000 > servers for at least 5 years and have never seen a crontab suddenly > disappear before. We've only had Puppet in place for a month or so. > > Regards,
Unfortunately, I've seen the same issue occur. I posted to the list about it a while back and had some others say they'd seen similiar. I've only seen this happen on Solaris so far but seeing it happen once was enough for me to pull the plug on using puppet to manage users crontab files on all our boxes, solaris and rhel. On RHEL I've worked around the issue by dropping crontab files in /etc/cron.d/ but on solaris I have no viable work-around at the moment. Others have mentioned that I should just manage the whole crontab file in puppet... but this isn't really an option for me at the moment. On solaris at least the issue seemed to be related to facter hanging (due to the picld daemon hanging). Not that this really solves your problem but if your on a *nix that supports it you might want to look at converting to dropping cron files in /etc/cron.d/ or similar. -- Romeo -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
