[CentOS-virt] Sanlock disk leases on drbd/gfs2 volume
Hi all, I have a 2 node cluster that consists of the following: * 1 drbd/gfs2 partition that holds VM images and XML * Sanlock configured with the disk lease directory on the same drbd/gfs partition Everything is working well, aside from one small issue I ran into. When testing fencing, on one particular test GFS began replaying the journal for the remaining node, and in the middle of it rgmanager attempted to recover the VM. Normally this wouldn't be an issue, as libvirt would just pause until GFS was ready, however since it's talking to sanlock first, sanlock attempted to acquire the lock, while GFS was not ready, and failed. This caused the recovery itself to fail. I'm attempting to keep the lease directory on the shared storage so that I do not have introduce another single point of failure in the cluster by having an outside NFS mount. It seems like I could get around this particular scenario by changing the recovery policy to restart (it's on relocate right now), and have it try restarts several times before giving up, but I wanted to see first if you guys had any advice for this issue as well. Perhaps I'm missing a setting that would correct this? Thanks! ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS] Strange issue with system time being off
Hi all, After poking around a bit I ended up just going the /etc/ntp/step-tickers route to resolve the issue and have the time in-sync as soon as the OS comes up. Thanks for all the help! On Sat, Aug 11, 2012 at 7:15 PM, Gordon Messmer yiny...@eburg.com wrote: On 08/09/2012 12:33 PM, Russell Jones wrote: The hardware clock is configured in local time. /etc/sysconfig/clock is set to UTC=false and ZONE=America/Chicago. What other settings are in that file? The system is treating your hardware clock as if it were UTC. Actually setting it to UTC is probably the easiest fix (and possibly the best one). ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Strange issue with system time being off
Hi all, I am having an issue with some older CentOS 5.3 servers. Every time the server boots, it gives the error Cannot access the hardware clock by any known method, and then promptly sets the time 5 hours behind the hardware clock, down to the second. After the system is up. hwclock works fine. hwclock --debug does not show any error at all. The hardware clock is configured in local time. /etc/sysconfig/clock is set to UTC=false and ZONE=America/Chicago. /etc/localtime is a copy of Chicago's zone file. /etc/adjtime is configured with LOCAL as the third row. I am at a loss as to what is causing this. Any assistance is appreciated! Thanks! ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Strange issue with system time being off
Thanks for the reply. The hwclock can be set properly from the OS. No BIOS permissions to even set for the clock, it's just a standard old 24 hour clock. On Thu, Aug 9, 2012 at 2:43 PM, m.r...@5-cent.us wrote: Russell Jones wrote: Hi all, I am having an issue with some older CentOS 5.3 servers. Every time the server boots, it gives the error Cannot access the hardware clock by any known method, and then promptly sets the time 5 hours behind the hardware clock, down to the second. So, it's obviously setting it to GMT. After the system is up. hwclock works fine. hwclock --debug does not show any error at all. The hardware clock is configured in local time. /etc/sysconfig/clock is set to UTC=false and ZONE=America/Chicago. /etc/localtime is a copy of Chicago's zone file. /etc/adjtime is configured with LOCAL as the third row. I am at a loss as to what is causing this. Any assistance is appreciated! Thanks! Wonder if there's some permission or ownership problem You might also check in the BIOS, if some protection is turned on. mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Strange issue with system time being off
Thanks, I tried again, rebooted, still 5 hours off slow. The second I do hwclock --hctosys the time is fine. That's silly to have to do that though, I feel like I am missing a configuration parameter somewhere. [root@nod705 ~]# date Thu Aug 9 10:06:36 CDT 2012 [root@nod705 ~]# hwclock Thu 09 Aug 2012 03:06:39 PM CDT -0.437183 seconds [root@nod705 ~]# cat /etc/sysconfig/clock # The ZONE parameter is only evaluated by system-config-date. # The timezone of the system is defined by the contents of /etc/localtime. ZONE=America/Chicago UTC=false ARC=false [root@nod705 ~]# cat /etc/adjtime 0.0 0 0.0 0 LOCAL On Thu, Aug 9, 2012 at 2:56 PM, Craig White craig.wh...@ttiltd.com wrote: On Aug 9, 2012, at 12:33 PM, Russell Jones wrote: Hi all, I am having an issue with some older CentOS 5.3 servers. Every time the server boots, it gives the error Cannot access the hardware clock by any known method, and then promptly sets the time 5 hours behind the hardware clock, down to the second. After the system is up. hwclock works fine. hwclock --debug does not show any error at all. The hardware clock is configured in local time. /etc/sysconfig/clock is set to UTC=false and ZONE=America/Chicago. /etc/localtime is a copy of Chicago's zone file. /etc/adjtime is configured with LOCAL as the third row. I am at a loss as to what is causing this. Any assistance is appreciated! Thanks! Chicago is GMT +5 if I recall correctly so it would seem that perhaps a previous install used UTC=true to set the hwclock after you get the time set (date -s 08/09/2012 14:54:00 or whatever) then set the hwclock to system time hwclock --systohc Craig ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Strange issue with system time being off
Craig, Let me clarify. I correct the time, and both date and hwclock both show the correct time. I reboot the server and date is again 5 hours slow. On Thu, Aug 9, 2012 at 3:22 PM, Craig White craig.wh...@ttiltd.com wrote: until you set your clock so that 'date' gives the right time, don't bother doing anything else. Once you get it set, then execute the hwclock --systohc Craig On Aug 9, 2012, at 1:08 PM, Russell Jones wrote: Thanks, I tried again, rebooted, still 5 hours off slow. The second I do hwclock --hctosys the time is fine. That's silly to have to do that though, I feel like I am missing a configuration parameter somewhere. [root@nod705 ~]# date Thu Aug 9 10:06:36 CDT 2012 [root@nod705 ~]# hwclock Thu 09 Aug 2012 03:06:39 PM CDT -0.437183 seconds [root@nod705 ~]# cat /etc/sysconfig/clock # The ZONE parameter is only evaluated by system-config-date. # The timezone of the system is defined by the contents of /etc/localtime. ZONE=America/Chicago UTC=false ARC=false [root@nod705 ~]# cat /etc/adjtime 0.0 0 0.0 0 LOCAL On Thu, Aug 9, 2012 at 2:56 PM, Craig White craig.wh...@ttiltd.com wrote: On Aug 9, 2012, at 12:33 PM, Russell Jones wrote: Hi all, I am having an issue with some older CentOS 5.3 servers. Every time the server boots, it gives the error Cannot access the hardware clock by any known method, and then promptly sets the time 5 hours behind the hardware clock, down to the second. After the system is up. hwclock works fine. hwclock --debug does not show any error at all. The hardware clock is configured in local time. /etc/sysconfig/clock is set to UTC=false and ZONE=America/Chicago. /etc/localtime is a copy of Chicago's zone file. /etc/adjtime is configured with LOCAL as the third row. I am at a loss as to what is causing this. Any assistance is appreciated! Thanks! Chicago is GMT +5 if I recall correctly so it would seem that perhaps a previous install used UTC=true to set the hwclock after you get the time set (date -s 08/09/2012 14:54:00 or whatever) then set the hwclock to system time hwclock --systohc Craig ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos -- Craig White ~ craig.wh...@ttiltd.com 1.800.869.6908 ~~ www.ttiassessments.com Need help communicating between generations at work to achieve your desired success? Let us help! ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Strange issue with system time being off
Also in case it wasn't clear, I have ran hwclock --systohc after date shows the correct time. On Thu, Aug 9, 2012 at 3:30 PM, Russell Jones arjone...@gmail.com wrote: Craig, Let me clarify. I correct the time, and both date and hwclock both show the correct time. I reboot the server and date is again 5 hours slow. On Thu, Aug 9, 2012 at 3:22 PM, Craig White craig.wh...@ttiltd.com wrote: until you set your clock so that 'date' gives the right time, don't bother doing anything else. Once you get it set, then execute the hwclock --systohc Craig On Aug 9, 2012, at 1:08 PM, Russell Jones wrote: Thanks, I tried again, rebooted, still 5 hours off slow. The second I do hwclock --hctosys the time is fine. That's silly to have to do that though, I feel like I am missing a configuration parameter somewhere. [root@nod705 ~]# date Thu Aug 9 10:06:36 CDT 2012 [root@nod705 ~]# hwclock Thu 09 Aug 2012 03:06:39 PM CDT -0.437183 seconds [root@nod705 ~]# cat /etc/sysconfig/clock # The ZONE parameter is only evaluated by system-config-date. # The timezone of the system is defined by the contents of /etc/localtime. ZONE=America/Chicago UTC=false ARC=false [root@nod705 ~]# cat /etc/adjtime 0.0 0 0.0 0 LOCAL On Thu, Aug 9, 2012 at 2:56 PM, Craig White craig.wh...@ttiltd.com wrote: On Aug 9, 2012, at 12:33 PM, Russell Jones wrote: Hi all, I am having an issue with some older CentOS 5.3 servers. Every time the server boots, it gives the error Cannot access the hardware clock by any known method, and then promptly sets the time 5 hours behind the hardware clock, down to the second. After the system is up. hwclock works fine. hwclock --debug does not show any error at all. The hardware clock is configured in local time. /etc/sysconfig/clock is set to UTC=false and ZONE=America/Chicago. /etc/localtime is a copy of Chicago's zone file. /etc/adjtime is configured with LOCAL as the third row. I am at a loss as to what is causing this. Any assistance is appreciated! Thanks! Chicago is GMT +5 if I recall correctly so it would seem that perhaps a previous install used UTC=true to set the hwclock after you get the time set (date -s 08/09/2012 14:54:00 or whatever) then set the hwclock to system time hwclock --systohc Craig ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos -- Craig White ~ craig.wh...@ttiltd.com 1.800.869.6908 ~~ www.ttiassessments.com Need help communicating between generations at work to achieve your desired success? Let us help! ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Strange issue with system time being off
Here's a question: run hwclock, then, when you reboot, go into the BIOS, and see what the time is. mark Thanks Mark. hwclock showed the right time before reboot. After reboot, entering BIOS it still showed the correct local time. After the server came up, date is slow by 5 hours. [root@nod705 ~]# date Thu Aug 9 11:26:12 CDT 2012 [root@nod705 ~]# hwclock Thu 09 Aug 2012 04:26:15 PM CDT -0.002574 seconds ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Strange issue with system time being off
On Thu, Aug 9, 2012 at 4:30 PM, m.r...@5-cent.us wrote: Russell Jones wrote: Here's a question: run hwclock, then, when you reboot, go into the BIOS, and see what the time is. Thanks Mark. hwclock showed the right time before reboot. After reboot, entering BIOS it still showed the correct local time. After the server came up, date is slow by 5 hours. Hmmm... and the BIOS doesn't have something that says use GMT? If not, sounds like there's a configuration file *somewhere* that's saying use GMT. I'm out of here for the day. See if something comes to mind tonight mark Nope, no timezone configuration options at all. Like I said, very strange. Usually time just works on a box. Thanks for the help ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Strange issue with system time being off
On Thu, Aug 9, 2012 at 6:59 PM, Woodchuck mar...@pennswoods.net wrote: On Thu, Aug 09, 2012 at 04:40:19PM -0700, Craig White wrote: On Aug 9, 2012, at 2:26 PM, Russell Jones wrote: Here's a question: run hwclock, then, when you reboot, go into the BIOS, and see what the time is. mark Thanks Mark. hwclock showed the right time before reboot. After reboot, entering BIOS it still showed the correct local time. After the server came up, date is slow by 5 hours. Let's back up a bit. I bet Mr Jones, the OP, is in the US central time zone, which right now is 5 hours earlier than UTC. I'm betting the hardware clock is set to UTC, but that Centos believes that the hw clock is set to local time, i.e. CST6CDT. (That is how it would be set for Windoze.) There is some pitiful setting to correct the Windoze problem, and it is being applied. It shouldn't be. Reboot, set bios clock to UTC. Then track down wherever Centos gets the idea that you have a dual boot windows machine whose clock is set to local time, and whack that. I'm reasonably confident that this is the problem. The exactly five hours off is what clued me. I think some others up-thread have been hinting about this, at least indirectly. Dave -- The principles of accounting are not arbitrary. They are natural law. -- Mencius Moldbug ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Hi Dave, Robert, Thanks for the help! Dave: There are no options for time zones in the BIOS clock. The time is just there to be set. It is currently set to 7:08 PM, which is the current Central Time. Robert: Great idea! I am fairly certain that is a good direction to go in. I will check this on Tuesday (next time I am in the office). ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] virDomainSetMaxMemory error
CentOS 5.6, x86_64 In Virt-Manager, when attempting to either change a guest's memory allocation or even just clicking Apply on the memory tab and not actually changing the values, the following error pops up: Error changing memory values: this function is not supported by the connection driver: virDomainSetMaxMemory When Googling around, I am finding reports of this error as early as two days ago, and as late as a year ago. Is there an option in KVM/Virt-Manager I am missing in order to resolve this problem, or is this bug really over a year old and not fixed in CentOS 5.6? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Centos 6 Update?
A bigger number? :-) On 4/6/2011 7:52 AM, compdoc wrote: What the hell is so special about CentOS 6? indeed ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Forcing IPv4 DNS lookups first before IPv6
Thank you! If forcing it to stop system-wide is not possible, is there any way of forcing IPv4 lookups to occur first then? On 4/4/2011 5:34 PM, Tom H wrote: On Mon, Apr 4, 2011 at 10:51 AM, Russell Jonesrjo...@eggycrew.com wrote: I am having a strange issue with CentOS 5.4 that I cannot seem to solve. Every DNS lookup results in records being requested first before A records. As a result, this causes a large amount of unnecessary DNS traffic on the network. IPv6 has been completely disabled on these servers: /etc/modprobe.conf, ipv6 off and net-pf-10 off /etc/sysconfig/network, NETWORKING_IPV6=no lsmod | grep ipv6 shows the kernel module no longer loaded. Yet watching TCP dump shows that records are requested before A records every time a login is requested from one of our local machines to another. Is there some sort of configuration directive I can use to force IPv4 lookups first before IPv6? Or even better, stop IPv6 lookups all together? Disabling ipv6 transport cannot prevent applications from making ipv6 queries - short of recompiling them as ipv4-only applications or having applications check whether there is a non-link-local ipv6 address before making an ipv6 query. I've seen these checks discussed but I don't think that they've been implemented - or, if they've been implemented, backported to CentOS 5. It's been going on for a while: https://www.redhat.com/archives/redhat-list/2009-March/msg00067.html ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] FTP server for registered and anonymous users
Need more information. - Are you using vsftpd? Proftpd? - Are your users separate local user accounts that all have their own home directories? - Have you already looked at the anonymous FTP configuration for the FTP server software you are wanting to use? - Have you already looked at the welcome banner configuration if you are just wanting to give general server info on login? On 4/5/2011 8:45 PM, Fidel Dominguez-Valero wrote: Friends I have a good ftp server working with authentication of users, but I want to put a folder with general information for everyone can read without having to log in, that is to be seen both registered users and guests too. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Forcing IPv4 DNS lookups first before IPv6
3 or 4 domains on the search path, this causes a large amount unneeded IPv6 DNS traffic. This behavior doesn't make a whole lot of sense, so I am hoping I'm missing something somewhere to force it to always do IPv4 DNS lookups first, or disable IPv6 lookups completely. All boxes' /etc/resolv.conf aren't special, just name server lines and then the search option with internal domains on it. We don't use IPv6 so don't need the functionality. On similar CentOS 4 boxes with the same configuration on the same network, it does not attempt IPv6 lookups at all with traceroutes or SSH logins. On 4/4/2011 10:50 AM, Adam Tauno Williams wrote: On Mon, 2011-04-04 at 09:51 -0500, Russell Jones wrote: Hello! I am having a strange issue with CentOS 5.4 that I cannot seem to solve. Every DNS lookup results in records being requested first before A records. As a result, this causes a large amount of unnecessary DNS traffic on the network. IPv6 has been completely disabled on these servers: Doubtful, if you are seeing lookups. Does ip addr show any IPv6 interfaces? /etc/modprobe.conf, ipv6 off and net-pf-10 off /etc/sysconfig/network, NETWORKING_IPV6=no lsmod | grep ipv6 shows the kernel module no longer loaded. Yet watching TCP dump shows that records are requested before A records every time a login is requested from one of our local machines to another You *only* sees these for login? Perhaps some authentication module you are using is causing them to happen? Is there some sort of configuration directive I can use to force IPv4 lookups first before IPv6? Or even better, stop IPv6 lookups all together? I don't believe you see IPv6 lookups from the normal resolver libraries unless there is at least one active IPv6 interface. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Forcing IPv4 DNS lookups first before IPv6
Thank you, but unfortunately this is a different issue. These boxes do not run bind, they resolve their DNS queries via dedicated bind servers on the network. Configuring the bind servers on the network a different way still would not stop the IPv6 traffic I am showing in the TCP dump from being sent. On 4/4/2011 11:54 AM, Stephen Harris wrote: On Mon, Apr 04, 2011 at 11:34:25AM -0500, Russell Jones wrote: [root@hostname1 ~]# tcpdump -v 'port 53' tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 11:07:24.989304 IP (tos 0x0, ttl 64, id 65039, offset 0, flags [DF], proto: UDP (17), length: 60) hostname1.59725 vdns1-hc.example.com.domain: [bad udp cksum 2bd2!] 26130+ ? hostname2.example.com. (32) Check https://bugzilla.redhat.com/show_bug.cgi?id=140528 and see if that resolves your issue. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Forcing IPv4 DNS lookups first before IPv6
Thanks. Yes, the modules are disabled via /etc/modprobe.conf: alias net-pf-10 off alias ipv6 off The issue at stake here is not queries timing out, as these aren't even external network queries, it's the queries being sent to begin with. We have thousands of CentOS 5 boxes all doing 3 or more IPv6 DNS queries for 1 IPv4 host. These aren't wanted or needed on the network, and it's causing a large amount of unneeded traffic and strain on our DNS servers. We need the traffic to go away, we don't want any IPv6 DNS queries at all, as they are useless to us. They should not be sent when IPv6 is disabled in both networking and kernel modules, and no IPv6 address exists on the interfaces, yet they still are. I'm unsure how enabling IPv6 via /etc/sysconfig/network is going to make the IPv6 DNS queries stop, but I tried it anyway: [root@hostname1 sysconfig]# nano -w network [root@hostname1 sysconfig]# service network restart Shutting down interface eth0: [ OK ] Shutting down loopback interface: [ OK ] FATAL: Module off not found. CRITICAL : [ipv6_test] Kernel is not compiled with IPv6 support Bringing up loopback interface:[ OK ] Bringing up interface eth0:[ OK ] FATAL: Module off not found. CRITICAL : [ipv6_test] Kernel is not compiled with IPv6 support Re-enabling the IPv6 kernel modules will just put us back to where we were to begin with. Any other ideas on how to make the queries stop? On 4/4/2011 12:10 PM, Brunner, Brian T. wrote: centos-boun...@centos.org wrote: Thank you, but unfortunately this is a different issue. These boxes do not run bind, they resolve their DNS queries via dedicated bind servers on the network. Configuring the bind servers on the network a different way still would not stop the IPv6 traffic I am showing in the TCP dump from being sent. Things described in the bug report are Adding NETWORKING_IPV6=yes to /etc/sysconfig/network prevents the queries to root nameservers with IPv6 addresses timing out. And alias net-pf-10 off to /etc/modprobe.conf Have you tried both of them? On 4/4/2011 11:54 AM, Stephen Harris wrote: On Mon, Apr 04, 2011 at 11:34:25AM -0500, Russell Jones wrote: [root@hostname1 ~]# tcpdump -v 'port 53' tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 11:07:24.989304 IP (tos 0x0, ttl 64, id 65039, offset 0, flags [DF], proto: UDP (17), length: 60) hostname1.59725 vdns1-hc.example.com.domain: [bad udp cksum 2bd2!] 26130+ ? hostname2.example.com. (32) Check https://bugzilla.redhat.com/show_bug.cgi?id=140528 and see if that resolves your issue. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Insert spiffy .sig here: Life is complex: it has both real and imaginary parts. //me *** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.Hubbell.com - Hubbell Incorporated** ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Forcing IPv4 DNS lookups first before IPv6
No such thing as dumb questions when you're asking other people for help :-) Here's the whole file: = passwd: files nis shadow: files nis group: files nis hosts: files dns nis bootparams: nisplus [NOTFOUND=return] files ethers: files netmasks: files networks: files protocols: files nis rpc:files services: files nis netgroup: files nis publickey: nisplus #automount: nis automount: ldap aliases:files nisplus === On 4/4/2011 1:22 PM, m.r...@5-cent.us wrote: Russell Jones wrote: Thanks. Yes, the modules are disabled via /etc/modprobe.conf: alias net-pf-10 off alias ipv6 off The issue at stake here is not queries timing out, as these aren't even external network queries, it's the queries being sent to begin with. We snip Really dumb question, which may have been answered: what's in /etc/nsswitch? mark ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
