While running Puppet on Solaris clients we seem to be losing our existing
cron entries when using the cron resource provided from puppet. This does
not happen all the time but often enough that it's becoming a problem.
This happens more often on zones than it does on the global zone itself.
At some point we go from having the standard crontab file with both the
puppet owned entry and our other standard cron entries to just the puppet
owned entry (along with it's header info) and nothing else.
This is on Solaris 10 (mostly update 6 or higher) on SPARC systems with
Puppet 2.6.3 and the standard cron daemon installed by Solaris.
Below is the code that is being executed on the clients, the random number
thing hashes a random start time based partially on the hostname and works
properly per host.
Any help or info would be appreciated, thanks!
----PUPPET CODE FOR HOSTS---
class coresystems::cron {
# Unique time in the range of 0-59 per node name..
$minute = fqdn_rand(59)
if $minute > 29
{
$minute2 = $minute - 30
}
else
{
$minute2 = $minute + 30
}
cron { "manual-puppet":
command => "/usr/bin/puppet agent --onetime --no-daemonize --logdest
syslog > /dev/null 2>&1",
user => "root",
hour => "*",
minute => [$minute, $minute2],
ensure => present,
}
}
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@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.
