Displaying 5 results from an estimated 5 matches for "oinksocket".
2012 Mar 12
2
perl .spec / srpm
Hi
Can anyone here point me in the direction of a .spec or SRPM for Perl 5.12.4 for
CentOS6?  Or even any newer version would do.
Whilst I'm asking, ditto a Perl-enabled version of OpenLDAP (latest stable
release)?  IIRC, the version in the base repo has the Perl extensions disabled.
Thanks,
Nick
2010 Nov 18
1
what scheduling algorithm does KVM use?
This may not be the best place to ask, but I was prompted by a question about
guest cores on KVM.
We currently use VMWare Server (v1.0) on CentOS5.
It supports up to two virtual CPUs, but not very well, as I understand it.
VMWare Server 2.0 might do better at supporting the same maximum of 2 CPUs, but
if my research is correct, they both use what is called "strict co-scheduling".
2010 Aug 10
1
problems with yum_priorities on CentOS5/RHEL5
Hello,
Many of you will have read this page, with its (somewhat ambiguous) endorsement
of yum_priorities:
 http://wiki.centos.org/AdditionalResources/Repositories/RPMForge
As I gather has been stated before on the centos list [1], that quote stops
short of outlining what exactly is wrong with yum_priorities (YP) and why it's
the best solution.  In fact it goes on to say:
> as of yet, no
2011 Aug 18
0
profiling KVM i/o on CentOS 5
Hi,
I am wondering what tools are available to troubleshoot KVM I/O problems on
CentOS 5, given that the kernel is 2.6.18 with some backports to support
virtualisation?
 kvm_stat / kvmtrace - These seem to be available in the kvm-tools package.
 ftrace related things seem not to be available.
 OProfile is available, can it be used?
 Also, SystemTap is available, can it be used?
Anything
2012 Feb 01
2
ip route and nexthop: the "CentOS" way
Hi,
I'm wanting to configure a CentOS 6 server to have a fall-back default route via
a second network interface.
Given:
 - eth0 with 192.168.0.10 on subnet 192.168.0.0/24 gateway 192.168.0.1
 - eth1 with 192.168.1.10 on subnet 192.168.1.0/24 gateway 192.168.1.1
Where eth0's network is a "back door" to the internet, and eth1's is the "front
door", I believe I can