Thanks for identifying the problem Kent - I can confirm it here on our Sol 10 U9 puppet servers which require the puppet user with a crontab
Other servers without a user crontab requirement don't nuke root's crontab I have updated bug 5752 Regards John On 5 January 2011 03:07, Kent <dri...@gmail.com> wrote: > Just FYI to people looking at this thread I filled bug 5752 on > puppetlabs.com for this issue. > Hopefully it gets resolved soon or I can figure out a work around > because right now we have to stop using the cron provider for all > users. > > -Kent > > On Jan 3, 2:12 pm, Kent <dri...@gmail.com> wrote: > > Ok that seems to be the problem but it's apparently still not fixed in > 2.6.3 > > on Solaris. > > I did figure out more on this issue, it seems that if you are managing a > > cron entry for a user that does not yet exist puppet nukes all the > current > > entries for any cron jobs it's currently managing for existing users. > Once > > all users exist everything works as expected. > > > > Since the cronjob pre-fetch occurs before the user(s) get added it always > > happens the first time you run puppet on a new host and doesn't seem to > keep > > a backup of the original crontab. > > -- > 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<puppet-users%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- John Warburton Ph: 0417 299 600 Email: jwarbur...@gmail.com -- 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.
