August 2017 - Discuss - lists.centos.org

Updated Apache httpd packages?
by Erik Osterholm 24 Aug '17

24 Aug '17

I'm concerned about the vulnerability at https://access.redhat.com/ errata/RHSA-2017:2479 I see via https://lists.centos.org/pipermail/centos-announce/ 2017-August/022518.html that Centos 6 has received the fix for this. Is there a roadmap for when Centos 7 will receive the fix? Thanks!

5 9

CentOS-announce Digest, Vol 150, Issue 3
by centos-announce-request＠centos.org 24 Aug '17

24 Aug '17

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://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-2017:2506 CentOS 6 dhcp BugFix Update (Johnny Hughes) 2. CEBA-2017:2504 CentOS 6 kernel BugFix Update (Johnny Hughes) 3. CEBA-2017:2501 CentOS 6 acl BugFix Update (Johnny Hughes) 4. CEBA-2017:2502 CentOS 6 java-1.8.0-openjdk BugFix Update (Johnny Hughes) 5. CEBA-2017:2503 CentOS 6 samba BugFix Update (Johnny Hughes) 6. CEEA-2017:2500 CentOS 6 unbound Enhancement Update (Johnny Hughes) 7. CEBA-2017:2505 CentOS 6 sssd BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Wed, 23 Aug 2017 18:00:06 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2017:2506 CentOS 6 dhcp BugFix Update Message-ID: <20170823180006.GA12741(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2017:2506 Upstream details at : https://access.redhat.com/errata/RHBA-2017:2506 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 31d4b1e77ecd473cfae41fbf4216158cc9b923d553556d412e637ff2fa8cec47 dhclient-4.1.1-53.P1.el6.centos.1.i686.rpm c35277ba2644e77feb9984275cd871a9e632e0392b9d332e0a85827e7906d1aa dhcp-4.1.1-53.P1.el6.centos.1.i686.rpm d35c82ff2e3d02889531fd6adb737c11890758c2252ad1cc85f11cd871a4e24a dhcp-common-4.1.1-53.P1.el6.centos.1.i686.rpm 9a0feab0407cb62c42d6e3d2488a0ec9a00c1812117bf9ff591742b3f578fc3c dhcp-devel-4.1.1-53.P1.el6.centos.1.i686.rpm x86_64: 1a5b9ef938292a1b272db6a52a341cb4cf470d78c9ee44b999b66837797a1c5c dhclient-4.1.1-53.P1.el6.centos.1.x86_64.rpm 069cbc470f4d064b759f1573f74102667aae852b3efc7c3999f5322f3f559e16 dhcp-4.1.1-53.P1.el6.centos.1.x86_64.rpm 6570ee68e9333cbf9698863b2ce4b90f3bd3135c27b537e78d0506b7673a4792 dhcp-common-4.1.1-53.P1.el6.centos.1.x86_64.rpm 9a0feab0407cb62c42d6e3d2488a0ec9a00c1812117bf9ff591742b3f578fc3c dhcp-devel-4.1.1-53.P1.el6.centos.1.i686.rpm 27b4ec55bae530671a45a52a54c84c175cb5d7d2169ac0a5b465ec9ea2b15f31 dhcp-devel-4.1.1-53.P1.el6.centos.1.x86_64.rpm Source: 904fbae9672602a5e167a228ea712b71460e2a1f705ef0922b5bbec9559dd9cf dhcp-4.1.1-53.P1.el6.centos.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Wed, 23 Aug 2017 18:01:56 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2017:2504 CentOS 6 kernel BugFix Update Message-ID: <20170823180156.GA13196(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2017:2504 Upstream details at : https://access.redhat.com/errata/RHBA-2017:2504 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 36f1caaa6c48a78430998ec9d682c77fc9df21d9a83304552120556ecd6422a4 kernel-2.6.32-696.10.1.el6.i686.rpm 8608dcfbc36435abd0c53888bf4cf42bef1d3b6db0d3a40c5f4d8deaf468f5be kernel-abi-whitelists-2.6.32-696.10.1.el6.noarch.rpm 045fb48f38b4cecf54daaa5592d9a02f69df0208cac0469c205649f2aa62969f kernel-debug-2.6.32-696.10.1.el6.i686.rpm 29f13703c00dbda98959ed95dea17d8af796b5b19a92b61c73c76def3cb73573 kernel-debug-devel-2.6.32-696.10.1.el6.i686.rpm d76cfa1de782160933f03fe983d9f65bf3c6d8a19ba3a493f17b503617c9fd91 kernel-devel-2.6.32-696.10.1.el6.i686.rpm b67a79c5f7f1ab3ee4901179c10a2ed752224ae8cc3372052bedef807993ce0a kernel-doc-2.6.32-696.10.1.el6.noarch.rpm 4fd75de3d8f4695b54c95fd530311ecec385197c7439312afb2f47562a63c18f kernel-firmware-2.6.32-696.10.1.el6.noarch.rpm b965f76a4170f1acd67eb026745c1cec18a05d7613059face9391081e2d9269b kernel-headers-2.6.32-696.10.1.el6.i686.rpm 575fb150297a97b200d17a562b87c117058c914162fb2e0065d05a0715f14a87 perf-2.6.32-696.10.1.el6.i686.rpm 45119a13d91a6e388f7a421c8b6608cfc5240c98de6d459a4c26b18d25960799 python-perf-2.6.32-696.10.1.el6.i686.rpm x86_64: c3354e273a4502253f6bb47dac4a6651c3248e62b3e367ddec7410115f146647 kernel-2.6.32-696.10.1.el6.x86_64.rpm 8608dcfbc36435abd0c53888bf4cf42bef1d3b6db0d3a40c5f4d8deaf468f5be kernel-abi-whitelists-2.6.32-696.10.1.el6.noarch.rpm a8d900bcedce07d2df857a9cf8fa2e9e1069d2e5c4b975ef711e0225448ac725 kernel-debug-2.6.32-696.10.1.el6.x86_64.rpm 29f13703c00dbda98959ed95dea17d8af796b5b19a92b61c73c76def3cb73573 kernel-debug-devel-2.6.32-696.10.1.el6.i686.rpm 09dbd4bd464ac4ef723b6cae81013bc40fccf8aecccdaff38e7a875ebc53a674 kernel-debug-devel-2.6.32-696.10.1.el6.x86_64.rpm af3867adb5216dbf71f3c9c126cf0de06996767ef65c05f0786c0210c9a0125e kernel-devel-2.6.32-696.10.1.el6.x86_64.rpm b67a79c5f7f1ab3ee4901179c10a2ed752224ae8cc3372052bedef807993ce0a kernel-doc-2.6.32-696.10.1.el6.noarch.rpm 4fd75de3d8f4695b54c95fd530311ecec385197c7439312afb2f47562a63c18f kernel-firmware-2.6.32-696.10.1.el6.noarch.rpm b496b65ca47516f47ea820c11ee7909f3147af4c1576cd0a06e8823c8d5e67e9 kernel-headers-2.6.32-696.10.1.el6.x86_64.rpm 19a1513d18dbbdafc6982b24b6346c77539b1cc1a8cdb2771b73808ee7e15293 perf-2.6.32-696.10.1.el6.x86_64.rpm f3f19f3b992692f8910046499b26773b025e8e0b5b501ceb39f6f91c6b4da9bf python-perf-2.6.32-696.10.1.el6.x86_64.rpm Source: 63c595b74270700871b44133cabae13243117cd858fddd66d0589d875eb1509f kernel-2.6.32-696.10.1.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Wed, 23 Aug 2017 18:02:41 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2017:2501 CentOS 6 acl BugFix Update Message-ID: <20170823180241.GA13450(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2017:2501 Upstream details at : https://access.redhat.com/errata/RHBA-2017:2501 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 56c8bd71d132223a86492533476fe9ff37c5ba7c09e21b5927a9efd5b2d717dd acl-2.2.49-7.el6_9.1.i686.rpm fdd9e75884a47e8ef4ebc8552e907cd27405f6e9efbb2be773dcae07c01fc294 libacl-2.2.49-7.el6_9.1.i686.rpm 48295e81557752bcce96dd7271fe5234560db841fe309a732a7e5810323e209c libacl-devel-2.2.49-7.el6_9.1.i686.rpm x86_64: 3afaabd15713abab6adc5033f35b9db225e792d651e42199d59c8444695893a5 acl-2.2.49-7.el6_9.1.x86_64.rpm fdd9e75884a47e8ef4ebc8552e907cd27405f6e9efbb2be773dcae07c01fc294 libacl-2.2.49-7.el6_9.1.i686.rpm 2d2bb216ec706020dd82ddb7f0971d799161d3e7fb35937e14eb1a77a8c183e0 libacl-2.2.49-7.el6_9.1.x86_64.rpm 48295e81557752bcce96dd7271fe5234560db841fe309a732a7e5810323e209c libacl-devel-2.2.49-7.el6_9.1.i686.rpm 32b91ef60f2813d8275e0b87dd8193efcc515f71a8fdc54f306ee334bc55ab95 libacl-devel-2.2.49-7.el6_9.1.x86_64.rpm Source: 5ce6a3887fb3a2026f08ba2dcfe43861c564fdcf2ba330d70701abb25f4a2a19 acl-2.2.49-7.el6_9.1.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Wed, 23 Aug 2017 18:03:38 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2017:2502 CentOS 6 java-1.8.0-openjdk BugFix Update Message-ID: <20170823180338.GA13875(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2017:2502 Upstream details at : https://access.redhat.com/errata/RHBA-2017:2502 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 29aa47221ed0af8e6682de084d4540d06c601a6c0de5c9b2cb4f0d7bbb218262 java-1.8.0-openjdk-1.8.0.141-3.b16.el6_9.i686.rpm 82e16e5070e31a9020997eba9b93b147edc625bd0de2e786f847297de1a3074a java-1.8.0-openjdk-debug-1.8.0.141-3.b16.el6_9.i686.rpm 62574067c088c23c6d955b6c633645b483e5d339d36c3da5c9a83e7a45316c22 java-1.8.0-openjdk-demo-1.8.0.141-3.b16.el6_9.i686.rpm efe75fdda3527e508b612992da6d4802f9da71eedc8ac16939f94b29082de8a1 java-1.8.0-openjdk-demo-debug-1.8.0.141-3.b16.el6_9.i686.rpm 9fdb6873649450892fda86320a97cfea4991ce997ece1968a058adead1305cee java-1.8.0-openjdk-devel-1.8.0.141-3.b16.el6_9.i686.rpm b6705809d914d7dfdb47de13e99924cfae3915b5f3857ea77d21323874361a44 java-1.8.0-openjdk-devel-debug-1.8.0.141-3.b16.el6_9.i686.rpm b5f2badc5bf4b10129a99a10a653e6abc4b2098fac4f5a6b5e521edd603d9eed java-1.8.0-openjdk-headless-1.8.0.141-3.b16.el6_9.i686.rpm 0a0663ac988035cf801a7446053555d09fbe4ced45e97152e0f9efd439323889 java-1.8.0-openjdk-headless-debug-1.8.0.141-3.b16.el6_9.i686.rpm 697147e970a7f210014853ad4a292c6ce00de1f09338d2cbb1bada2a1dea6aeb java-1.8.0-openjdk-javadoc-1.8.0.141-3.b16.el6_9.noarch.rpm ced0c9be3af069982b0bb2b491df0f12f90fe9230425f3150ac7974a35e09784 java-1.8.0-openjdk-javadoc-debug-1.8.0.141-3.b16.el6_9.noarch.rpm 1f3df35edddb81c4f8df5ed438cb8692d8a2395e3e8b9b198c4f7e76567c5cde java-1.8.0-openjdk-src-1.8.0.141-3.b16.el6_9.i686.rpm 36dd102f5166929c45675f3e0b4f44167e851663fb909ce2152d59813463bc33 java-1.8.0-openjdk-src-debug-1.8.0.141-3.b16.el6_9.i686.rpm x86_64: bcef0720030aa7686ac1d05487e4944ed75328f20e5e07af087fc6e9537b123f java-1.8.0-openjdk-1.8.0.141-3.b16.el6_9.x86_64.rpm 031f02121c2e2f5577e2124787f7df0465fe739ba622be843ee6df2299fc0ec7 java-1.8.0-openjdk-debug-1.8.0.141-3.b16.el6_9.x86_64.rpm eb17cf3738d447bedb2aa8fb839ba7060d6c65b261ef9ddb989df0146528e42b java-1.8.0-openjdk-demo-1.8.0.141-3.b16.el6_9.x86_64.rpm f97cc7d63f151e26b5e622094e744462d83fe0f390664bd8fa7b39bcaac4df56 java-1.8.0-openjdk-demo-debug-1.8.0.141-3.b16.el6_9.x86_64.rpm 4844af6c9421c0530f3339a3c41dcabad174297866993cb7e7db26ba776250e9 java-1.8.0-openjdk-devel-1.8.0.141-3.b16.el6_9.x86_64.rpm c1ee5081c1347aabab55c11df2af0d0c86302ce2b08fa0a712adbaa41481c00d java-1.8.0-openjdk-devel-debug-1.8.0.141-3.b16.el6_9.x86_64.rpm 3bc5f354c12f7b6cfb99a4744ba466aa9d734d994a6474538fa6adc29d25414e java-1.8.0-openjdk-headless-1.8.0.141-3.b16.el6_9.x86_64.rpm af993d0a3e481916d29a621549a87a05c8ce9b4ff800e20a2b3f0f17a3e4b05d java-1.8.0-openjdk-headless-debug-1.8.0.141-3.b16.el6_9.x86_64.rpm 697147e970a7f210014853ad4a292c6ce00de1f09338d2cbb1bada2a1dea6aeb java-1.8.0-openjdk-javadoc-1.8.0.141-3.b16.el6_9.noarch.rpm ced0c9be3af069982b0bb2b491df0f12f90fe9230425f3150ac7974a35e09784 java-1.8.0-openjdk-javadoc-debug-1.8.0.141-3.b16.el6_9.noarch.rpm 60e766a44b71709b81024f3449f9d0a58a28f57ef8a2478b66fd021bda4b3ca4 java-1.8.0-openjdk-src-1.8.0.141-3.b16.el6_9.x86_64.rpm 213d25f86aae1878a802e2281897d38f09624e4ef42dcf0aefbbaf056b1b37d3 java-1.8.0-openjdk-src-debug-1.8.0.141-3.b16.el6_9.x86_64.rpm Source: 2f5bf796b01b62d0f84d5f162ccd24689e6195379a761db829c176d292504d3f java-1.8.0-openjdk-1.8.0.141-3.b16.el6_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 5 Date: Wed, 23 Aug 2017 18:04:15 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2017:2503 CentOS 6 samba BugFix Update Message-ID: <20170823180415.GA14358(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2017:2503 Upstream details at : https://access.redhat.com/errata/RHBA-2017:2503 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 87269f714a65dd129fca8497dd8b037337fb99868de85c4a429b42d9f13bd0d2 libsmbclient-3.6.23-44.el6_9.i686.rpm 7010b7851ad11bf90b6c804f3ad163e148ebdce72e0ffa2707f5e47564398bc6 libsmbclient-devel-3.6.23-44.el6_9.i686.rpm e9c2f8f869542a0ad4aaacf1bb2ebd95ba1aeb2b9866ad204964b12f2d9a0915 samba-3.6.23-44.el6_9.i686.rpm 2e6d7682d23d823b2b791245497532f72fb07cc7f719eae622eb9542b60c8beb samba-client-3.6.23-44.el6_9.i686.rpm e61cd439e12710eb6af6a65bd0146716afed4be2f6da933ef36f54f584cbb146 samba-common-3.6.23-44.el6_9.i686.rpm 73eddc6e1b6d13601df165a93a60345057a8cf0442d172e51405533636db5795 samba-doc-3.6.23-44.el6_9.i686.rpm e8c2763e776470aa92d6fdfbf89fa24bceeaa4ea169967e343868765fcd570dd samba-domainjoin-gui-3.6.23-44.el6_9.i686.rpm 674c4f38741bb2c92a2fc99d7ec993fc65d787116b3e7b54bebbddf97dfa72a3 samba-swat-3.6.23-44.el6_9.i686.rpm 05fa3c1e498572c70a66c960330663843d127adfa2c8624e10e306e1f6c3862b samba-winbind-3.6.23-44.el6_9.i686.rpm b2bb5fa267c592a950d31987d493552f144894f66261ad7cb647a3ef78b544e4 samba-winbind-clients-3.6.23-44.el6_9.i686.rpm cc45242631859f54be41370195540ac2526d12b861dd338af94ee6329c01b50c samba-winbind-devel-3.6.23-44.el6_9.i686.rpm 17d40cdb7f23806604bd5808986bd5b4dfd883fb49aed3b3374e884cff4aec8c samba-winbind-krb5-locator-3.6.23-44.el6_9.i686.rpm x86_64: 87269f714a65dd129fca8497dd8b037337fb99868de85c4a429b42d9f13bd0d2 libsmbclient-3.6.23-44.el6_9.i686.rpm 9ba6b7253311bfed18bb3523849a92b31d755dfae228acaec53144079f491221 libsmbclient-3.6.23-44.el6_9.x86_64.rpm 7010b7851ad11bf90b6c804f3ad163e148ebdce72e0ffa2707f5e47564398bc6 libsmbclient-devel-3.6.23-44.el6_9.i686.rpm 77e46d8910bfceb778676cbba018cf2a40295321d592418202c5af269cb1b8cf libsmbclient-devel-3.6.23-44.el6_9.x86_64.rpm 21018e8fe062e1589d484cb208a6f90dc03e7e69c895af2e01a158879942a122 samba-3.6.23-44.el6_9.x86_64.rpm cd1277c4736080daf752f69651edab8aea20b49f1ed2dc93ab43558266f92c13 samba-client-3.6.23-44.el6_9.x86_64.rpm e61cd439e12710eb6af6a65bd0146716afed4be2f6da933ef36f54f584cbb146 samba-common-3.6.23-44.el6_9.i686.rpm 28c2dfe75c2b510abb31fd29c5f92878d878aab839ac7d7c3d77c286846d33cf samba-common-3.6.23-44.el6_9.x86_64.rpm 1bc5b16aa7f71146a4b523d3d1c0684287de5e1e9b539dff8b14b7573876d28a samba-doc-3.6.23-44.el6_9.x86_64.rpm 27189348fedd2b1be13f64f792c594ee1007f6c12dae96af4e47bfb33634f670 samba-domainjoin-gui-3.6.23-44.el6_9.x86_64.rpm e23a85368e28e90c1491aff86b9bffa0863ca7a30e9830c878f88432e68add28 samba-glusterfs-3.6.23-44.el6_9.x86_64.rpm f4755292e85ff60bb0b039b18fe193e69be40ad26d1b390629b95a48c48ca58b samba-swat-3.6.23-44.el6_9.x86_64.rpm 500229f658d887638590fb05c6bca7b43868f40cf7032538c92d211ac3aa5c5c samba-winbind-3.6.23-44.el6_9.x86_64.rpm b2bb5fa267c592a950d31987d493552f144894f66261ad7cb647a3ef78b544e4 samba-winbind-clients-3.6.23-44.el6_9.i686.rpm ff1deaa1f55f103d7f02d352cdc142bb5306bbb4ee821dcac95d45165431cfbb samba-winbind-clients-3.6.23-44.el6_9.x86_64.rpm cc45242631859f54be41370195540ac2526d12b861dd338af94ee6329c01b50c samba-winbind-devel-3.6.23-44.el6_9.i686.rpm 1488541aa150dd17c739144146acb975bd4f4565c1c9d424d6b02262d2e69d22 samba-winbind-devel-3.6.23-44.el6_9.x86_64.rpm ca71de881c47e6eb18d6742d698a38789d022e5b0624df21ed655dc8dd91aa36 samba-winbind-krb5-locator-3.6.23-44.el6_9.x86_64.rpm Source: 19c9c2264fc0813d95442abc9358c34387b4760204e1318487bb9919a1470756 samba-3.6.23-44.el6_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 6 Date: Wed, 23 Aug 2017 18:04:36 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2017:2500 CentOS 6 unbound Enhancement Update Message-ID: <20170823180436.GA14632(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2017:2500 Upstream details at : https://access.redhat.com/errata/RHEA-2017:2500 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 2fac524811e1dbf01a6cd6bd931d4628a5adba2d20d0cd97f0cb342ea064b8b3 unbound-1.4.20-23.el6_9.4.i686.rpm ed1ce6f7b787138dd29af1064ce5046fa6fa49c0849f6facf1cc683ec1c61cdb unbound-devel-1.4.20-23.el6_9.4.i686.rpm 929982cc3197d5bfa6b770bace24e395a14ec98ff4e4db3377da3a2c29db32cf unbound-libs-1.4.20-23.el6_9.4.i686.rpm 46e553a20ee09820c08415a89ad3a5be5c978c1794ca2419caf913737183dd02 unbound-python-1.4.20-23.el6_9.4.i686.rpm x86_64: b870310bbc3ed3d0386e25b3bf72be92d256032c2c272a5ac3e94d109fddb661 unbound-1.4.20-23.el6_9.4.x86_64.rpm ed1ce6f7b787138dd29af1064ce5046fa6fa49c0849f6facf1cc683ec1c61cdb unbound-devel-1.4.20-23.el6_9.4.i686.rpm cd93e772f13decfbcd5ee60ead21d04d7a734a22370b1c83e185f75ab2465d07 unbound-devel-1.4.20-23.el6_9.4.x86_64.rpm 929982cc3197d5bfa6b770bace24e395a14ec98ff4e4db3377da3a2c29db32cf unbound-libs-1.4.20-23.el6_9.4.i686.rpm b9991f293eddceba22b2cd66e15f451ddb4338fb3fcf1811f728fc640dcf4074 unbound-libs-1.4.20-23.el6_9.4.x86_64.rpm 46e553a20ee09820c08415a89ad3a5be5c978c1794ca2419caf913737183dd02 unbound-python-1.4.20-23.el6_9.4.i686.rpm 73f0e380f4a8e9e75439325e0ed9cb3371fecdbaaea6ae1fa6e4485f1f0d4797 unbound-python-1.4.20-23.el6_9.4.x86_64.rpm Source: 5e5a69b22ec6f36c6c3263d665855e11ee7c28cf339120ae15d16bcc45cf9eec unbound-1.4.20-23.el6_9.4.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 7 Date: Wed, 23 Aug 2017 18:06:11 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2017:2505 CentOS 6 sssd BugFix Update Message-ID: <20170823180611.GA15460(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2017:2505 Upstream details at : https://access.redhat.com/errata/RHBA-2017:2505 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: a13401b5a68e93e194fa862f3502ad7c93976151e61df31543612279904316d4 libipa_hbac-1.13.3-57.el6_9.i686.rpm 7f12b9d12a0ea77382b0d3b776d77b04d5a2e4945ef022e33007074216de3dcb libipa_hbac-devel-1.13.3-57.el6_9.i686.rpm 5038172ca941498feae2da10afdd3c3196f2a7d9be0f1bac583fb38c085df10f libsss_idmap-1.13.3-57.el6_9.i686.rpm 5657074aafc12930b7c43e1221555cf76175052dfa5cf0b054d0ce6a0e27ce47 libsss_idmap-devel-1.13.3-57.el6_9.i686.rpm 701993ad8ce2dd85022d74a2ddc0c393b4f3675cd8635e5692f8bfd3214f0213 libsss_nss_idmap-1.13.3-57.el6_9.i686.rpm e33158734216b89323680ab4b23ed7ee51ca50ac9804cf34a1470fe04e50d1da libsss_nss_idmap-devel-1.13.3-57.el6_9.i686.rpm ad5ac6f7439d62997536b84755e20b7688913a3b4fd04afe622ba4f8c4fa8dd5 libsss_simpleifp-1.13.3-57.el6_9.i686.rpm 26a9d7d29a9c5bb89da20ac0774b8bb80cac735faddc44bd41e07baab8f0e1ed libsss_simpleifp-devel-1.13.3-57.el6_9.i686.rpm d5cc77c29545b83ff183425acd004c6149c0a60eacb0e811391d49c107602cd2 python-libipa_hbac-1.13.3-57.el6_9.i686.rpm e0c4ec8e31dd30b28079f628cab53e5f9940b067288c22c3f029e774829f09d4 python-libsss_nss_idmap-1.13.3-57.el6_9.i686.rpm 29f3a7938d5b30a99b6a8aee70499a1643a8a63dcca8c944b692947ece5c784e python-sss-1.13.3-57.el6_9.i686.rpm c7b8df5b47960010dcd0b9464e17f8df42205f739754816573d5c8d5f58a330d python-sssdconfig-1.13.3-57.el6_9.noarch.rpm d1d7f68a5b700a7599129c12f7c7aeae764536631cd988b211a9cf9521eaed2b python-sss-murmur-1.13.3-57.el6_9.i686.rpm d3b70d514a3e7a3c8b5ccb654718bd8ae829371ccf4dcb7f9d22a2a9b29bc45a sssd-1.13.3-57.el6_9.i686.rpm 2fe9180dc9ec9b552890a5ada4445e48353573e1b47b9db508125d5602a44383 sssd-ad-1.13.3-57.el6_9.i686.rpm 0e18519ce4ec99044ddfc9b2f16bbcba96057a078ebbd8c9544c06e351d36d66 sssd-client-1.13.3-57.el6_9.i686.rpm 532039b14de6f3b8fc11e516ea25810ed419acd28d4843bf842b9c219f1e82e5 sssd-common-1.13.3-57.el6_9.i686.rpm 9199a323b752c421afde17234ae1232a442ef4d49cb06033d8741995270d9ce4 sssd-common-pac-1.13.3-57.el6_9.i686.rpm c733c43f0a22930700bb0d46e4cd57293e9335f9bff49180edb43f4ec2c1c3ac sssd-dbus-1.13.3-57.el6_9.i686.rpm 6783419d96794196655edaa9171e8022cd052ef52062f494e712c741a358bb92 sssd-ipa-1.13.3-57.el6_9.i686.rpm 7bde1eb73e97da65079b7ea00f144b033ad7ad57b29d918db06913e2daea2ed7 sssd-krb5-1.13.3-57.el6_9.i686.rpm e1f422785b790cb6ff7278543799ab5518e6d3347c6d14688b0d13b30e52ddd2 sssd-krb5-common-1.13.3-57.el6_9.i686.rpm 4ed9ee3cf8b2bcd81bc638af7394b96686b9605949c2e2c0a42e20bee07759a5 sssd-ldap-1.13.3-57.el6_9.i686.rpm 8bcf5312b87932b4d7c2f6b8b45fe48faca924e90e1c244d81d410899d979c40 sssd-proxy-1.13.3-57.el6_9.i686.rpm 81bcb25b9f2ae1ed30456741db7df9a37c1a0405555614a7b5ae95a2bd44dd5e sssd-tools-1.13.3-57.el6_9.i686.rpm x86_64: a13401b5a68e93e194fa862f3502ad7c93976151e61df31543612279904316d4 libipa_hbac-1.13.3-57.el6_9.i686.rpm 9115fd0f410b9c54c12ef053717bc785c0a57c4e4c9142dd79215db39c7ef5b1 libipa_hbac-1.13.3-57.el6_9.x86_64.rpm 7f12b9d12a0ea77382b0d3b776d77b04d5a2e4945ef022e33007074216de3dcb libipa_hbac-devel-1.13.3-57.el6_9.i686.rpm cc15202f7287617ead9e33088307ca232d69205367bcfc48b629b4257be2bce2 libipa_hbac-devel-1.13.3-57.el6_9.x86_64.rpm 5038172ca941498feae2da10afdd3c3196f2a7d9be0f1bac583fb38c085df10f libsss_idmap-1.13.3-57.el6_9.i686.rpm 22509a00ea3a552a38a2fbe1fcd3d52aaf1fab61a88829529d0cdec4393991f9 libsss_idmap-1.13.3-57.el6_9.x86_64.rpm 5657074aafc12930b7c43e1221555cf76175052dfa5cf0b054d0ce6a0e27ce47 libsss_idmap-devel-1.13.3-57.el6_9.i686.rpm 8c5b2dbfe15941133e9dc6b9f04651f8fd6907a201a9321bc29a51f0a2ee06c6 libsss_idmap-devel-1.13.3-57.el6_9.x86_64.rpm 701993ad8ce2dd85022d74a2ddc0c393b4f3675cd8635e5692f8bfd3214f0213 libsss_nss_idmap-1.13.3-57.el6_9.i686.rpm a7077dc3b6b7a12044ee0b6788e182cb9a5ab48450c5127c7bb5ab62ce340ff4 libsss_nss_idmap-1.13.3-57.el6_9.x86_64.rpm e33158734216b89323680ab4b23ed7ee51ca50ac9804cf34a1470fe04e50d1da libsss_nss_idmap-devel-1.13.3-57.el6_9.i686.rpm 4d1a4f732ae27501bb013674f1b0b85028fc2d4a4ae061d1244db2bff8a477f5 libsss_nss_idmap-devel-1.13.3-57.el6_9.x86_64.rpm ad5ac6f7439d62997536b84755e20b7688913a3b4fd04afe622ba4f8c4fa8dd5 libsss_simpleifp-1.13.3-57.el6_9.i686.rpm 5629876de7fba52273539241f6cfbfb2c7ff1983fa02bc70eebb6bfa29a6b68d libsss_simpleifp-1.13.3-57.el6_9.x86_64.rpm 26a9d7d29a9c5bb89da20ac0774b8bb80cac735faddc44bd41e07baab8f0e1ed libsss_simpleifp-devel-1.13.3-57.el6_9.i686.rpm b1820d13dcd398ec17dcacc051ba6e81130fdca41e10b121968fbbbf5f5be456 libsss_simpleifp-devel-1.13.3-57.el6_9.x86_64.rpm 209f7352d918cb4adef50373529bdac4a5430e2379d7acd7a4724eb98bb13179 python-libipa_hbac-1.13.3-57.el6_9.x86_64.rpm 477897405d5762c897ce497069c6a7eac5b6c94a846956de9ca473049c18bc57 python-libsss_nss_idmap-1.13.3-57.el6_9.x86_64.rpm 2b95cc2a5bc3fbb2f64a25fc369a633701f61c28031f1583a81890ef6f234197 python-sss-1.13.3-57.el6_9.x86_64.rpm c7b8df5b47960010dcd0b9464e17f8df42205f739754816573d5c8d5f58a330d python-sssdconfig-1.13.3-57.el6_9.noarch.rpm 71c0760de386f0b713d147a11b0237801abfb3ce1db0befc729925e9149768d4 python-sss-murmur-1.13.3-57.el6_9.x86_64.rpm 1557f7ef5bb01a5b84a6a59a07e79add62c83545cd7b8f9d014e8a1fb699b3c3 sssd-1.13.3-57.el6_9.x86_64.rpm eba82b031016f13ea9721b946e084e918b2356f55da5b35be1cf011dc8760517 sssd-ad-1.13.3-57.el6_9.x86_64.rpm 0e18519ce4ec99044ddfc9b2f16bbcba96057a078ebbd8c9544c06e351d36d66 sssd-client-1.13.3-57.el6_9.i686.rpm 01f72a1a1e4bad08ff860a7fc7809d7a1c42e4f34cb4e774d8c6a81d618864d6 sssd-client-1.13.3-57.el6_9.x86_64.rpm d10d8155de1517c6bed677ee6dcfacd70b5bd9ff7d26c8fd832b7db6756e1c84 sssd-common-1.13.3-57.el6_9.x86_64.rpm b7aa3ad5384c6f917113f2ae28e15282bff563fcf533f7affbeb6a8af0582a2d sssd-common-pac-1.13.3-57.el6_9.x86_64.rpm 1ce45883ba5e42de2ba4b0f3d32ed518e0271065ca77cb4ab1e85af63e853d73 sssd-dbus-1.13.3-57.el6_9.x86_64.rpm c6016d578a734908687cb2a4e7c574b08bc8f77e197bf87ae7219b435b5b34e5 sssd-ipa-1.13.3-57.el6_9.x86_64.rpm 588fbde858c7d5f47e3f86dc0b54de543e01069338f6b313d9ea559e7281add3 sssd-krb5-1.13.3-57.el6_9.x86_64.rpm af20075ea6e142f484b4b6ffadc1f4480236835b162a0d708c65c75b869dc1ca sssd-krb5-common-1.13.3-57.el6_9.x86_64.rpm 70d654af09bd053d31546883d946bcb1c4a965006d344b48d84d47e0bce59b17 sssd-ldap-1.13.3-57.el6_9.x86_64.rpm 48928584868468445c42869789fadca83f09c62d2067727d4239504f08fd32ae sssd-proxy-1.13.3-57.el6_9.x86_64.rpm cfd0168886af56b426ad73a0085c4cc26a6450e067514049a7a5b5d6137db527 sssd-tools-1.13.3-57.el6_9.x86_64.rpm Source: 4d7f4a06ff19037727fce55eb84c8f8d8526abe2c6651c1ac809eeec21213b0b sssd-1.13.3-57.el6_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 150, Issue 3 ***********************************************

