Discuss

discuss@lists.centos.org

34753 discussions

CentOS 6.2 x86_64 Squirrelmail Problem
by Prabhpal S. Mavi 12 Apr '12

12 Apr '12

Greetings Friends, is any one knows why i see squirrelmail login interface like below Live Example Can Be Seen Here: https://mail.digital-infotech.com/webmail i have tried to install configure from source as well rather than RPM but all the same.security permissions have been verified also. and i have no clue any more. help would be greatly appreciated Thanks / Regards <> < bgcolor="#ffffff" border="0" cellspacing="0" cellpadding="0" width="100%"><><> SquirrelMail version 1.4.22-2.el6 By the SquirrelMail Project Team < bgcolor="#ffffff" border="0" width="350"><>< bgcolor="#dcdcdc">Digital Infotech Limited Login <>< bgcolor="#ffffff"> < bgcolor="#ffffff" border="0" width="100%"><>< width="30%">Name: < width="70%"> <>< width="30%">Password: < width="70%"> <><> Thanks / Regards Prabhpal S. Mavi Email: prabhpal(a)digital-infotech.net Sent Through .Net Domain From iPhone

3 4

Problem with latest kernel install
by Arthur Pemberton 12 Apr '12

12 Apr '12

After a simple `yum update` I got the following on reboot. Could not load /lib/modules/2.6.32-220.7.1.el6.x86_64/modules.dep: No such file or director FATAL: Could not load /lib/module.el6.x86_64/modules.dep: No such file or directory FATAL: Could not load /lib/modules/2.6.32-220.7.1.el6.x86_64/modules.dep: No such file or directory FATAL: Could not load /lib/modules/2.6.32-220.7.1.el6.x86_64/modules.dep: No such file or directory FATAL: Could not load /lib/modules/2.6.32-220.7.1.el6.x86_64/modules.dep: No such file or directory FATAL: Could not load /lib/modules/2.6.32-220.7.1.el6.x86_64/modules.dep: No such file or directory FATAL: Could not load /lib/modules/2.6.32-220.7.1.el6.x86_64/modules.dep: No such file or directory FATAL: Could not load /lib/modules/2.6.32-220.7.1.el6.x86_64/modules.dep: No such file or directory FATAL: Could not load /lib/modules/2.6.32-220.7.1.el6.x86_64/modules.dep: No such file or directory FATAL: Could not load /lib/modules/2.6.32-220.7.1.el6.x86_64/modules.dep: No such file or directory What's the best way to resolve this?

2 2

FSCK on mounted filesystem (LVM/DRBD)?
by Rafał Radecki 12 Apr '12

12 Apr '12

Hi All. I have two running servers (drbd primary, drbd secondary). When there is a problem with one of them we switch to the second one. Currently on the /dev/drbd0 (it has /xxx ext3 filesystem directly on it) we have some filesystem problems (after fsck -n). I would like to correct these errors but the filesystem should be unmounted first (I would like to avoid it if possible). Is there a way to make fsck -a on mounted filesystem for ext3? My setup is: ext3 filesystem (problems) ^ DRBD ^ LVS ^ RAID Any ideas? Best regards, Rafal.

3 4

centos 6.2 md0 boot - no boot actually
by aurfalien 12 Apr '12

12 Apr '12

Hi all, Taken from this link; https://www.centos.org/modules/newbb/print.php?form=1&topic_id=34988&forum=… Seems like I am having the same issue. I assigned my boot loader to be on /dev/md0 rather then the default of /dev/sda1 Does any one have insight to this? Thanks in advance. BTW, I have no swap partition and will do a swap file instead, easier to manage. Do I need swap to boot? - aurf

4 5

Hyper Threading Feature
by Kaushal Shriyan 12 Apr '12

12 Apr '12

Hi, Any performance bottleneck if HT (Hyper Threading) is enabled in quad core processors on CentOS 5.8 running MySQL DB Server ? Please help me understand about pros and cons of this feature. Regards, Kaushal

3 2

screen brightness changes depending on which application is run
by Jeff Cen 12 Apr '12

12 Apr '12

