Discuss

discuss@lists.centos.org

34753 discussions

Re: [CentOS] KVM and DHCP
by James B. Byrne 14 Mar '14

14 Mar '14

On Thu, March 13, 2014 16:32, Les Mikesell wrote: > On Thu, Mar 13, 2014 at 3:11 PM, James B. Byrne <byrnejb(a)harte-lyne.ca> wrote: >> >> In any case, to fix this via virt-manager's __virtual hardware details__ >> interface one must select the __NIC__ and change the settings from <Virtual >> network default 'NAT'> to <Specify shared device name> and then input the >> bridge interface name <br0> in the text box that subsequently appears. One >> must also change the Device model: from <Hypervisor default> to <virtio>. > > I get a dropdown for the source device settings that include the host > devices, including the bridge br devices. > > -- > Les Mikesell > lesmikesell(a)gmail.com > > When creating a new machine under advanced options all I see on the drop down menu is the following: * Virtual network default 'NAT' <- selected * Host eth0 (Not bridged) <- greyed - not selectable * Host eth1 (Not bridged) <- greyed - not selectable * Host lo (Not bridged) <- greyed - not selectable * Host virbr0 (Not bridged) <- greyed - not selectable * Host vnet0 (Not bridged) <- greyed - not selectable * Host vnet1 (Not bridged) <- greyed - not selectable * Host vnet2 (Not bridged) <- greyed - not selectable * Host vnet0 (Not bridged) <- greyed - not selectable Specify shared device name <- black - selectable If I select <Specify shared device name> then, and only then, a text box with the label 'Bridge name:' appears. My memory is always suspect but I seem to recall that the defined bridge, br0' was explicitly listed as an available choice in a previous version of virt-manager and not obscured in this fashion. The term <Specify shared device name> does not, in my mind, equate to the word 'bridge'. Given the text box label that appears only when one selects <Specify a shared device name> evidently indicates that this selection only expects a bridge one wonders why such a vague phrase is used instead of something like <Specify a bridge(d) device name>. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

2 1

CentOS-announce Digest, Vol 109, Issue 7
by centos-announce-request＠centos.org 14 Mar '14