1 0

Centos and CVE-2017-1000117
by Herbert Chang 23 Aug '17

23 Aug '17

hi centos community, as many of you probably have been following along, a few days ago CVE 2017-1000117 <https://bugzilla.redhat.com/show_bug.cgi?id=1480386> was identified and redhat was prompt to release patches to fedora 25/26. I haven't seen any chatter thus far from CentOS, so was wondering if anyone knew the status of the patches landing in CentOS, and more specifically, for CentOS 6 and git 1.7.x that's currently latest in the repos. thanks! Herbert -- Herbert Chang clypd | engineer 781.540.1653 herbert(a)clypd.com <http://www.clypd.com/> Connect with us: Twitter <https://twitter.com/clypd> | LinkedIn <https://www.linkedin.com/company/clypd-inc-> | Facebook <https://www.facebook.com/clypd>

6 6

Installation on Knights Landing (KNL) machines failure
by Arif Ali 22 Aug '17

22 Aug '17

Hi all, We have a customer, where we are trying to install CentOS 7.3 on the new Intel Knights Landing nodes, unfortunately, we are unable to install then using PXE boot. Now, I have a lot of experience of installation of machines using PXE boot, so the setup of that is not the problem. Both myself and my colleagues have looked through the problem, and we are unable to get much diagnosis of the problem. When booting the machine via the network, it loads the ramdisk, and then we get no output, and then the machine reboots. Unfortunately, we have unable to get anything else on the screen. The machines don't have VGA, and monitor capable ports, so we are stuck with Serial Over Lan over IPMI. We have however, after some searching via search engines, we found some documentation suggesting that RHEL 7.2 and then with significant updates on 7.3 do work on these types of machines. We have then followed the same process to try installing the machines, and we have managed to get the machine up, and in a working order. However, we'd like to use CentOS 7.3, and would like to find the process of doing so, if it is any different I was wondering to see if anyone else has seen any similar issues, and if there is a problem here, that we haven't tackled? Any further debugging we can do? Any assistance on this would be much appreciated -- regards, Arif Ali

