Issue #11612 has been updated by Alex Harvey.

I have implemented a fix based on style changes implemented by Jeff McCune in 
#11609 and the 'ux' perl script referred to above.

On my Itanium test machine the output looks like this -

<pre>
$ facter |grep proc
processor0 => Intel(R) Itanium 2 9100  @ 1598 MHz
processor1 => Intel(R) Itanium 2 9100  @ 1598 MHz
processorcount => 2
</pre>

In the case of my Itanium test box, that's coming from machinfo -

<pre>
# machinfo |egrep 'processor model:|Clock speed'
   Clock speed = 1598 MHz
         processor model:             1   Intel(R) Itanium 2 9100 series
</pre>

I wonder if this is better or worse than simply reporting what's in the 
processor model field verbatim and not ever reporting the CPU speed?  I see CPU 
speed is being reported in Linux, but that's only because CPU speed is on the 
same line as CPU model in /proc/cpuinfo.
----------------------------------------
Bug #11612: add facter support for  ia 11.31 hpux processor discover and a bug 
fix for network interface
https://projects.puppetlabs.com/issues/11612#change-74656

Author: hongbo hu
Status: Code Insufficient
Priority: Normal
Assignee: Alex Harvey
Category: library
Target version: 1.6.x
Keywords: facter hpux 
Branch: https://github.com/puppetlabs/facter/pull/232
Affected Facter version: 


1. add cpu information support to facter support HPUX 11.31 IA64

2. when server has  mc-sg  the network card has standby lan card marked
with '*' ,when run faster ,it'll show ifconfig no such interface error

pull requre at github
https://github.com/puppetlabs/facter/pull/127
I'll add more feature for hp and aix 


-- 
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.

Reply via email to