14 Mar '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. CESA-2014:0285 Important CentOS 5 kernel Update (Johnny Hughes) 2. CESA-2014:0293 Important CentOS 6 udisks Update (Johnny Hughes) 3. CESA-2014:0292 Important CentOS 6 389-ds-base Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 13 Mar 2014 10:35:06 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2014:0285 Important CentOS 5 kernel Update To: centos-announce(a)centos.org Message-ID: <20140313103506.GA1764(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2014:0285 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0285.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: fcf8cc74b66ebb078c45f1336aab7bf7a48eeb43e727a0066a9c6627a0e539a7 kernel-2.6.18-371.6.1.el5.i686.rpm 13431333cd5d14a99829d0086817c53791e226eff8bd70b42a5e552f82fe2e85 kernel-debug-2.6.18-371.6.1.el5.i686.rpm c404ec8f0eee94ffd56c89aaa5d483e2cfc264f0ff21571d0e1d0baaf0868e4c kernel-debug-devel-2.6.18-371.6.1.el5.i686.rpm 64e925a55a70f155ffe85a5dcb81a2ac0b2f075397203d8905b79d9e8c7ebe7a kernel-devel-2.6.18-371.6.1.el5.i686.rpm 7b7131ccccaf007449a1d37977fea8b2a2f162b672b674a56efe493bc727405e kernel-doc-2.6.18-371.6.1.el5.noarch.rpm acde0cbcdc23e7fc19f11073b752cd1e23953e756c3451a51c414142054bab01 kernel-headers-2.6.18-371.6.1.el5.i386.rpm 76937ee2563061f14e196115f44617e7d3069ff8d7ae2b460a8d9065ee269413 kernel-PAE-2.6.18-371.6.1.el5.i686.rpm 19fef7fa923524425ddd774b53008a9add8c80993740e9985c65f8b9049ea63c kernel-PAE-devel-2.6.18-371.6.1.el5.i686.rpm 35ca8458082c88ef2726952d7b918123a96bb2b6b00019a38ae76efd771489d7 kernel-xen-2.6.18-371.6.1.el5.i686.rpm 560497c5017201f321e48bc17525b6763a06dca1a12386571c2286a8361d5d48 kernel-xen-devel-2.6.18-371.6.1.el5.i686.rpm x86_64: efd03ec79e18fc49eae11b99a48c9ebee21b139b2981471a27342261953eb7d7 kernel-2.6.18-371.6.1.el5.x86_64.rpm 2fb9a086af37f0d87815387cf5038b38c71d77f84419e9a3bf06d87a9fad135a kernel-debug-2.6.18-371.6.1.el5.x86_64.rpm 73643a8dd6b3d5903f37ed76ee31f3d1fd22b9de2ddf188fe284b9d929d0b33b kernel-debug-devel-2.6.18-371.6.1.el5.x86_64.rpm 514ef220b8cea436a04b3467b5f4ae0adab9af2b17d3a10a2a821655bff3895a kernel-devel-2.6.18-371.6.1.el5.x86_64.rpm 7b7131ccccaf007449a1d37977fea8b2a2f162b672b674a56efe493bc727405e kernel-doc-2.6.18-371.6.1.el5.noarch.rpm d622d2c233f429d03ba02e95c72b02d65210f211ec71ba8d2a8cc8fb5e2d6de2 kernel-headers-2.6.18-371.6.1.el5.x86_64.rpm d7619c7c3255b8b73419528595bf320f4de8258bb99eb340313e51541710e878 kernel-xen-2.6.18-371.6.1.el5.x86_64.rpm 8bec65cd5812e22ffa4912012fef8216e7b7a650958a8fe80945a846c5e15137 kernel-xen-devel-2.6.18-371.6.1.el5.x86_64.rpm Source: 36b11ff5c4df065624903f54127f4843602f31b221a6ac49cc7027368db442d1 kernel-2.6.18-371.6.1.el5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Thu, 13 Mar 2014 21:38:21 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2014:0293 Important CentOS 6 udisks Update To: centos-announce(a)centos.org Message-ID: <20140313213821.GA51546(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2014:0293 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0293.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 6a7e447f943f804e2e9d8367f27a294c673ae9511ec3633e77f3d83d3bd3cdad udisks-1.0.1-7.el6_5.i686.rpm dd4dd623e69b1cb1ce7b893e5fa47ccad21e6fbca62e164c50488cbd479999f5 udisks-devel-1.0.1-7.el6_5.i686.rpm 2e315e3000db0fb932afa907ebc322ca0bd9de192fb2a0bd31ff61962d8e89a8 udisks-devel-docs-1.0.1-7.el6_5.noarch.rpm x86_64: 008cc6b158a94aa2a7b17d6bf14b7b6771637ae9a7b3be57e68a249a27535cdb udisks-1.0.1-7.el6_5.x86_64.rpm dd4dd623e69b1cb1ce7b893e5fa47ccad21e6fbca62e164c50488cbd479999f5 udisks-devel-1.0.1-7.el6_5.i686.rpm 9cbf02b31e364d173963050d7b4dfaf6c85bf7397c9581d8595e95c3294f5cca udisks-devel-1.0.1-7.el6_5.x86_64.rpm 2e315e3000db0fb932afa907ebc322ca0bd9de192fb2a0bd31ff61962d8e89a8 udisks-devel-docs-1.0.1-7.el6_5.noarch.rpm Source: 8975dbcff3201f58a71c6502d659648c0eaa6959e76f4e21c33fffaa85f138f6 udisks-1.0.1-7.el6_5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net ------------------------------ Message: 3 Date: Thu, 13 Mar 2014 21:39:06 +0000 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2014:0292 Important CentOS 6 389-ds-base Update To: centos-announce(a)centos.org Message-ID: <20140313213906.GA51792(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2014:0292 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0292.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 093e81daa795444190e43151f81aabf6b7aa49c686ea5bc9d12a337b8d990332 389-ds-base-1.2.11.15-32.el6_5.i686.rpm 567046fea065a1e85e533d7c676330ab0c7fa9a3356f0065685fbefca2084739 389-ds-base-devel-1.2.11.15-32.el6_5.i686.rpm c31c88d289576e19019e0639cf4cb3fb282886cfc2f5a68414948c36e483f249 389-ds-base-libs-1.2.11.15-32.el6_5.i686.rpm x86_64: 340a52479375fb0317c6a089a0b2f04858b4246065124df1e7a6a4d4ae74752d 389-ds-base-1.2.11.15-32.el6_5.x86_64.rpm 567046fea065a1e85e533d7c676330ab0c7fa9a3356f0065685fbefca2084739 389-ds-base-devel-1.2.11.15-32.el6_5.i686.rpm d4ebd42e2e00865ca5c444e0cb5a7214d489b9d597c3549b5658beb11eeffdbc 389-ds-base-devel-1.2.11.15-32.el6_5.x86_64.rpm c31c88d289576e19019e0639cf4cb3fb282886cfc2f5a68414948c36e483f249 389-ds-base-libs-1.2.11.15-32.el6_5.i686.rpm 8222746c12e8dd50af127e18458533e4165679c31a17e0afc7c21e0b7cbc4448 389-ds-base-libs-1.2.11.15-32.el6_5.x86_64.rpm Source: e4b47cdd45fea8086d5e74c8f894508c6399d7d7987895d7435893c420345063 389-ds-base-1.2.11.15-32.el6_5.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 109, Issue 7 ***********************************************