3 3

Where to start with making a CentOS-based distro
by Julian DeMille 22 Aug '17

22 Aug '17

I'm currently looking into making a distro based on CentOS; how would one do that? -- Julian DeMille CEO, demilleTech Flight Simulations, LLC. 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 message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

1 0

Problem with softwareraid
by Mr Typo 20 Aug '17

20 Aug '17

Hello all, i have already had a discussion on the software raid mailinglist and i want to switch to this one :) I am having a really strange problem with my md0 device running centos7. after a new start of my server the md0 was gone. now after trying to find the problem i detected the following: Booting any installed kernel gives me NO md0 device. (ls /dev/md* doesnt give anything). a 'cat /proc/partitions show me now /dev/sd[a-d]1 partition. partprobe and a mdadm assemble gives me "disk busy" [root@quad live]# cat mdstat Personalities : [raid6] [raid5] [raid4] [raid10] unused devices: <none> [root@quad ~]# partprobe device-mapper: remove ioctl on WDC_WD20EFRX-68AX9N0_WD-WMC301255087p1 failed: Device or resource busy Warning: parted was unable to re-read the partition table on /dev/mapper/WDC_WD20EFRX-68AX9N0_WD-WMC301255087 (Device or resource busy). This means Linux won't know anything about the modifications you made. .... .... [root@quad ~]# mdadm --assemble --force /dev/md0 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 mdadm: /dev/sda1 is busy - skipping mdadm: /dev/sdb1 is busy - skipping mdadm: /dev/sdc1 is busy - skipping mdadm: /dev/sdd1 is busy - skipping booting from a usb stick for rescue my centos everything works. the md0 device exists and is mounted. (rw). [root@quad usb-rescue]# cat mount | grep '/data' /dev/mapper/data-store on /mnt/sysimage/store type xfs (rw,noatime,seclabel,attr2,largeio,nobarrier,inode64,logbufs=8,logbsize=256k,sunit=256,swidth=768,noquota) /dev/mapper/data-tm on /mnt/sysimage/var/lib/vdr/video type xfs (rw,noatime,seclabel,attr2,largeio,nobarrier,inode64,logbufs=8,logbsize=256k,sunit=256,swidth=768,noquota) 3rd option: i am booting the installed rescue kernel from disk: i am getting a md0 device, but its not started. when i stop the md0 i cant assemble it anymore (disk busy) /dev/md0: Version : 1.2 Creation Time : Wed Aug 20 19:28:52 2014 Raid Level : raid5 Used Dev Size : 1953382272 (1862.89 GiB 2000.26 GB) Raid Devices : 4 Total Devices : 4 Persistence : Superblock is persistent Update Time : Thu Aug 17 22:38:14 2017 State : active, Not Started Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Layout : left-symmetric Chunk Size : 128K Name : quad.core.sartori.at:0 (local to host quad.core.sartori.at) UUID : 9d020f27:c0542472:b95a18d2:5741114d Events : 25458 Number Major Minor RaidDevice State 0 8 1 0 active sync /dev/sda1 1 8 17 1 active sync /dev/sdb1 2 8 33 2 active sync /dev/sdc1 4 8 49 3 active sync /dev/sdd1 anyone got an idea, in which direction the problem could be? more logs needed? please help, i have no ideas anymore. regards Andy

