search for: ciurcio

I previously reported this on the centos mailing list: http://lists.centos.org/pipermail/centos/2009-November/085672.html And I've found out that Red Hat has backported the VT-d support from Xen 3.3 to RHEL 5.4. http://lists.centos.org/pipermail/centos/2009-November/085677.html It seams to me that the "classic" Xen pci-passthru (up to Xen 3.2) works only on some minor cases as

I'm using Dovecot 1.1.7 on CentOS 5.2. I've changed my passdb from passwd to pam, it works fine, but I've found this messages on /var/log/secure: dovecot-auth: PAM adding faulty module: /lib64/security/pam_limits.so dovecot-auth: PAM unable to dlopen(/lib64/security/pam_limits.so) dovecot-auth: PAM [error: /lib64/security/pam_limits.so: failed to map segment from shared object:

Hello, We had the following situation where including two classes that were ensuring the installation of the same package "php5-imagick" and it was causing an error indicating that two ressources of the same name are forbidden (sorry, I don''t have the exact message error since we fixed quickly the error). Since we are newbies in puppet, we would like to understand what this

Hi there, After updating a server from CentOS 5.3 to 5.4 my Xen pci-passthru setup has some troubles. The server has two NICs, one used by dom0 and the other assigned to a domU and one SCSI controler assigned to another domU. It has been working fine since CentOS 5.1, when I did the initial setup. After upgrading to 5.4, I get this error when starting the domU with one of the NICs assigned:

hello: i currently am using Puppet to run some commands in a sequence. there are two sequences of exec resources. we found that we cannot use require => Exec and it does not work at all as expected. here is some sample code. exec { "exec-AAA": command => "/bin/true", returns => 0, notify => Exec["exec-BBB"], } exec { "exec-BBB":