1 0

Advanced Fat32 mount in /etc/fstab
by John Doe 14 Mar '14

14 Mar '14

Hi, my name is Steven. I am trying to figure out the mount command to put into /etc/fstab; Basically I want a FAT32 partition mounted, but I want specific user/group ownership for a normal user of the mountpoint and all directorys/files in it. I currently have this in /etc/fstab: /dev/sda8 /home/steven/sda8 vfat locale=en_US.utf8,windows_names,uid=500,gid=501,umask=0022,noatime 0 0 but i get the following: [root@centos steven]# mount /dev/sda8 mount: wrong fs type, bad option, bad superblock on /dev/sda8, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so

2 3

Re: [CentOS] KVM and DHCP
by James B. Byrne 13 Mar '14

13 Mar '14

On Thu, March 13, 2014 15:49, Reindl Harald wrote: > > > Am 13.03.2014 20:43, schrieb James B. Byrne: >> CentOS-6.5 >> >> We have a KVM guest running MS-WinV7pro. This guest is joined to an Active >> Directory Domain. That domain provides DHCP to the members. The KVM guest >> does not obtain its IP from the domain but from the local host's qemu >> hypervisor instead. >> >> Is there anyway to get around this and have the guest MS-Win OS get its DHCP >> from the same place as the rest of the domain members? > > smells like you are using NAT for your guest instead > bridge it to the host network, the guest does not > know from where it gets DHCP infos and there should > not be more than one dhcpd on a network segment, anything > else leads to race-conditions - the faster dhcpd wins > > http://www.dedoimedo.com/computers/kvm-bridged.html > > maybe the article is outdated, try google as i did > https://www.google.at/search?q=kvm+nat+versus+bridging > > Yes, that was it. Apparently if one creates a kvm guest via the virt-manager gui application then NAT is automatically selected as the default. It may be that the other guests were originally hand-crafted via virsh and the br0 interface was specified for them, but I doubt that. I have been using virt-manager since day one on this project and I am getting a queasy feeling that virt-manager's behaviour has obscurely changed in significant ways since I first began using it. This is not the first problem that I have had creating new guests with recent versions of virt-manager which were not in evidence with earlier use. In any case, to fix this via virt-manager's __virtual hardware details__ interface one must select the __NIC__ and change the settings from <Virtual network default 'NAT'> to <Specify shared device name> and then input the bridge interface name <br0> in the text box that subsequently appears. One must also change the Device model: from <Hypervisor default> to <virtio>. Thanks for the pointer. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

2 1

logwatch named logs
by John R Pierce 13 Mar '14

13 Mar '14

ever since implementing the no-recursion-on-outside queries fix on one of my name servers, my logwatch emails have been 10-20MB/day, filled with crud like... client 10.191.192.212 query (cache) 'm.777.liyuanxi.com/A/IN' denied: 1 Time(s) client 10.192.34.96 query (cache) 'dyjwntl.www.0411gogo.com/A/IN' denied: 1 Time(s) client 10.192.43.105 query (cache) 'doitxwx.777.liyuanxi.com/A/IN' denied: 1 Time(s) client 10.192.90.161 query (cache) 'v.www.90uc.com/A/IN' denied: 1 Time(s) any idea how to suppress this? this is centos 5.latest with bind 9.7 -- john r pierce 37N 122W somewhere on the middle of the left coast

8 11

KVM and DHCP
by James B. Byrne 13 Mar '14

13 Mar '14

CentOS-6.5 We have a KVM guest running MS-WinV7pro. This guest is joined to an Active Directory Domain. That domain provides DHCP to the members. The KVM guest does not obtain its IP from the domain but from the local host's qemu hypervisor instead. Is there anyway to get around this and have the guest MS-Win OS get its DHCP from the same place as the rest of the domain members? -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

2 1

apache, krb5 annoyances
by m.roth＠5-cent.us 13 Mar '14

13 Mar '14

Something I've been fighting since yesterday... I got trac installed, and working. Then I had to add security. Got all the moving pieces in - mod_ssl, auth_kerb. If I go to https://hostname/trac, everything's fine, a popup window asks for username and password. But if I go to https://hostname.f.q.d.n/trac, it fails, returning a 500? 501? Internal server error. I'm on a workstation running CentOS 6.5; my user, on Windows and running IE, gets the same. But if I open another firefox window with -P --no-remote, and pick another profile, it works. I certainly have no idea what to try in IE.... But I think there's some other misconfiguration of apache. Anyone have any thoughts on the matter? I don't think management will appreciate a head-shaped hole in the wall by my cube.... mark

