You can get the hang without using listen. Any time ruby has two file handles open, the way it handles /proc changes -- so you can hit the bug in #10418 without enabling listen. I was able to do so quite easily. It's not a consistent workaround.
On Jan 5, 2012, at 10:55 PM, Ger Apeldoorn wrote: > In my 1st post, the versions of the problematic configurations are mentioned. > > During the PE upgrade, I also created new configfiles without 'listen = > true'. This is what probably fixed it for me, 'listen' is specifically > mentioned in the bugreport. > > Ger. > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/puppet-users/-/Aczw695ilTIJ. > 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. -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness -- 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.
