Issue #2355 has been updated by Daniel Pittman.
Er, this code seems to have gone in a while back, but I am confused by two things: One, we set a version despite it being committed. Two, how the heck it actually achieves *anything*, since Ruby 1.8 uses pretend threads in the interpreter, so blocking one "thread" will block the whole process entirely. Which kind of defeats the purpose of the whole change and all, unless I am missing something? As a side note, this change had pretty much zero in-place documentation, so I have spent the last six months wondering on and off why on earth this was done in a separate thread and all. ---------------------------------------- Bug #2355: facts hanging on reading /proc filesystem https://projects.puppetlabs.com/issues/2355 Author: Bernhard Furtmueller Status: Closed Priority: Normal Assignee: Paul Nasrat Category: library Target version: 1.5.9 Keywords: Branch: Hi! This is more or less a duplicate of http://projects.reductivelabs.com/issues/2032 At least on /proc/xen/capabilities I got the same hang on an RHEL4.7 xenu host. I found 2 approaches in the sources to remedy the problem: * Reading threadsafe like in lib/facter/util/memory.rb * Reading via a subprocess /bin/cat like in lib/facter/util/uptime.rb Could someone give advice how I should go forward to create a acceptable patch. br, allesmueller -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