3 6

Centos 7 Install
by Jerry Geis 20 Aug '17

20 Aug '17

I have a Centos 7 install that seems to be filling up disk space to 100% on the root partition. in /tmp I found files of names... systemd-private-XXXXXXXX-colord and rtkit I have never seen these files before. there were also files of XXXXXXXXXXXXX.tmp in the /tmp folder. Why are these files appearing? I have a number of installs and never came across this before. Thanks, Jerry

9 16

CentOS6, IP6tables, Routing, TPROXY (squid34 epel package)
by Walter H. 20 Aug '17

20 Aug '17

Hello, how do achieve this: how must files /etc/sysconfig/network-scripts/ look like to be the same as entering the following two commands ... ip -f inet6 rule add fwmark 1 lookup 100 ip -f inet6 route add local ::/0 dev lo table 100 is there the localhost device lo correct, or does it have to be br0? e.g. a file route-br0 with 192.168.1.0/24 via 10.10.10.1 dev br0 does the routing to the segment 192.168.1.0/24 via 10.10.10.1 /etc/sysconfig/ip6tables <BEGIN> *mangle :PREROUTING ACCEPT [0:0] :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :POSTROUTING ACCEPT [0:0] -N DIVERT -A DIVERT -j MARK --set-mark 1 -A DIVERT -j ACCEPT -A PREROUTING -i br0 -p tcp -m socket -j DIVERT -A PREROUTING -i br0 -p tcp -d 2a02:1788:2fd::b2ff:5302 --dport 80 -j TPROXY --tproxy-mark 0x1/0x1 --on-port 3129 COMMIT *filter :INPUT DROP [0:0] :FORWARD DROP [0:0] :OUTPUT DROP [0:0] -A INPUT -i br0 -m tcp -p tcp --dport 22 -m state --state NEW -j ACCEPT -A INPUT -i br0 -m tcp -p tcp --dport 80 -m state --state NEW -j ACCEPT -A INPUT -i br0 -m tcp -p tcp --dport 443 -m state --state NEW -j ACCEPT -A INPUT -i br0 -m tcp -p tcp --dport 3129 -m state --state NEW -j ACCEPT </END> the goal should be, that for specific IPv6 hosts (destination), the packets are redirected through the proxy running on the router box, other destinations should be just forwarded without proxy ... LAN port = br0 (dual stack), HE tunnel port = sit1 (ipv6 only), WAN port = eth1 (ipv4 only) Thanks, Walter

