search for: processor0

...mask => 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 rubyversion => 1.8.5 se...

...hey may seem simple but all I did previously was get the source code, study it a bit, read the README and build from source. Now that I have a dual-core machine how does Xen know how to split resources for the instances? Does one give any parameters to the dom0 to boot with to tell it to "use processor0"? Any parameters for the domUs required? I''ve never bothered with X windows for the domUs before. If I wanted to would it be better to use vnc or SDL? How about qemu, would that be good for a VT-enabled machine? Or why not just go the "simple" way and use kvm+qemu? Thanks...

How come this doesnt work? I write this in a normal ruby script it works just fine. <% for cpu in (0..processorcount) %> I want to loop through the number of processor so a specific action can be taken to generate content for a file. I get an error on the master of: bad value for range at /etc/puppet" -Chris -- You received this message because you are subscribed to the Google

...Linux kernelrelease => 2.6.16.27-0.9-bigsmp macaddress => 00:10:18:17:BF:E6 00:10:17:17:BF:E6 00:10:18:18:BF:E6 00:10:18:16:BF:D5 00:10:18:17:BF:E6 00:14:5E:69:80:8D memoryfree => 5.26 GB memorysize => 5.94 GB operatingsystem => SuSE operatingsystemrelease => 2.6.16.27-0.9-bigsmp processor0 => Intel(R) Xeon(TM) CPU 2.80GHz processor1 => Intel(R) Xeon(TM) CPU 2.80GHz processor2 => Intel(R) Xeon(TM) CPU 2.80GHz processor3 => Intel(R) Xeon(TM) CPU 2.80GHz processor4 => Intel(R) Xeon(TM) CPU 2.80GHz processor5 => Intel(R) Xeon(TM) CPU 2.80GHz processor6 => Intel(R) Xe...

Hello, I have another quick one about puppet dashboard. We are using the Debian one for Squeeze (1.0.4) and as the database has significantly grown, if/when we click on a list of unresponsive nodes to check them, the web interface sits there doing nothing then the puppetmaster process starts timing out for all nodes compiling their catalogs. Has anyone got a workaround for this? Does it involve

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

I am trying to streamline the current distribution specific setup and creation of VE''s within OpenVZ with puppet. My first attempt has gone horribly wrong as you will see below. Here''s the script I wrote to replace the redhat specific setup that OpenVZ used: [jleggett@lxp6d15m3 scripts]$ cat redhat-add_ip.sh #!/bin/bash # # Debug - take out later set -x