Because I like to live dangerously I upgraded to 2.6.5 and it seems like this has resolved the CPU problem completely for me.
On Tue, Feb 1, 2011 at 3:17 PM, Udo Waechter <udo.waech...@uni-osnabrueck.de > wrote: > > On 01.02.2011, at 18:14, Brice Figureau wrote: > > > On Tue, 2011-02-01 at 10:30 -0500, Ashley Penney wrote: > >> This is the crux of the situation for me too - Puppetlabs blame it on > >> a Ruby bug that hasn't been resolved with RHEL6 (in my situation) but > >> this wasn't an issue until .3 for me too. I feel that fact that many > >> of us have this problem since upgrading means it can be fixed within > >> Puppet, rather than Ruby, because it was fine before. > > > > Do you mean puppet 2.6.2 wasn't exhibiting this problem? > Yes for me. > --udo. > > -- > :: udo waechter - r...@zoide.net :: N 52º16'30.5" E 8º3'10.1" > :: genuine input for your ears: http://auriculabovinari.de > :: your eyes: http://ezag.zoide.net > :: your brain: http://zoide.net > > > > > -- > 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. > > -- 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.