2 1

Problem with SNMP rpm
by Lucas Dutra 19 Aug '17

19 Aug '17

Hello everyone, Im trying to configure SNMP to use Kerberos authentication, but im having some trouble. The standard package of snmp dont have the kerberos module included, then i needed to create a new package. So i found the last centos snmp source rpm, version "net-snmp-5.7.2-24.el7_3.2.x86_64", and modified the .spec file to generate a new rpm with the kerberos module. But in the middle of compilation process, this happens: *checking for security modules to use... ksm usm* *checking for krb5-config... /bin/krb5-config* *checking for krb5... checking for krb5_init_context in -lkrb5... yes* *yes* *checking for heimdal... no* *checking to see which crypto API we need to use... checking for krb5_c_encrypt... yes* *(cached) old MIT crypto API* This "old MIT crypto API" dont happen if i use the same configuration with the standard snmp tar.gz And that is the problem, i need to receive "new MIT crypto API" to work. I have the Kerberos properly installed and running. Sorry if this looks confusing, but what im trying to say is that i guess this rpm is broken and need update. I used the same configuration with the rpm and the tar.gz . The tar.gz worked and the rpm didn't. This problem is for the ksm module, not the entire rpm is broken. Someone know who i cant contact to warn about this? Or if there is a new version out there. I searched for a new version but i didn't find anything. I used the 5.7.2 rpm and 5.7.3 tar.gz Thanks for the attention. Lucas.

1 0

CentOS 7 and Majordomo
by tslbai 19 Aug '17

19 Aug '17

Hi, i was running the latest ;-) Version of Majordomo (1.94.5) successful on CentOS 6.5 for years. Since i installed CentOS 7, majordomo isn't working any more (sendmail error). Is there anyone, who is running majordomo on CentOS 7 or has any hint? I know that Majordomo ist very old and greatcircle isn't supporting ist since years and the majordomo-Mailing-list ended 2003. I know about Mailman too, but i'd like to use majordomo as a small and tiny solution for a particular usecase. Thanks for any hint about running majordomo on CentOS 7. Bye, Florian

1 0

rsyslog stops logging on service reload?
by John Jasen 18 Aug '17

18 Aug '17

I have multiple servers running stock CentOS 7 rsyslog 7.4.7-16.el7, which are configured to log locally and over TCP to a remote logserver, also running stock CentOS 7 rsyslog. The remote server uses imptcp to receive, and pretty basic rules to parse and commit to disk. I have several systems that log prolifically, but periodically, they stop soon after the remote log server HUPs (daily logrotate). Very soon after they stop logging (completely, even to local files), the services on these systems block, and our monitoring system starts alerting. Restarting rsyslog on the clients proves ineffectual. The situation may clear itself without intervention after 90 minutes to several hours. However, this does not happen on all client systems in a similar situation (CentOS 7, large volume of constant log data); nor does it happen daily. Any ideas as to what's going on? Thanks in advance.

2 2

Power Fail Protection Update II
by Chris Olson 18 Aug '17

18 Aug '17

Many thanks once again to those that responded to my original posting (and my follow up message) with information about Network UPS Tools, other Linux-based tools like rtcwake, and commercial UPS products. We have quite a bit more evaluation and testing work to do before a power fail protection method is selected. I hope the discussion is as beneficial to others as it is to my organization. Along the way, one of our users pointed out that some of our CentOS 6 desktop/deskside machines actually throttle back power consumption in different ways than others. Instead of the yellow/amber LED display in the center of the power button, they flash green and then go solid green after the power button is pushed and the system wakes up. We have also noted that none of our CentOS 6 systems restart on their own when power is restored. This is the case whether power is lost during normal operation or when the systems are in a standby state when line power is lost. These two conditions or states (yellow/amber vs flashing green) have us wondering exactly what standby mode these systems are in and what settings may have been selected to send them to their standby state. Is there some sort of standard that applies to the standby states and are there BIOS settings or configuration files that control the what, how, and when standby is directed? Thanks to all and best regards.

1 0

fcitx-anthy request (for Japanese users)
by Scott Robbins 18 Aug '17

18 Aug '17

Apropos of the discussion this week with the person trying to get Chinese input going on CentOS, I filed a request for enhancement with Fedora's EPEL to add fcitx-anthy as a package. Currently, I'm able to get it working with the Fedora 20 rpm, but it would be nice to not have to search for it. It's been assigned (I'm not sure how meaningful that is, depending upon the assignee's free time), but anyone who would like to add their support to the request can view the bug at https://bugzilla.redhat.com/show_bug.cgi?id=1471924 -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6

2 17

CentOS 7.x Russian certification
by Gorazd 18 Aug '17

18 Aug '17

Dear all, does anyone have any idea where to get a list of all CentOS 7.x versions that are certified to be used within Russia. My guess is that organizations, such as FSTEK, TR-CU declares those versions/distributions of CentOS that are certified to be used with commercial projects in Russia. Anyone with some information on this, plase advice, I would be very grateful. Regards, Gorazd

2 1

Power Fail Protection Update
by Chris Olson 17 Aug '17

17 Aug '17

Many thanks to those that responded to my original posting with information about Network UPS Tools and commercial UPS products. In our planning a path forward to implement UPS-based power fail protection, we have come across what appears to be an issue with the state of the CentOS 6 machines being UPS protected. Most of these machines are desktop/deskside machines that are likely to be idle during non-work hours. It is also likely that they will be hibernating or in a power save mode. In the power save mode, these machines do not respond to keyboard or mouse activity. They also do not respond to network traffic such as a ping from other systems on the network. The method we use to wake them up is a quick push on the power button when the hibernation state is indicated by the button's yellow LED display. This state of hibernation leaves us wondering if these systems will be able to respond to network messages sent by the UPS. We have not yet made it all the way through the NUT and UPS documentation. The hibernation answer may very well be therein, but we have not found it so far. Any help or direction regarding the hibernation issue as it relates to UPS power fail protection will be appreciated. Thanks again and best regards.

