Discuss

discuss@lists.centos.org

34758 discussions

Re: [CentOS] CentOS7 Minimal installation on Vmware missing network interface
by reynierpm＠gmail.com 31 Aug '14

31 Aug '14

On Sun, Aug 31, 2014 at 1:56 PM, Reindl Harald <h.reindl(a)thelounge.net> wrote: > i don't see you VMware configuration in your post > > Which configuration you need? The one I made at Windows side? The Vmware is running on Windows 7 (I didn't send here since I don't know if I can attach images to this list and to not be banned so I omit then) > you need to use the "vmxnet3" ethernet interface for the VM > that module is part of the Linux upstream Kernel for a long time > > that below is straight out-of-box on REHL7 > the open-vm-tools now are only the user-space daemon > the times where you need to compile kernel modules are gone 2013 > > [root@localhost:~]$ lsmod | grep vm > vmw_balloon 13415 0 > vmxnet3 49541 0 > vmw_vmci 67106 0 > vmw_pvscsi 22858 4 > What about if I didn't see vmxnet3? [root@webserver ~]# lsmod | grep vm vmw_balloon 13415 0 vmw_vmci 67106 0 vmwgfx 135143 1 ttm 83948 1 vmwgfx drm 297829 2 ttm,vmwgfx

1 0

EPEL-7 is Released
by Karanbir Singh 31 Aug '14

31 Aug '14

hi folks, I know lots of people have been waiting for this : https://lists.fedoraproject.org/pipermail/epel-announce/2014-August/000030.… EPEL-7 is now considered GA and available to all users. -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

9 15

pidgin for CentOS 7
by m.roth＠5-cent.us 30 Aug '14

30 Aug '14

Has any repo - epel, maybe, built the messaging client pidgin for CentOS 7? My manager's been trying empathy, and tells me it's very much not ready for prime time..... mark

3 3

CentOS-announce Digest, Vol 114, Issue 16
by centos-announce-request＠centos.org 30 Aug '14