Hi, I found my LCD screen brightness increase when I use firefox and other white background editors and screen brightness decrease when I use dark background applications, such as terminals with black background . The change in screen brightness depending on the applications has been annoying. My centos version is ver 5.7 64 bit. Has anyone seen a similar problem or have a solution for that? Thanks in advance. Jeff

4 5

6.2 x86_64 "mtrr_cleanup: can not find optimal value"
by Michael McNulty 12 Apr '12

12 Apr '12

Hi, I have server that has been running 5.x - 5.8 for a few years without issue and decided to move it to a fresh install of 6.2. First thing I noticed is a good part of the log has these mtrr messages finally ending with "mtrr_cleanup: can not find optimal value" and "please specify mtrr_gran_size/mtrr_chunk_size". I have been searching around and reading the kernel docs but are bit lost on the impact. The system CPU is a q6600 so it supports mtrr. It has 8gb of RAM and a G33 intel chipset (maximum memory is 8gb), 256mb onboard Intel video. Problem exists with DVD 6.2 kernel and latest in yum update 2.6.32-220.7.1.el6.x86_64. If I disable the Bios "memory remap feature", mtrr appears to have found it settings. But it says total ram covered is 7415M, so I lose some memory since when enabled it shows 8183M but mtrr fails. A little concerned about putting this back into production with this but hope to get it resolved rather than reinstall 5.8. Will mtrr failing result in stability or performance loss? Is there any performance loss disabling memory remap in bios other than losing 600k? thx Is this happening because the chipset only supports 8gb of memory and therefore mtrr cannot remap memory above 8gb? (assuming not since problem did not exist in 5.x centos) -- Mike Bios Memory remap feature: enabled Apr 11 17:25:36 kernel: total RAM covered: 8183M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 64K num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 128K num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 256K num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 512K num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 1M num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 2M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 4M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 8M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 16M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 32M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 64M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 128M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 256M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: *BAD*gran_size: 64K chunk_size: 512M num_reg: 8 lose cover RAM: -256M Apr 11 17:25:36 kernel: gran_size: 64K chunk_size: 1G num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: *BAD*gran_size: 64K chunk_size: 2G num_reg: 8 lose cover RAM: -1G Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 128K num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 256K num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 512K num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 1M num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 2M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 4M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 8M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 16M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 32M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 64M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 128M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 256M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: *BAD*gran_size: 128K chunk_size: 512M num_reg: 8 lose cover RAM: -256M Apr 11 17:25:36 kernel: gran_size: 128K chunk_size: 1G num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: *BAD*gran_size: 128K chunk_size: 2G num_reg: 8 lose cover RAM: -1G Apr 11 17:25:36 kernel: gran_size: 256K chunk_size: 256K num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 256K chunk_size: 512K num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 256K chunk_size: 1M num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 256K chunk_size: 2M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 256K chunk_size: 4M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 256K chunk_size: 8M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 256K chunk_size: 16M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 256K chunk_size: 32M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 256K chunk_size: 64M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 256K chunk_size: 128M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 256K chunk_size: 256M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: *BAD*gran_size: 256K chunk_size: 512M num_reg: 8 lose cover RAM: -256M Apr 11 17:25:36 kernel: gran_size: 256K chunk_size: 1G num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: *BAD*gran_size: 256K chunk_size: 2G num_reg: 8 lose cover RAM: -1G Apr 11 17:25:36 kernel: gran_size: 512K chunk_size: 512K num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 512K chunk_size: 1M num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 512K chunk_size: 2M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 512K chunk_size: 4M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 512K chunk_size: 8M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 512K chunk_size: 16M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 512K chunk_size: 32M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 512K chunk_size: 64M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 512K chunk_size: 128M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 512K chunk_size: 256M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: *BAD*gran_size: 512K chunk_size: 512M num_reg: 8 lose cover RAM: -256M Apr 11 17:25:36 kernel: gran_size: 512K chunk_size: 1G num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: *BAD*gran_size: 512K chunk_size: 2G num_reg: 8 lose cover RAM: -1G Apr 11 17:25:36 kernel: gran_size: 1M chunk_size: 1M num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 1M chunk_size: 2M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 1M chunk_size: 4M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 1M chunk_size: 8M num_reg: 8 lose cover RAM: 4864M Apr 11 17:25:36 kernel: gran_size: 1M chunk_size: 16M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 1M chunk_size: 32M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 1M chunk_size: 64M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 1M chunk_size: 128M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: gran_size: 1M chunk_size: 256M num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: *BAD*gran_size: 1M chunk_size: 512M num_reg: 8 lose cover RAM: -256M Apr 11 17:25:36 kernel: gran_size: 1M chunk_size: 1G num_reg: 8 lose cover RAM: 0G Apr 11 17:25:36 kernel: *BAD*gran_size: 1M chunk_size: 2G num_reg: 8 lose cover RAM: -1G Apr 11 17:25:36 kernel: gran_size: 2M chunk_size: 2M num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 2M chunk_size: 4M num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 2M chunk_size: 8M num_reg: 8 lose cover RAM: 4865M Apr 11 17:25:36 kernel: gran_size: 2M chunk_size: 16M num_reg: 8 lose cover RAM: 1M Apr 11 17:25:36 kernel: gran_size: 2M chunk_size: 32M num_reg: 8 lose cover RAM: 1M Apr 11 17:25:36 kernel: gran_size: 2M chunk_size: 64M num_reg: 8 lose cover RAM: 1M Apr 11 17:25:36 kernel: gran_size: 2M chunk_size: 128M num_reg: 8 lose cover RAM: 1M Apr 11 17:25:36 kernel: gran_size: 2M chunk_size: 256M num_reg: 8 lose cover RAM: 1M Apr 11 17:25:36 kernel: *BAD*gran_size: 2M chunk_size: 512M num_reg: 8 lose cover RAM: -255M Apr 11 17:25:36 kernel: gran_size: 2M chunk_size: 1G num_reg: 8 lose cover RAM: 1M Apr 11 17:25:36 kernel: *BAD*gran_size: 2M chunk_size: 2G num_reg: 8 lose cover RAM: -1023M Apr 11 17:25:36 kernel: gran_size: 4M chunk_size: 4M num_reg: 8 lose cover RAM: 771M Apr 11 17:25:36 kernel: gran_size: 4M chunk_size: 8M num_reg: 8 lose cover RAM: 4867M Apr 11 17:25:36 kernel: gran_size: 4M chunk_size: 16M num_reg: 8 lose cover RAM: 3M Apr 11 17:25:36 kernel: gran_size: 4M chunk_size: 32M num_reg: 8 lose cover RAM: 3M Apr 11 17:25:36 kernel: gran_size: 4M chunk_size: 64M num_reg: 8 lose cover RAM: 3M Apr 11 17:25:36 kernel: gran_size: 4M chunk_size: 128M num_reg: 8 lose cover RAM: 3M Apr 11 17:25:36 kernel: gran_size: 4M chunk_size: 256M num_reg: 8 lose cover RAM: 3M Apr 11 17:25:36 kernel: *BAD*gran_size: 4M chunk_size: 512M num_reg: 8 lose cover RAM: -253M Apr 11 17:25:36 kernel: gran_size: 4M chunk_size: 1G num_reg: 8 lose cover RAM: 3M Apr 11 17:25:36 kernel: *BAD*gran_size: 4M chunk_size: 2G num_reg: 8 lose cover RAM: -1021M Apr 11 17:25:36 kernel: gran_size: 8M chunk_size: 8M num_reg: 8 lose cover RAM: 263M Apr 11 17:25:36 kernel: gran_size: 8M chunk_size: 16M num_reg: 8 lose cover RAM: 263M Apr 11 17:25:36 kernel: gran_size: 8M chunk_size: 32M num_reg: 7 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 8M chunk_size: 64M num_reg: 7 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 8M chunk_size: 128M num_reg: 7 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 8M chunk_size: 256M num_reg: 7 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 8M chunk_size: 512M num_reg: 8 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 8M chunk_size: 1G num_reg: 7 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 8M chunk_size: 2G num_reg: 8 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 16M chunk_size: 16M num_reg: 8 lose cover RAM: 263M Apr 11 17:25:36 kernel: gran_size: 16M chunk_size: 32M num_reg: 7 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 16M chunk_size: 64M num_reg: 7 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 16M chunk_size: 128M num_reg: 7 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 16M chunk_size: 256M num_reg: 7 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 16M chunk_size: 512M num_reg: 8 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 16M chunk_size: 1G num_reg: 7 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 16M chunk_size: 2G num_reg: 8 lose cover RAM: 7M Apr 11 17:25:36 kernel: gran_size: 32M chunk_size: 32M num_reg: 8 lose cover RAM: 23M Apr 11 17:25:36 kernel: gran_size: 32M chunk_size: 64M num_reg: 7 lose cover RAM: 23M Apr 11 17:25:36 kernel: gran_size: 32M chunk_size: 128M num_reg: 7 lose cover RAM: 23M Apr 11 17:25:36 kernel: gran_size: 32M chunk_size: 256M num_reg: 7 lose cover RAM: 23M Apr 11 17:25:36 kernel: gran_size: 32M chunk_size: 512M num_reg: 8 lose cover RAM: 23M Apr 11 17:25:36 kernel: gran_size: 32M chunk_size: 1G num_reg: 7 lose cover RAM: 23M Apr 11 17:25:36 kernel: gran_size: 32M chunk_size: 2G num_reg: 8 lose cover RAM: 23M Apr 11 17:25:36 kernel: gran_size: 64M chunk_size: 64M num_reg: 7 lose cover RAM: 55M Apr 11 17:25:36 kernel: gran_size: 64M chunk_size: 128M num_reg: 7 lose cover RAM: 55M Apr 11 17:25:36 kernel: gran_size: 64M chunk_size: 256M num_reg: 7 lose cover RAM: 55M Apr 11 17:25:36 kernel: gran_size: 64M chunk_size: 512M num_reg: 8 lose cover RAM: 55M Apr 11 17:25:36 kernel: gran_size: 64M chunk_size: 1G num_reg: 7 lose cover RAM: 55M Apr 11 17:25:36 kernel: gran_size: 64M chunk_size: 2G num_reg: 8 lose cover RAM: 55M Apr 11 17:25:36 kernel: gran_size: 128M chunk_size: 128M num_reg: 6 lose cover RAM: 119M Apr 11 17:25:36 kernel: gran_size: 128M chunk_size: 256M num_reg: 7 lose cover RAM: 119M Apr 11 17:25:36 kernel: gran_size: 128M chunk_size: 512M num_reg: 8 lose cover RAM: 119M Apr 11 17:25:36 kernel: gran_size: 128M chunk_size: 1G num_reg: 7 lose cover RAM: 119M Apr 11 17:25:36 kernel: gran_size: 128M chunk_size: 2G num_reg: 8 lose cover RAM: 119M Apr 11 17:25:36 kernel: gran_size: 256M chunk_size: 256M num_reg: 5 lose cover RAM: 247M Apr 11 17:25:36 kernel: gran_size: 256M chunk_size: 512M num_reg: 5 lose cover RAM: 247M Apr 11 17:25:36 kernel: gran_size: 256M chunk_size: 1G num_reg: 5 lose cover RAM: 247M Apr 11 17:25:36 kernel: gran_size: 256M chunk_size: 2G num_reg: 6 lose cover RAM: 247M Apr 11 17:25:36 kernel: gran_size: 512M chunk_size: 512M num_reg: 4 lose cover RAM: 503M Apr 11 17:25:36 kernel: gran_size: 512M chunk_size: 1G num_reg: 5 lose cover RAM: 503M Apr 11 17:25:36 kernel: gran_size: 512M chunk_size: 2G num_reg: 6 lose cover RAM: 503M Apr 11 17:25:36 kernel: gran_size: 1G chunk_size: 1G num_reg: 3 lose cover RAM: 1015M Apr 11 17:25:36 kernel: gran_size: 1G chunk_size: 2G num_reg: 3 lose cover RAM: 1015M Apr 11 17:25:36 kernel: gran_size: 2G chunk_size: 2G num_reg: 2 lose cover RAM: 2039M Apr 11 17:25:36 kernel: mtrr_cleanup: can not find optimal value Apr 11 17:25:36 kernel: please specify mtrr_gran_size/mtrr_chunk_size cat /proc/mtrr reg00: base=0x0d0000000 ( 3328MB), size= 256MB, count=1: uncachable reg01: base=0x0e0000000 ( 3584MB), size= 512MB, count=1: uncachable reg02: base=0x000000000 ( 0MB), size= 8192MB, count=1: write-back reg03: base=0x200000000 ( 8192MB), size= 512MB, count=1: write-back reg04: base=0x220000000 ( 8704MB), size= 256MB, count=1: write-back reg05: base=0x0cf700000 ( 3319MB), size= 1MB, count=1: uncachable reg06: base=0x0cf800000 ( 3320MB), size= 8MB, count=1: uncachable cat /proc/meminfo MemTotal: 8050140 kB Now with: Bios Memory remap feature: disabled cat /proc/meminfo MemTotal: 7276000 kB Apr 11 15:33:41 ns2 kernel: total RAM covered: 7415M Apr 11 15:33:41 ns2 kernel: Found optimal setting for mtrr clean up Apr 11 15:33:41 ns2 kernel: gran_size: 64K chunk_size: 16M num_reg: 6 lose cover RAM: 0G /proc/mtrr (bios memory remap disabled) reg00: base=0x000000000 ( 0MB), size= 2048MB, count=1: write-back reg01: base=0x080000000 ( 2048MB), size= 1024MB, count=1: write-back reg02: base=0x0c0000000 ( 3072MB), size= 256MB, count=1: write-back reg03: base=0x0cf700000 ( 3319MB), size= 1MB, count=1: uncachable reg04: base=0x0cf800000 ( 3320MB), size= 8MB, count=1: uncachable reg05: base=0x100000000 ( 4096MB), size= 4096MB, count=1: write-back reg06: base=0x0d0000000 ( 3328MB), size= 256MB, count=1: write-combining