4 3

CentOS-announce Digest, Vol 150, Issue 2
by centos-announce-request＠centos.org 17 Aug '17

17 Aug '17

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://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-2017:2485 Important CentOS 6 git Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 17 Aug 2017 10:26:34 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:2485 Important CentOS 6 git Security Update Message-ID: <20170817102634.GA25190(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:2485 Important Upstream details at : https://access.redhat.com/errata/RHSA-2017:2485 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: c3d50bf1e6327e69adee222ded15d4416e6a45a0f5eef9a7338cda96c6a97f4f emacs-git-1.7.1-9.el6_9.noarch.rpm 7ec4e9e29cace79b9a1d8d6320817319aac603af77b8aad38c8c850e9a9d118b emacs-git-el-1.7.1-9.el6_9.noarch.rpm 91e909b4dbcc937198226d9664a7c9170f987f8c0d620e4cdeb8297202a745af git-1.7.1-9.el6_9.i686.rpm 77ca5f9cf10f412ba72e2ee6fc6be083b0281cfb4ad948523a79ae7a6c3a3955 git-all-1.7.1-9.el6_9.noarch.rpm 885ba5d4abd9b8d2f6a6cb860d3d1e724153048558e5f2fc8d58a5848e7f89bc git-cvs-1.7.1-9.el6_9.noarch.rpm 78bdf784c49d83d6a84406de5ff4c952646c15ed497a417f3a7e776b60aadd47 git-daemon-1.7.1-9.el6_9.i686.rpm d5279c2b49e038f68a837de3b3e3f7876e7ff4e9d36bc0f0b9b6ec22a6c723ff git-email-1.7.1-9.el6_9.noarch.rpm 2f20e5ca6af534075d080bb629a82774f6f6d2981380ab68e5771d6a8daf5d1d git-gui-1.7.1-9.el6_9.noarch.rpm f041ee76b09bf85c93f150e633b0f457a712ad9edacb0d3d9010e9b8767e3770 gitk-1.7.1-9.el6_9.noarch.rpm ee5f9f0e3bc5d579bccf2708b84d07f54cee955efe9f8da0a32f187c9ffbb836 git-svn-1.7.1-9.el6_9.noarch.rpm ed48d84b39f9c74b6e16434c28ad2e93333c9743a29a8a7712de3eba78accd84 gitweb-1.7.1-9.el6_9.noarch.rpm db23d3712122cd544b0e33deab5bd654c1558906889ebc6ae8c44629e1cd2efa perl-Git-1.7.1-9.el6_9.noarch.rpm x86_64: c3d50bf1e6327e69adee222ded15d4416e6a45a0f5eef9a7338cda96c6a97f4f emacs-git-1.7.1-9.el6_9.noarch.rpm 7ec4e9e29cace79b9a1d8d6320817319aac603af77b8aad38c8c850e9a9d118b emacs-git-el-1.7.1-9.el6_9.noarch.rpm fd0f5ec88f14342c35ac1b255a85a4676a498bf73e39142028970e157eea58a9 git-1.7.1-9.el6_9.x86_64.rpm 77ca5f9cf10f412ba72e2ee6fc6be083b0281cfb4ad948523a79ae7a6c3a3955 git-all-1.7.1-9.el6_9.noarch.rpm 885ba5d4abd9b8d2f6a6cb860d3d1e724153048558e5f2fc8d58a5848e7f89bc git-cvs-1.7.1-9.el6_9.noarch.rpm 146ed31a8e45fb06a546c0483dfe144dac5c5c3971d793c6570ed3599663dba5 git-daemon-1.7.1-9.el6_9.x86_64.rpm d5279c2b49e038f68a837de3b3e3f7876e7ff4e9d36bc0f0b9b6ec22a6c723ff git-email-1.7.1-9.el6_9.noarch.rpm 2f20e5ca6af534075d080bb629a82774f6f6d2981380ab68e5771d6a8daf5d1d git-gui-1.7.1-9.el6_9.noarch.rpm f041ee76b09bf85c93f150e633b0f457a712ad9edacb0d3d9010e9b8767e3770 gitk-1.7.1-9.el6_9.noarch.rpm ee5f9f0e3bc5d579bccf2708b84d07f54cee955efe9f8da0a32f187c9ffbb836 git-svn-1.7.1-9.el6_9.noarch.rpm ed48d84b39f9c74b6e16434c28ad2e93333c9743a29a8a7712de3eba78accd84 gitweb-1.7.1-9.el6_9.noarch.rpm db23d3712122cd544b0e33deab5bd654c1558906889ebc6ae8c44629e1cd2efa perl-Git-1.7.1-9.el6_9.noarch.rpm Source: 74f8d2e2bf749caf808e0246164c0c453aa7a09a917ce439764b8588d767c69b git-1.7.1-9.el6_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 150, Issue 2 ***********************************************

1 0

CentOS-announce Digest, Vol 150, Issue 1
by centos-announce-request＠centos.org 16 Aug '17