30 Aug '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. lists.centos.org scheduled migration (Fabian Arrotin) 2. CESA-2014:1110 Important CentOS 6 glibc Update (Johnny Hughes) 3. CESA-2014:1110 Important CentOS 5 glibc Update (Johnny Hughes) 4. CESA-2014:1110 Important CentOS 7 glibc Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 29 Aug 2014 14:38:04 +0200 From: Fabian Arrotin <arrfab(a)centos.org> Subject: [CentOS-announce] lists.centos.org scheduled migration To: centos-announce(a)centos.org Message-ID: <5400742C.2010806(a)centos.org> Content-Type: text/plain; charset=UTF-8 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, We'd just like to inform you that the current machine hosting all the CentOS mailing lists (on http://lists.centos.org) needs to be replaced and so the mailman service needs to be moved/migrated to a new host. Migration is scheduled for Monday September 1st, 7:30 AM, UTC time. You can convert to local time with $(date -d '2014-09-01 07:30 UTC') Expected downtime is ~1 hour but we hope to be able to restart the service earlier. If you have questions, comments or feedback, please join the #centos-devel channel on irc.freenode.net. Kind Regards, - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlQAdCwACgkQnVkHo1a+xU5LnACeL2+2OX1o7qqK6zwDq6zPPQSA 2QsAnAuylNkFbqAccwBslS3Y11Cd0ohP =TinJ -----END PGP SIGNATURE----- ------------------------------ Message: 2 Date: Fri, 29 Aug 2014 20:28:37 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2014:1110 Important CentOS 6 glibc Update To: centos-announce(a)centos.org Message-ID: <20140829202837.GA48782(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2014:1110 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-1110.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 442d9dc89c9f8d3d77cc79721ec65fe60f4e4d7cfd2b1947484d5236acecb4c5 glibc-2.12-1.132.el6_5.4.i686.rpm b5cacd4979954d5532ce72d7c857ef77a7caf75395e98c44a913397872d1cb1b glibc-common-2.12-1.132.el6_5.4.i686.rpm afc427fb642cb2ae5006eefb2733c543fd39df85571a92b75a1a304595570561 glibc-devel-2.12-1.132.el6_5.4.i686.rpm 18f6823611d45473bffce71029cf79d85839417bdeda9748781ba1fe7fbea8d8 glibc-headers-2.12-1.132.el6_5.4.i686.rpm ea376cce69c837419ff04d760be85377a6e8ff172d87daf9224925feb1602610 glibc-static-2.12-1.132.el6_5.4.i686.rpm 6c93161285a5994d28213cd9e03b5b21701dffe221763fd2053f9395787dee2c glibc-utils-2.12-1.132.el6_5.4.i686.rpm 92cd5363fbdb126b5e47183d4371519e3c29ec75b07ad795a93fcfb931ddc47d nscd-2.12-1.132.el6_5.4.i686.rpm x86_64: 442d9dc89c9f8d3d77cc79721ec65fe60f4e4d7cfd2b1947484d5236acecb4c5 glibc-2.12-1.132.el6_5.4.i686.rpm 6ea6318915ee0b531ff699b4b21f95fd4138ca9d2280d3263960a1bebb3bfd59 glibc-2.12-1.132.el6_5.4.x86_64.rpm 7b7bdc21adfba2341a31188197d9727aebfbc80fe0578587d20692b9841d88ca glibc-common-2.12-1.132.el6_5.4.x86_64.rpm afc427fb642cb2ae5006eefb2733c543fd39df85571a92b75a1a304595570561 glibc-devel-2.12-1.132.el6_5.4.i686.rpm cf89dc43a5408fd4de8f88857653aa2d1972784272c721b54178206162c8e945 glibc-devel-2.12-1.132.el6_5.4.x86_64.rpm ed2817755b7de1d677a053e6fd43833f9fbd0fcd7b5961461364ba40196a1b33 glibc-headers-2.12-1.132.el6_5.4.x86_64.rpm ea376cce69c837419ff04d760be85377a6e8ff172d87daf9224925feb1602610 glibc-static-2.12-1.132.el6_5.4.i686.rpm 61385e33102dcc7fb3b5611411b9266b0a1229bdefe36c911efb6643ef0ac599 glibc-static-2.12-1.132.el6_5.4.x86_64.rpm 4f98b752ea0cb7679dd879019f264bc214b282c0b461b9630185ecf50e07a803 glibc-utils-2.12-1.132.el6_5.4.x86_64.rpm c484f29b457d8808ae01f4fc93be78ed986012cb49524a5a002fd749ffa9a272 nscd-2.12-1.132.el6_5.4.x86_64.rpm Source: 58cf86d913c3904ea5ba3b3788ae9e36b95a267306071474fa854d3ea899147c glibc-2.12-1.132.el6_5.4.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 3 Date: Fri, 29 Aug 2014 20:36:18 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2014:1110 Important CentOS 5 glibc Update To: centos-announce(a)centos.org Message-ID: <20140829203618.GA18162(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2014:1110 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-1110.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 66837e2c1ba580009b54c74498fa1035ae5fd2e45117152c1d831e1a2f0da2ca glibc-2.5-118.el5_10.3.i386.rpm e618a34ff9b24d0f36bc373c0b1906f407e49c9441dd9e65f2d2653dd544d842 glibc-2.5-118.el5_10.3.i686.rpm d1a97a6efd38cb5699a2830ffa0d73e19099d31f1b85b8cab57b3b31fd200e58 glibc-common-2.5-118.el5_10.3.i386.rpm 1a59edecdbc341ce147144462157c61f314821e985c6469a9453de62e059edee glibc-devel-2.5-118.el5_10.3.i386.rpm ac89acd5988da930f37240dc48665dbaa86ac548be7f170704c537c74788a6ca glibc-headers-2.5-118.el5_10.3.i386.rpm d272d6aa24fe1ab776ff07ff574396d49ad219d3c4379e6730b9160e629d44b1 glibc-utils-2.5-118.el5_10.3.i386.rpm 1331a260431bfd414e6e12f19caf33e206fd3af55ede54851cb746590ee9f66a nscd-2.5-118.el5_10.3.i386.rpm x86_64: e618a34ff9b24d0f36bc373c0b1906f407e49c9441dd9e65f2d2653dd544d842 glibc-2.5-118.el5_10.3.i686.rpm c06f007179e3cc6ab154ae25b93a42960a8c843bb6c6e5173cb6f61c64574320 glibc-2.5-118.el5_10.3.x86_64.rpm a9e7e45cfd39d6dddc1bf699da261157758847fa8123b306c1c9b3f9b3300f03 glibc-common-2.5-118.el5_10.3.x86_64.rpm 1a59edecdbc341ce147144462157c61f314821e985c6469a9453de62e059edee glibc-devel-2.5-118.el5_10.3.i386.rpm 9cc224e816d7167d4f2552a6085d32b9dbee1b9c3870f54fe6e140df6ff14204 glibc-devel-2.5-118.el5_10.3.x86_64.rpm dcaef2a9cb2456d1f855e4e5fafb17df8bceeae6ea6b8231650b9c8a9fd1ae08 glibc-headers-2.5-118.el5_10.3.x86_64.rpm 7c461379fe6759f331aaf5da8d91511e50531535d01dce8db807064760b712d1 glibc-utils-2.5-118.el5_10.3.x86_64.rpm 513b70f0bf8a75bda1629d84d9d64305885c7fe49f07c7cd5c99b28a1d8d0865 nscd-2.5-118.el5_10.3.x86_64.rpm Source: ea413bbe3a9035f89decda67b742f5930062aad27f79a3f7e6f33353970fcccb glibc-2.5-118.el5_10.3.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 4 Date: Fri, 29 Aug 2014 21:03:35 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2014:1110 Important CentOS 7 glibc Security Update To: centos-announce(a)centos.org Message-ID: <20140829210335.GA7423(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2014:1110 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-1110.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 49e489ef9a3ddb83fc0b03eb8e6eb0cf475258d5bb01e1177d0ecf77ba3cdbe5 glibc-2.17-55.el7_0.1.i686.rpm 5c06db28ca86d6916c31f79473f32d69002626d869787a4122f66e61d2d9bc84 glibc-2.17-55.el7_0.1.x86_64.rpm f421ef1f0f781b0b712702b690c46762129c5ee6a5de187629973452020e669b glibc-common-2.17-55.el7_0.1.x86_64.rpm a0340a64ce3d3ae9250a82bc8eab5e5f3d409d59b17170a30ac1c1f2a108d523 glibc-devel-2.17-55.el7_0.1.i686.rpm 25e166fd078397c113c0a625142e53d9987b17b74ab8dca323a4fe49ae5f21c0 glibc-devel-2.17-55.el7_0.1.x86_64.rpm b64a72ae4f3a02af4da25dda5e34b0a5151005ba8720b95d1384459a5fe911a5 glibc-headers-2.17-55.el7_0.1.x86_64.rpm e4f6d10d290fdb50faee17af5af7aacbf888924b05dcf46fd47af16496d85af3 glibc-static-2.17-55.el7_0.1.i686.rpm c74a3c47948de40ce5514e230fb526eb98d61a40153b950dcedba1e5b0f5a6cc glibc-static-2.17-55.el7_0.1.x86_64.rpm 87ed53e9770b6d81b560b03aecc798ccd2c869b3c29b5a090ae0b55c6636b58e glibc-utils-2.17-55.el7_0.1.x86_64.rpm c40e8c17aead091303764e31002ad613fa344609283911b50354828715da54ac nscd-2.17-55.el7_0.1.x86_64.rpm Source: 228af88fceca72f088fd0e445eba1a676ae7cf862fa07cb675b64f3369a47099 glibc-2.17-55.el7_0.1.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 114, Issue 16 ************************************************

1 0

bind zone files graphical management tool
by Robert Moskowitz 30 Aug '14

30 Aug '14

On a server that does not have a gui, only command line. In the past I have used webmin, and was happy with it, but it is more than I really need. I COULD rsync the files to my notebook and maintain them there. Probably should just for backup! But is there anything else that is 'safe' to use. vi gets tiring after a while.

5 6

Re: [CentOS] Hanging SSH in CentOS 7 and Systemd
by Oliver Schad 30 Aug '14

30 Aug '14

Reindl Harald <h.reindl(a)thelounge.net> wrote: > Am 30.08.2014 um 01:40 schrieb Oliver Schad: > >> https://bugzilla.redhat.com/show_bug.cgi?id=626477 > > > > Seems back again. I just wondering how such easy things can be so > > hard so solve. > > Oh no - don't tell me that update below fucks it up again > and not systemd this time - /etc/rc.d/init.d/network is > part of "initscripts" and i have not rebooted the machine > after the update because nothing loaded changed Don't know what you mean. I've already found the ticket above before I've posted here. I tried to fix it with the change of /usr/lib/systemd/system/systemd-user-sessions.service or /usr/lib/systemd/system/sshd.service with dependencies to systemd-networkd.service and network.target but it changes nothing (obvious) in the behaviour. Best Regards Oli

1 1

Re: [CentOS] Hanging SSH in CentOS 7 and Systemd
by Oliver Schad 29 Aug '14

29 Aug '14

Hi Harald, On Sat, 30 Aug 2014 00:45:02 +0200 Reindl Harald <h.reindl(a)thelounge.net> wrote: > Am 30.08.2014 um 00:26 schrieb Oliver Schad: > > I have a problem with my SSH sessions if I reboot with CentOS 7: my > > SSH sessions seems terminated after the network is already shutdown. > > > > How to fix that with Systemd? > > what have you done on your system? > how is your network started (NM, netwoerk.service) Through network.service Because I had trouble with the NetworkManager I've switched back to "normal" network management. > that was fixed long before RHEL7 GA even if it > took many months after first appear in Fedora 20 > > https://bugzilla.redhat.com/show_bug.cgi?id=626477 Seems back again. I just wondering how such easy things can be so hard so solve. Best Regards Oli

1 0

Hanging SSH in CentOS 7 and Systemd
by Oliver Schad 29 Aug '14

29 Aug '14

Hi all, I have a problem with my SSH sessions if I reboot with CentOS 7: my SSH sessions seems terminated after the network is already shutdown. How to fix that with Systemd? Thank you in advance and best regards Oli

1 0

Inconsistent printing on Centos 7
by Frank Cox 29 Aug '14

29 Aug '14

I have ongoing issues with my Xerox Phaser 2550 printer under Centos 7. It always worked without any issues on Centos 6 before I upgraded to Centos 7. The problem manifests itself by regularly (but not every time) printing page after page of garbage instead of the document that I wanted to print out. Sometimes it works, sometimes it doesn't. The same document might print fine now but then I get pages of garbage the next time I print. I have it set up as a shared printer on my network; the other computers on my network are all Centos 6. Printing from another computer on my network sometimes works but more often prints pages of garbage. When experimenting with this last night printing test pages from system-config-printer on a Centos 6 machine to the printer on this Centos 7 machine, I sometimes got a "Connecting to printer" message and then nothing printed until I restarted cups on the Centos 6 computer. This didn't happen every time; once again sometimes I got a test page printed, sometimes I got pages of garbage, sometimes I got the "connecting to printer" message and had to restart cups on the Centos 6 computer. Having become tired of this, I disconnected the printer from my Centos 7 machine and connected it to one of the Centos 6 machines and it worked without error when printing from that computer directly and when printing to it from another Centos 6 machine. The printer also showed up by magic as a discovered printer on the other Centos 6 machine, but didn't show up on the Centos 7 machine until I loaded system-config-printer on Centos 7, "new", and told it to search for network printers on the Centos 6 machine. Therefore, automatic printer discovery doesn't seem to work on this Centos 7 machine either. Now that the printer is connected to a Centos 6 machine again it appears to work fine when talking to other Centos 6 machines on the network and the printer is automatically discovered. After searching for the network printer from the Centos 7 machine and setting it up using the default (just hitting ok after it found the printer), my first attempt at printing a test page gave me a sheet that says this: #PDF-BANNER Template default-testpage.pdf Show printer-name printer-info printer-location printer-make-and-model printer-d river-name printer-driver-version paper-size imageable-area job-id options time- at-creation time-at-processing This obviously wasn't what I expected to see, so I ran system-config-printer on the Centos 7 machine again and changed the printer driver for that printer to Xerox Phaser 3150, the same as the setting on the Centos 6 machine that the printer is now connected to. Now the test page prints fine, but I get two sheets out of the printer every time I print the test page. The first one says "**** Warning: glyf overlaps cmap, truncating." Then the test page prints as expected. After printing the test page I get a printer error icon (printer with a red dot and white line on it) in the notification area on my panel. Clicking on that icon does nothing and hovering over it does nothing either but the only way it goes away is if I log out and log back in. In conclusion, the printing really doesn't work properly from this Centos 7 machine, regardless of whether the printer is directly connected or if I'm printing over the network. Direct connecting the printer causes it to print pages of garbage some of the time, automatic remote printer discovery doesn't work, and manually setting up up to print to the remote printer still generates an error of some kind but does appear to print. I can find nothing in /var/log/cups that tells me anything useful. /var/log/cups/error_log isn't updated when I print to the remote printer, even though the printer error icon shows up on my panel. page_log just tells me that it printed a page. All of this stuff works perfectly and automatically from Centos 6 (both printing to the local printer on a Centos 6 machine and printing over the network from a Centos 6 machine to another Centos 6 machine). -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

3 5

Re: [CentOS] CentOS Digest, Vol 115, Issue 21
by Bill Gee 29 Aug '14

29 Aug '14

On Thursday, August 21, 2014 12:00:03 centos-request(a)centos.org wrote: > Re: [CentOS] SELinux vs. logwatch and virsh > From: Daniel J Walsh <dwalsh(a)redhat.com> > To: CentOS mailing list <centos(a)centos.org> > > On 08/18/2014 02:13 PM, Bill Gee wrote: > > Hi Dan - > > > > "ausearch -m avc -ts recent" produces no output. If I run it as "ausearch > > -f virsh" then it produces output similar to this. Each day's run of > > logwatch produces three of these audit log entries. The a1 and a2 values > > are different for each entry, but everything else is the same. > > > > =============== > > time->Mon Aug 18 03:21:03 2014 > > type=SYSCALL msg=audit(1408350063.257:7492): arch=c000003e syscall=21 > > success=no exit=-13 a0=11ee230 a1=4 a2=7fff722837b0 a3=7fff72283640 > > items=0 ppid=2815 pid=2816 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 > > egid=0 sgid=0 fsgid=0 tty=(none) ses=981 comm="bash" exe="/usr/bin/bash" > > subj=system_u:system_r:logwatch_t:s0-s0:c0.c1023 key=(null) > > type=AVC msg=audit(1408350063.257:7492): avc: denied { read } > > for pid=2816 comm="bash" name="virsh" dev="dm-0" ino=135911290 > > scontext=system_u:system_r:logwatch_t:s0-s0:c0.c1023 > > tcontext=system_u:object_r:virsh_exec_t:s0 tclass=file > > =============== > > > > I thought about using audit2allow as you suggest. The problem is then I > > don't really know what change is required. What exactly will it > > do? And is there a guarantee that it will work? > > logwatch is executing virsh probably to communicate with libvirt to > rotate logs or something. You can look in /etc/logrotate.d for a script > with virsh to tell you what the command is trying to do. Hi Dan - I know EXACTLY what virsh is being called for. I wrote the script! It has nothing to do with logrotate. I want virsh to tell logwatch what the status is of all virtual machines running on the host. Logwatch will then include that in its daily summary report. SELinux is getting in the way. Regards - Bill Gee

3 11

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