Displaying 3 results from an estimated 3 matches for "physicalprocessorcount".
2009 Dec 09
3
facter 1.5.7 all lsb* items missing
...MB
memorysize => 1.98 GB
netmask => 255.255.255.240
netmask_eth0 => 255.255.255.240
network_eth0 => 1xxxxx
operatingsystem => RedHat
operatingsystemrelease => 5.4
path =>
/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin
physicalprocessorcount => 0
processor0 => Intel(R) Xeon(R) CPU E7450 @ 2.40GHz
processor1 => Intel(R) Xeon(R) CPU E7450 @ 2.40GHz
processorcount => 2
productname => VMware Virtual Platform
ps => ps -ef
puppetversion => 0.24.8
rubysitedir => /usr/lib/ruby/site_ruby/1.8
rubyver...
2011 Oct 10
0
Announce: Facter 1.6.2. available
...core id of a specific core relative to
the cpu. This could cause misreporting of processor count. The regex to
count cores was restricted to prevent this. Additional x86_64 tests were
added to verify this behavior.
##Fix (7996) Add solaris processor facts
Adds processorcount and physicalprocessorcount facts for solaris.
Added minor whitespace change for physicalprocessorcount spec that
ccompanied adding a solaris section to the spec.
Thanks to Merritt Krakowitzer for his contributions to this patch.
##Fix (9295) Initial detection of Hyper-V hypervisor
pulled out from video c...
2013 Apr 18
4
fact_stomp_server
Does anyone have any insight into this error message?
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
The fact named fact_stomp_server does not appear to be a valid hostname.
The value of '''' does not match ''^[a-zA-Z0-9.-]+$''. A common cause of this
problem is running puppet agent as a normal user instead of root, or the
fact is