16 Aug '17

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://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. New CentOS Atomic Release and Kubernetes System Containers Now Available (Jason Brooks) 2. CESA-2017:2456 Critical CentOS 6 firefox Security Update (Johnny Hughes) 3. CESA-2017:2424 Critical CentOS 6 java-1.7.0-openjdk Security Update (Johnny Hughes) 4. CESA-2017:2478 Critical CentOS 6 httpd Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 11 Aug 2017 11:53:14 -0700 From: Jason Brooks <jbrooks(a)redhat.com> To: "The CentOS developers mailing list." <centos-devel(a)centos.org>, atomic-devel <atomic-devel(a)projectatomic.io>, atomic-announce(a)projectatomic.io, centos-announce(a)centos.org Subject: [CentOS-announce] New CentOS Atomic Release and Kubernetes System Containers Now Available Message-ID: <CAF=rfpDokA6CUrO2W0aY3gEuOpJ384ThhH-6fwJxwf6OueAg_Q(a)mail.gmail.com> Content-Type: text/plain; charset="UTF-8" Last week, the CentOS Atomic SIG released an updated version (https://wiki.centos.org/SpecialInterestGroup/Atomic/Download) of CentOS Atomic Host (7.1707), a lean operating system designed to run Docker containers, built from standard CentOS 7 RPMs, and tracking the component versions included in Red Hat Enterprise Linux Atomic Host. The release, which came as part of the monthly CentOS release stream, was a modest one, including only a single glibc bugfix update (https://lists.centos.org/pipermail/centos-announce/2017-July/022505.html) The next Atomic Host release will be based on the RHEL 7.4 source code (https://seven.centos.org/2017/08/centos-linux-7-1708-based-on-rhel-7-4-sour…) and will include support for overlayfs container storage, among other enhancements. Outside of the Atomic Host itself, the SIG has updated its Kubernetes container images to be usable as system containers (http://www.projectatomic.io/blog/2016/09/intro-to-system-containers/) What's more, in addition to the Kubernetes 1.5.x-based containers that derive from RHEL, the Atomic SIG is now producing packages and containers that provide the current 1.7.x version of Kubernetes. ## Containerized Master The downstream release of CentOS Atomic Host ships without the kubernetes-master package built into the image. You can install the master kubernetes components (apiserver, scheduler, and controller-manager) as system containers, using the following commands: # atomic install --system --system-package=no --name kube-apiserver registry.centos.org/centos/kubernetes-apiserver:latest # atomic install --system --system-package=no --name kube-scheduler registry.centos.org/centos/kubernetes-scheduler:latest # atomic install --system --system-package=no --name kube-controller-manager registry.centos.org/centos/kubernetes-controller-manager:latest ## Kubernetes 1.7.x The CentOS Virt SIG is now producing Kubernetes 1.7.x rpms, available through this yum repo (https://github.com/CentOS/CentOS-Dockerfiles/blob/master/kubernetes-sig/mas…) The Atomic SIG is maintaining system containers based on these rpms that can be installed as as follows: ### on your master # atomic install --system --system-package=no --name kube-apiserver registry.centos.org/centos/kubernetes-sig-apiserver:latest # atomic install --system --system-package=no --name kube-scheduler registry.centos.org/centos/kubernetes-sig-scheduler:latest # atomic install --system --system-package=no --name kube-controller-manager registry.centos.org/centos/kubernetes-sig-controller-manager:latest ### on your node(s) # atomic install --system --system-package=no --name kubelet registry.centos.org/centos/kubernetes-sig-kubelet:latest # atomic install --system --system-package=no --name kube-proxy registry.centos.org/centos/kubernetes-sig-proxy:latest Both the 1.5.x and 1.7.x sets of containers have been tested with the kubernetes ansible scripts (https://github.com/kubernetes/contrib/tree/master/ansible) provided in the upstream contrib repository, and function as drop-in replacements for the installed rpms. If you prefer to run Kubernetes from installed rpms, you can layer the master components onto your Atomic Host image using rpm-ostree package layering with the command: `atomic host install kubernetes-master`. The containers referenced in these systemd service files are built in and hosted from the CentOS Community Container Pipeline (https://wiki.centos.org/ContainerPipeline) based on Dockerfiles from the CentOS-Dockerfiles repository (https://github.com/CentOS/CentOS-Dockerfiles/tree/master/kubernetes) ## Download CentOS Atomic Host CentOS Atomic Host is available as a VirtualBox or libvirt-formatted Vagrant box, or as an installable ISO, qcow2 or Amazon Machine image. For links to media, see the CentOS wiki (https://wiki.centos.org/SpecialInterestGroup/Atomic/Download) ## Upgrading If you're running a previous version of CentOS Atomic Host, you can upgrade to the current image by running the following command: $ sudo atomic host upgrade ## Release Cycle The CentOS Atomic Host image follows the upstream Red Hat Enterprise Linux Atomic Host cadence. After sources are released, they're rebuilt and included in new images. After the images are tested by the SIG and deemed ready, we announce them. ## Getting Involved CentOS Atomic Host is produced by the CentOS Atomic SIG (http://wiki.centos.org/SpecialInterestGroup/Atomic) based on upstream work from Project Atomic (http://www.projectatomic.io/) If you'd like to work on testing images, help with packaging, documentation -- join us! The SIG meets weekly on Thursdays at 16:00 UTC in the #centos-devel channel, and you'll often find us in #atomic and/or #centos-devel if you have questions. You can also join the atomic-devel (https://lists.projectatomic.io/mailman/listinfo/atomic-devel) mailing list if you'd like to discuss the direction of Project Atomic, its components, or have other questions. ## Getting Help If you run into any problems with the images or components, feel free to ask on the centos-devel (http://lists.centos.org/mailman/listinfo/centos-devel) mailing list. Have questions about using Atomic? See the atomic (https://lists.projectatomic.io/mailman/listinfo/atomic) mailing list or find us in the #atomic channel on Freenode. ------------------------------ Message: 2 Date: Tue, 15 Aug 2017 20:20:53 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:2456 Critical CentOS 6 firefox Security Update Message-ID: <20170815202053.GA55144(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:2456 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2017:2456 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: f29636840b84fd6d5a4a102d02a19c569a3c8e5bb122fffab931a57fdaf87ae8 firefox-52.3.0-3.el6.centos.i686.rpm x86_64: f29636840b84fd6d5a4a102d02a19c569a3c8e5bb122fffab931a57fdaf87ae8 firefox-52.3.0-3.el6.centos.i686.rpm fa94722eb61a41e0c0c12c31dab803aeb3387e9ba83ad52a305dc1880d5764b8 firefox-52.3.0-3.el6.centos.x86_64.rpm Source: 85eb85c49ccac809e5eb899b3680735e5ba1521c378866ccfa98982462801152 firefox-52.3.0-3.el6.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Tue, 15 Aug 2017 20:23:35 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:2424 Critical CentOS 6 java-1.7.0-openjdk Security Update Message-ID: <20170815202335.GA55418(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:2424 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2017:2424 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 53a24f4fed4dffa5d60f5f6f5aae09cae0d5aa675aae5c89bc89568f150c375b java-1.7.0-openjdk-1.7.0.151-2.6.11.0.el6_9.i686.rpm 87ed44696e8f5d9f3a409e48e8e45c9963ee8bd5d66d85432f99fde5fe700fc6 java-1.7.0-openjdk-demo-1.7.0.151-2.6.11.0.el6_9.i686.rpm a22a1605fd7fd61c1edff42b837d048263c9ed3d62ddc6cb057df9db9b8488d3 java-1.7.0-openjdk-devel-1.7.0.151-2.6.11.0.el6_9.i686.rpm ab1fa5c00fc66e895c699909ba6f7a033359a2cb6c853b45db77bac414f83faa java-1.7.0-openjdk-javadoc-1.7.0.151-2.6.11.0.el6_9.noarch.rpm ddc41007c6b80e937826f9b08adb8529537e45224b7d9c77e88a5137333dec08 java-1.7.0-openjdk-src-1.7.0.151-2.6.11.0.el6_9.i686.rpm x86_64: bd3d2e33f5f05c97acdb4463ee838e1ac990de77704401a13cbee82d6359c93b java-1.7.0-openjdk-1.7.0.151-2.6.11.0.el6_9.x86_64.rpm 077188b99553fa5323ce61ae133048b4a3fbf12bb6feeb494734af627cf5fb62 java-1.7.0-openjdk-demo-1.7.0.151-2.6.11.0.el6_9.x86_64.rpm aa5efd1300c3240590bf4ecaaf00040eb1a3ae3674279de2c768c734921eef85 java-1.7.0-openjdk-devel-1.7.0.151-2.6.11.0.el6_9.x86_64.rpm ab1fa5c00fc66e895c699909ba6f7a033359a2cb6c853b45db77bac414f83faa java-1.7.0-openjdk-javadoc-1.7.0.151-2.6.11.0.el6_9.noarch.rpm 51f85429d7fb4aebb500b6ba73e717f7dbc6597191db9dd8c0b108d9f1e7aac4 java-1.7.0-openjdk-src-1.7.0.151-2.6.11.0.el6_9.x86_64.rpm Source: f7fea14d8c97e7251cb3129c2c0bc23485ed534d36f80a9e1feb6d301abbe207 java-1.7.0-openjdk-1.7.0.151-2.6.11.0.el6_9.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Tue, 15 Aug 2017 20:25:39 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2017:2478 Critical CentOS 6 httpd Security Update Message-ID: <20170815202539.GA55716(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2017:2478 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2017:2478 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 68b712bfb3b1a08748f4bdac924dc30fa5683977333c9ff052a525d2e9347259 httpd-2.2.15-60.el6.centos.5.i686.rpm aeff46346d66dcb687524a05882f21b6c7596f433859c2a443354af33bc3deed httpd-devel-2.2.15-60.el6.centos.5.i686.rpm ae7886ff13fef00ae7272ccced1ec6e3d4cdd0db02a3e9ba37a37d7b7548d087 httpd-manual-2.2.15-60.el6.centos.5.noarch.rpm 30d1a73a78e580d5314b7140799e23af42c0023560c863ceab681eae175e815b httpd-tools-2.2.15-60.el6.centos.5.i686.rpm c6ee5b709d021faaa9abd61f8316948ed2043ce53d935b9063285bf3d41994f8 mod_ssl-2.2.15-60.el6.centos.5.i686.rpm x86_64: 6c4577f55b8b3f40a1223be39a61ee1185ce7b9a0588ef4ad60fbf45d5e431e7 httpd-2.2.15-60.el6.centos.5.x86_64.rpm aeff46346d66dcb687524a05882f21b6c7596f433859c2a443354af33bc3deed httpd-devel-2.2.15-60.el6.centos.5.i686.rpm 4c9cc089ac1d30b9b50bd1ff2a2a3eaf0c09cc969b0b543f6a7d9ffd01f5cf4f httpd-devel-2.2.15-60.el6.centos.5.x86_64.rpm ae7886ff13fef00ae7272ccced1ec6e3d4cdd0db02a3e9ba37a37d7b7548d087 httpd-manual-2.2.15-60.el6.centos.5.noarch.rpm 5cc5dfdd78d76f2c020cfab998363aa8345cdc477d48af3a1c1cd48dd364098f httpd-tools-2.2.15-60.el6.centos.5.x86_64.rpm b2f9c90fc09cb85894f20ead9cbf4405cf92ac1748860aa280e7af96c21e17fb mod_ssl-2.2.15-60.el6.centos.5.x86_64.rpm Source: ee426ab362997f52fcfd19d7e5610359d47a3a5439cbba2ecff7455c35bd9b85 httpd-2.2.15-60.el6.centos.5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 150, Issue 1 ***********************************************

1 0

Power Fail Protection
by Chris Olson 15 Aug '17

15 Aug '17

Some of our largest systems run Windows because it supports engineering applications that we use regularly. These applications have unattended runs that often take between ten and fifteen hours to complete. We have taken the recommendation of the application supplier and equipped these Windows machines with UPS protection for 30 minutes at full load. The UPSs are Ethernet connected. A support application on the Windows engineering machine communicates with the UPS to detect and address any facility power failure. The long run engineering application is then suspended at a restart point and the system is shut down. We initiate job completion manually from the suspension restart point after the system has reliable power and is rebooted. If we wanted to protect our CentOS systems from facility power failure in a similar way, is there operating system or other standard support that we might employ? Most of the Linux-based applications are not as critical as the engineering applications on the Windows machines. There is a significant amount of processor idle time on several of the CentOS systems during non-work hours when the systems are unattended. Several CentOS systems are supported currently with UPSs, but they run out and the system loses power if it is unattended.

4 5

Custom kickstart post section on usb thumbdrive
by Jerry Geis 14 Aug '17

14 Aug '17

Hi All, I am attempting to create a custom USB drive for kickstart install. I found this: 1. get the ISO file of CentOS 7 2. mount -o loop CentOS-7.0*.iso /mnt/ 3. mkdir -p /CentOS-7-ISO-respin/{CentOS-7-unpacked,CentOS-7-iso} 4. rsync -avz /mnt/ /CentOS-7-ISO-respin/RHEL-7-unpacked 5. put your kickstart file into /CentOS-7-ISO-respin/RHEL-7-unpacked 6. add a new line to /CentOS-7-ISO-respin/RHEL-7-unpacked/isolinux/isolinux.cfg (this way you can use the ISO also from a DVD) label linux_ks menu label ^Install CentOS 7 with Kickstart kernel vmlinuz append initrd=initrd.img inst.stage2=hd:sdb2:/ ks=hd:sdb1:/ks.cfg 7. create the ISO with: /usr/bin/genisoimage -untranslated-filenames -volid 'CentOS-7.0-KS-x86_64' -J -joliet-long -rational-rock -translation-table -input-charset utf-8 -x ./lost+found -b isolinux/isolinux.bin -c isolinux/ boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table 8. dd if=/CentOS-7-ISO-respin/CentOS-7-CSB-iso/CentOS-7.0-KS-x86_64-DVD.iso of=/dev/XXX (where XXX is the Device Name of your USB drive without the partition number e.g. /dev/sdb) (Careful, that command destroys all data on the Stick) But I would also like to create a custom directory on the ISO and put some files in there for a custom POST section. I was not able to find an example with a custom POST section on the ISO. Anyone have any examples? Thanks, Jerry

