Re: [CentOS] init/upstart issue? ypbind and autofs

2012-02-14 Thread Lars Hecking
> | The other machine doesn't have NetworkManager installed. Removed it > | here > | and NIS/autofs started working correctly. > > You don't have to remove NetworkManager you just need to tell the interface > not to be managed by NM in order for it to work. Won't help in this case, I think

Re: [CentOS] Dovecot problems

2012-02-14 Thread Steve Campbell
I'm not sure I understand all of the consequences of just moving these folders from /home/user/mail to the new servers. So far, I seem to have things working OK with a pop, imap, and horde webmail situation for any particular account. It required using "namespace", but it seems to work. Can any

Re: [CentOS] [CentOS-announce] CEBA-2012:0124 CentOS 6 kernel Update

2012-02-14 Thread Steve Clark
On 02/14/2012 06:00 AM, Johnny Hughes wrote: > CentOS Errata and Bugfix Advisory 2012:0124 > > Upstream details at :https://rhn.redhat.com/errata/RHBA-2012-0124.html > > The following updated files have been uploaded and are currently > syncing to the mirrors: ( sha256sum Filename ) > > > i386: > 7

[CentOS] CentOS-announce Digest, Vol 84, Issue 7

2012-02-14 Thread centos-announce-request
Send CentOS-announce mailing list submissions to centos-annou...@centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-requ..

Re: [CentOS] schily tools

2012-02-14 Thread Joerg Schilling
Les Mikesell wrote: > > Well, I verified that gtar fails with even a simple case and I did not see > > any > > problem with star since 6 years even with thousands of incremental > > restores. > > So I am not sure what you are talkin about. > > > > Gtar doesn't fail, it just requires some extra st

Re: [CentOS] QEMU configuration not persistent

2012-02-14 Thread Paul Heinlein
On Mon, 13 Feb 2012, Emmett Culley wrote: > Still doesn't persist. Each time I reboot I have to use > virt-manager to change video to cirrus from vmvga, then remove the > IDE driver that points to the wrong storage location and add a new > virtio storage device pointing to the correct image (a

Re: [CentOS] bug in repo affecting perl

2012-02-14 Thread Blake Hudson
Nicolas Thierry-Mieg wrote the following on 2/13/2012 9:11 PM: > why do you think there's a problem? if you have an x86_64 system, you > are expected to use x86_64 perl, and that's what you have in the os > and updates dir for that arch, with the newer version in updates. Same > if you have an

[CentOS] iptables nat PREROUTING chain

2012-02-14 Thread Nataraj
Is there a way to add a rule to the nat table (CentOS 5.7) that would alter the port number of tcp packets destined for the server itself? I have ip_forwarding enabled, but the packets don't seem to hit the prerouting chain. I have the following redirect rule in the prerouting table. I also trie

Re: [CentOS] iptables nat PREROUTING chain

2012-02-14 Thread Robert Spangler
On Tuesday 14 February 2012 15:21, the following was written: > Is there a way to add a rule to the nat table (CentOS 5.7) that would > alter the port number of tcp packets destined for the server itself? I > have ip_forwarding enabled, but the packets don't seem to hit the > prerouting chain

Re: [CentOS] iptables nat PREROUTING chain

2012-02-14 Thread Nataraj
On 02/14/2012 01:28 PM, Robert Spangler wrote: > On Tuesday 14 February 2012 15:21, the following was written: > >> Is there a way to add a rule to the nat table (CentOS 5.7) that would >> alter the port number of tcp packets destined for the server itself? I >> have ip_forwarding enabled, but

Re: [CentOS] [SOLVED] iptables nat PREROUTING chain

2012-02-14 Thread Nataraj
On 02/14/2012 02:39 PM, Nataraj wrote: > On 02/14/2012 01:28 PM, Robert Spangler wrote: >> On Tuesday 14 February 2012 15:21, the following was written: >> >>> Is there a way to add a rule to the nat table (CentOS 5.7) that would >>> alter the port number of tcp packets destined for the server it

Re: [CentOS] bug in repo affecting perl

2012-02-14 Thread Nicolas Thierry-Mieg
Blake Hudson wrote: > > > Nicolas Thierry-Mieg wrote the following on 2/13/2012 9:11 PM: >> why do you think there's a problem? if you have an x86_64 system, you >> are expected to use x86_64 perl, and that's what you have in the os >> and updates dir for that arch, with the newer version in update

Re: [CentOS] bug in repo affecting perl

2012-02-14 Thread Nicolas Thierry-Mieg
Nicolas Thierry-Mieg wrote: > Blake Hudson wrote: >> >> >> Nicolas Thierry-Mieg wrote the following on 2/13/2012 9:11 PM: >>> why do you think there's a problem? if you have an x86_64 system, you >>> are expected to use x86_64 perl, and that's what you have in the os >>> and updates dir for that ar

Re: [CentOS] bug in repo affecting perl

2012-02-14 Thread John R Pierce
On 02/14/12 3:59 PM, Nicolas Thierry-Mieg wrote: > BTW: why do you need 32bit perl? Since the package exists and you have > it installed, I guess there must be use-cases... but perl being > interpreted, I'm curious as to what they could be. usually in my experience, the requirement for 32 bit perl

[CentOS] LDAP encryption, not sure.

2012-02-14 Thread Fajar Priyanto
Hi all, I'm setting up a local LDAP server with a pass-through authentication to another LDAP. I'm not clear about the encryption. Say the case is like this. CompB is set to have LDAP authentication. A ---> SSH ---> CompB ---> Local LDAP:389 ---> SASLAUTHD --> Global LDAP: 636 1. Password on the

Re: [CentOS] schily tools

2012-02-14 Thread Les Mikesell
On Tue, Feb 14, 2012 at 12:41 PM, Joerg Schilling wrote: >> >> Gtar doesn't fail, it just requires some extra steps to accommodate some >> very unlikely circumstances.  Your star runs will not work at all in very >> likely circumstances (which you conveniently avoid testing). > > Trying to underst

Re: [CentOS] QEMU configuration not persistent

2012-02-14 Thread Florian La Roche
> After that, I'd get more drastic: > > 1. virsh shutdown $DOM. > 2. virsh dumpxml $DOM > /tmp/dom.xml > 3. virsh undefine $DOM > 4. virsh create /tmp/dom.xml > 5. virsh edit $DOM > 6. virsh start $DOM --console > > And then see if things get better. I just edit the xml files and then issue a "v