1 0

createrepo and parallel drpm generation
by Johnny Hughes 13 Mar '14

13 Mar '14

I wanted to point out this functionality in case others want to test it: http://centosnow.blogspot.com/2014/03/createrepo-and-parallel-delta-rpms-on… For the record, this cuts down the metadata generation to 1/4 of the original time on my test platform. Other relevant links: http://lists.baseurl.org/pipermail/yum-devel/2014-February/010580.html https://github.com/imcleod/createrepo/tree/feature/parallel_deltas_full http://people.centos.org/hughesjr/createrepo_delta/ Thanks, Johnny Hughes

1 0

Re: [CentOS] Anyone using trac on centos?
by m.roth＠5-cent.us 13 Mar '14

13 Mar '14

Hi, Dan, Daniel J Walsh wrote: > On 03/12/2014 04:52 PM, m.roth(a)5-cent.us wrote: >> Peter Brady wrote: >>> On 13/03/14 5:02 AM, m.roth(a)5-cent.us wrote: >>>> (Besides Paul, who's busy?) >>>> >>>> I just need one question answered: I keep reading the docs, and given >>>> the old traditional /var/www I get that part of trac should be >>>> installed in /var/www/trac/<myproj> (I think); what I can't figure out >>>> is whether there is *anything* under the document root, that is, >>>> /var/www/html/trac/<myproject>. >>>> >>>> Anyone have a clue? Do I even need it as a placeholder, or does >>>> anything actually go in there? <snip> >>> For the single site install I've got a few things in /var/www/html: >>> >>> [root@develop www]# ls html/ >> <snip> Thanks, Peter. Between you and Paul, and, of course, much >> googling, <snip> >> Installing the agilo-plugin was easy (well, I'll know when my user gets >> going). Now shutting up selinux.... And no, what I found was *wrong*, it >> was telling you to use chcon, which does *not* last across reboots. >> semanage (bleah!).... >> > Mark what changes did you have to make for SELinux? So far, all I've done is to change the fcontexts to httpd_sys_content_t, except for the cgi, which is httpd_sys_script_exec_t. I hadn't managed to google what to do with the trac.fsgi, which selinux doesn't seem to like as the latter context. What I was referring to, above, was someone's post that I found while googling, who was saying you should chcon, which, as much as you know how much I adore selinux (NOT!), I know to use semanage and restorecon. Hmmm, I see the nightly run of updatedb is complaining: I have the cgi-bin directory itself as httpd_sys_script_exec_t - what should that be, anyway? The more I think of it, the less I like some of this.... -rw-r--r--. apache root system:object_r:httpd_sys_content_t:s0 README -rw-r--r--. apache root system:object_r:httpd_sys_content_t:s0 VERSION drwxr-xr-x. apache root system:object_r:httpd_sys_content_t:s0 attachments drwxr-xr-x. apache root system:object_r:httpd_sys_script_exec_t:s0 cgi-bin drwxr-xr-x. apache root system:object_r:httpd_sys_content_t:s0 conf drwxr-xr-x. apache root system:object_r:httpd_sys_content_t:s0 db drwxr-xr-x. apache root system:object_r:httpd_sys_content_t:s0 htdocs drwxr-xr-x. apache root system:object_r:httpd_sys_content_t:s0 log drwxr-xr-x. apache root system:object_r:httpd_sys_content_t:s0 plugins drwxr-xr-x. apache root system:object_r:httpd_sys_content_t:s0 templates Seems to me that none of that but VERSION and htdocs should be content.... Advice? Let's get this correct, and I'll post, and email trac about what they should do. Right now, <http://trac.edgewall.org/wiki/TracWithSeLinux> is what they say, and they mention chcon with CentOS 6.3. I see they have a policy (which, for some reason, is *not* part of the trac package via upstream). I suppose I could implement it, but I'd rather get someone who actually knows what they're talking about look at what they say and advise me, Dan. mark.

1 0

Anyone using trac on centos?
by m.roth＠5-cent.us 13 Mar '14

13 Mar '14

(Besides Paul, who's busy?) I just need one question answered: I keep reading the docs, and given the old traditional /var/www I get that part of trac should be installed in /var/www/trac/<myproj> (I think); what I can't figure out is whether there is *anything* under the document root, that is, /var/www/html/trac/<myproject>. Anyone have a clue? Do I even need it as a placeholder, or does anything actually go in there? mark

4 4

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