Discuss

discuss@lists.centos.org

34758 discussions

Need help resolving yum update issues on mixed architecture system
by Alfred von Campe 25 Feb '14

25 Feb '14

I have been using 32-bit CentOS since the 4.X days without a real need for 64-bit, but in preparation for CentOS 7, I have installed 64-bit CentOS 6 on a test system to qualify all our builds. However, in order to build some of our current 32-bit applications, I had to install some i686 packages, including glib. Now when I try to do a "yum update" on this test system, I get the dreaded "Error: Multilib version problems found." issue. I have tried following the instructions from yum (--exclude=glib.i686, yum check, etc.) to resolve this to no avail. What is the best way to proceed with the "yum update" so that all (64-bit and 32-bit) packages are updated? Thanks, Alfred

4 6

FYI: CentOS legalese
by jb 25 Feb '14

25 Feb '14

Putting the Genie Back in the Bottle: More RedHat Legal Shenanigans with CentOS http://nerdvittles.com/?p=8721 Closing the Book on CentOS: [...] http://nerdvittles.com/ Thanks to the author of the above articles. jb

6 5

Multicast packages dropped
by Uwe.Poliak＠amann.com 25 Feb '14

25 Feb '14

Hi, I have recently updated one of my systems from CentOs 6.4 to CentOS 6.5. This systems is used as a RIPv2 routing server with quagga which is the termination point of some GRE tunnels. While running CentOS 6.4 I see the multicast packages arriving at the eth0 and the GRE tunnel interface. While running under CentOs 6.5 I can see the multicast packages arriving at the eth0 but not on the GRE tunnel interface. I am receiving and sending routes at the eth0 interface, but I am only able to send updates through the GRE tunnel not receive them. All interfaces are multicast enabled: eth0 Link encap:Ethernet Hardware Adresse 00:50:56:B8:27:52 inet Adresse:10.139.10.2 Bcast:10.139.10.255 Maske:255.255.255.0 inet6 Adresse: fe80::250:56ff:feb8:2752/64 Gültigkeitsbereich:Verbindung UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7190594 errors:0 dropped:0 overruns:0 frame:0 TX packets:6209862 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:1000 RX bytes:2425775260 (2.2 GiB) TX bytes:2357002233 (2.1 GiB) net2bdo Link encap:UNSPEC Hardware Adresse 0A-8B-0A-02-FF-FF-E0-A4-00-00-00-00-00-00-00-00 inet Adresse:192.168.250.21 P-z-P:192.168.250.22 Maske:255.255.255.252 UP PUNKTZUPUNKT RUNNING NOARP MULTICAST MTU:1400 Metric:1 RX packets:118143 errors:7913 dropped:0 overruns:0 frame:7913 TX packets:115334 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:0 RX bytes:21714417 (20.7 MiB) TX bytes:32111515 (30.6 MiB) net2bdp Link encap:UNSPEC Hardware Adresse 0A-8B-0A-02-00-00-E0-18-00-00-00-00-00-00-00-00 inet Adresse:192.168.250.25 P-z-P:192.168.250.26 Maske:255.255.255.252 UP PUNKTZUPUNKT RUNNING NOARP MULTICAST MTU:1400 Metric:1 RX packets:78025 errors:7001 dropped:0 overruns:0 frame:7001 TX packets:85049 errors:0 dropped:0 overruns:0 carrier:0 Kollisionen:0 Sendewarteschlangenlänge:0 RX bytes:18388666 (17.5 MiB) TX bytes:38376786 (36.5 MiB) While doing a tcpdump (tcpdump –ni eth0 proto 47 | grep 224.0.0.9), I can see the multicast packages arriving inside the GRE tunnel (see last package): 10:40:34.366661 IP 10.139.10.2 > 192.168.252.26: GREv0, length 536: IP 192.168.250.25.router > 224.0.0.9.router: RIPv2, Response, length: 504 10:40:34.366680 IP 10.139.10.2 > 192.168.252.26: GREv0, length 536: IP 192.168.250.25.router > 224.0.0.9.router: RIPv2, Response, length: 504 10:40:34.366702 IP 10.139.10.2 > 192.168.252.26: GREv0, length 536: IP 192.168.250.25.router > 224.0.0.9.router: RIPv2, Response, length: 504 10:40:34.366721 IP 10.139.10.2 > 192.168.252.26: GREv0, length 356: IP 192.168.250.25.router > 224.0.0.9.router: RIPv2, Response, length: 324 10:40:39.830508 IP 192.168.252.26 > 10.139.10.2: GREv0, length 136: IP 192.168.250.26.router > 224.0.0.9.router: RIPv2, Response, length: 104 While doing the same on the Tunnel interface (tcpdump –ni net2bdp host 224.0.0.9), I do not see the incoming multicast packages any more: 10:42:32.391849 IP 192.168.250.25.router > 224.0.0.9.router: RIPv2, Response, length: 504 10:42:32.391887 IP 192.168.250.25.router > 224.0.0.9.router: RIPv2, Response, length: 504 10:42:32.391945 IP 192.168.250.25.router > 224.0.0.9.router: RIPv2, Response, length: 504 10:42:32.391975 IP 192.168.250.25.router > 224.0.0.9.router: RIPv2, Response, length: 324 I am using quagga 0.99.15 as the RIPv2 daemon. The configuration is as follows: Zebra.conf: interface eth0 multicast ipv6 nd suppress-ra ! interface net2xxx multicast ipv6 nd suppress-ra ! interface net2yyy multicast ipv6 nd suppress-ra ! ! ip forwarding ! Ripd.conf: ! key chain cis-xxx-yyyy key 1 key-string xxxxxx ! key chain cis-aaa-bbb key 1 key-string xxxxxx ! interface eth0 ip rip send version 2 ip rip receive version 2 ! interface net2xxx ip rip receive version 2 ip rip authentication mode md5 auth-length old-ripd ip rip authentication key-chain cis-xxx-yyy ! interface net2yyy ip rip receive version 2 ip rip authentication mode md5 auth-length old-ripd ip rip authentication key-chain cis-aaa-bbb ! router rip version 2 redistribute connected redistribute static network network-address-of -eth0/24 network network-address-of-net2xxx/30 network network-address-of-net2yyy/30 distribute-list incoming in distribute-list out-to-fw out eth0 distribute-list out-to-tunnel out net2xxx distribute-list out-to-tunnel out net2yyy ! access-list incoming permit 10.0.0.0/8 access-list incoming permit 172.16.0.0/12 access-list incoming permit 192.168.0.0/16 access-list incoming deny any access-list out-to-fw permit x.x.x.0/23 access-list out-to-fw permit x.x.0.0/16 access-list out-to-fw permit x.x.x.0/23 access-list out-to-fw permit x.x.x.0/24 access-list out-to-fw permit x.x.x.0/23 access-list out-to-tunnel deny y.y.0.0/16 access-list out-to-tunnel permit 10.0.0.0/8 access-list out-to-tunnel permit 172.16.0.0/12 access-list out-to-tunnel permit 192.168.0.0/16 access-list out-to-tunnel deny any ! line vty rip authentication is working as the routes are transmitted to the remote router but not from the remote router to the local server. The RIP or ZEBRA configuration were the same before the update (working) and after the update (no longer working). Has there be anything changed in multicast handling in combination with GRE tunnels with CentOS 6.5? Do you need any additional information? Mit freundlichen Grüßen / Kind regards Uwe Poliak AMANN GROUP IS – Information Systems, Technical Services Phone +49 7143 277-420, Fax +49 7143 277-901 420 E-Mail Uwe.Poliak(a)amann.com<mailto:Uwe.Poliak@amann.com> Amann & Soehne GmbH & Co. KG Hauptstrasse 1, 74357 Boennigheim – Germany www.amann.com<http://www.amann.com/> Kommanditgesellschaft Sitz Boennigheim; USt-IdNr. DE 144 960 031 Registergericht Stuttgart HRA 300309 Pers. Haftende Gesellschafterin: Amann Beteiligungen GmbH Sitz Boennigheim Registergericht Stuttgart HRB 301997 Geschaeftsfuehrer: Bodo Th. Boelzle (Vorsitzender), Wolfgang Findeis, Peter Morgalla