2 2

CentOS-announce Digest, Vol 86, Issue 7
by centos-announce-request＠centos.org 12 Apr '12

12 Apr '12

Send CentOS-announce mailing list submissions to centos-announce(a)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-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2012:0474 Moderate CentOS 5 tomcat5 Update (Johnny Hughes) 2. CESA-2012:0475 Moderate CentOS 6 tomcat6 Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 11 Apr 2012 19:16:37 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2012:0474 Moderate CentOS 5 tomcat5 Update To: centos-announce(a)centos.org Message-ID: <20120411191637.GA23538(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2012:0474 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-0474.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 677aab86c5faad3cc25e07d6fcdd53fd6fb4e8242b73f4a32712a1a80dedd6fd tomcat5-5.5.23-0jpp.31.el5_8.i386.rpm 55e26ac2b214de4b57c9b0a6c4c1fd2299c9835fa014eabf676779e26c304f33 tomcat5-admin-webapps-5.5.23-0jpp.31.el5_8.i386.rpm 6bcdf8cb158e5fc138b402ca880b6249670617042a0aada816ae03b1592b8ca8 tomcat5-common-lib-5.5.23-0jpp.31.el5_8.i386.rpm e5c65e3a50790835f2162fd8bf1f4437b91abd5840ef0e77271d4bc8b181930d tomcat5-jasper-5.5.23-0jpp.31.el5_8.i386.rpm ead6379bbb33dd3d3667d115327f9a1a7125aa7fe102e6dfea82ea8041f63f3d tomcat5-jasper-javadoc-5.5.23-0jpp.31.el5_8.i386.rpm 94c4b03230c5117156a9688577e80fcae51215f49745a13e78a20f2da0e98c52 tomcat5-jsp-2.0-api-5.5.23-0jpp.31.el5_8.i386.rpm d4f83bcdda017f21141015d3916ec98addfc8d2dd41e89d0b680dd7f4938b0af tomcat5-jsp-2.0-api-javadoc-5.5.23-0jpp.31.el5_8.i386.rpm 6ca2b63866656bb8f9f770fb512191dba0880b39288fe3a60f1198fbb9968b93 tomcat5-server-lib-5.5.23-0jpp.31.el5_8.i386.rpm 2453bd661c35aa866f773add148258255a4a23ce4d56937c7e358f36b651b161 tomcat5-servlet-2.4-api-5.5.23-0jpp.31.el5_8.i386.rpm e784ecf1cca6810ee234e8aa6668df952db59efcaf8387dccc612f0f8df91e33 tomcat5-servlet-2.4-api-javadoc-5.5.23-0jpp.31.el5_8.i386.rpm 22e71457a2a5af9dbbaf33467e0f0f2f925758e9e4ee1a8f9872039e8ccb9f41 tomcat5-webapps-5.5.23-0jpp.31.el5_8.i386.rpm x86_64: e38d54727cda210978acd8de956ef1bfd043ac07bd42dd1046fe7bd268e4dbec tomcat5-5.5.23-0jpp.31.el5_8.x86_64.rpm 9ecf46f19443096dfb36f711d6dafc60d2dc662d59ff31ec1dfa31adc2a37b12 tomcat5-admin-webapps-5.5.23-0jpp.31.el5_8.x86_64.rpm 4a51457a1fd9990dd75a54a948b9bb5fa0e661b0c84588633bb45376558d6f6f tomcat5-common-lib-5.5.23-0jpp.31.el5_8.x86_64.rpm 007007a9beef1b8e7dbc1d1f20e62e5134c1714e9f650f7d2bf396302cbb9c20 tomcat5-jasper-5.5.23-0jpp.31.el5_8.x86_64.rpm 7d79042a574270e29a72bb17fc656fea592bf357a65d3989d94c222b773c09df tomcat5-jasper-javadoc-5.5.23-0jpp.31.el5_8.x86_64.rpm d8157c65e93c697494f01fd18772c9256680bb4a4535d892273b63c281cb3493 tomcat5-jsp-2.0-api-5.5.23-0jpp.31.el5_8.x86_64.rpm 4ce03eb51bdf8bc00044f7c3ba54ac73534de566d5fa2be1a6a8809523d1b91a tomcat5-jsp-2.0-api-javadoc-5.5.23-0jpp.31.el5_8.x86_64.rpm 23e98b5e65059582403a8d792cc59fbe613318f93edf8f57828f1b057f78c66f tomcat5-server-lib-5.5.23-0jpp.31.el5_8.x86_64.rpm 20b9f1110dbe2f1e5229f0b21bf9112d2c5fe9676de16374cd72a236291f4bc0 tomcat5-servlet-2.4-api-5.5.23-0jpp.31.el5_8.x86_64.rpm ce532e3efdc63fda701158b0ee3b6af59be4492a1b1ff1d6d14e4092abdadd57 tomcat5-servlet-2.4-api-javadoc-5.5.23-0jpp.31.el5_8.x86_64.rpm 80a2ff2e617dc51e247dcfd63a900cae784ac80f69130b279b2f337bc1f30625 tomcat5-webapps-5.5.23-0jpp.31.el5_8.x86_64.rpm Source: 58e94b9bc8dd59d494fed7476ab279b8f3f792fffefbf8f490bb6b773dc6b355 tomcat5-5.5.23-0jpp.31.el5_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Wed, 11 Apr 2012 20:13:41 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2012:0475 Moderate CentOS 6 tomcat6 Update To: centos-announce(a)centos.org Message-ID: <20120411201341.GA26692(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2012:0475 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-0475.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 74270df5268ece50d978c615795eab1671a142b3bf900d54095fbab2b447f42c tomcat6-6.0.24-36.el6_2.noarch.rpm cf3c4d2abbd7a6bfc1a96aa06e022274c89643cd00e2d2b5b6cedfbcc159e235 tomcat6-admin-webapps-6.0.24-36.el6_2.noarch.rpm 5a7e87389b0194d65cf2b62bbe309f235070683789e9183f6d0c0257099fca9b tomcat6-docs-webapp-6.0.24-36.el6_2.noarch.rpm 60bf53ad8baa5d6d033a84f6b85e06a4afdfdd07c0b70eebc5adb41b0ad2062c tomcat6-el-2.1-api-6.0.24-36.el6_2.noarch.rpm 35ab12080f1f172c7dcc3235fe5e9439b9e3d4321e22f9f80a125b5042f4ced8 tomcat6-javadoc-6.0.24-36.el6_2.noarch.rpm f68e6d247f8ec8781644001957826d1247dc04f9c04164134c9ee7fec421189e tomcat6-jsp-2.1-api-6.0.24-36.el6_2.noarch.rpm f868d3d378d85e7114309ac1bcc6edb9285a15ec25d25eceb66e3ff9236e6c04 tomcat6-lib-6.0.24-36.el6_2.noarch.rpm 30522f9653a242b10594b63f4e70e1be6031f86c7fe77ebfbf8c75d948cb3ad4 tomcat6-servlet-2.5-api-6.0.24-36.el6_2.noarch.rpm a107c27695891977bd4c1f2c87033720809996177e4e4177ffe9f79285983bb8 tomcat6-webapps-6.0.24-36.el6_2.noarch.rpm x86_64: d7d1ca95551a544bcfc72de89655ddc32359747c63fd105c1f33afe18d578ea8 tomcat6-6.0.24-36.el6_2.noarch.rpm 5902bba8182f98018fdf1f89d0c281e2099d1eef9ea95ec1efa74c507878439a tomcat6-admin-webapps-6.0.24-36.el6_2.noarch.rpm 0447f92c911e85ca53fc5674bcdbabd0fcedf63d9c1a7edd77c430386a07c05b tomcat6-docs-webapp-6.0.24-36.el6_2.noarch.rpm 3a3eef5645c5c66a63c14c23c13455f05896fa38ce5b01631c58732301d7d578 tomcat6-el-2.1-api-6.0.24-36.el6_2.noarch.rpm 0c8607543c3bce13fd057914151039323535109df9cf26737c1b225772c31e46 tomcat6-javadoc-6.0.24-36.el6_2.noarch.rpm c6773a21e7d6158f650add40ad1b2410f7fc848f619daf5241b96e7566e86ff5 tomcat6-jsp-2.1-api-6.0.24-36.el6_2.noarch.rpm eaa97269281b7537777c6879fb8a8ff6513b9dbc56630f0c6d47a301a9f717cf tomcat6-lib-6.0.24-36.el6_2.noarch.rpm fa32c69282562c0a6e22e64e5b7e4e23d546bd70b05b8df171f248ffa3c7ae0c tomcat6-servlet-2.5-api-6.0.24-36.el6_2.noarch.rpm 4da49f3e1b0887b571a209eaf3f1905475aeb1fea95889db168068bcbf769939 tomcat6-webapps-6.0.24-36.el6_2.noarch.rpm Source: fd68b8c5cc07ed65b81e6d242c51b8001e4b215960b307282931f2ab05099ccb tomcat6-6.0.24-36.el6_2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 86, Issue 7 **********************************************

1 0

URGENT -- pseudo network interface creating problem with dhcp-- centos 5.5
by sri 12 Apr '12

12 Apr '12

Group, My linux box, running with Centos-5.5, is showing up (??) a pseudo network interface for Eth0. On Switch where my Eth0 is connected, observed 2 MAC-Addresses. If a DHCP server present in LAN, the second pseudo interface is picking up a DHCP IP Address too. Furthermore you can ping both Eth0 ip and Psedo Eth0 IP from the switch. The intensity of the problem is more when port-security is configured on SW for that port. “ifconfig –a” is not showing that pseudo interface. >From dmesg output, no new things observed related while detecting the eth0 NIC during bootup. Only proof for this pseudo inerface’s mac address is SW showing it (on the SW port connected to my box eth0) in “show mac address-table” output Is there anything that I have to check to nail down the issue. Any pointers are highly appreciated. -- -- Krishna Mohan B

6 9

quickly setting /etc/rc levels
by aurfalien 11 Apr '12

11 Apr '12

Hi all, I vaguely recall being able to auto set various /etc/rc levels based on /etc/init.d/scriptname. I am about to create the sym links by hand but wondering if any one has a shortcut to auto set the links? Thanks in advance, - aurf

3 3

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss