Thank you Paul, and thank you everyone else for your replies. Presumably fact values can be broken down into two categories:
a) those values which exist in Factor's code base somewhere b) those values which are obtained from elsewhere Those in a) can be deduced just by looking at the Factor codebase. Those in b) cannot, in general. Even those values those in a), most will be emitted depending on some criteria obtained from the environment. Not much point, otherwise. This means that although they can be listed as 'possible' it may not always be able to say when. Therefore, to really know what values are possible, and what systems they are associated with - and equally importantly, to spot anomalies - I imagine one would need to survey many different machines (as well as inspect the Facter code base). Maybe Puppet Labs is already collecting this information? If not, would seem a useful goal. PL's clients would be one source, but I'm wondering if there's also some way to gather the information from the community. To this end, perhaps contributions of fact information could be made easier if there were an (anonymising?) fact-reporting tool, perhaps incorporating ideas from Nan Liu's script. Users could then use it a part of a bug-report, or request for help, or just to contribute to the community database. (Thinking of a compelling incentive to contribute is difficult, but even so, the possibility to do it needs to exist first.) Unfortunately I don't have the resources to volunteer to create such a thing, but possibly the idea is worth adding to the comments of the ticket. Cheers, N -- 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.