2 2

Problem with cron
by Joseph Hesse 25 Feb '14

25 Feb '14

I have a root cron job that powers down my server every day at 1am and 6pm. The output of '# crontab -l' is shown below. * 1,18 * * * poweroff Last night, after the server powered down at 6pm, I decided I wanted to use the server so I started it with the power button. The server, after a minute or so, powered itself down. This behaviour happened repeatedly until I waited past 7pm. Then the server did not poweroff. Apparently a cron job that executed correctly at 6pm was executing minutes past 6pm when the server was restarted. This is totally unexpected behavior. Here is the output of the cron log file. The name of the server has been redacted. # grep -i 'Feb 22' cron-20140223 | grep -i poweroff Feb 22 18:00:01 xxxxxxxxxx CROND[2875]: (root) CMD (poweroff) Feb 22 18:12:01 xxxxxxxxxx CROND[1894]: (root) CMD (poweroff) Feb 22 18:16:01 xxxxxxxxxx CROND[1893]: (root) CMD (poweroff) Feb 22 18:18:01 xxxxxxxxxx CROND[1896]: (root) CMD (poweroff) Feb 22 18:22:01 xxxxxxxxxx CROND[1915]: (root) CMD (poweroff) Feb 22 18:25:01 xxxxxxxxxx CROND[1919]: (root) CMD (poweroff) Feb 22 18:34:01 xxxxxxxxxx CROND[1890]: (root) CMD (poweroff) Is there a fix for this behavior? Thank you, Joe

