Issue #2242 has been updated by Daniel Pittman.
The information is technically correct, from someone who knows OpenVZ well. :) What I am not certain of is what, if any, information the LXC-based containers expose in this regard. I assume they don't bundle the various namespace segregations, so they don't expose a single "environment ID" like value, but would want confirmation from someone who knows that part of the Linux kernel code. ---------------------------------------- Bug #2242: Simplify OpenVZ detection, based on /proc/self/status https://projects.puppetlabs.com/issues/2242 Author: Christian Hofstaedtler Status: Accepted Priority: Normal Assignee: Category: Target version: 1.6.0 Keywords: Branch: Affected Facter version: virtual.rb currently does lot's of things to detect different virtualization environments. As some of them represent their state in /proc/self/status, it would be cool if this could be unified. Paul also wanted to create tests for virtual.rb, based on /proc/self/status. OpenVZ states in /proc/self/status: envID == 0 -> openvzhn envID present but > 0 -> openvzve -- 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.