2 1

Centos 7 specific cure for Spamassassin DNS lookup problem
by Gary Stainburn 14 Aug '17

14 Aug '17

I have the following error message in my /var/log/spamd spf: lookup failed: available_nameservers: No DNS servers available! Having Googled the error message I've found a number of responses which involve patching Perl or Spamassassin or other cures. Before I start changing things I was wondering if there was a Centos 7 specific resolution. Where possible, on production machines I prefer to stay with RPM's rather than amending software directly. Also, many of these responses are over 10 years old, so I'm a little sceptical about their success today. Gary

4 7

Kernel:[Hardware Error]:
by Fred Smith 13 Aug '17

13 Aug '17

I had a series of kernel hardware error reports today while I was away from my computer: Message from syslogd@fcshome at Aug 12 10:12:24 ... kernel:[Hardware Error]: MC2 Error: VB Data ECC or parity error. Message from syslogd@fcshome at Aug 12 10:12:24 ... kernel:[Hardware Error]: Error Status: Corrected error, no action required. Message from syslogd@fcshome at Aug 12 10:12:24 ... kernel:[Hardware Error]: CPU:2 (15:2:0) MC2_STATUS[-|CE|MiscV|-|-|-|-|CECC]: 0x98444000010c0176 Message from syslogd@fcshome at Aug 12 10:12:24 ... kernel:[Hardware Error]: cache level: L2, tx: DATA, mem-tx: EV never saw anything like that before. cpu is: $ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 21 model : 2 model name : AMD FX(tm)-6300 Six-Core Processor stepping : 0 microcode : 0x600084f cpu MHz : 1400.000 cache size : 2048 KB physical id : 0 siblings : 6 core id : 0 cpu cores : 3 apicid : 16 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc art rep_good nopl nonstop_tsc extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb arat cpb hw_pstate npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold bmi1 bogomips : 7023.90 TLB size : 1536 4K pages clflush size : 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm 100mhzsteps hwpstate cpb eff_freq_ro six core AMD, above is one of the cores. Any clues to figure out the errors, and/or mitigate? thanks! Fred -- ------------------------------------------------------------------------------- .---- Fred Smith / ( /__ ,__. __ __ / __ : / / / / /__) / / /__) .+' Home: fredex(a)fcshome.stoneham.ma.us / / (__ (___ (__(_ (___ / :__ 781-438-5471 -------------------------------- Jude 1:24,25 ---------------------------------

6 7

what is CodeMeter and why is it running on my CentOS box?
by Fred Smith 13 Aug '17

13 Aug '17

I just stumbled over /var/log/CodeMeter, which contains a number of large log files. I know I'm getting old and forgetful, but I can't remember intentionally installing that package. Yum just says "installed" instead of listing a repo. Looking at codemeter.com, it seems to work with something called a "cm stick". I don't have one, don't want one, and never heard of them. Is there any reason I should be leery of just "yum remove"ing the package? thanks! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- "Not everyone who says to me, 'Lord, Lord,' will enter the kingdom of heaven, but only he who does the will of my Father who is in heaven." ------------------------------ Matthew 7:21 (niv) -----------------------------

3 4

ovirt-engine package for oVirt 4.1.x in CentOS offical mirrors disappears?
by C. L. Martinez 13 Aug '17

13 Aug '17

Hi all, I am trying to install oVirt 4.1.x from centos repos but it seems ovirt-engine doesn't exists. But instead, ovirt-hosted-engine-setup exists? Is ovirt-engine package removed? In the official oVirt repos, exists. Thanks.

2 3

Acroread9 crash in CentOS7
by wwp 13 Aug '17

13 Aug '17

Hello, I'm getting a crash with acroread on my CentOS7 (AdobeReader_enu-9.5.5-1.i486). I install the official rpms from ftp://ftp.adobe.com/pub/adobe/reader/unix/, tried 9.5.5, and former v9, v8, v7. /usr/bin/acroread loads well, but when you click a menu, bang. Same if you start acroread w/ a .pdf filename in parameter, the window opens up then crashes. I modified the acroread script to run the binary from within gdb, I get this: Program received signal SIGSEGV, Segmentation fault. 0xf5437cee in compute_face () from /lib/libcairo.so.2 Unfortunately, the system completely hangs when it happens (acroread from gdb) and I must kill acroread from a tty, so I cannot get a more detailed backtrace for now. Is that something somebody here already saw? Regards, -- wwp

3 4

Re: [CentOS] Btrfs going forward, was: Errors on an SSD drive
by Chris Murphy 12 Aug '17

12 Aug '17

Changing the subject since this is rather Btrfs specific now. On Fri, Aug 11, 2017 at 5:41 AM, hw <hw(a)gc-24.de> wrote: > Chris Murphy wrote: >> >> On Wed, Aug 9, 2017, 11:55 AM Mark Haney <mark.haney(a)neonova.net> wrote: >> >>> To be honest, I'd not try a btrfs volume on a notebook SSD. I did that on >>> a >>> couple of systems and it corrupted pretty quickly. I'd stick with >>> xfs/ext4 >> >> >> if you manage to get the drive working again. >>> >>> >> >> Sounds like a hardware problem. Btrfs is explicitly optimized for SSD, the >> maintainers worked for FusionIO for several years of its development. If >> the drive is silently corrupting data, Btrfs will pretty much immediately >> start complaining where other filesystems will continue. Bad RAM can also >> result in scary warnings where you don't with other filesytems. And I've >> been using it in numerous SSDs for years and NVMe for a year with zero >> problems. > > > That´s one thing I´ve been wondering about: When using btrfs RAID, do you > need to somehow monitor the disks to see if one has failed? Yes. The block layer has no faulty device handling, i.e. it just reports whatever problems the device or the controller report. Where md/mdadm and md/LVM have implemented policies for ejecting (setting a device to faulty) a block device. Btrfs does not do that, it'll just keep trying to use a faulty device. So you have to setup something that monitors for either physical device errors, or btrfs errors or both, depending on what you want. > >> On CentOS though, I'd get newer btrfs-progs RPM from Fedora, and use >> either >> an elrepo.org kernel, a Fedora kernel, or build my own latest long-term >> from kernel.org. There's just too much development that's happened since >> the tree found in RHEL/CentOS kernels. > > > I can´t go with a more recent kernel version before NVIDIA has updated their > drivers to no longer need fence.h (or what it was). > > And I thought stuff gets backported, especially things as important as file > systems. There's 1500 to 3000 line changes to Btrfs code per kernel release. There's too much to backport most of it. Serious fixes do get backported by upstream to longterm kernels, but to what degree, you have to check the upstream changelogs to know about it. And right now most backports go to only 4.4 and 4.9. And I can't tell you what kernel-3.10.0-514.10.2.el7.x86_64.rpm translates into, that requires a secret decoder ring near as I can tell as it's a kernel made from multiple branches, and then also a bunch of separate patches. >> Also FWIW Red Hat is deprecating Btrfs, in the RHEL 7.4 announcement. >> Support will be removed probably in RHEL 8. I have no idea how it'll >> affect >> CentOS kernels though. It will remain in Fedora kernels. > > > That would suck badly to the point at which I´d have to look for yet another > distribution. The only one ramaining is arch. > > What do they suggest as a replacement? The only other FS that comes close > is > ZFS, and removing btrfs alltogether would be taking living in the past too > many > steps too far. Red Hat are working on a new user space wrapper and volume format based on md, device mapper, LVM, and XFS. http://stratis-storage.github.io/ https://stratis-storage.github.io/StratisSoftwareDesign.pdf It's an aggressive development schedule and as so much of it is journaling and CoW based I have no way to assess whether it ends up with its own set of problems, not dissimilar to Btrfs. We'll just have to see. But if there are underlying guts in the device-mapper that do things better/faster/easier than Btrfs, the Btrfs devs have said they can hook into device-mapper for these things to consolidate code base, in particular for the multiple device handling. By its own vague time table it will be years before it has "rough ZFS features" and again estimating bootloader support, and to what degree other distros pick up on it, it very well could end up being widely adopted, or it could be a Red Hat only thing in practice. Canonical appears to be charging ahead with OpenZFS included by default out of the box (although not for rootfs yet I guess), and that has an open ended and possibly long window before legal issues get tested. But this is by far the most cross platform solution: FreeBSD, Illumos, Linux, macOS. And ZoL has RHEL/CentOS specific packages. But I can't tell you for sure what ZoL's faulty device behavior is either, whether it ejects faulty or flaky devices and when, or if like Btrfs is just tolerates it. The elrepo.org folks can still sanely set CONFIG_BTRFS_FS=m, but I suspect if RHEL unsets that in RHEL 8 kernels, that CentOS will do the same. -- Chris Murphy

7 13

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss August 2017