3 3

Re: [CentOS] Monitor Wireless Networks OT
by Tom Bishop 25 Feb '14

25 Feb '14

On Thu, Feb 20, 2014 at 9:39 AM, Joseph Hesse <joehesse(a)gmail.com> wrote: > Hi, > I am having interference with my neighbouring wireless networks. > Is there a linux tool that enables me to monitor the ESSID, channel, > power output and other information for neighbouring wireless networks? > I am especially interested in the channel so I can choose a different one. > Thank you, > Joe > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > http://lists.centos.org/mailman/listinfo/centos > There is a really good Android app, WIFI analyzer https://play.google.com/store/apps/details?id=com.farproc.wifi.analyzer if you have access to a phone or better yet a tablet. Very nice and allows you to look at all kinds of things, I also know of another one called Wifi Radar for linux but not nears as good.

7 10

CentOS-announce Digest, Vol 108, Issue 13
by centos-announce-request＠centos.org 25 Feb '14

25 Feb '14

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. CEBA-2014:0198 CentOS 5 am-utils Update (Johnny Hughes) 2. CEBA-2014:0199 CentOS 6 psmisc Update (Johnny Hughes) 3. CEBA-2014:0203 CentOS 6 upstart Update (Johnny Hughes) 4. CEBA-2014:0201 CentOS 6 qt Update (Johnny Hughes) 5. CESA-2014:0206 Moderate CentOS 5 openldap Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Mon, 24 Feb 2014 12:03:01 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2014:0198 CentOS 5 am-utils Update To: centos-announce(a)centos.org Message-ID: <20140224120301.GA31143(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2014:0198 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-0198.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: fa262a7f55c06f92f03b7bca9dc49d48763243b25b0a7c22899f29ee48077f83 am-utils-6.1.5-9.el5_10.i386.rpm x86_64: 60833fa25ebea8ac74a6f6903dd067f05e53ee0e9c5cc46b63d3a7a1fd914a73 am-utils-6.1.5-9.el5_10.x86_64.rpm Source: 044f7106e95f814cdd9b0b1d82946d539ef57de1aa02916981d18080ae21fe42 am-utils-6.1.5-9.el5_10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Mon, 24 Feb 2014 12:09:21 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2014:0199 CentOS 6 psmisc Update To: centos-announce(a)centos.org Message-ID: <20140224120921.GA23977(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2014:0199 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-0199.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 1170157e8007a92b41414570564f664cd41e537ab066873ac013b5c8ae0cf223 psmisc-22.6-19.el6_5.i686.rpm x86_64: 4e9e713ea928bd50fa12eb6ad830dde2df2052eca085336f81ce512a8748edd6 psmisc-22.6-19.el6_5.x86_64.rpm Source: 9d372e6de68a5d29a0c00b4e0e665b772da0625273f4e377783b69f53437b508 psmisc-22.6-19.el6_5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 3 Date: Mon, 24 Feb 2014 14:27:09 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2014:0203 CentOS 6 upstart Update To: centos-announce(a)centos.org Message-ID: <20140224142709.GA28635(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2014:0203 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-0203.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 7106e07c74ae089bc82d0db6281d611767c1dee8174d8a501b0b23f715bb1760 upstart-0.6.5-13.el6_5.2.i686.rpm x86_64: d72256cdea3ac828edd342b768d1776147bb3a1b874cb0d72181b6244b54eb3a upstart-0.6.5-13.el6_5.2.x86_64.rpm Source: d3f220ea9b89d990704504a841c70f70ae57b46692876a628cc3881f612e1e99 upstart-0.6.5-13.el6_5.2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 4 Date: Mon, 24 Feb 2014 19:10:48 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CEBA-2014:0201 CentOS 6 qt Update To: centos-announce(a)centos.org Message-ID: <20140224191048.GA32015(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2014:0201 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-0201.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 727dc3b50f032ae08c8d130621aceb876cced3a08e182011d6f9c2dae1ea7c73 phonon-backend-gstreamer-4.6.2-28.el6_5.i686.rpm 1686e6fd2945f1f60a0ce1ebda82478df6e5add704ff53094f7229291696c37d qt-4.6.2-28.el6_5.i686.rpm e7c3aa1bca0836229870fc134639f8ae259a005c6ddeea485359e0eb8a933ffb qt-demos-4.6.2-28.el6_5.i686.rpm cf7ef9207864269a4d7883ffe7528fd00c72dafa5737e764dff7d3861377084c qt-devel-4.6.2-28.el6_5.i686.rpm 5f703f88837affd78d5fbc0b05fc5bf0d148ffeecc22712727f22cf11ef74e02 qt-doc-4.6.2-28.el6_5.noarch.rpm 2731f1ca31c1f6469f2a9d733e938fd2502bbcb163a84eb1f0b79dfe416ec010 qt-examples-4.6.2-28.el6_5.i686.rpm ffb305458cd1486a12cde230d9bd952177df23bc62f4b882e5c06963733ed241 qt-mysql-4.6.2-28.el6_5.i686.rpm 4749bee519b98cf8562b063f612d7bfba8c08e65841e5d3066f44ddb03e22bee qt-odbc-4.6.2-28.el6_5.i686.rpm 5ff539e2db4be62ec136fd5229593599b151c3e1586d6de4f84be9d23bd0702b qt-postgresql-4.6.2-28.el6_5.i686.rpm c8501d46f4ffcd00c5a5970b9972c7a75082755cdaaa1a905ba6016acf74a770 qt-sqlite-4.6.2-28.el6_5.i686.rpm 37ac4ce2721ed117a55453b99ac411e9a07801772f963f97737ed3c1b3a10f7b qt-x11-4.6.2-28.el6_5.i686.rpm x86_64: 727dc3b50f032ae08c8d130621aceb876cced3a08e182011d6f9c2dae1ea7c73 phonon-backend-gstreamer-4.6.2-28.el6_5.i686.rpm 8021cb284cbbd9d00900e973c2114405ddc9fc77bd68b419ef9fcdc15771157c phonon-backend-gstreamer-4.6.2-28.el6_5.x86_64.rpm 1686e6fd2945f1f60a0ce1ebda82478df6e5add704ff53094f7229291696c37d qt-4.6.2-28.el6_5.i686.rpm 84e3f84d7e79e1427872642b447d0b55c328c2a672290ab707dfc9ef3a140366 qt-4.6.2-28.el6_5.x86_64.rpm 6e66a68daa4f49bd27badca716c43ce953f9a83a9b502fa00988961c8fecfc99 qt-demos-4.6.2-28.el6_5.x86_64.rpm cf7ef9207864269a4d7883ffe7528fd00c72dafa5737e764dff7d3861377084c qt-devel-4.6.2-28.el6_5.i686.rpm aa0ee3a37dd6f8b3d5856146eec1ad56107c521376de8efd8449185b982e64f2 qt-devel-4.6.2-28.el6_5.x86_64.rpm 5f703f88837affd78d5fbc0b05fc5bf0d148ffeecc22712727f22cf11ef74e02 qt-doc-4.6.2-28.el6_5.noarch.rpm 9c3325346b36e34f1606c64a915d1fa980697f22ee99706c04bbd2559c5b7faa qt-examples-4.6.2-28.el6_5.x86_64.rpm ffb305458cd1486a12cde230d9bd952177df23bc62f4b882e5c06963733ed241 qt-mysql-4.6.2-28.el6_5.i686.rpm 7a43fbf4339b413d8936ed2cb55f7250213788c25d1510ec4f9d02f5fee85c1a qt-mysql-4.6.2-28.el6_5.x86_64.rpm 4749bee519b98cf8562b063f612d7bfba8c08e65841e5d3066f44ddb03e22bee qt-odbc-4.6.2-28.el6_5.i686.rpm d684b43ad68a25f3577239b665a20255d292fff7acfaabaca127571d3943c2ec qt-odbc-4.6.2-28.el6_5.x86_64.rpm 5ff539e2db4be62ec136fd5229593599b151c3e1586d6de4f84be9d23bd0702b qt-postgresql-4.6.2-28.el6_5.i686.rpm b1288c6b526092b641b044ebe68769b6c56affe268dd7f51e9036dbd74f00e66 qt-postgresql-4.6.2-28.el6_5.x86_64.rpm c8501d46f4ffcd00c5a5970b9972c7a75082755cdaaa1a905ba6016acf74a770 qt-sqlite-4.6.2-28.el6_5.i686.rpm 2dfd1adce9551aa453130c21bf6855ff56e8e4f5050b51976cba70b04b4864a3 qt-sqlite-4.6.2-28.el6_5.x86_64.rpm 37ac4ce2721ed117a55453b99ac411e9a07801772f963f97737ed3c1b3a10f7b qt-x11-4.6.2-28.el6_5.i686.rpm 2d9e0c2368254386685c5dca0418b7cc8a03189de26d62e3a066ae7cea7316ad qt-x11-4.6.2-28.el6_5.x86_64.rpm Source: e47a7f9cd170d887fd523562cffcf3bc679cc4453c27daebe5b1b7ed4efcad78 qt-4.6.2-28.el6_5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 5 Date: Mon, 24 Feb 2014 19:35:05 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2014:0206 Moderate CentOS 5 openldap Update To: centos-announce(a)centos.org Message-ID: <20140224193505.GA20599(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2014:0206 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0206.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 6cba76a0dd1ef32cc168ec8fe64e402e2c2db9d5a0497b99876d9f286bbfb287 compat-openldap-2.3.43_2.2.29-27.el5_10.i386.rpm 0a7d4df3156b7d9686e662c400355b0174f82b02a43e1794c2bc2ec0d96206b2 openldap-2.3.43-27.el5_10.i386.rpm ddea16bc11c802f55604e97b1c4c5d5317a5c85ff78b3422d1b5f3fbcef2c301 openldap-clients-2.3.43-27.el5_10.i386.rpm 5e3e08c8aefea27505bf109ccbfd19b33f3807a20965827ffdeebc048960e12d openldap-devel-2.3.43-27.el5_10.i386.rpm 11724a0d07a82379c6045d32073e42737a96b25bd041c1d2a27a0acb9c76d877 openldap-servers-2.3.43-27.el5_10.i386.rpm 5e8e8b9c9dae54af0aa9b4f9ba71fcc36c4eb47cd0fe001a32940a21b53658a5 openldap-servers-overlays-2.3.43-27.el5_10.i386.rpm 5039b10b8371fcc9633002d559a63c0c9b7241633394865b4b5ec3f6d1e3bd09 openldap-servers-sql-2.3.43-27.el5_10.i386.rpm x86_64: 6cba76a0dd1ef32cc168ec8fe64e402e2c2db9d5a0497b99876d9f286bbfb287 compat-openldap-2.3.43_2.2.29-27.el5_10.i386.rpm 71b46e2a5ff7dc75303c8e26c641f57025ece63f1c3d0afa5412abbefd348ffd compat-openldap-2.3.43_2.2.29-27.el5_10.x86_64.rpm 0a7d4df3156b7d9686e662c400355b0174f82b02a43e1794c2bc2ec0d96206b2 openldap-2.3.43-27.el5_10.i386.rpm 81f2f34f57d9e5f02e18e715e52b195455ebaef3ea3e5dafa01d7ff9c0065042 openldap-2.3.43-27.el5_10.x86_64.rpm 4c55b52a0aac0009d5c0ccc1a5115c7a7e676ce28c16aeba8c0183d5a239ca25 openldap-clients-2.3.43-27.el5_10.x86_64.rpm 5e3e08c8aefea27505bf109ccbfd19b33f3807a20965827ffdeebc048960e12d openldap-devel-2.3.43-27.el5_10.i386.rpm d56b74a85f04312b8f2a04c734efc38fee4f7dda5f5cce0d62bd0c3b3973bc8a openldap-devel-2.3.43-27.el5_10.x86_64.rpm c330bf7fac71a862f08e14c689c2826a6411fb7d778cef2c8ed99d89c2b968dd openldap-servers-2.3.43-27.el5_10.x86_64.rpm 58c3cf4506d89abb7a3ef5404cc29659d3c3777edb87f1d39a66b676d6cc5252 openldap-servers-overlays-2.3.43-27.el5_10.x86_64.rpm 9b9ae74620fc2059090f9119609c706197f3c42ac02921c5220545c80694fbfd openldap-servers-sql-2.3.43-27.el5_10.x86_64.rpm Source: cbbbf8778b574b1b050f45a9e9576914442ab52a129a5952c689b7fa7bc5131f openldap-2.3.43-27.el5_10.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 108, Issue 13 ************************************************

1 0

KVM and Win7-64 Sound
by david 25 Feb '14

25 Feb '14

Dear Gurus I have been unable to make sound (and microphone) work in Windows 7 (64-bit) as a VM with KVM. Google searches reveal this to be a common problem, with various solutions recommended, primarily Ubuntu oriented, none of which have worked for me. So I wonder if anyone has a working Windows sound condition with: Centos 6.5 with KVM, all on a 64-bit Intel platform. Sound works on the host machine, verified when I switch into GUI mode and run a sound-producing program Sound does not work in the Windows 7 (64-bit) PRO installation as a Virtual Machine, and I have tried specifying the emulated hardware as AC97, and ICH6. Any working examples? David

2 1

Changing from samba 3.0.33 to Samba 3,6,6
by Timothy Kesten 24 Feb '14

24 Feb '14

Hi Folks, I'd like to change from Samba 3.0.33 to 3.6.6. Reason: WINDOWS 7 and PDC Is something to consider when changing (config-Files or so on)? Have I to uninstall Samba 3.0.33 before or just run an update? Thx for hints. Timothy

2 1

Cange from Samba 3.0 to samba 3 3.6.6
by Timothy Kesten 24 Feb '14

24 Feb '14

Hi Folks, I'd like to change from Smaba 3.0.33 to 3.6.6. Reason: WINDOWS 7 and PDC Is something to consider when changing (config-Files or so on)? Have I to uninstall Samba 3.0.33 before or just run an update? Thx for hints. Timothy

1 0

Growing HW RAID arrays, Online
by Billy Crook 24 Feb '14

24 Feb '14

We add disks to an LSI raid array periodically to increase the amount of available space for business needs. It is understood that this process starts with metal, and has many layers that must each adjust to make use of the additional space. Each of these layers also says that it can do that 'online' without interruption or rebooting. But making it happen is not that easy. When the HW raid controller's grow completes, we echo 1 to /sys/bus/scsi/devices/#:#:#:#/rescan and the kernel notices and updates the size of the block device. (sdc in this case) sdc1 is the only partition on the device, and should consume the entire device. sdc1 is a PV in a VG that holds production data and must not become unavailable at any time. After growing sdc as mentioned earlier, parted notices that the end-of-drive partition table is missing, fixes it, and grows its disk size to match the new size of sdc. It all makes sense up to this point. but what happens next is what I need some advice on. How do we grow sdc1, online? parted says it doesn't support 'resize' on the filesystem (LVM PV). The usual answer to parted's lack of support for filesystems, and insistence to only resize partitions when it can stick its nose in the filesystem and do that too is: parted sdc rm 1, parted mkpart primary 0% 100% (thus making a new partition "Around" the old one) That should work, but I can't get the kernel to 'notice' that sdc1 is now larger. hdparm -z barfs up an error that sdc is in use. I know that rebooting likely will fix it. But we cannot reboot. We also cannot keep making more partitions every time we add a disk. So that's not a solution either. We need to GROW the gpt partitions online, or use another partitioning type that supports >6TB I've googled it for hours and found no good solutions. This same situation would affect VMs with virtual disks that grow over time to satisfy business needs, as well as servers mounting iSCSI/FC storage that grows over time. How would you grow this online? Going without partitions at all and putting the pv directly on sdc is no good either. So we need partitions, and msdos tables don't support >2TB and the only other in practical use that I know of is gpt, and thse aparently can't expand online! Here's where I'm at now in case you're curious [root@host lib]# parted /dev/sdc unit s print free Model: SMC SMC2108 (scsi) Disk /dev/sdc: 8189439999s Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags 1 34s 8189439966s 8189439933s primary Information: Don't forget to update /etc/fstab, if necessary. [root@host lib]# cat /sys/bus/scsi/devices/0\:2\:2\:0/block\:sdc/size 8189440000 [root@host lib]# cat /sys/bus/scsi/devices/0\:2\:2\:0/block\:sdc/sdc1/size 7019519933 # I bet the above 7billion will be around 8billion at the next reboot. (Each physical disk has about a billion sectors -- Billy Crook * Network and Security Administrator * RiskAnalytics, LLC

6 10

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