- Discuss - lists.centos.org

how to limit cpu usage for specified processes
by qw 07 Sep '16

07 Sep '16

Hi, Is there some tool or method in centos that can limit cpu usage to some percentage for specified processes that consume large cpu resource? I found cpulimit which is only able to limit one process. what I want is one tool that can limit several same processes' cpu usage. Thanks! Regards andrew

3 2

Where to get good threadpool c library
by qw 07 Sep '16

07 Sep '16

Hi, I can find many c libraries of good threadpool on centos. But is there some good threadpool c library for centos/linux? Thanks! regards andrew

1 0

Strange behaviour when using sudo+sh+executable.
by Rafał Radecki 07 Sep '16

07 Sep '16

Hi All. I am trying to install some software. Part of its installation is an invocation of command similar to: # sudo -H -E -u postgres /bin/bash -c /usr/bin/python2.7 /bin/bash: /usr/bin/python2.7: Permission denied >From my perspective: # ls -l /bin/bash /usr/bin/python2.7 -rwxr-xr-x. 1 root root 960376 Jul 8 2015 /bin/bash -rwxr-xr-x. 1 root root 7136 Oct 11 2015 /usr/bin/python2.7 # su - postgres Last login: Tue Sep 6 11:51:45 CEST 2016 on pts/6 -sh-4.2$ /bin/bash -c /usr/bin/python2.7 Python 2.7.5 (default, Oct 11 2015, 17:47:16) [GCC 4.8.3 20140911 (Red Hat 4.8.3-9)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> I tried the same for /bin/top. From my perspective this is quite a strange behaviour. Can someone help with this problem? BR, Rafal.

2 2

Re: [CentOS] group write permissions not being respected
by Chris Murphy 07 Sep '16

07 Sep '16

On Tue, Sep 6, 2016, 8:08 PM Pat Haley <phaley(a)mit.edu> wrote: > > Trying the gluster client seems to fix the problem. > Hmm, suggests an NFS export issue then, rather than permissions issue? Chris Murphy

1 0

None
by None 07 Sep '16

07 Sep '16

by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u8727fcW006708 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <centos(a)centos.org>; Tue, 6 Sep 2016 22:07:42 -0400 To: centos(a)centos.org References: <d059a28c-b866-5056-dda6-29e3077ca907(a)mit.edu> <8d10f9b1-0ed9-0217-ae0e-726acd1d9a87(a)gmail.com> <8d59038f-3dbe-5bff-9673-fbada1d3f31c(a)mit.edu> <b9abfd5a5a37f29bff085aae6174877f.squirrel(a)host290.hostmonster.com> <d9ac7e12-3283-ea9e-a5b0-5dcd8d27d87d(a)mit.edu> <CAJCQCtTfr6rvPGH7uMNzYE9-Q+BfZ784a5n=4S5NekA7O8VxAA(a)mail.gmail.com> <c29b1a4f-a3d5-b61e-7206-b6e32a89f72c(a)mit.edu> <CAJCQCtQ6vq6OQsbgZjxz2qqgjGwh-XEwsoeBYjzwNMMcvQkDrQ(a)mail.gmail.com> From: Pat Haley <phaley(a)mit.edu> Message-ID: <8b172cfc-7a1a-39e2-a259-a698f2fa63ba(a)mit.edu> Date: Tue, 6 Sep 2016 22:07:35 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <CAJCQCtQ6vq6OQsbgZjxz2qqgjGwh-XEwsoeBYjzwNMMcvQkDrQ(a)mail.gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOIsWRmVeSWpSXmKPExsUixG6nrptXdj7cYP5DE4tlZxYwOzB6rGyb zBzAGMVlk5Kak1mWWqRvl8CVMbv5EVPBCfGKBZ/CGxhnCHcxcnJICJhInGh6ydzFyMUhJNDG JHG/8yobhHOCUeLq/8ksEM4BJomW/suMIC3CAo4SL15uZwOxRQREJXoWv4LquMIsMeHuRyaQ BJuAgsS6W2fYQWxeASuJqXdvgDWzCKhI7Dv+ihnEFhWIkLi16iMjRI2gxMmZT1hAbE6BQIm5 E2eC2cwCthJ35u5mhrDlJba/ncM8gZF/FpKWWUjKZiEpW8DIvIpRNiW3Sjc3MTOnODVZtzg5 MS8vtUjXVC83s0QvNaV0EyM4/FyUdjBO/Od1iFGAg1GJh7di97lwIdbEsuLK3EOMkhxMSqK8 aoFAIb6k/JTKjMTijPii0pzU4kOMEhzMSiK8swrPhwvxpiRWVqUW5cOkpDlYlMR5u2YcCBcS SE8sSc1OTS1ILYLJynBwKEnwVpcCNQoWpaanVqRl5pQgpJk4OEGG8wANzwCp4S0uSMwtzkyH yJ9iVJQS550JkhAASWSU5sH1gtODGvuhV4ziQK8I8y4HqeIBpha47ldAg5mABq/bfRpkcEki QkqqgdHumJ85C5vW18rsVTyCu9hbrXdG2i/MkH2WXn78eE+i2V6Lk/ebckNVCli+3O24tr6E bfeV0xsEjxTsCnVyNN0hMzf47a/tF/aLrCntn2w/MVOm4uYq+am5pdVfVWufLhcQn1Nz3Db2 jNUdszzZz0YlYSf0ikR1G3PO+afcqT8ke64wUXd1ixJLcUaioRZzUXEiANN4uRjqAgAA Subject: Re: [CentOS] group write permissions not being respected X-BeenThere: centos(a)centos.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe: <https://lists.centos.org/mailman/options/centos>, <mailto:centos-request@centos.org?subject=unsubscribe> List-Archive: <http://lists.centos.org/pipermail/centos/> List-Post: <mailto:centos@centos.org> List-Help: <mailto:centos-request@centos.org?subject=help> List-Subscribe: <https://lists.centos.org/mailman/listinfo/centos>, <mailto:centos-request@centos.org?subject=subscribe> X-List-Received-Date: Wed, 07 Sep 2016 02:07:43 -0000 Trying the gluster client seems to fix the problem. On 09/02/2016 12:57 AM, Chris Murphy wrote: > On Thu, Sep 1, 2016, 8:11 AM Pat Haley <phaley(a)mit.edu> wrote: > >> For the enforcing=0, is that referring to SELinux? If so, we are not >> running SELinux. >> > > OK so neither that nor chcon nor context mount option apply. It's something > else. > > > > > >> On 08/31/2016 11:38 PM, Chris Murphy wrote: >> >> ---------------------------------------------------------------------------------------- >>> Try booting with enforcing=0 and if that fixes it, you need to find out >>> what security label is needed for gluster. >> ---------------------------------------------------------------------------------------- >> For the enforcing=0, is that referring to SELinux? If so, we are not >> running SELinux. >> >> ----------------------------------------------------------------------------------------- >> >>> Chances are it's easiest to use -o context= mount option on the brick, >> but >>> if the brick is not exclusive to gluster you'll need chcon -R. >> ----------------------------------------------------------------------------------------- >> We aren't sure exactly what you mean by this second paragraph, can >> you expand on this? Are these two exclusive options exclusive? We aren't >> sure what you what you mean by "exclusive to gluster" >> >> ----------------------------------------------------------------------------------------- >>> If that's not it, maybe try the gluster client instead of using NFS. See >> if >>> you get a different result that narrows down what's going on. >>> >>> My vague recollection is for Samba, without the correct SELinux label, I >>> could neither read nor write. >>> >>> >>> Chris Murphy >>> _______________________________________________ >>> CentOS mailing list >>> CentOS(a)centos.org >>> https://lists.centos.org/mailman/listinfo/centos >> -- >> >> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >> Pat Haley Email: phaley(a)mit.edu >> Center for Ocean Engineering Phone: (617) 253-6824 >> Dept. of Mechanical Engineering Fax: (617) 253-8125 >> MIT, Room 5-213 http://web.mit.edu/phaley/www/ >> 77 Massachusetts Avenue >> Cambridge, MA 02139-4301 >> >> _______________________________________________ >> CentOS mailing list >> CentOS(a)centos.org >> https://lists.centos.org/mailman/listinfo/centos >> > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley(a)mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301

1 0

389 Directory Server
by Paolo Rughetti 06 Sep '16

06 Sep '16

Hi all, I would like install 389 Directory Server on a Centos 6.8 server. I followed the instructions reported in : https://wiki.centos.org/HowTos/DirectoryServerSetup?highlight=%28directory%… and installed with yum the following packages : 389-ds-base-1.2.11.15-75.el6_8.x86_64 389-ds-console-1.2.6-1.el6.noarch 389-ds-base-libs-1.2.11.15-75.el6_8.x86_64 389-adminutil-1.1.19-1.el6.x86_64 389-admin-1.1.35-1.el6.x86_64 To proceed with the installation I would like to read the instructions reported here : https://access.redhat.com/documentation/en/red-hat-directory-server/ where I can choose the product version between 8.0 to 10. I would like to know which version of 389 Directory Server match installed packages so I can select the right manual. I would like also to know if it is better install the last version of 389 from http://www.port389.org. Thanking you in advance. Bets regards. -- *---*---*---*---*---*---*---*---*---*---*---*---*---*---* Paolo Rughetti Consiglio Nazionale delle Ricerche Istituto per le Applicazioni del Calcolo "M. Picone" Via dei Taurini 19 00185 ROME ITALY _____________________________ |\___________________________/| |E-mail: p.rughetti(a)iac.cnr.it| |Tel: 039-06-49270956 | |Fax: 039-06-4404306 | |_____________________________| *---*---*---*---*---*---*---*---*---*---*---*---*---*---*

2 1

more than one IP address on network device?
by Walter H. 06 Sep '16

06 Sep '16

Hello /etc/sysconfig/network-scripts/ifcfg-eth0 looks like this: # Intel Corporation 82545EM Gigabit Ethernet Controller (Copper) TYPE=Ethernet NAME=eth0 NM_CONTROLLED=no IPV4_FAILURE_FATAL=yes UUID=cc2635ff-3c14-48ba-b19a-84c5b9d36a9d ONBOOT=yes DEVICE=eth0 BOOTPROTO=none HWADDR=00:50:56:01:00:01 BROADCAST=192.168.0.255 IPADDR=192.168.0.10 NETMASK=255.255.255.0 NETWORK=192.168.0.0 GATEWAY=192.168.0.1 DNS1=192.168.0.1 DNS2=192.168.0.100 DOMAIN='domain.tld' USERCTL=no IPV6INIT=yes IPV6ADDR=ipv6addr IPV6_AUTOCONF=no IPV6_DEFAULTGW=ipv6addr-gateway IPV6_DEFAULTDEV=eth0 if I would need an additional IPv6 address I'd just add IPV6ADDR_SECONDARIES="ipv6addr" to this file; if I would need an additional IPv4 address this works only by a virtual device e.g. eth0:1 like this: /etc/sysconfig/network-scripts/ifcfg-eth0:1 # Intel Corporation 82545EM Gigabit Ethernet Controller (Copper), Alias 1 TYPE=Ethernet DEVICE=eth0:1 ONPARENT=yes BOOTPROTO=none BROADCAST=192.168.0.255 IPADDR=192.168.0.17 NETMASK=255.255.255.0 NETWORK=192.168.0.0 GATEWAY=192.168.0.1 DNS1=192.168.0.1 DNS2=192.168.0.100 why can't I add this to the virtual device eth0:1, if I needed both an additional IPv4 and an additional IPv6 address? IPV6INIT=yes IPV6ADDR=ipv6addr IPV6_AUTOCONF=no IPV6_DEFAULTGW=ipv6addr-gateway IPV6_DEFAULTDEV=eth0:1 Thanks, Walter

12 20

/etc/sysconfig/network HOSTNAME settings
by Walter H. 06 Sep '16

06 Sep '16

Hello, I found different ways to define the hostname ... this HOSTNAME="host.domain.tld" or this: HOSTNAME="host" DOMAIN="domain.tld" what is the correct way? Thanks, Walter

2 1

mounting lvm2
by Alice Wonder 06 Sep '16

06 Sep '16

CentOS 7 for everything I am probably never using lvm again. I have never not once actually benefited from its capabilities but this is probably the third or fourth time it has gotten in my way. Issue is that I use the tools so rarely that I can't recall what needs to be done to properly mount the drives on another system and finding that info on the web is becoming more difficult as the noise in search results increases, more and more results are damn youtube videos, and my eyes are deteriorating. So its just fixed ext4 for me in the future, KISS. End of rant. PC mobo died. Most data I need from it backed up to github, few things done that day didn't make the last commit and I'd rather not do them again. Trying to mount drive on my laptop via USB interface. Which is easy when drives are plain old ext4 and not ext4 sitting on top lvm2. * end frustrated rant * [root@localhost ~]# vgs VG #PV #LV #SN Attr VSize VFree centos 1 3 0 wz--n- 111.30g 0 centos 1 3 0 wz--n- 223.08g 0 [root@localhost ~]# vgscan Reading all physical volumes. This may take a while... Found volume group "centos" using metadata type lvm2 Found volume group "centos" using metadata type lvm2 [root@localhost ~]# [root@localhost ~]# pvdisplay /dev/sdb2 --- Physical volume --- PV Name /dev/sdb2 VG Name centos PV Size 111.30 GiB / not usable 4.00 MiB Allocatable yes (but full) PE Size 4.00 MiB Total PE 28492 Free PE 0 Allocated PE 28492 PV UUID mnFTy9-PoVX-paaA-iBML-kXh5-1Zk5-PQTPW1 [root@localhost ~]# That's the volume that I need to mount, it is in a VG named centos which is the same VG name as what the laptop I am using uses. I have created /mnt/tmp which is where I want to mount it. I am a bit worried both having the same VG name (centos) may be an issue, I believe the next step is suppose to be to use vgchange to activate the volume group but I am a bit hesitant to issuing that command with an argument that includes a volume group that is already active. There is only one physical disc in the volume I need to mount, that was a lesson I learned the hard way previously - don't use multiple disks in a LVM2 volume without hardware redundancy. And with today's disk sizes it really isn't needed, not for what I do. Where do I go from here to mount that volume? Thanks. -- -=- Sent my from my laptop, may not be able to respond timely

4 4

Network manager cannot connet to the Internet
by sunyeping 06 Sep '16

06 Sep '16

Dear all, I find out of a sudden my Network manager cannot connect to the Internet. My OS is Centos 6.7, and the version of Network manager is Applet 0.8.1. When clinking the Network manager icon at the upper right conner at the Desktop of my compuer, I can see in the pop-up manu that there are two network cards (Intel 82573E Gigabit Ethernet Controller (Copper) and Intel 82573L Gigabit Ethernet Controller) but only one link (System eth1) available. Usually when clicking the "System eth1" the Internet connection would be established. However from this morning clicking the "System eth1" only gives connect failure information. I don't know whether this is caused by intalling a large software package (ambertool 16 ) which requires many updates in my system yesterday. But when I give "ifconfig" command in a gnome terminal, the output information seems to be correct: [sunyp@localhost Desktop]$ ifconfig eth0 Link encap:Ethernet HWaddr 00:25:90:72:E2:86 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:16 Memory:faee0000-faf00000 eth1 Link encap:Ethernet HWaddr 00:25:90:72:E2:87 inet6 addr: fe80::225:90ff:fe72:e287/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:49 errors:0 dropped:0 overruns:0 frame:0 TX packets:11 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:16386 (16.0 KiB) TX bytes:3038 (2.9 KiB) Interrupt:17 Memory:fafe0000-fb000000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:90 errors:0 dropped:0 overruns:0 frame:0 TX packets:90 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6737 (6.5 KiB) TX bytes:6737 (6.5 KiB) What I can do now? Could anyone help me with this problem? Best regards. Yeping Sun

3 2

Whether to use systemd to start services
by Stalker, Tim 06 Sep '16

06 Sep '16

I'm wondering if it's normally required to start services with systemd as opposed to sysv? I currently load a few services using the old init.d/service funtionality, which still works fine. Is this ok or is sysv going to be fully discontinued in the future? The service I load is celeryd via init.d but so far finding few pointers as to how to do this with a celery.service file. I can load the service with this line execStart=/etc/init.d/celeryd Thanks, Tim

2 1

CentOS-announce Digest, Vol 139, Issue 1
by centos-announce-request＠centos.org 06 Sep '16

06 Sep '16

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-2016:1797 Moderate CentOS 6 ipa Security Update (Johnny Hughes) 2. CESA-2016:1809 Important CentOS 6 thunderbird Security Update (Johnny Hughes) 3. CESA-2016:1809 Important CentOS 7 thunderbird Security Update (Johnny Hughes) 4. CESA-2016:1797 Moderate CentOS 7 ipa Security Update (Johnny Hughes) 5. CEBA-2016:1782 CentOS 5 kernel BugFix Update (Johnny Hughes) 6. CEEA-2016:1780 CentOS 7 megaraid_sas Enhancement Update (Johnny Hughes) 7. CESA-2016:1809 Important CentOS 5 thunderbird Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Mon, 5 Sep 2016 21:43:35 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1797 Moderate CentOS 6 ipa Security Update Message-ID: <20160905214335.GA53161(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1797 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1797.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 9a76945f5e53fe3c46ba6b2e8d41153083e277ed1489e061e0362b367cf24d4c ipa-admintools-3.0.0-50.el6.centos.2.i686.rpm 6f680dcb53cac90df163ec295785294f0ec32f24b15597a5daca0313b08381ee ipa-client-3.0.0-50.el6.centos.2.i686.rpm 84e184732f6308d01aafb08ab5fb9a1ae598e8e7571ff3e0f3a1ffdf7ab7ea1e ipa-python-3.0.0-50.el6.centos.2.i686.rpm 07fef5c092bac45a50d3247960ecdc0dec541fbfbec477d3349e1448d35c14d6 ipa-server-3.0.0-50.el6.centos.2.i686.rpm 4d5b11679dc5e57df4fa0dc140286d0b9ef412427595428b34082022512b3d76 ipa-server-selinux-3.0.0-50.el6.centos.2.i686.rpm deeeed4c887d0e4e30d89488530783aa9753a5b745a4ecbe693871a48304acea ipa-server-trust-ad-3.0.0-50.el6.centos.2.i686.rpm x86_64: 587735bf88f12a0bafd20ee1a9705a95005bc96a0de2e38af2b7fda50000ef0e ipa-admintools-3.0.0-50.el6.centos.2.x86_64.rpm 031cba9a9b15305d4012ec302075d00775177f2b90edc81708d05e7d3eb6231f ipa-client-3.0.0-50.el6.centos.2.x86_64.rpm be36a599f91e5145e3bfe7f2667df00bc8ce3a687116faf44319b4aa489cb11a ipa-python-3.0.0-50.el6.centos.2.x86_64.rpm eb88f0ebfae6ab06720dd9e7fc39084f49be08e779348489881a89e784727ef6 ipa-server-3.0.0-50.el6.centos.2.x86_64.rpm 83f5893b4987c35cec70208fc24b6d4b791711b98c872af999ffd65174e7feb5 ipa-server-selinux-3.0.0-50.el6.centos.2.x86_64.rpm bafa5aff6a70875f2c61f6b98743d699e33ba416d14cfc8376fe9942c8455b3f ipa-server-trust-ad-3.0.0-50.el6.centos.2.x86_64.rpm Source: eedfa288be6cc62b86d9256c2858fcf24a0ee92f76ae69bed4c6138e3a1a651c ipa-3.0.0-50.el6.centos.2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Tue, 6 Sep 2016 00:52:40 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1809 Important CentOS 6 thunderbird Security Update Message-ID: <20160906005240.GA57754(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1809 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1809.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 160bf41d5398da8512e7fa77a05c3a0dc80d7360cfa79391a8a81cfc4ecb6352 thunderbird-45.3.0-1.el6.centos.i686.rpm x86_64: 6373b92e88b90d043376aa5d712bf272ad3ef57cdf869ffced7c8ab225c121e2 thunderbird-45.3.0-1.el6.centos.x86_64.rpm Source: 30a522d59cf4ea68f38a2abaeff0678b933f47ac3f24d488548a33d66c50d526 thunderbird-45.3.0-1.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, 6 Sep 2016 01:03:39 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1809 Important CentOS 7 thunderbird Security Update Message-ID: <20160906010339.GA611(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1809 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1809.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: b27f983a9dec3f17f00b47d9d7666b09f4cec07dda59f802698355cb03f7637f thunderbird-45.3.0-1.el7.centos.x86_64.rpm Source: 6212956c18c7e6d7dde1b6008ef6ce2ba4b4cbe1be20ab3a7df8760c9d64074d thunderbird-45.3.0-1.el7.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Tue, 6 Sep 2016 01:06:50 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1797 Moderate CentOS 7 ipa Security Update Message-ID: <20160906010650.GA738(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1797 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1797.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: a7723ce570b09c36f1ada06495f1f94a29da95d4c67fd0e65bef2b88887e3759 ipa-admintools-4.2.0-15.0.1.el7.centos.19.x86_64.rpm d87a6bb3956f5260d41dcedfe36a9baec7769896554203cb2aae40094f84d19f ipa-client-4.2.0-15.0.1.el7.centos.19.x86_64.rpm edef4178644b2c9563a267ffa829b27788e2835a4f3da1c99e41298ff181ddda ipa-python-4.2.0-15.0.1.el7.centos.19.x86_64.rpm 6e4ec8cea775914ea5901ca0cb79f11784382402a2d3dee3087c292e2941f47d ipa-server-4.2.0-15.0.1.el7.centos.19.x86_64.rpm 008c9b943528d60aac4f50114a3b414d969f3d8833a70d2384370b48d2c93501 ipa-server-dns-4.2.0-15.0.1.el7.centos.19.x86_64.rpm 4d05bc6e0bbb71e03c1b30875ab2753510885e2b31af15039c05c12960c30b4e ipa-server-trust-ad-4.2.0-15.0.1.el7.centos.19.x86_64.rpm Source: 02a7bacd4d9918c760425e5dbefd0f3fddfbbc7ea676f2d6e5ac05f62b689a49 ipa-4.2.0-15.0.1.el7.centos.19.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 5 Date: Tue, 6 Sep 2016 02:32:18 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:1782 CentOS 5 kernel BugFix Update Message-ID: <20160906023218.GA2750(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:1782 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1782.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 1cceade3db635e6bf40767b8aa889f606f9cd2dc520fb052a96b6e57238feaa0 kernel-2.6.18-412.el5.i686.rpm 8945438f684a6aa25b76fd80feb732b9ac3e255d04b58de5505564a7145bd3b5 kernel-debug-2.6.18-412.el5.i686.rpm 61d2a461ba59ac6e320467b30bf6c42e987404f38d66cb31a5dd79521d3b3687 kernel-debug-devel-2.6.18-412.el5.i686.rpm 72605760160a752047e16fd5df9ed9fe570adc9971cff8541cee85c0c8b46a53 kernel-devel-2.6.18-412.el5.i686.rpm 42f7cc1cbb5cef688e2ce0c2eb08762893388a62d82abf9c29e9177c925aa805 kernel-doc-2.6.18-412.el5.noarch.rpm 2d9bb3dec0d4fc5d10c0b0387f29548873e4a1f392a6ab6942d1b89aa59ff438 kernel-headers-2.6.18-412.el5.i386.rpm b4172316d3e8f8abf971e584ff1f6430608ecd3a39a1905eb100b863a326779b kernel-PAE-2.6.18-412.el5.i686.rpm e6ab24b639e50767707b7f12db2df390bd3ca890dfae45a1a3f8d3140c5fd72a kernel-PAE-devel-2.6.18-412.el5.i686.rpm cb983ecf3dfc441fab4fce2d37b3bf7f7ff5aac9fe540b7f9f2960314e62c54e kernel-xen-2.6.18-412.el5.i686.rpm 65ae34ecd9bea1bf2602db9a86c2c18cf092def5f66974c355ea406d6e1a141f kernel-xen-devel-2.6.18-412.el5.i686.rpm x86_64: 84f47ad942923cf26eee3b7d5b11f568432dd0254f4134e00e691e44a05ce487 kernel-2.6.18-412.el5.x86_64.rpm 05514dabf3ebedfdc73dac2f3a6b5fa225652a6b975466e5dcbfad6750600b77 kernel-debug-2.6.18-412.el5.x86_64.rpm ff51e7bcf97ce8d7e06ba182b887c027179d8b8f098ea27e4fce26b742735997 kernel-debug-devel-2.6.18-412.el5.x86_64.rpm ba7bb3a039d17b1b77c6b61d1bcb10a5b525d86409b5d62675f6e3050fd74491 kernel-devel-2.6.18-412.el5.x86_64.rpm 42f7cc1cbb5cef688e2ce0c2eb08762893388a62d82abf9c29e9177c925aa805 kernel-doc-2.6.18-412.el5.noarch.rpm 7fc9955692715dbdc376b44010bea114e71f4504c31174102edc4666242111bc kernel-headers-2.6.18-412.el5.x86_64.rpm 8e2b726c35e8abf898ba536ae46bd2d5dda07e05ccaabb20149e36cdbfe2a632 kernel-xen-2.6.18-412.el5.x86_64.rpm 69087d91bc243cbea186d77f15ed57b5f53da6871ab9fe2d8a71484bf7f6a04e kernel-xen-devel-2.6.18-412.el5.x86_64.rpm Source: 396e2d189ecfb2c31254e7d657e208ac3c9ea0e31f7ae399ca7a5f9b36b97495 kernel-2.6.18-412.el5.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: JohnnyCentOS ------------------------------ Message: 6 Date: Tue, 6 Sep 2016 03:16:44 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2016:1780 CentOS 7 megaraid_sas Enhancement Update Message-ID: <20160906031644.GA4629(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2016:1780 Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-1780.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 3f942683663a5acf3ec76fbc4da33363451ff5778ea1da2dec382806510af15f kmod-megaraid_sas-06.811.02.00-1.el7_2.x86_64.rpm Source: 1433047acea21ed246eb8eaf21f0b6856722158687bdc521ab9a6466566d798d megaraid_sas-06.811.02.00-1.el7_2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 7 Date: Tue, 6 Sep 2016 03:19:56 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1809 Important CentOS 5 thunderbird Security Update Message-ID: <20160906031956.GA4578(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1809 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1809.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 4cb84a2e017f0e5ed15f2c76e633f1ed84c23d466fb11c856847cbd3e49a3533 thunderbird-45.3.0-1.el5.centos.i386.rpm x86_64: 5ef01b379661dcf482838ccac167aeb9fca091b6fa2cfab1ca0a0facf3d41523 thunderbird-45.3.0-1.el5.centos.x86_64.rpm Source: f6a805f44b19087570cae54f6790916279351bf878bd9f51f742bd7175803877 thunderbird-45.3.0-1.el5.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: JohnnyCentOS ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 139, Issue 1 ***********************************************

1 0

hacking grub to control number of retained kernels.
by Fred Smith 06 Sep '16

06 Sep '16

I've recently had this problem on two C7 systems, wherein when doing "yum update", I get a warning about /boot being low on space. both systems were installed using the partition size recommended by Anaconda, right now "df -h" shows /boot as 494M, with 79M free. I don't store unrelated crap on /boot, I assume that yum and/or grub will manage it for me. So, why, after over a year, is it running low on space on two different systems? Is there some location in /boot where junk piles up, but shouldn't, that I have to know about so I can clean it out? I see EIGHT initramfs files in /boot, two per kernel, same name but one has a kdump just before the .img suffix. do I need those for old kernels that I may or may not ever boot? (they're 30 to 50 MB each). For the moment I've edited /etc/grub.conf and changed installonly_limit from 4 to 3. (related question: do I need to manually remove the oldest kernel, having done this, or will yum/grub clean it up the next time there's a kernel to install?) thanks! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- I can do all things through Christ who strengthens me. ------------------------------ Philippians 4:13 -------------------------------

4 4

Centos7 kickstart & pxe
by johan.vermeulen7＠telenet.be 05 Sep '16

05 Sep '16

Hello All, I'm trying to get kickstart to work through pxe. So far I've set up dhcp server, tftp and so on. But it seems at some point I always get stuck because the iso file is write-protected. I've tried remounting it rw, and I 've dd the iso first, I then get EM not a block device. Any help would be appreciated. Greetings, J.

3 4

/etc/sysconfig/network HOSTNAME settings
by Walter H. 04 Sep '16

04 Sep '16

Hello, I found different ways to define the hostname ... this HOSTNAME="host.domain.tld" or this: HOSTNAME="host" DOMAIN="domain.tld" what is the correct way? Thanks, Walter

3 2

How do I install uwsgi + python 3?
by Yuri Kanivetsky 04 Sep '16

04 Sep '16

Hi, >From what I can see, epel doesn't have python 3's pip. But when I install python35u (ius) and uwsgi-python-plugin3, uwsgi's python doesn't seem to find virtual env's packages. When I install python34u (ius) and uwsgi-plugin-python3, I get a conflict. Am I doing anything wrong? Regards, Yuri

1 0

Re: [CentOS] Networking/routing issue
by tdukes＠palmettoshopper.com 03 Sep '16

03 Sep '16

-------- Original Message -------- Subject: Re: [CentOS] Networking/routing issue From: Ulf Volmer <u.volmer(a)u-v.de> Date: Sat, September 03, 2016 5:47 am To: centos(a)centos.org On 09/03/2016 01:31 PM, TE Dukes wrote: > Centos 6.8 server eth0 > 192.168.1.110 > gateway 192.168.1.111 > eth1 > 192.168.1.111 > gateway > 192.168.1.100 > | > | > Switch > other computers and devices > gateway 192.168.1.110 > > I want to send all internal traffic through 192.168.1.110, all external > traffic through 192.168.1.111, then back through 192.168.1.110. As far as i understand, you have two interfaces in the same subnet. This is usually a bad idea. best regards Ulf Volmer A few of the examples I tried, had them on different subnets. I will change that and see what happens. Thanks

1 0

Networking/routing issue
by TE Dukes 03 Sep '16

03 Sep '16

Hello, I've been working on this for over a week. I don't think its working the way it should. Here's what I'm trying to do: I have a Windstream dsl router with wireless > 192.168.1.100 | | Centos 6.8 server eth0 > 192.168.1.110 > gateway 192.168.1.111 eth1 > 192.168.1.111 > gateway 192.168.1.100 | | Switch > other computers and devices > gateway 192.168.1.110 I want to send all internal traffic through 192.168.1.110, all external traffic through 192.168.1.111, then back through 192.168.1.110. I did an iptables -t nat -A POSTROUTING -o eth1 -j MASQUERADE Issues: Outside connectivity for all other computers and devices only works if eth0 is also connected to the router, server works Iptraf shows no traffic on eth1 Hope I haven't confused you as I have thoroughly confused myself. TIA TE Dukes

3 3

Re: [CentOS] Network manager cannot connet to the Internet
by sunyeping 03 Sep '16

03 Sep '16

Hi, Earl, Thank you very much for your prompt response.There is no output for "ip route"I don't know what is my default gateway and how to check it? And how to check the device that I am connecting to? Best regards. Yeping------------------------------------------------------------------From:Earl A Ramirez <earlaramirez(a)gmail.com>Time:2016 Sep 3 (Sat) 18:38To:CentOS mailing list <centos(a)centos.org>Subject:Re: [CentOS] Network manager cannot connet to the Internet What is the output of ip route show, can you ping your gateway, first see if you can ping your default gateway and if you can't you will have to check the device that your are connecting to. -- Kind Regards Earl Ramirez _______________________________________________ CentOS mailing list CentOS(a)centos.org https://lists.centos.org/mailman/listinfo/centos

1 0

Re: [CentOS] CentOS Digest, Vol 140, Issue 1
by SUDHANSHU BHUTANI 02 Sep '16

02 Sep '16

On Thu, Sep 1, 2016 at 5:30 PM, <centos-request(a)centos.org> wrote: > Send CentOS mailing list submissions to > centos(a)centos.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.centos.org/mailman/listinfo/centos > or, via email, send a message with subject or body 'help' to > centos-request(a)centos.org > > You can reach the person managing the list at > centos-owner(a)centos.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of CentOS digest..." > > > Today's Topics: > > 1. Re: CentOS 6 - logwatch report not in HTML format (Arun Khan) > 2. Re: NODEJS010-NPM is not getting installed due to dependency > errors on Custom Centos ISO installation (Jim Perrin) > 3. Re: CentOS 6 - logwatch report not in HTML format > (Alexander Farber) > 4. Re: CentOS 6 - logwatch report not in HTML format (Arun Khan) > 5. Re: CentOS 6 - logwatch report not in HTML format > (Alexander Farber) > 6. Re: group write permissions not being respected (Gordon Messmer) > 7. Re: CentOS 6 - logwatch report not in HTML format (Arun Khan) > 8. Re: group write permissions not being respected (Pat Haley) > 9. Re: group write permissions not being respected (m.roth(a)5-cent.us) > 10. Re: group write permissions not being respected (Pat Haley) > 11. Re: group write permissions not being respected (Chris Murphy) > 12. Perl Unsafe Module Path Handling Directory Traversal > Vulnerability ( CVE-2016-1238) (Sidharth Sharma) > 13. Bind Vulnerability CVE-2016-2775 (Sidharth Sharma) > 14. Re: "Windows" share issue; access via smb:// fails, "mount -t > cifs" works (Toralf Lund) > 15. Re: Bind Vulnerability CVE-2016-2775 (James Pearson) > 16. Re: Bind Vulnerability CVE-2016-2775 (Mike Burger) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 31 Aug 2016 07:11:11 -0700 > From: Arun Khan <knura9(a)gmail.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] CentOS 6 - logwatch report not in HTML format > Message-ID: > <CAHhM8gCz6SDqu8i5aHkUU58Sb91cHdNKUy=J_rYP25X48gk22Q(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On Mon, Aug 29, 2016 at 10:24 PM, Alexander Farber > <alexander.farber(a)gmail.com> wrote: >> No, I mean there is sometimes a variable for mail format too: > > The HTML formatting is a logwatch option, invoked through the > logwatch.conf file. > > -- Arun Khan > > > ------------------------------ > > Message: 2 > Date: Wed, 31 Aug 2016 09:20:26 -0500 > From: Jim Perrin <jperrin(a)centos.org> > To: centos(a)centos.org > Subject: Re: [CentOS] NODEJS010-NPM is not getting installed due to > dependency errors on Custom Centos ISO installation > Message-ID: <a607d751-c5e7-91eb-9e81-b6cdb379ecfa(a)centos.org> > Content-Type: text/plain; charset=windows-1252 > > > > On 08/31/2016 03:48 AM, SUDHANSHU BHUTANI wrote: >> Hi, >> >> I have built successfully all the dependent packages of nodejs010 and npm. >> >> I have used following command:- >> *rpmbuild --define 'scl nodejs010' --bb SPEC/name_of_spec.spec* > > You should really use mock, so that you don't have unintended libraries > from your build host included/linked/required in the resulting rpm. Thanks Jim for responding. I tried with mock configuration, but, not sure, i am still getting the same errors via repoclosre tool:- This directory has got all the RPMs formed by mock. [root@localhost YUM_CISCO_RPMS]# repoclosure -r Cisco-yum-dep-check Reading in repository metadata - please wait.... Checking Dependencies Repos looked at: 1 Cisco-yum-dep-check Num Packages in Repos: 1515 package: nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(readable-stream) < 0:2 package: nodejs010-nodejs-cmd-shim-2.0.0-2.el7.centos.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(graceful-fs) < 0:4 package: nodejs010-nodejs-columnify-1.3.2-3.el7.centos.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(strip-ansi) >= 0:2.0.0 package: nodejs010-nodejs-fstream-ignore-1.0.2-1.el7.centos.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(minimatch) < 0:3 package: nodejs010-nodejs-gauge-1.2.2-3.el7.centos.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(has-unicode) < 0:2 package: nodejs010-nodejs-init-package-json-1.9.1-1.el7.centos.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(promzard) >= 0:0.3.0 package: nodejs010-nodejs-npm-registry-client-7.0.8-1.el7.centos.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(retry) >= 0:0.8.0 nodejs010-npm(request) >= 0:2.47.0 nodejs010-npm(concat-stream) >= 0:1.4.6 package: nodejs010-nodejs-which-1.2.0-1.el7.centos.noarch from Cisco-yum-dep-check unresolved deps: nodejs010-npm(is-absolute) < 0:0.2 The only difference from my (for build of nodejs010-nodejs-which-1.2.0-1.el7.centos.noarch.rpm) build-log and http://cbs.centos.org/kojifiles/packages/nodejs010-nodejs-are-we-there-yet/… is following line:- *Requires: nodejs010-nodejs(engine) nodejs010-npm(delegates) nodejs010-npm(readable-stream)* - >> THIS IS FROM CBS mock log and following is my build log:- *Requires: nodejs010-nodejs(engine) nodejs010-npm(delegates) >= 0.1.0 nodejs010-npm(delegates) < 0.2 nodejs010-npm(readable-stream) >= 1.1.13 nodejs010-npm(readable-stream) < 2* I am not sure, why parsing of these version is defining a range, maybe its coming from package.json file. I feel, its related to nodejs010-build package which has root/usr/lib/rpm/nodejs010.req, i defined mock configuration like this:- config_opts['root'] = 'epel-7-x86_64' config_opts['target_arch'] = 'x86_64' config_opts['legal_host_arches'] = ('x86_64',) config_opts['chroot_setup_cmd'] = 'install @buildsys-build scl-utils-build nodejs010-build' Do they look good? Following is my build.log [sbhutani@localhost ~]$ cat nodejs-build/nodejs010- Display all 316 possibilities? (y or n) [sbhutani@localhost ~]$ cat nodejs-build/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.src.rpm/build.log Mock Version: 1.2.18 ENTER ['do'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'], chrootPath='/var/lib/mock/epel-7-x86_64/root'shell=FalseprintOutput=Falseenv={'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '}gid=135user='mockbuild'timeout=0logger=<mockbuild.trace_decorator.getLog object at 0x22e3390>uid=1000) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '} and shell False Building target platforms: x86_64 Building for target x86_64 Wrote: /builddir/build/SRPMS/nodejs-are-we-there-yet-1.0.4-1.el7.centos.src.rpm Child return code was: 0 Mock Version: 1.2.18 ENTER ['do'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'], chrootPath='/var/lib/mock/epel-7-x86_64/root'shell=FalseprintOutput=Trueenv={'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '}gid=135user='mockbuild'timeout=0logger=<mockbuild.trace_decorator.getLog object at 0x1772390>uid=1000) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '} and shell False Building target platforms: x86_64 Building for target x86_64 Wrote: /builddir/build/SRPMS/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.src.rpm Child return code was: 0 Mock Version: 1.2.18 ENTER ['do'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'], chrootPath='/var/lib/mock/epel-7-x86_64/root'shell=FalseprintOutput=Falseenv={'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '}gid=135user='mockbuild'timeout=0logger=<mockbuild.trace_decorator.getLog object at 0x142d390>uid=1000) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '} and shell False Building target platforms: x86_64 Building for target x86_64 Wrote: /builddir/build/SRPMS/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.src.rpm Child return code was: 0 ENTER ['do'](['bash', '--login', '-c', u'/usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'], chrootPath='/var/lib/mock/epel-7-x86_64/root'shell=Falseuid=1000env={'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '}gid=135user='mockbuild'timeout=0private_network=Truelogger=<mockbuild.trace_decorator.getLog object at 0x142d390>printOutput=False) Executing command: ['bash', '--login', '-c', u'/usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/nodejs-are-we-there-yet.spec'] with env {'LANG': 'en_US.UTF-8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': '<mock-chroot> \\s-\\v\\$ '} and shell False Building target platforms: x86_64 Building for target x86_64 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.cNqdgI + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf package + /usr/bin/gzip -dc /builddir/build/SOURCES/are-we-there-yet-1.0.4.tgz + /usr/bin/tar -xf - + STATUS=0 + '[' 0 -ne 0 ']' + cd package + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + rm -rf node_modules + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.iiP8RP + umask 022 + cd /builddir/build/BUILD + cd package + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.IFmFuX + umask 022 + cd /builddir/build/BUILD + '[' /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64 '!=' / ']' + rm -rf /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64 ++ dirname /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64 + mkdir -p /builddir/build/BUILDROOT + mkdir /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64 + cd package + mkdir -p /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64/opt/rh/nodejs010/root/usr/lib/node_modules/are-we-there-yet + cp -pr package.json index.js /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64/opt/rh/nodejs010/root/usr/lib/node_modules/are-we-there-yet + /usr/lib/rpm/nodejs010-symlink-deps /opt/rh/nodejs010/root/usr/lib/node_modules + /usr/lib/rpm/find-debuginfo.sh --strict-build-id -m --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 /builddir/build/BUILD/package /usr/lib/rpm/sepdebugcrcfix: Updated 0 CRC32s, 0 CRC32s did match. + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/brp-scl-compress /opt/rh/nodejs010/root + /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/brp-scl-python-bytecompile /usr/bin/python 1 /opt/rh/nodejs010/root + /usr/lib/rpm/brp-python-hardlink + /usr/lib/rpm/redhat/brp-java-repack-jars Processing files: nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.noarch Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.7DYIy5 + umask 022 + cd /builddir/build/BUILD + cd package + DOCDIR=/builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64/opt/rh/nodejs010/root/usr/share/doc/nodejs010-nodejs-are-we-there-yet-1.0.4 + export DOCDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64/opt/rh/nodejs010/root/usr/share/doc/nodejs010-nodejs-are-we-there-yet-1.0.4 + cp -pr README.md /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64/opt/rh/nodejs010/root/usr/share/doc/nodejs010-nodejs-are-we-there-yet-1.0.4 + exit 0 Finding Provides: /usr/lib/rpm/nodejs010.prov Finding Requires(interp): Finding Requires(rpmlib): Finding Requires(verify): Finding Requires(pre): Finding Requires(post): Finding Requires(preun): Finding Requires(postun): Finding Requires(pretrans): Finding Requires(posttrans): Finding Requires: /usr/lib/rpm/nodejs010.req Provides: nodejs010-nodejs-are-we-there-yet = 1.0.4-1.el7.centos nodejs010-npm(are-we-there-yet) = 1.0.4 Requires(rpmlib): rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 Requires: nodejs010-nodejs(engine) nodejs010-npm(delegates) >= 0.1.0 nodejs010-npm(delegates) < 0.2 nodejs010-npm(readable-stream) >= 1.1.13 nodejs010-npm(readable-stream) < 2 Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64 Wrote: /builddir/build/RPMS/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.noarch.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.yi6hbn + umask 022 + cd /builddir/build/BUILD + cd package + /usr/bin/rm -rf /builddir/build/BUILDROOT/nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.x86_64 + exit 0 Child return code was: 0 [sbhutani@localhost ~]$ Can any one catch difference between my build.log and CBS build.log. If hhorak is on this mailing list who actually built this package on CBS, can help? Appreciate your inputs. >> >> Following is the list of RPMs cloned and built from GIT:- >> > > <snip> > > >> >> *However, when we copy these RPMS to our ISO, anaconda installer fails >> to install due to dependency errors:-* > > > You should use the 'repoclosure' utility to make sure that you have met > all the dependencies of packages in the repo on your iso. > > > >> How is it possible, to get these errors, how come packages are not >> satisfying minimum dependency for working of NPM? > > > repoclosure should tell you. You may be missing something scl related. > > >> >> If i do yumdownloader for all these above RPMs from repo: [centos-sclo-rh] >> : http://mirror.centos.org/centos/7/sclo/x86_64/rh/nodejs010/) then i >> get following RPMs without "centos" name:- > > > Correct. This is an rpm macro change. by default the 'centos' is added > in there. > > >> >> *If i copy paste above RPMS to my custom ISO, then anaconda >> successfully installs these packages, without any errors* > > > This would suggest something is wrong with your build. See previous > statement about using mock vs rpmbuild. > > >> *What is there is these already built RPMs (taken from repo: [centos-sclo-rh] >> : http://mirror.centos.org/centos/7/sclo/x86_64/rh/nodejs010/) which >> is not there in my built RPMS?* > > That's kind of up to you to figure out, since we can't see your custom > built ones. > > >> Any pointers for this, as we feel, there is some inconsistency in the >> version available on git.centos.org/git/rpms/<name_of_pkg>.git ? > > More likely it's in your build method. > > > -- > Jim Perrin > The CentOS Project | http://www.centos.org > twitter: @BitIntegrity | GPG Key: FA09AD77 > > > ------------------------------ > > Message: 3 > Date: Wed, 31 Aug 2016 16:58:17 +0200 > From: Alexander Farber <alexander.farber(a)gmail.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] CentOS 6 - logwatch report not in HTML format > Message-ID: > <CAADeyWiMVpHh=CDZ6zi_OEq+5HwysoqTAOABDnM4mkYeFDhxYA(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > logwatch is run as cronjob. > > On Wed, Aug 31, 2016 at 4:11 PM, Arun Khan <knura9(a)gmail.com> wrote: > >> On Mon, Aug 29, 2016 at 10:24 PM, Alexander Farber >> <alexander.farber(a)gmail.com> wrote: >> > No, I mean there is sometimes a variable for mail format too: >> >> The HTML formatting is a logwatch option, invoked through the >> logwatch.conf file. >> >> -- Arun Khan >> _______________________________________________ >> CentOS mailing list >> CentOS(a)centos.org >> https://lists.centos.org/mailman/listinfo/centos >> > > > ------------------------------ > > Message: 4 > Date: Wed, 31 Aug 2016 08:31:28 -0700 > From: Arun Khan <knura9(a)gmail.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] CentOS 6 - logwatch report not in HTML format > Message-ID: > <CAHhM8gDhhgRNb1C2rKRdE+v8w_fEhBmCvarf3MxO=njxL7w3-g(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On Wed, Aug 31, 2016 at 7:58 AM, Alexander Farber > <alexander.farber(a)gmail.com> wrote: >> logwatch is run as cronjob. > > Let's take cron out of the picture. Invoking logwatch from an > interactive shell -- no joy. The report still goes out in text > format. > > -- Arun Khan > > > ------------------------------ > > Message: 5 > Date: Wed, 31 Aug 2016 17:59:44 +0200 > From: Alexander Farber <alexander.farber(a)gmail.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] CentOS 6 - logwatch report not in HTML format > Message-ID: > <CAADeyWiYQ_TNjZHZ9af2x3TM_Lq+U9LE+y4aheb6BXV_TBwGaQ(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > You should have provided more info initially. > > "goes out in text format" might mean several things. > > On Wed, Aug 31, 2016 at 5:31 PM, Arun Khan <knura9(a)gmail.com> wrote: > >> On Wed, Aug 31, 2016 at 7:58 AM, Alexander Farber >> <alexander.farber(a)gmail.com> wrote: >> > logwatch is run as cronjob. >> >> Let's take cron out of the picture. Invoking logwatch from an >> interactive shell -- no joy. The report still goes out in text >> format. >> >> -- Arun Khan >> _______________________________________________ >> CentOS mailing list >> CentOS(a)centos.org >> https://lists.centos.org/mailman/listinfo/centos >> > > > ------------------------------ > > Message: 6 > Date: Wed, 31 Aug 2016 09:50:45 -0700 > From: Gordon Messmer <gordon.messmer(a)gmail.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] group write permissions not being respected > Message-ID: <8d10f9b1-0ed9-0217-ae0e-726acd1d9a87(a)gmail.com> > Content-Type: text/plain; charset=windows-1252; format=flowed > > On 08/30/2016 03:01 PM, Pat Haley wrote: >> the owner of a directory can still write to that directory but any >> other member of the associated group cannot, even though the directory >> clearly has group write permissions set > > > Use "getfacl" on both the client and server side to view the complete > permission set. What do those look like? > > > > ------------------------------ > > Message: 7 > Date: Wed, 31 Aug 2016 10:00:42 -0700 > From: Arun Khan <knura9(a)gmail.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] CentOS 6 - logwatch report not in HTML format > Message-ID: > <CAHhM8gBBc+i9VH=eiGM+K7ePerQbv4Nraa5ck7YMEixrhbzaoQ(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On Wed, Aug 31, 2016 at 8:59 AM, Alexander Farber > <alexander.farber(a)gmail.com> wrote: >> You should have provided more info initially. >> >> "goes out in text format" might mean several things. >> > > I don't know what you mean by "several things" > > In the context of logwatch the only options are HTML or TEXT. Please see my OP. > > Thanks for your assistance. > > -- Arun Khan > > > ------------------------------ > > Message: 8 > Date: Wed, 31 Aug 2016 13:11:09 -0400 > From: Pat Haley <phaley(a)mit.edu> > To: centos(a)centos.org > Cc: Steve Postma <SPostma(a)ztechnet.com> > Subject: Re: [CentOS] group write permissions not being respected > Message-ID: <8d59038f-3dbe-5bff-9673-fbada1d3f31c(a)mit.edu> > Content-Type: text/plain; charset=windows-1252; format=flowed > > > So far, those look the same > > client: > > [root@mseas FixOwn]# getfacl /gdata/bibliography/Work/GroupBib/trunk/ > getfacl: Removing leading '/' from absolute path names > # file: gdata/bibliography/Work/GroupBib/trunk/ > # owner: phaley > # group: mseasweb > # flags: -s- > user::rwx > group::rwx > other::r-x > > server: > > [root@mseas-data2 ~]# getfacl /gdata/bibliography/Work/GroupBib/trunk/ > getfacl: Removing leading '/' from absolute path names > # file: gdata/bibliography/Work/GroupBib/trunk/ > # owner: phaley > # group: mseasweb > # flags: -s- > user::rwx > group::rwx > other::r-x > > > On 08/31/2016 12:50 PM, Gordon Messmer wrote: >> On 08/30/2016 03:01 PM, Pat Haley wrote: >>> the owner of a directory can still write to that directory but any >>> other member of the associated group cannot, even though the >>> directory clearly has group write permissions set >> >> >> Use "getfacl" on both the client and server side to view the complete >> permission set. What do those look like? >> >> _______________________________________________ >> CentOS mailing list >> CentOS(a)centos.org >> https://lists.centos.org/mailman/listinfo/centos > > -- > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Pat Haley Email: phaley(a)mit.edu > Center for Ocean Engineering Phone: (617) 253-6824 > Dept. of Mechanical Engineering Fax: (617) 253-8125 > MIT, Room 5-213 http://web.mit.edu/phaley/www/ > 77 Massachusetts Avenue > Cambridge, MA 02139-4301 > > > > ------------------------------ > > Message: 9 > Date: Wed, 31 Aug 2016 14:04:28 -0400 > From: m.roth(a)5-cent.us > To: "CentOS mailing list" <centos(a)centos.org> > Subject: Re: [CentOS] group write permissions not being respected > Message-ID: > <b9abfd5a5a37f29bff085aae6174877f.squirrel(a)host290.hostmonster.com> > Content-Type: text/plain;charset=utf-8 > > Stupid question, and note I missed most of the earlier posts in this > thread: what are the permissions on the directory that this directory are > in? > > mark > > > > ------------------------------ > > Message: 10 > Date: Wed, 31 Aug 2016 15:06:25 -0400 > From: Pat Haley <phaley(a)mit.edu> > To: centos(a)centos.org > Subject: Re: [CentOS] group write permissions not being respected > Message-ID: <d9ac7e12-3283-ea9e-a5b0-5dcd8d27d87d(a)mit.edu> > Content-Type: text/plain; charset=windows-1252; format=flowed > > > For example the directory /gdata/bibliography/Work/GroupBib/trunk/ can > be written in by user phaley but not by other users who are member of > the group mseasweb. The directory has permissions > > [root@mseas ~]# ls -lh /gdata/bibliography/Work/GroupBib > total 12K > drwxrwsr-x 4 phaley mseasweb 4.0K Aug 30 12:31 trunk > > The parent directory (/gdata/bibliography/Work/GroupBib) has permissions > > [root@mseas ~]# ls -lh /gdata/bibliography/Work/ > total 8.0K > drwxrwsr-x 6 phaley mseasweb 4.0K Aug 30 14:01 GroupBib > > > > On 08/31/2016 02:04 PM, m.roth(a)5-cent.us wrote: >> Stupid question, and note I missed most of the earlier posts in this >> thread: what are the permissions on the directory that this directory are >> in? >> >> mark >> >> _______________________________________________ >> CentOS mailing list >> CentOS(a)centos.org >> https://lists.centos.org/mailman/listinfo/centos > > -- > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Pat Haley Email: phaley(a)mit.edu > Center for Ocean Engineering Phone: (617) 253-6824 > Dept. of Mechanical Engineering Fax: (617) 253-8125 > MIT, Room 5-213 http://web.mit.edu/phaley/www/ > 77 Massachusetts Avenue > Cambridge, MA 02139-4301 > > > > ------------------------------ > > Message: 11 > Date: Thu, 01 Sep 2016 03:38:11 +0000 > From: Chris Murphy <lists(a)colorremedies.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] group write permissions not being respected > Message-ID: > <CAJCQCtTfr6rvPGH7uMNzYE9-Q+BfZ784a5n=4S5NekA7O8VxAA(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Try booting with enforcing=0 and if that fixes it, you need to find out > what security label is needed for gluster. > > Chances are it's easiest to use -o context= mount option on the brick, but > if the brick is not exclusive to gluster you'll need chcon -R. > > If that's not it, maybe try the gluster client instead of using NFS. See if > you get a different result that narrows down what's going on. > > My vague recollection is for Samba, without the correct SELinux label, I > could neither read nor write. > > > Chris Murphy > > > ------------------------------ > > Message: 12 > Date: Thu, 1 Sep 2016 11:03:30 +0530 > From: Sidharth Sharma <sharma.sidharth86(a)gmail.com> > To: centos(a)centos.org > Subject: [CentOS] Perl Unsafe Module Path Handling Directory Traversal > Vulnerability ( CVE-2016-1238) > Message-ID: > <CAAQ4EFk7qgWvq=ZtSOugxsgQ1S54y8cFbiG33POQme8+cDrcSw(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Hello Experts, > > When we can expect Security Update for Perl Vulnerability CVE-2016-1238 on > CentOS 6.8 and 7.2? > > -- > With Thanks & Regards: > Sidharth Sharma > > > ------------------------------ > > Message: 13 > Date: Thu, 1 Sep 2016 11:05:36 +0530 > From: Sidharth Sharma <sharma.sidharth86(a)gmail.com> > To: centos(a)centos.org > Subject: [CentOS] Bind Vulnerability CVE-2016-2775 > Message-ID: > <CAAQ4EF=2AeThtVjJitR3JHGhuunRJ4AZHiYDcrp4vcKFxUV=UQ(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Hello Experts, > > When we can expect Security Update for Bind Vulnerability on Centos 6.8/7.2? > ISC BIND Lightweight Resolver Protocol Req Processing Dos Vulnerability: > CVE-2016-2775 > > -- > With Thanks & Regards: > Sidharth Sharma > > > ------------------------------ > > Message: 14 > Date: Thu, 1 Sep 2016 10:26:34 +0200 > From: Toralf Lund <toralf.lund(a)pgs.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] "Windows" share issue; access via smb:// fails, > "mount -t cifs" works > Message-ID: <2265d62b-32b6-6d51-5848-df84f5800723(a)pgs.com> > Content-Type: text/plain; charset="utf-8"; format=flowed > > On 30/08/16 10:00, Toralf Lund wrote: >> Hi, >> >> Is anyone here using smb:// URLs to access "Windows" shares? I've been >> doing this for a while with common file systems at work, and it used >> to work just fine. Then I while back, I started getting issues; I will >> now just keep getting asked for a password when I try to access >> something through smb://. I thought at first that this meant there had >> been some kind of change related to permissions on the shares, but now >> I find that I can mount them just fine using "mount -t cifs". > I found out a bit more about this - I believe that I have the issue > described here: > > http://community.netapp.com/t5/Network-Storage-Protocols-Discussions/samba-… > > In other words, the problem is that "SPNEGO" fails. If I add "client use > spnego = no" to /etc/samba/smb.conf, smbclient access works (I found > that I also got a problem there), but unfortunately, gvfs-mount still > doesn't. The debug output that I get if I run gvfsd on the command line > with "GVFS_DEBUG=1" and "GVFS_SMB_DEBUG=99" actually still report SPNEGO > errors, so it would appear that the smp.conf option is for some reason > ignored. In other words the question may be: > > How do I disabled SPNEGO for gvfs-mount? > > Also, the above suggest that whether this problem occurs depends on > whether "you have SMB signing turned on or not under the 'cifs' options > section", but it not clear to me what options exactly this refers to. > Anyone? > > Oh, and some other posts I found seem to indicate that mount.cifs > doesn't support SPNEGO yet, so I guess that's why a "normal" mount works. > > - Toralf > > >> >> In other words, I get: >> >> gvfs-mount smb://mydomain\;toralf.lund@theserver/myshare >> Password required for share myshare on theserver >> Password: >> Password required for share myshare on theserver >> Password: >> Password required for share myshare on theserver >> Password: >> >> [ I enter the correct password, but gvs-mount keeps asking... >> Behaviour is the same if I try to open the URL in the file manager >> instead. ] >> >> mount -t cifs -o user=toralf.lund,workgroup=mydomain >> //theserver/myshare /tmp_mnt/ >> Password: >> >> [ At this stage the filesystem is mounted, as long as I enter the >> correct password. ] >> >> Does anyone have any idea what is going on here? Why does the VFS >> mount fail when mount.cifs works on the same share? Is there a >> difference in the way authentication works, or something? Has there >> been a change to the smb support that might explain this? >> >> This is on a CentOS 6 x86_64 installation with all updates applied. >> >> - Toralf >> > > > > ------------------------------ > > Message: 15 > Date: Thu, 1 Sep 2016 08:34:08 +0000 > From: James Pearson <james-p(a)moving-picture.com> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] Bind Vulnerability CVE-2016-2775 > Message-ID: > <85C0B54E4752CA4F873E7C78CF0B26F5010FB3748D(a)LNDWSMBX01.ad.mpc.local> > Content-Type: text/plain; charset="us-ascii" > > Sidharth Sharma: >> >> When we can expect Security Update for Bind Vulnerability on Centos 6.8/7.2? >> ISC BIND Lightweight Resolver Protocol Req Processing Dos Vulnerability: > >CVE-2016-2775 > > See: > > https://access.redhat.com/security/cve/cve-2016-2775 > > James Pearson > > ------------------------------ > > Message: 16 > Date: Thu, 01 Sep 2016 07:45:04 -0400 > From: Mike Burger <mburger(a)bubbanfriends.org> > To: CentOS mailing list <centos(a)centos.org> > Subject: Re: [CentOS] Bind Vulnerability CVE-2016-2775 > Message-ID: <400e82588e4172b96a928e1e3aeef9e3(a)bubbanfriends.org> > Content-Type: text/plain; charset=US-ASCII; format=flowed > > On 2016-09-01 4:34 am, James Pearson wrote: >> Sidharth Sharma: >>> >>> When we can expect Security Update for Bind Vulnerability on Centos >>> 6.8/7.2? >>> ISC BIND Lightweight Resolver Protocol Req Processing Dos >>> Vulnerability: >> >CVE-2016-2775 >> >> See: >> >> https://access.redhat.com/security/cve/cve-2016-2775 > > Ouch! > > Affected Packages State > Platform Package State > Red Hat Enterprise Linux 5 bind97 Will not fix > Red Hat Enterprise Linux 6 bind Will not fix > Red Hat Enterprise Linux 5 bind Will not fix > Red Hat Enterprise Linux 7 bind Will not fix > > -- > Mike Burger > http://www.bubbanfriends.org > > "It's always suicide-mission this, save-the-planet that. No one ever > just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1 > > > ------------------------------ > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos > > > End of CentOS Digest, Vol 140, Issue 1 > **************************************

1 0

Re: [CentOS] group write permissions not being respected
by Chris Murphy 02 Sep '16

02 Sep '16

On Thu, Sep 1, 2016, 8:11 AM Pat Haley <phaley(a)mit.edu> wrote: > > For the enforcing=0, is that referring to SELinux? If so, we are not > running SELinux. > OK so neither that nor chcon nor context mount option apply. It's something else. > > On 08/31/2016 11:38 PM, Chris Murphy wrote: > > ---------------------------------------------------------------------------------------- > > Try booting with enforcing=0 and if that fixes it, you need to find out > > what security label is needed for gluster. > > ---------------------------------------------------------------------------------------- > For the enforcing=0, is that referring to SELinux? If so, we are not > running SELinux. > > ----------------------------------------------------------------------------------------- > > > Chances are it's easiest to use -o context= mount option on the brick, > but > > if the brick is not exclusive to gluster you'll need chcon -R. > > ----------------------------------------------------------------------------------------- > We aren't sure exactly what you mean by this second paragraph, can > you expand on this? Are these two exclusive options exclusive? We aren't > sure what you what you mean by "exclusive to gluster" > > ----------------------------------------------------------------------------------------- > > If that's not it, maybe try the gluster client instead of using NFS. See > if > > you get a different result that narrows down what's going on. > > > > My vague recollection is for Samba, without the correct SELinux label, I > > could neither read nor write. > > > > > > Chris Murphy > > _______________________________________________ > > CentOS mailing list > > CentOS(a)centos.org > > https://lists.centos.org/mailman/listinfo/centos > > -- > > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > Pat Haley Email: phaley(a)mit.edu > Center for Ocean Engineering Phone: (617) 253-6824 > Dept. of Mechanical Engineering Fax: (617) 253-8125 > MIT, Room 5-213 http://web.mit.edu/phaley/www/ > 77 Massachusetts Avenue > Cambridge, MA 02139-4301 > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos >

1 0

Centos v6.8 and double received bytes
by Steve Malenfant 02 Sep '16

02 Sep '16

I'm observing double the amount of "recv" bytes in latest Centos v6.8 with ixgbe 4.2.1-k. Anybody seeing the same? $ ethtool -i em1 driver: ixgbe version: 4.2.1-k $ uname -an Linux chndcdmid01.rd.ph.cox.net 2.6.32-642.4.2.el6.x86_64 #1 SMP Tue Aug 23 19:58:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Doing comparison on 2 days at same hour just to show the difference. This is an HTTP cache server, having higher RX than TX means something is bad... We don't rely much on the RECV side, but our graph showed a huge difference between upgrades. Before upgrade (v6.7, 4.0.1-k) : 07:00:01 PM IFACE rxpck/s txpck/s rxkB/s txkB/s rxcmp/s txcmp/s rxmcst/s 07:00:01 PM em1 3971.90 5384.15 14981.65 26376.80 0.00 0.00 0.00 07:10:01 PM em1 3918.26 5367.79 13136.21 25528.40 0.00 0.00 0.00 07:20:01 PM em1 3868.94 5273.08 11997.37 25155.92 0.00 0.00 0.00 07:30:01 PM em1 3895.50 5597.56 10851.74 28583.84 0.00 0.00 0.00 07:40:01 PM em1 3956.80 5706.12 12230.66 29553.73 0.00 0.00 0.00 07:50:01 PM em1 4016.39 5801.69 11957.35 29979.04 0.00 0.00 0.00 After upgrade (v6.8, 4.2.1-k) : 07:00:01 PM IFACE rxpck/s txpck/s rxkB/s txkB/s rxcmp/s txcmp/s rxmcst/s 07:00:01 PM em1 20857.40 8736.13 59710.07 35102.76 0.00 0.00 0.00 07:10:01 PM em1 19508.00 8429.40 58120.70 36036.64 0.00 0.00 0.00 07:20:01 PM em1 19128.20 8471.45 55502.07 37312.56 0.00 0.00 0.00 07:30:01 PM em1 19402.55 8329.93 53586.60 35386.52 0.00 0.00 0.00 07:40:01 PM em1 19188.27 8105.83 51463.72 33585.55 0.00 0.00 0.00 07:50:01 PM em1 19544.32 7843.08 49590.64 30981.99 0.00 0.00 0.00 Steve

1 0

Perl Unsafe Module Path Handling Directory Traversal Vulnerability ( CVE-2016-1238)
by Sidharth Sharma 01 Sep '16

01 Sep '16

Hello Experts, When we can expect Security Update for Perl Vulnerability CVE-2016-1238 on CentOS 6.8 and 7.2? -- With Thanks & Regards: Sidharth Sharma

3 2

None
by None 01 Sep '16

01 Sep '16

by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u81EAcLM001706 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <centos(a)centos.org>; Thu, 1 Sep 2016 10:10:39 -0400 To: centos(a)centos.org References: <d059a28c-b866-5056-dda6-29e3077ca907(a)mit.edu> <8d10f9b1-0ed9-0217-ae0e-726acd1d9a87(a)gmail.com> <8d59038f-3dbe-5bff-9673-fbada1d3f31c(a)mit.edu> <b9abfd5a5a37f29bff085aae6174877f.squirrel(a)host290.hostmonster.com> <d9ac7e12-3283-ea9e-a5b0-5dcd8d27d87d(a)mit.edu> <CAJCQCtTfr6rvPGH7uMNzYE9-Q+BfZ784a5n=4S5NekA7O8VxAA(a)mail.gmail.com> From: Pat Haley <phaley(a)mit.edu> Message-ID: <c29b1a4f-a3d5-b61e-7206-b6e32a89f72c(a)mit.edu> Date: Thu, 1 Sep 2016 10:10:37 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <CAJCQCtTfr6rvPGH7uMNzYE9-Q+BfZ784a5n=4S5NekA7O8VxAA(a)mail.gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrBIsWRmVeSWpSXmKPExsUixG6novvA7ES4wbKPehbLzixgdmD0WNk2 mTmAMYrLJiU1J7MstUjfLoEro2v1ZZaCOfwVK46dZmxgPMPTxcjJISFgInF78VLGLkYuDiGB NiaJ20cnsEM4Jxglzs1sYoNwDjBJrJ+7ig2kRVjAUeLFy+1gtoiAqETP4ldQRXeYJI60zQJL sAkoSKy7dYYdxOYVsJL4d3IFI4jNIqAi8aJxLiuILSoQIXFr1UdGiBpBiZMzn7CA2JwCgRLr Lh1iArGZBWwl7szdzQxhy0tsfzuHeQIj/ywkLbOQlM1CUraAkXkVo2xKbpVubmJmTnFqsm5x cmJeXmqRrrFebmaJXmpK6SZGUABySvLtYJzU4H2IUYCDUYmHl8PoRLgQa2JZcWXuIUZJDiYl UV61uOPhQnxJ+SmVGYnFGfFFpTmpxYcYJTiYlUR4D5sAlfOmJFZWpRblw6SkOViUxHm7ZhwI FxJITyxJzU5NLUgtgsnKcHAoSfA+NwVqFCxKTU+tSMvMKUFIM3FwggznARruCVLDW1yQmFuc mQ6RP8WoKCXOuw9kqwBIIqM0D64XnCDU2A+9YhQHekWY9xNIOw8wucB1vwIazAQ0uOTacZDB JYkIKakGxoOFsj1Rp4xfa7cUW2gsW9+qayH73/TzFO/+g6u3Wb6v+HPW0z8uKeiJLaPmsu11 l026ZTQmeqT62Nhkb1h4eObdzGncssKrr2y7/M3yebNoiKDarJbj2px6ziePT344Q5vRWchE c7qp9Kldn943ef0s3M7aGtRsOuFFWdDBrh/ap1R3TYrmUWIpzkg01GIuKk4EAG7WrU3rAgAA Subject: Re: [CentOS] group write permissions not being respected X-BeenThere: centos(a)centos.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe: <https://lists.centos.org/mailman/options/centos>, <mailto:centos-request@centos.org?subject=unsubscribe> List-Archive: <http://lists.centos.org/pipermail/centos/> List-Post: <mailto:centos@centos.org> List-Help: <mailto:centos-request@centos.org?subject=help> List-Subscribe: <https://lists.centos.org/mailman/listinfo/centos>, <mailto:centos-request@centos.org?subject=subscribe> X-List-Received-Date: Thu, 01 Sep 2016 14:10:40 -0000 For the enforcing=0, is that referring to SELinux? If so, we are not running SELinux. On 08/31/2016 11:38 PM, Chris Murphy wrote: ---------------------------------------------------------------------------------------- > Try booting with enforcing=0 and if that fixes it, you need to find out > what security label is needed for gluster. ---------------------------------------------------------------------------------------- For the enforcing=0, is that referring to SELinux? If so, we are not running SELinux. ----------------------------------------------------------------------------------------- > Chances are it's easiest to use -o context= mount option on the brick, but > if the brick is not exclusive to gluster you'll need chcon -R. ----------------------------------------------------------------------------------------- We aren't sure exactly what you mean by this second paragraph, can you expand on this? Are these two exclusive options exclusive? We aren't sure what you what you mean by "exclusive to gluster" ----------------------------------------------------------------------------------------- > If that's not it, maybe try the gluster client instead of using NFS. See if > you get a different result that narrows down what's going on. > > My vague recollection is for Samba, without the correct SELinux label, I > could neither read nor write. > > > Chris Murphy > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley(a)mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301

1 0

Bind Vulnerability CVE-2016-2775
by Sidharth Sharma 01 Sep '16

01 Sep '16

Hello Experts, When we can expect Security Update for Bind Vulnerability on Centos 6.8/7.2? ISC BIND Lightweight Resolver Protocol Req Processing Dos Vulnerability: CVE-2016-2775 -- With Thanks & Regards: Sidharth Sharma

4 3

"Windows" share issue; access via smb:// fails, "mount -t cifs" works
by Toralf Lund 01 Sep '16

01 Sep '16

Hi, Is anyone here using smb:// URLs to access "Windows" shares? I've been doing this for a while with common file systems at work, and it used to work just fine. Then I while back, I started getting issues; I will now just keep getting asked for a password when I try to access something through smb://. I thought at first that this meant there had been some kind of change related to permissions on the shares, but now I find that I can mount them just fine using "mount -t cifs". In other words, I get: gvfs-mount smb://mydomain\;toralf.lund@theserver/myshare Password required for share myshare on theserver Password: Password required for share myshare on theserver Password: Password required for share myshare on theserver Password: [ I enter the correct password, but gvs-mount keeps asking... Behaviour is the same if I try to open the URL in the file manager instead. ] mount -t cifs -o user=toralf.lund,workgroup=mydomain //theserver/myshare /tmp_mnt/ Password: [ At this stage the filesystem is mounted, as long as I enter the correct password. ] Does anyone have any idea what is going on here? Why does the VFS mount fail when mount.cifs works on the same share? Is there a difference in the way authentication works, or something? Has there been a change to the smb support that might explain this? This is on a CentOS 6 x86_64 installation with all updates applied. - Toralf

1 1

Re: [CentOS] group write permissions not being respected
by Chris Murphy 01 Sep '16

01 Sep '16

Try booting with enforcing=0 and if that fixes it, you need to find out what security label is needed for gluster. Chances are it's easiest to use -o context= mount option on the brick, but if the brick is not exclusive to gluster you'll need chcon -R. If that's not it, maybe try the gluster client instead of using NFS. See if you get a different result that narrows down what's going on. My vague recollection is for Samba, without the correct SELinux label, I could neither read nor write. Chris Murphy

1 0

None
by None 31 Aug '16

31 Aug '16

by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u7VJ6PIp019192 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <centos(a)centos.org>; Wed, 31 Aug 2016 15:06:26 -0400 To: centos(a)centos.org References: <d059a28c-b866-5056-dda6-29e3077ca907(a)mit.edu> <8d10f9b1-0ed9-0217-ae0e-726acd1d9a87(a)gmail.com> <8d59038f-3dbe-5bff-9673-fbada1d3f31c(a)mit.edu> <b9abfd5a5a37f29bff085aae6174877f.squirrel(a)host290.hostmonster.com> From: Pat Haley <phaley(a)mit.edu> Message-ID: <d9ac7e12-3283-ea9e-a5b0-5dcd8d27d87d(a)mit.edu> Date: Wed, 31 Aug 2016 15:06:25 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <b9abfd5a5a37f29bff085aae6174877f.squirrel(a)host290.hostmonster.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrBIsWRmVeSWpSXmKPExsUixCmqrLtJ63i4wb2P5hbLzixgdmD0WNk2 mTmAMYrLJiU1J7MstUjfLoEr4/byu8wFPzgrrs+7zNjA+Im9i5GTQ0LARGLh8c1sXYxcHEIC bUwSi39fYIZwTjJKLLyznRXCOcgkcWvPV7AWYQFHiRcvt7OB2CICohI9i19BtT9hlPj2ayoT SIJNQEFi3a0zYA28AlYSzVcOgDWwCKhKLFndxQJiiwpESNxa9ZERokZQ4uTMJ2BxToEAiTVH L7GC2MwCthJ35u5mhrDlJba/ncM8gZF/FpKWWUjKZiEpW8DIvIpRNiW3Sjc3MTOnODVZtzg5 MS8vtUjXTC83s0QvNaV0EyMoANldlHcwvuzzPsQowMGoxMPr8OZYuBBrYllxZe4hRkkOJiVR 3pZXQCG+pPyUyozE4oz4otKc1OJDjBIczEoivMc0j4cL8aYkVlalFuXDpKQ5WJTEebtmHAgX EkhPLEnNTk0tSC2CycpwcChJ8M4CaRQsSk1PrUjLzClBSDNxcIIM5wEafkQDZHhxQWJucWY6 RP4Uo6KUOO8CkIQASCKjNA+uF5wg1NgPvWIUB3pFmJcNmC6EeIDJBa77FdBgJqDBBXcOgwwu SURISTUwekkEz/r5Ts9xgmniZrvezD3CvKIqb+P5P7Azrpy5cn5G7td1kfqrlaa+VBA73XvY ZouP+Ivat6VOp7UWyp70ygmaZWdk1XxgxvSrG8NWq98uvbZ9SdDf16tCGhUapSbLbogpWLg4 4YjHrLdMmouWrTp5Z9rsdxN3z2/M+KtT5s2zT+ad3u3EViWW4oxEQy3mouJEAMZPH+/rAgAA Subject: Re: [CentOS] group write permissions not being respected X-BeenThere: centos(a)centos.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe: <https://lists.centos.org/mailman/options/centos>, <mailto:centos-request@centos.org?subject=unsubscribe> List-Archive: <http://lists.centos.org/pipermail/centos/> List-Post: <mailto:centos@centos.org> List-Help: <mailto:centos-request@centos.org?subject=help> List-Subscribe: <https://lists.centos.org/mailman/listinfo/centos>, <mailto:centos-request@centos.org?subject=subscribe> X-List-Received-Date: Wed, 31 Aug 2016 19:06:26 -0000 For example the directory /gdata/bibliography/Work/GroupBib/trunk/ can be written in by user phaley but not by other users who are member of the group mseasweb. The directory has permissions [root@mseas ~]# ls -lh /gdata/bibliography/Work/GroupBib total 12K drwxrwsr-x 4 phaley mseasweb 4.0K Aug 30 12:31 trunk The parent directory (/gdata/bibliography/Work/GroupBib) has permissions [root@mseas ~]# ls -lh /gdata/bibliography/Work/ total 8.0K drwxrwsr-x 6 phaley mseasweb 4.0K Aug 30 14:01 GroupBib On 08/31/2016 02:04 PM, m.roth(a)5-cent.us wrote: > Stupid question, and note I missed most of the earlier posts in this > thread: what are the permissions on the directory that this directory are > in? > > mark > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley(a)mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301

1 0

Re: [CentOS] group write permissions not being respected
by m.roth＠5-cent.us 31 Aug '16

31 Aug '16

Stupid question, and note I missed most of the earlier posts in this thread: what are the permissions on the directory that this directory are in? mark

1 0

None
by None 31 Aug '16

31 Aug '16

by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u7VHB9vm012262 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 31 Aug 2016 13:11:10 -0400 To: centos(a)centos.org References: <d059a28c-b866-5056-dda6-29e3077ca907(a)mit.edu> <8d10f9b1-0ed9-0217-ae0e-726acd1d9a87(a)gmail.com> From: Pat Haley <phaley(a)mit.edu> Message-ID: <8d59038f-3dbe-5bff-9673-fbada1d3f31c(a)mit.edu> Date: Wed, 31 Aug 2016 13:11:09 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <8d10f9b1-0ed9-0217-ae0e-726acd1d9a87(a)gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrFIsWRmVeSWpSXmKPExsUixG6nrrue/3i4wZSrFhbLzixgtpjy+x2T A5PHyrbJzB4XG5ewBjBFcdmkpOZklqUW6dslcGV8u2xY8Iq7oqd/OmMD4z7OLkYODgkBE4np a6K6GLk4hATamCSOdD1kgXA2Mkq8OLSFDcJZySQx5fg2xi5GTg5hAUeJFy+3s4HYIgKiEj2L X4HZQgK5EjNPHGQDmcosoC7RvpQVJMwmoCCx7tYZdhCbV8BKYvmPZ2A2i4CqxMTPH5lAbFGB CIlbqz4yQtQISpyc+YQFxOYUsJVYc/8QWA0zkH1n7m5mCFteYvvbOcwTGAVmIWmZhaRsFpKy BYzMqxhlU3KrdHMTM3OKU5N1i5MT8/JSi3SN9HIzS/RSU0o3MYKClFOSdwfjv7tehxgFOBiV eHgd3hwLF2JNLCuuzD3EKMnBpCTK2/IKKMSXlJ9SmZFYnBFfVJqTWnyIUYKDWUmEN4fneLgQ b0piZVVqUT5MSpqDRUmct2vGgXAhgfTEktTs1NSC1CKYrAwHh5IEbwYfUKNgUWp6akVaZk4J QpqJgxNkOA/Q8A8gNbzFBYm5xZnpEPlTjIpS4rx3eYESAiCJjNI8uF5wElFjP/SKURzoFWFe E5B2HmACgut+BTSYCWhwwZ3DIINLEhFSUg2MW8WcvRwnrJQpPGj6JO7Mjrup8+QnHfE2yHkh feS98eZoudO7Ti/PjZrzfUGd1fkVN6onGvKEzHjbKJ9wrrthyjrn+H/bG/OzzjAuDWaoKZjC x/Tlc9TrqfXiNZmXf+3s6Mk2LGQ3VEoRKrhyoCz4jM/zKU9+ZzlNP1jnIqd469Nuiw4NMdk9 SizFGYmGWsxFxYkAxP5Cf/0CAAA= Cc: Steve Postma <SPostma(a)ztechnet.com> Subject: Re: [CentOS] group write permissions not being respected X-BeenThere: centos(a)centos.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe: <https://lists.centos.org/mailman/options/centos>, <mailto:centos-request@centos.org?subject=unsubscribe> List-Archive: <http://lists.centos.org/pipermail/centos/> List-Post: <mailto:centos@centos.org> List-Help: <mailto:centos-request@centos.org?subject=help> List-Subscribe: <https://lists.centos.org/mailman/listinfo/centos>, <mailto:centos-request@centos.org?subject=subscribe> X-List-Received-Date: Wed, 31 Aug 2016 17:11:11 -0000 So far, those look the same client: [root@mseas FixOwn]# getfacl /gdata/bibliography/Work/GroupBib/trunk/ getfacl: Removing leading '/' from absolute path names # file: gdata/bibliography/Work/GroupBib/trunk/ # owner: phaley # group: mseasweb # flags: -s- user::rwx group::rwx other::r-x server: [root@mseas-data2 ~]# getfacl /gdata/bibliography/Work/GroupBib/trunk/ getfacl: Removing leading '/' from absolute path names # file: gdata/bibliography/Work/GroupBib/trunk/ # owner: phaley # group: mseasweb # flags: -s- user::rwx group::rwx other::r-x On 08/31/2016 12:50 PM, Gordon Messmer wrote: > On 08/30/2016 03:01 PM, Pat Haley wrote: >> the owner of a directory can still write to that directory but any >> other member of the associated group cannot, even though the >> directory clearly has group write permissions set > > > Use "getfacl" on both the client and server side to view the complete > permission set. What do those look like? > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley(a)mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301

1 0

CentOS 6 - logwatch report not in HTML format
by Arun Khan 31 Aug '16

31 Aug '16

CentOS 6 (amd64) up to date with latest security / bug fixes. The logwatch reports come in plain text even though the config states HTML. <begin /etc/logwatch/conf/logwatch.conf> mailer = "/usr/sbin/sendmail -t" TmpDir = /tmp MailFrom = logwatch(a)example.com MailTo = admin1 admin2 admin3 Range = yesterday Detail = Medium HostName = www.example.com Print = No Output = mail Format = html <end /etc/logwatch/conf/logwatch.conf> The same settings in Debian/Ubuntu servers send the reports in HTML format. In my search, I did not come across any solution for CentOS 6. Any ideas on how to get logwatch to generate HTML reports? Thanks for your help. -- Arun Khan

2 8

Re: [CentOS] group write permissions not being respected
by Gordon Messmer 31 Aug '16

31 Aug '16

On 08/30/2016 03:01 PM, Pat Haley wrote: > the owner of a directory can still write to that directory but any > other member of the associated group cannot, even though the directory > clearly has group write permissions set Use "getfacl" on both the client and server side to view the complete permission set. What do those look like?

1 0

NODEJS010-NPM is not getting installed due to dependency errors on Custom Centos ISO installation
by SUDHANSHU BHUTANI 31 Aug '16

31 Aug '16

Hi, I have built successfully all the dependent packages of nodejs010 and npm. I have used following command:- *rpmbuild --define 'scl nodejs010' --bb SPEC/name_of_spec.spec* Following is the list of RPMs cloned and built from GIT:- nodejs010-2.1-5.el7.centos.x86_64.rpm nodejs010-http-parser-2.0-6.20121128gitcd01361.el7.centos.x86_64.rpm nodejs010-http-parser-devel-2.0-6.20121128gitcd01361.el7.centos.x86_64.rpm nodejs010-libuv-0.10.30-1.el7.centos.x86_64.rpm nodejs010-libuv-devel-0.10.30-1.el7.centos.x86_64.rpm nodejs010-node-gyp-3.2.0-2.el7.centos.noarch.rpm nodejs010-nodejs-0.10.40-1.el7.centos.x86_64.rpm nodejs010-nodejs-abbrev-1.0.5-1.el7.centos.noarch.rpm nodejs010-nodejs-ansi-0.3.0-1.el7.centos.noarch.rpm nodejs010-nodejs-ansicolors-0.3.2-1.el7.centos.noarch.rpm nodejs010-nodejs-ansistyles-0.1.3-1.el7.centos.x86_64.rpm nodejs010-nodejs-archy-1.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.noarch.rpm nodejs010-nodejs-array-index-0.1.1-1.el7.centos.noarch.rpm nodejs010-nodejs-asap-1.0.0-4.el7.centos.noarch.rpm nodejs010-nodejs-async-some-1.0.2-2.el7.centos.noarch.rpm nodejs010-nodejs-balanced-match-0.2.1-2.el7.centos.noarch.rpm nodejs010-nodejs-bl-1.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-block-stream-0.0.7-2.el7.centos.noarch.rpm nodejs010-nodejs-brace-expansion-1.1.1-2.el7.centos.noarch.rpm nodejs010-nodejs-builtin-modules-1.1.0-1.el7.centos.noarch.rpm nodejs010-nodejs-builtins-1.0.2-2.el7.centos.noarch.rpm nodejs010-nodejs-caseless-0.11.0-1.el7.centos.noarch.rpm nodejs010-nodejs-char-spinner-1.0.1-2.el7.centos.noarch.rpm nodejs010-nodejs-chmodr-1.0.2-1.el7.centos.noarch.rpm nodejs010-nodejs-chownr-1.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-clone-0.2.0-3.el7.centos.noarch.rpm nodejs010-nodejs-cmd-shim-2.0.0-2.el7.centos.noarch.rpm nodejs010-nodejs-columnify-1.3.2-3.el7.centos.noarch.rpm nodejs010-nodejs-concat-map-0.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-concat-stream-1.4.4-5.el7.centos.noarch.rpm nodejs010-nodejs-config-chain-1.1.9-1.el7.centos.noarch.rpm nodejs010-nodejs-core-util-is-1.0.1-2.el7.centos.noarch.rpm nodejs010-nodejs-debug-2.2.0-2.el7.centos.noarch.rpm nodejs010-nodejs-debuglog-1.0.1-4.el7.centos.noarch.rpm nodejs010-nodejs-defaults-1.0.0-5.el7.centos.noarch.rpm nodejs010-nodejs-delegates-0.1.0-1.el7.centos.noarch.rpm nodejs010-nodejs-devel-0.10.40-1.el7.centos.x86_64.rpm nodejs010-nodejs-dezalgo-1.0.2-3.el7.centos.noarch.rpm nodejs010-nodejs-editor-1.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-forever-agent-0.5.0-2.el7.centos.noarch.rpm nodejs010-nodejs-fstream-1.0.3-2.el7.centos.noarch.rpm nodejs010-nodejs-fstream-ignore-1.0.2-1.el7.centos.noarch.rpm nodejs010-nodejs-fstream-npm-1.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-fs-vacuum-1.2.6-3.el7.centos.noarch.rpm nodejs010-nodejs-fs-write-stream-atomic-1.0.3-3.el7.centos.noarch.rpm nodejs010-nodejs-gauge-1.2.2-3.el7.centos.noarch.rpm nodejs010-nodejs-github-url-from-git-1.4.0-1.el7.centos.noarch.rpm nodejs010-nodejs-github-url-from-username-repo-1.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-glob-5.0.15-1.el7.centos.noarch.rpm nodejs010-nodejs-graceful-fs-4.1.2-3.el7.centos.noarch.rpm nodejs010-nodejs-has-unicode-2.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-hosted-git-info-2.1.4-3.el7.centos.noarch.rpm nodejs010-nodejs-inflight-1.0.4-2.el7.centos.noarch.rpm nodejs010-nodejs-inherits-2.0.0-13.el7.centos.noarch.rpm nodejs010-nodejs-ini-1.2.0-1.el7.centos.noarch.rpm nodejs010-nodejs-init-package-json-1.9.1-1.el7.centos.noarch.rpm nodejs010-nodejs-is-absolute-0.2.3-3.el7.centos.noarch.rpm nodejs010-nodejs-isarray-0.0.1-3.el7.centos.noarch.rpm nodejs010-nodejs-is-builtin-module-1.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-is-relative-0.2.1-2.el7.centos.noarch.rpm nodejs010-nodejs-is-unc-path-0.1.1-2.el7.centos.noarch.rpm nodejs010-nodejs-is-windows-0.1.0-3.el7.centos.noarch.rpm nodejs010-nodejs-jju-1.2.1-1.el7.centos.noarch.rpm nodejs010-nodejs-json-parse-helpfulerror-1.0.3-1.el7.centos.noarch.rpm nodejs010-nodejs-json-stringify-safe-5.0.0-2.el7.centos.noarch.rpm nodejs010-nodejs-lockfile-1.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-lodash._basetostring-3.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-lodash._createpadding-3.6.1-1.el7.centos.noarch.rpm nodejs010-nodejs-lodash.pad-3.1.1-1.el7.centos.noarch.rpm nodejs010-nodejs-lodash.padleft-3.1.1-1.el7.centos.noarch.rpm nodejs010-nodejs-lodash.padright-3.1.1-1.el7.centos.noarch.rpm nodejs010-nodejs-lodash.repeat-3.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-lru-cache-2.7.0-1.el7.centos.noarch.rpm nodejs010-nodejs-mime-db-1.15.0-3.el7.centos.noarch.rpm nodejs010-nodejs-mime-types-2.1.3-1.el7.centos.noarch.rpm nodejs010-nodejs-minimatch-3.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-minimist-0.0.8-1.el7.centos.noarch.rpm nodejs010-nodejs-mkdirp-0.5.0-1.el7.centos.noarch.rpm nodejs010-nodejs-ms-0.7.1-2.el7.centos.noarch.rpm nodejs010-nodejs-mute-stream-0.0.4-3.el7.centos.noarch.rpm nodejs010-nodejs-node-uuid-1.4.1-2.el7.centos.noarch.rpm nodejs010-nodejs-nopt-3.0.6-1.el7.centos.noarch.rpm nodejs010-nodejs-normalize-git-url-3.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-normalize-package-data-2.3.5-1.el7.centos.noarch.rpm nodejs010-nodejs-npm-cache-filename-1.0.2-1.el7.centos.noarch.rpm nodejs010-nodejs-npm-install-checks-1.0.6-1.el7.centos.noarch.rpm nodejs010-nodejs-npmlog-2.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-npm-package-arg-4.1.0-1.el7.centos.noarch.rpm nodejs010-nodejs-npm-registry-client-7.0.8-1.el7.centos.noarch.rpm nodejs010-nodejs-npm-user-validate-0.1.1-1.el7.centos.noarch.rpm nodejs010-nodejs-once-1.3.0-1.el7.centos.noarch.rpm nodejs010-nodejs-opener-1.4.1-1.el7.centos.noarch.rpm nodejs010-nodejs-osenv-0.1.3-1.el7.centos.noarch.rpm nodejs010-nodejs-os-homedir-1.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-os-tmpdir-1.0.1-3.el7.centos.noarch.rpm nodejs010-nodejs-path-array-1.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-path-is-absolute-1.0.0-1.el7.centos.noarch.rpm nodejs010-nodejs-path-is-inside-1.0.0-1.el7.centos.x86_64.rpm nodejs010-nodejs-process-nextick-args-1.0.2-1.el7.centos.noarch.rpm nodejs010-nodejs-promzard-0.2.0-7.el7.centos.noarch.rpm nodejs010-nodejs-proto-list-1.2.2-5.el7.centos.noarch.rpm nodejs010-nodejs-qs-0.6.5-5.el7.centos.noarch.rpm nodejs010-nodejs-read-1.0.5-1.el7.centos.noarch.rpm nodejs010-nodejs-readable-stream-2.0.2-3.el7.centos.noarch.rpm nodejs010-nodejs-readdir-scoped-modules-1.0.2-1.el7.centos.noarch.rpm nodejs010-nodejs-read-installed-4.0.3-1.el7.centos.noarch.rpm nodejs010-nodejs-read-package-json-2.0.2-1.el7.centos.noarch.rpm nodejs010-nodejs-realize-package-specifier-3.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-request-2.42.0-6.el7.centos.noarch.rpm nodejs010-nodejs-retry-0.6.0-6.el7.centos.noarch.rpm nodejs010-nodejs-rimraf-2.4.3-1.el7.centos.noarch.rpm nodejs010-nodejs-semver-5.0.3-1.el7.centos.noarch.rpm nodejs010-nodejs-sha-2.0.1-2.1.el7.centos.noarch.rpm nodejs010-nodejs-slide-1.1.6-1.el7.centos.noarch.rpm nodejs010-nodejs-sorted-object-1.0.0-3.el7.centos.noarch.rpm nodejs010-nodejs-spdx-correct-1.0.2-1.el7.centos.noarch.rpm nodejs010-nodejs-spdx-exceptions-1.0.4-1.el7.centos.noarch.rpm nodejs010-nodejs-spdx-expression-parse-1.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-spdx-license-ids-1.0.1-2.el7.centos.noarch.rpm nodejs010-nodejs-string_decoder-0.10.31-1.el7.centos.noarch.rpm nodejs010-nodejs-strip-ansi-0.2.0-1.el7.centos.noarch.rpm nodejs010-nodejs-tar-2.2.1-1.el7.centos.noarch.rpm nodejs010-nodejs-text-table-0.2.0-1.el7.centos.x86_64.rpm nodejs010-nodejs-tunnel-agent-0.3.0-2.el7.centos.noarch.rpm nodejs010-nodejs-uid-number-0.0.5-1.el7.centos.noarch.rpm nodejs010-nodejs-umask-1.1.0-4.el7.centos.noarch.rpm nodejs010-nodejs-unc-path-regex-0.1.1-2.el7.centos.noarch.rpm nodejs010-nodejs-util-deprecate-1.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-util-extend-1.0.1-4.el7.centos.noarch.rpm nodejs010-nodejs-validate-npm-package-license-3.0.1-1.el7.centos.noarch.rpm nodejs010-nodejs-validate-npm-package-name-2.2.2-3.el7.centos.noarch.rpm nodejs010-nodejs-wcwidth-1.0.0-4.el7.centos.noarch.rpm nodejs010-nodejs-which-1.2.0-1.el7.centos.noarch.rpm nodejs010-nodejs-wrappy-1.0.1-2.el7.centos.noarch.rpm nodejs010-nodejs-write-file-atomic-1.1.2-3.el7.centos.noarch.rpm nodejs010-npm-2.14.13-7.el7.centos.noarch.rpm nodejs010-runtime-2.1-5.el7.centos.x86_64.rpm nodejs010-scldevel-2.1-5.el7.centos.x86_64.rpm *However, when we copy these RPMS to our ISO, anaconda installer fails to install due to dependency errors:-* nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.centos.noarch requires nodejs010-npm(readable-stream) < 2 nodejs010-nodejs-cmd-shim-2.0.0-2.el7.centos.noarch requires nodejs010-npm(graceful-fs) < 4 nodejs010-nodejs-columnify-1.3.2-3.el7.centos.noarch requires nodejs010-npm(strip-ansi) >= 2.0.0 nodejs010-nodejs-fstream-ignore-1.0.2-1.el7.centos.noarch requires nodejs010-npm(minimatch) < 3 nodejs010-nodejs-gauge-1.2.2-3.el7.centos.noarch requires nodejs010-npm(has-unicode) < 2 nodejs010-nodejs-init-package-json-1.9.1-1.el7.centos.noarch requires nodejs010-npm(promzard) >= 0.3.0 nodejs010-nodejs-npm-registry-client-7.0.8-1.el7.centos.noarch requires nodejs010-npm(concat-stream) >= 1.4.6 nodejs010-nodejs-npm-registry-client-7.0.8-1.el7.centos.noarch requires nodejs010-npm(request) >= 2.47.0 nodejs010-nodejs-npm-registry-client-7.0.8-1.el7.centos.noarch requires nodejs010-npm(retry) >= 0.8.0 nodejs010-nodejs-which-1.2.0-1.el7.centos.noarch requires nodejs010-npm(is-absolute) < 0.2 How is it possible, to get these errors, how come packages are not satisfying minimum dependency for working of NPM? If i do yumdownloader for all these above RPMs from repo: [centos-sclo-rh] : http://mirror.centos.org/centos/7/sclo/x86_64/rh/nodejs010/) then i get following RPMs without "centos" name:- nodejs010-2.1-5.el7.x86_64.rpm nodejs010-http-parser-2.0-6.20121128gitcd01361.el7.x86_64.rpm nodejs010-http-parser-devel-2.0-6.20121128gitcd01361.el7.x86_64.rpm nodejs010-libuv-0.10.30-1.el7.x86_64.rpm nodejs010-libuv-devel-0.10.30-1.el7.x86_64.rpm nodejs010-node-gyp-3.2.0-2.el7.noarch.rpm nodejs010-nodejs-0.10.40-1.el7.x86_64.rpm nodejs010-nodejs-abbrev-1.0.5-1.el7.noarch.rpm nodejs010-nodejs-ansi-0.3.0-2.el7.noarch.rpm nodejs010-nodejs-ansicolors-0.3.2-1.el7.noarch.rpm nodejs010-nodejs-ansistyles-0.1.3-1.el7.x86_64.rpm nodejs010-nodejs-archy-1.0.0-1.el7.noarch.rpm nodejs010-nodejs-are-we-there-yet-1.0.4-1.el7.noarch.rpm nodejs010-nodejs-array-index-0.1.1-1.el7.noarch.rpm nodejs010-nodejs-asap-1.0.0-4.el7.noarch.rpm nodejs010-nodejs-async-some-1.0.2-2.el7.noarch.rpm nodejs010-nodejs-balanced-match-0.2.1-2.el7.noarch.rpm nodejs010-nodejs-bl-1.0.0-1.el7.noarch.rpm nodejs010-nodejs-block-stream-0.0.7-2.el7.noarch.rpm nodejs010-nodejs-brace-expansion-1.1.1-2.el7.noarch.rpm nodejs010-nodejs-builtin-modules-1.1.0-1.el7.noarch.rpm nodejs010-nodejs-builtins-1.0.2-2.el7.noarch.rpm nodejs010-nodejs-caseless-0.11.0-1.el7.noarch.rpm nodejs010-nodejs-char-spinner-1.0.1-2.el7.noarch.rpm nodejs010-nodejs-chmodr-1.0.2-1.el7.noarch.rpm nodejs010-nodejs-chownr-1.0.1-1.el7.noarch.rpm nodejs010-nodejs-clone-0.2.0-3.el7.noarch.rpm nodejs010-nodejs-cmd-shim-2.0.0-2.el7.noarch.rpm nodejs010-nodejs-columnify-1.3.2-3.el7.noarch.rpm nodejs010-nodejs-concat-map-0.0.1-1.el7.noarch.rpm nodejs010-nodejs-concat-stream-1.4.4-5.el7.noarch.rpm nodejs010-nodejs-config-chain-1.1.9-1.el7.noarch.rpm nodejs010-nodejs-core-util-is-1.0.1-2.el7.noarch.rpm nodejs010-nodejs-debug-2.2.0-2.el7.noarch.rpm nodejs010-nodejs-debuglog-1.0.1-4.el7.noarch.rpm nodejs010-nodejs-defaults-1.0.0-5.el7.noarch.rpm nodejs010-nodejs-delegates-0.1.0-1.el7.noarch.rpm nodejs010-nodejs-devel-0.10.40-1.el7.x86_64.rpm nodejs010-nodejs-dezalgo-1.0.2-3.el7.noarch.rpm nodejs010-nodejs-editor-1.0.0-1.el7.noarch.rpm nodejs010-nodejs-forever-agent-0.5.0-2.el7.noarch.rpm nodejs010-nodejs-fstream-1.0.3-2.el7.noarch.rpm nodejs010-nodejs-fstream-ignore-1.0.2-1.el7.noarch.rpm nodejs010-nodejs-fstream-npm-1.0.1-1.el7.noarch.rpm nodejs010-nodejs-fs-vacuum-1.2.6-3.el7.noarch.rpm nodejs010-nodejs-fs-write-stream-atomic-1.0.3-3.el7.noarch.rpm nodejs010-nodejs-gauge-1.2.2-3.el7.noarch.rpm nodejs010-nodejs-github-url-from-git-1.4.0-1.el7.noarch.rpm nodejs010-nodejs-github-url-from-username-repo-1.0.0-1.el7.noarch.rpm nodejs010-nodejs-glob-5.0.15-1.el7.noarch.rpm nodejs010-nodejs-graceful-fs-4.1.2-3.el7.noarch.rpm nodejs010-nodejs-has-unicode-2.0.0-1.el7.noarch.rpm nodejs010-nodejs-hosted-git-info-2.1.4-3.el7.noarch.rpm nodejs010-nodejs-inflight-1.0.4-2.el7.noarch.rpm nodejs010-nodejs-inherits-2.0.0-13.el7.noarch.rpm nodejs010-nodejs-ini-1.2.0-1.el7.noarch.rpm nodejs010-nodejs-init-package-json-1.9.1-1.el7.noarch.rpm nodejs010-nodejs-is-absolute-0.2.3-3.el7.noarch.rpm nodejs010-nodejs-isarray-0.0.1-3.el7.noarch.rpm nodejs010-nodejs-is-builtin-module-1.0.0-1.el7.noarch.rpm nodejs010-nodejs-is-relative-0.2.1-2.el7.noarch.rpm nodejs010-nodejs-is-unc-path-0.1.1-2.el7.noarch.rpm nodejs010-nodejs-is-windows-0.1.0-3.el7.noarch.rpm nodejs010-nodejs-jju-1.2.1-1.el7.noarch.rpm nodejs010-nodejs-json-parse-helpfulerror-1.0.3-1.el7.noarch.rpm nodejs010-nodejs-json-stringify-safe-5.0.0-2.el7.noarch.rpm nodejs010-nodejs-lockfile-1.0.0-1.el7.noarch.rpm nodejs010-nodejs-lodash._basetostring-3.0.1-1.el7.noarch.rpm nodejs010-nodejs-lodash._createpadding-3.6.1-1.el7.noarch.rpm nodejs010-nodejs-lodash.pad-3.1.1-1.el7.noarch.rpm nodejs010-nodejs-lodash.padleft-3.1.1-1.el7.noarch.rpm nodejs010-nodejs-lodash.padright-3.1.1-1.el7.noarch.rpm nodejs010-nodejs-lodash.repeat-3.0.1-1.el7.noarch.rpm nodejs010-nodejs-lru-cache-2.7.0-1.el7.noarch.rpm nodejs010-nodejs-mime-db-1.15.0-3.el7.noarch.rpm nodejs010-nodejs-mime-types-2.1.3-1.el7.noarch.rpm nodejs010-nodejs-minimatch-3.0.0-1.el7.noarch.rpm nodejs010-nodejs-minimist-0.0.8-1.el7.noarch.rpm nodejs010-nodejs-mkdirp-0.5.0-1.el7.noarch.rpm nodejs010-nodejs-ms-0.7.1-2.el7.noarch.rpm nodejs010-nodejs-mute-stream-0.0.4-3.el7.noarch.rpm nodejs010-nodejs-node-uuid-1.4.1-2.el7.noarch.rpm nodejs010-nodejs-nopt-3.0.6-1.el7.noarch.rpm nodejs010-nodejs-normalize-git-url-3.0.1-1.el7.noarch.rpm nodejs010-nodejs-normalize-package-data-2.3.5-1.el7.noarch.rpm nodejs010-nodejs-npm-cache-filename-1.0.2-1.el7.noarch.rpm nodejs010-nodejs-npm-install-checks-1.0.6-1.el7.noarch.rpm nodejs010-nodejs-npmlog-2.0.0-1.el7.noarch.rpm nodejs010-nodejs-npm-package-arg-4.1.0-1.el7.noarch.rpm nodejs010-nodejs-npm-registry-client-7.0.8-1.el7.noarch.rpm nodejs010-nodejs-npm-user-validate-0.1.1-1.el7.noarch.rpm nodejs010-nodejs-once-1.3.0-1.el7.noarch.rpm nodejs010-nodejs-opener-1.4.1-1.el7.noarch.rpm nodejs010-nodejs-osenv-0.1.3-1.el7.noarch.rpm nodejs010-nodejs-os-homedir-1.0.1-1.el7.noarch.rpm nodejs010-nodejs-os-tmpdir-1.0.1-3.el7.noarch.rpm nodejs010-nodejs-path-array-1.0.0-1.el7.noarch.rpm nodejs010-nodejs-path-is-absolute-1.0.0-1.el7.noarch.rpm nodejs010-nodejs-path-is-inside-1.0.0-1.el7.x86_64.rpm nodejs010-nodejs-process-nextick-args-1.0.2-1.el7.noarch.rpm nodejs010-nodejs-promzard-0.2.0-7.el7.noarch.rpm nodejs010-nodejs-proto-list-1.2.2-5.el7.noarch.rpm nodejs010-nodejs-qs-1.2.2-1.el7.noarch.rpm nodejs010-nodejs-read-1.0.5-1.el7.noarch.rpm nodejs010-nodejs-readable-stream-2.0.2-3.el7.noarch.rpm nodejs010-nodejs-readdir-scoped-modules-1.0.2-1.el7.noarch.rpm nodejs010-nodejs-read-installed-4.0.3-1.el7.noarch.rpm nodejs010-nodejs-read-package-json-2.0.2-1.el7.noarch.rpm nodejs010-nodejs-realize-package-specifier-3.0.1-1.el7.noarch.rpm nodejs010-nodejs-request-2.42.0-6.el7.noarch.rpm nodejs010-nodejs-retry-0.6.0-6.el7.noarch.rpm nodejs010-nodejs-rimraf-2.4.3-1.el7.noarch.rpm nodejs010-nodejs-semver-5.0.3-1.el7.noarch.rpm nodejs010-nodejs-sha-2.0.1-2.1.el7.noarch.rpm nodejs010-nodejs-slide-1.1.6-1.el7.noarch.rpm nodejs010-nodejs-sorted-object-1.0.0-3.el7.noarch.rpm nodejs010-nodejs-spdx-correct-1.0.2-1.el7.noarch.rpm nodejs010-nodejs-spdx-exceptions-1.0.4-1.el7.noarch.rpm nodejs010-nodejs-spdx-expression-parse-1.0.1-1.el7.noarch.rpm nodejs010-nodejs-spdx-license-ids-1.0.1-2.el7.noarch.rpm nodejs010-nodejs-string_decoder-0.10.31-1.el7.noarch.rpm nodejs010-nodejs-strip-ansi-0.2.0-1.el7.noarch.rpm nodejs010-nodejs-tar-2.2.1-1.el7.noarch.rpm nodejs010-nodejs-text-table-0.2.0-1.el7.x86_64.rpm nodejs010-nodejs-tunnel-agent-0.3.0-2.el7.noarch.rpm nodejs010-nodejs-uid-number-0.0.5-1.el7.noarch.rpm nodejs010-nodejs-umask-1.1.0-4.el7.noarch.rpm nodejs010-nodejs-unc-path-regex-0.1.1-2.el7.noarch.rpm nodejs010-nodejs-util-deprecate-1.0.1-1.el7.noarch.rpm nodejs010-nodejs-util-extend-1.0.1-4.el7.noarch.rpm nodejs010-nodejs-validate-npm-package-license-3.0.1-1.el7.noarch.rpm nodejs010-nodejs-validate-npm-package-name-2.2.2-3.el7.noarch.rpm nodejs010-nodejs-wcwidth-1.0.0-4.el7.noarch.rpm nodejs010-nodejs-which-1.2.0-1.el7.noarch.rpm nodejs010-nodejs-wrappy-1.0.1-2.el7.noarch.rpm nodejs010-nodejs-write-file-atomic-1.1.2-3.el7.noarch.rpm nodejs010-npm-2.14.13-6.el7.noarch.rpm nodejs010-runtime-2.1-5.el7.x86_64.rpm *If i copy paste above RPMS to my custom ISO, then anaconda successfully installs these packages, without any errors* *What is there is these already built RPMs (taken from repo: [centos-sclo-rh] : http://mirror.centos.org/centos/7/sclo/x86_64/rh/nodejs010/) which is not there in my built RPMS?* Any pointers for this, as we feel, there is some inconsistency in the version available on git.centos.org/git/rpms/<name_of_pkg>.git ? Regards Sudhanshu Bhutani

2 1

None
by None 30 Aug '16

30 Aug '16

by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u7UM1iPO028599 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <centos(a)centos.org>; Tue, 30 Aug 2016 18:01:45 -0400 To: centos(a)centos.org From: Pat Haley <phaley(a)mit.edu> Message-ID: <d059a28c-b866-5056-dda6-29e3077ca907(a)mit.edu> Date: Tue, 30 Aug 2016 18:01:44 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrPIsWRmVeSWpSXmKPExsUixG6nouvFdCzc4PUCIYtlZxYwOzB6rGyb zBzAGMVlk5Kak1mWWqRvl8CV0bNoOlPBCc6KTQ9PsDcwTmfvYuTkkBAwkXjZsomti5GLQ0ig jUni8MVtUM5JRokZM6ZAOQeZJKY/2c8I0iIiICrRs/gVG4jNJqAgse7WGbBRwkCjmldeZAKx eQWsJL43bQezWQRUJeZOaGcGsUUFIiRurfrICFEjKHFy5hMWEJtZwExi3uaHzBC2vMT2t3OY JzDyzkJSNgtJ2SwkZQsYmVcxyqbkVunmJmbmFKcm6xYnJ+blpRbpGurlZpbopaaUbmIEhROn JM8OxjNvvA4xCnAwKvHwZsw4Gi7EmlhWXJl7iFGSg0lJlDf8L1CILyk/pTIjsTgjvqg0J7X4 EKMEB7OSCO91xmPhQrwpiZVVqUX5MClpDhYlcd6uGQfChQTSE0tSs1NTC1KLYLIyHBxKErw7 QBoFi1LTUyvSMnNKENJMHJwgw3mAhnuDDS8uSMwtzkyHyJ9iVJQS5xUFSQiAJDJK8+B6wfGu xn7oFaM40CvCvJcYgKp4gKkCrvsV0GAmoMEFdw6DDC5JREhJNTDOn+LY8sOJSVhFfnV4VzaH T8iDcx+0dvn36Fluta5/vWa3rODTN3LmNl7/W21uh59fwpKvfHjqMtdZ9z/tc/MKZN9/zYhn ocKdJ3P7bu9nyWx6U+Q44dhR8+nzNdf0b5hqFX9bxvtEguS/b/MebPXkTHr/ZmV4+PPttabT hGf57usu5fV/dH+mEktxRqKhFnNRcSIAKBIMXtICAAA= Subject: [CentOS] group write permissions not being respected X-BeenThere: centos(a)centos.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe: <https://lists.centos.org/mailman/options/centos>, <mailto:centos-request@centos.org?subject=unsubscribe> List-Archive: <http://lists.centos.org/pipermail/centos/> List-Post: <mailto:centos@centos.org> List-Help: <mailto:centos-request@centos.org?subject=help> List-Subscribe: <https://lists.centos.org/mailman/listinfo/centos>, <mailto:centos-request@centos.org?subject=subscribe> X-List-Received-Date: Tue, 30 Aug 2016 22:01:46 -0000 Hi We have just migrated our data to a new file server (more space, old server was showing its age). We have a volume for collaborative use, based on group membership. In our new server, the group write permissions are not being respected (e.g. the owner of a directory can still write to that directory but any other member of the associated group cannot, even though the directory clearly has group write permissions set). This is occurring regardless of how many groups the user is a member of (i.e. users that are members of fewer then 16 groups are still affected). the relevant fstab line from the server looks like localhost:/data-volume /gdata glusterfs defaults 0 0 and for a client: mseas-data2:/gdata /gdata nfs defaults 0 0 Any help would be greatly appreciated. Thanks -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley(a)mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301

1 0

None
by None 30 Aug '16

30 Aug '16

by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u7ULNSNq006624 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <centos(a)centos.org>; Tue, 30 Aug 2016 17:23:29 -0400 To: centos(a)centos.org References: <d80864bd-9497-86be-d8db-cdf3c0378d7c(a)mit.edu> <20160829172355.849cf429eb17bf94dd738fa0(a)melvilletheatre.com> From: Pat Haley <phaley(a)mit.edu> Message-ID: <2e155be1-9265-a189-724b-3ab2659d38dc(a)mit.edu> Date: Tue, 30 Aug 2016 17:23:27 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160829172355.849cf429eb17bf94dd738fa0(a)melvilletheatre.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrKIsWRmVeSWpSXmKPExsUixCmqrRv082i4wc2bKhbLzixgdmD0WNk2 mTmAMYrLJiU1J7MstUjfLoErY8oKr4I7QhWPvy9mbmC8xdfFyMkhIWAiMeHnW7YuRi4OIYE2 Jonvr+8xQTgnGSWeblnADuEcZJI4+7aHGaRFWMBB4s/PdjYQW0RAVKJn8SswW0igSuL9pIus IDabgILEultngJo5OHgFrCTurdECCbMIqErs7pjBAmKLCkRI3Fr1kRHE5hUQlDg58wlYnFPA S2LpSpBWTg5mAVuJO3N3M0PY8hLb385hnsDIPwtJyywkZbOQlC1gZF7FKJuSW6Wbm5iZU5ya rFucnJiXl1qka6aXm1mil5pSuokRFHrsLso7GF/2eR9iFOBgVOLhzZhxNFyINbGsuDL3EKMk B5OSKO+eDqAQX1J+SmVGYnFGfFFpTmrxIUYJDmYlEd7P34ByvCmJlVWpRfkwKWkOFiVx3q4Z B8KFBNITS1KzU1MLUotgsjIcHEoSvJe/AzUKFqWmp1akZeaUIKSZODhBhvMADZf8ATK8uCAx tzgzHSJ/ilFRSpz3JchWAZBERmkeXC84NaixH3rFKA70ijDvBJB2HmBaget+BTSYCWhwwZ3D IINLEhFSUg2MXoXXLeI4mYVE/+/6wH6wcoE9U0T+PJM1BlkHD9Wf0vBY8KxlmrXtvGccL6Sj 7i79srzxJr9ZlPiykLwtlgyeWz8o+dev1xDPb1llFMNy/n4Bx6+UoNfBix8Hq6552ppktzJu y4MgFr6g7y9qb/DKnzLobU95usB1rsxeP72OdVU5x4UWtz9SYinOSDTUYi4qTgQA4LNe++gC AAA= Subject: Re: [CentOS] CentOS 6: files now owned by nobody:nobody X-BeenThere: centos(a)centos.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe: <https://lists.centos.org/mailman/options/centos>, <mailto:centos-request@centos.org?subject=unsubscribe> List-Archive: <http://lists.centos.org/pipermail/centos/> List-Post: <mailto:centos@centos.org> List-Help: <mailto:centos-request@centos.org?subject=help> List-Subscribe: <https://lists.centos.org/mailman/listinfo/centos>, <mailto:centos-request@centos.org?subject=subscribe> X-List-Received-Date: Tue, 30 Aug 2016 21:23:31 -0000 The setting the Domain = line in /etc/idmapd.conf option solved our problem Thanks On 08/29/2016 07:23 PM, Frank Cox wrote: > On Mon, 29 Aug 2016 18:59:31 -0400 > Pat Haley wrote: > >> We noticed that all the files were owned by nobody > Here are my notes for dealing with this issue: > > If all users come up as nobody on a nfs mount: > > Add nfs server name to the Domain = line in /etc/idmapd.conf on both the server and the clients, i.e. Domain = nameof.server > > /sbin/service rpcidmapd restart > /sbin/service nfslock restart > /sbin/service nfs restart > > Also, the complete hostname as specified (nameof.server) must be in /etc/hosts on the nfs clients as well as the server > > --------------- > try > /usr/sbin/nfsidmap -c > on the client. > Since I put this into my /etc/rc.local , I don't have the problem any > longer. > --------------- > 1) /etc/idmapd.conf > # Set domain to the domain name shared by your NFS servers. > Domain: mycompany.com > Set local-realms to the name of the nfs servers you'll be using. THIS > WASN'T MENTIONED ELSEWHERE. > Local-Realms: nfs1.mycompany.com,nfs2.mycompany.com > # make the above changes on all the servers in question. > > 2) /etc/hosts: list with all the NFS servers you specified in local-realms above. This way DNS errors don't make your servers get hung > 1.2.3.4 nfs1.mycompany.com > 1.2.3.5 nfs2.mycompany.com > > 3) Make sure you synchronize your /etc/passwd files so that the account > IDs match up or you'll get very strange results. > > 4) Reboot EVERYTHING. Restarting services was not enough. > For documentation's sake, I restarted rpcidmapd, nfslock, and nfs, but didn't get the correct permissions until reboot. It doesn't seem important to run the nfs service on the > clients. > > 5) Client mount: > # CLI > /bin/mount -t nfs servername:/path/to/share /local/mount/point > > # /etc/fstab > servername.com:/path/to/share /local/mount/mount nfs ro,nolock 0 0 > > # mount -a > > -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley(a)mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301

1 0

Re: [CentOS] CentOS 6: files now owned by nobody:nobody
by Jonathan Billings 30 Aug '16

30 Aug '16

On Mon, Aug 29, 2016 at 06:59:31PM -0400, Pat Haley wrote: > ... We > noticed that all the files were owned by nobody (with nobody as the group). If its NFSv4, then its most likely a problem with your idmapper. Make sure that the rpc.idmapd is running on your client, and that your server has appropriate ID mapping enabled. If its NFSv4, are you using sec=krb5*? -- Jonathan Billings <billings(a)negate.org>

2 1

.htaccess file
by TE Dukes 30 Aug '16

30 Aug '16

Hello, My home system on a DSL line is getting worn out by bad behavior robots. Awhile back, I created a .htaccess file that block countries by IP blocks. Its 2MB in size. I have been running Linux since Slackware 1.0 and moved to Redhat around 2.0. I started after running a BBS using a doorway for newsgroups. Been hooked ever since. So, today, I tried following the directions for apache.org website, https://httpd.apache.org/docs/current/howto/htaccess.html to move the .htaccess <https://httpd.apache.org/docs/current/howto/htaccess.html%20to%20move%20the %20.htaccess> file to a file located in a directory /var/www/htdocs. I'm just not following or understanding. The .htaccess file works but on a slow DSL, I don't want the hits. I added the following to my httpd.conf: <Directory "/var/www/htdocs"> AddType text/htdocs ".txt" </Directory> And copied my .htaccess to /var/www/htdocs as htaccess.txt In the example from the apache website, I don't get the: AddType text/example ".exm" Where did they come up .exm? TIA

6 16

None
by None 29 Aug '16

29 Aug '16

by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u7TNPWl1024422 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <centos(a)centos.org>; Mon, 29 Aug 2016 19:25:33 -0400 To: centos(a)centos.org References: <d80864bd-9497-86be-d8db-cdf3c0378d7c(a)mit.edu> <73650851-909c-c43a-a926-53cbdf14af6f(a)hogranch.com> From: Pat Haley <phaley(a)mit.edu> Message-ID: <7fe0f111-e54b-6f26-d816-a82851ddd0bd(a)mit.edu> Date: Mon, 29 Aug 2016 19:25:28 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <73650851-909c-c43a-a926-53cbdf14af6f(a)hogranch.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOIsWRmVeSWpSXmKPExsUixG6nrpt35Ei4wYsubotlZxYwOzB6rGyb zBzAGMVlk5Kak1mWWqRvl8CVcfjCYsaCi3wVl2beZGlgbObuYuTkkBAwkXi19idjFyMXh5BA G5PEgemTmSCck4wS7X9vsEM4B5kk7jx+wwzSIizgIPHnZzsbiC0iICrRs/gVmC0kUCBxcdVH JhCbTUBBYt2tM+wgNq+AlcSdttNgNSwCqhIbzy1hBLFFBSIkbq36yAhRIyhxcuYTFhCbE2j+ snOLwOYwC9hK3Jm7mxnClpfY/nYO8wRG/llIWmYhKZuFpGwBI/MqRtmU3Crd3MTMnOLUZN3i 5MS8vNQiXSO93MwSvdSU0k2MoPDjlOTdwfjvrtchRgEORiUeXgunI+FCrIllxZW5hxglOZiU RHmnxgOF+JLyUyozEosz4otKc1KLDzFKcDArifBmHgDK8aYkVlalFuXDpKQ5WJTEebtmHAgX EkhPLEnNTk0tSC2CycpwcChJ8EocBmoULEpNT61Iy8wpQUgzcXCCDOcBGv7zEMjw4oLE3OLM dIj8KUZFKXFeR5CEAEgiozQPrhecHtTYD71iFAd6RZj3EMgKHmBqget+BTSYCWhwwZ3DIINL EhFSUg2MtRuzrx96Znrb3Jt1f0vz9MNWL/5JBMb1/RXy/fB5Q+S907I8qTN2M14+rpuzfO68 mWuTyy+/PL6g0WS56+LWBIuKnRatOnlWseeTJ3M5RHeeDpqVttdg0RyGQBflxju85xlOVFzd 5/+Oy7lEeWp0Q1zWW7mp4m+9HzTMurBGZKFZZIeT2P1QJZbijERDLeai4kQAP19NXOoCAAA= Subject: Re: [CentOS] CentOS 6: files now owned by nobody:nobody X-BeenThere: centos(a)centos.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe: <https://lists.centos.org/mailman/options/centos>, <mailto:centos-request@centos.org?subject=unsubscribe> List-Archive: <http://lists.centos.org/pipermail/centos/> List-Post: <mailto:centos@centos.org> List-Help: <mailto:centos-request@centos.org?subject=help> List-Subscribe: <https://lists.centos.org/mailman/listinfo/centos>, <mailto:centos-request@centos.org?subject=subscribe> X-List-Received-Date: Mon, 29 Aug 2016 23:25:35 -0000 I believe NFSv4. On the machine that contains the physical disks (is that the "server" or the "NSF mount"?) the relevant line from /etc/fstab seems to be UUID=bde58f42-4ac4-4763-b0a8-f83723f0e2a0 /home ext4 defaults 1 2 while on my front-end machine its mseas-data2:/home /home nfs defaults 0 0 where mseas-data2 is the name of the machine that contains the physical disks. Note that it isn't just root that's becoming "nobody" but all the users Thanks On 08/29/2016 07:14 PM, John R Pierce wrote: > On 8/29/2016 3:59 PM, Pat Haley wrote: >> We are running a cluster under CentOS 6.6. We recently attached a >> new NAS device, running CentOS 6.8 and rsync'd our user file system >> to it. We noticed that all the files were owned by nobody (with >> nobody as the group). We copied over the /etc/passwd and /etc/group >> files from our front-end server to our NAS server. If we log in to >> the NAS server we see the files owned by their correct owners. >> However, doing an ls from the front-end server or any of the compute >> nodes still shows the files owned by "nobody". We rebooted one of >> the compute nodes but it still sees the files owned by nobody. > > a CentOS server isn't really a 'NAS device', as NAS implies an > appliance storage device. > > this is NFS? NFSv3, or NFSv4? what NFS options are on the server > and on the NFS mount? quite often NFS servers force root to nobody. > > -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley(a)mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301

1 0

Re: [CentOS] CentOS 6: files now owned by nobody:nobody
by Frank Cox 29 Aug '16

29 Aug '16

On Mon, 29 Aug 2016 18:59:31 -0400 Pat Haley wrote: > We noticed that all the files were owned by nobody Here are my notes for dealing with this issue: If all users come up as nobody on a nfs mount: Add nfs server name to the Domain = line in /etc/idmapd.conf on both the server and the clients, i.e. Domain = nameof.server /sbin/service rpcidmapd restart /sbin/service nfslock restart /sbin/service nfs restart Also, the complete hostname as specified (nameof.server) must be in /etc/hosts on the nfs clients as well as the server --------------- try /usr/sbin/nfsidmap -c on the client. Since I put this into my /etc/rc.local , I don't have the problem any longer. --------------- 1) /etc/idmapd.conf # Set domain to the domain name shared by your NFS servers. Domain: mycompany.com Set local-realms to the name of the nfs servers you'll be using. THIS WASN'T MENTIONED ELSEWHERE. Local-Realms: nfs1.mycompany.com,nfs2.mycompany.com # make the above changes on all the servers in question. 2) /etc/hosts: list with all the NFS servers you specified in local-realms above. This way DNS errors don't make your servers get hung 1.2.3.4 nfs1.mycompany.com 1.2.3.5 nfs2.mycompany.com 3) Make sure you synchronize your /etc/passwd files so that the account IDs match up or you'll get very strange results. 4) Reboot EVERYTHING. Restarting services was not enough. For documentation's sake, I restarted rpcidmapd, nfslock, and nfs, but didn't get the correct permissions until reboot. It doesn't seem important to run the nfs service on the clients. 5) Client mount: # CLI /bin/mount -t nfs servername:/path/to/share /local/mount/point # /etc/fstab servername.com:/path/to/share /local/mount/mount nfs ro,nolock 0 0 # mount -a -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

1 0

Re: [CentOS] CentOS 6: files now owned by nobody:nobody
by John R Pierce 29 Aug '16

29 Aug '16

On 8/29/2016 3:59 PM, Pat Haley wrote: > We are running a cluster under CentOS 6.6. We recently attached a new > NAS device, running CentOS 6.8 and rsync'd our user file system to > it. We noticed that all the files were owned by nobody (with nobody > as the group). We copied over the /etc/passwd and /etc/group files > from our front-end server to our NAS server. If we log in to the NAS > server we see the files owned by their correct owners. However, doing > an ls from the front-end server or any of the compute nodes still > shows the files owned by "nobody". We rebooted one of the compute > nodes but it still sees the files owned by nobody. a CentOS server isn't really a 'NAS device', as NAS implies an appliance storage device. this is NFS? NFSv3, or NFSv4? what NFS options are on the server and on the NFS mount? quite often NFS servers force root to nobody. -- john r pierce, recycling bits in santa cruz

1 0

None
by None 29 Aug '16

29 Aug '16

by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id u7TMxYi2018663 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <centos(a)centos.org>; Mon, 29 Aug 2016 18:59:35 -0400 To: centos(a)centos.org From: Pat Haley <phaley(a)mit.edu> Message-ID: <d80864bd-9497-86be-d8db-cdf3c0378d7c(a)mit.edu> Date: Mon, 29 Aug 2016 18:59:31 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrPIsWRmVeSWpSXmKPExsUixCmqrRux70i4wcJOMYtlZxYwOzB6rGyb zBzAGMVlk5Kak1mWWqRvl8CVcf70RNaC2RwVk/dMY2pgnMvWxcjJISFgIrGldTJrFyMXh5BA G5PEmwOT2SGck4wSfx/1sUA4B5kkjvW9ZQVpEREQlehZ/AqsnU1AQWLdrTPsILawgLHE3ua3 zCA2r4CVxPGHvxhBbBYBVYlLM+aA1YsKREjcWvWREaJGUOLkzCcsIDazgJnEvM0PmSFseYnt b+cwT2DknYWkbBaSsllIyhYwMq9ilE3JrdLNTczMKU5N1i1OTszLSy3SNdPLzSzRS00p3cQI Cid2F+UdjC/7vA8xCnAwKvHwWjgdCRdiTSwrrsw9xCjJwaQkyjs1HijEl5SfUpmRWJwRX1Sa k1p8iFGCg1lJhNd/E1CONyWxsiq1KB8mJc3BoiTO2zXjQLiQQHpiSWp2ampBahFMVoaDQ0mC l3UvUKNgUWp6akVaZk4JQpqJgxNkOA/Q8DCQGt7igsTc4sx0iPwpRkUpcd7SPUAJAZBERmke XC843tXYD71iFAd6RZhXG6SdB5gq4LpfAQ1mAhpccOcwyOCSRISUVAOjXLhTjFpr1FumG1/e yu09w9DuVbNZTuJk4jPXvRyHVbvEGhunT5ZIN6wyd0pjkj3HJq2gf+nhVe9Y6/MPrcRURdiW 8T4+IfCG4fqRE4GrfRi4NgcfrdK3mffA53rf31wjY2bWSWkT2ErO62i8jZ4sc/XUWea/dVHF s5/vuLg31zr/m1Zw5yolluKMREMt5qLiRADDYFna0gIAAA== Subject: [CentOS] CentOS 6: files now owned by nobody:nobody X-BeenThere: centos(a)centos.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: CentOS mailing list <centos.centos.org> List-Unsubscribe: <https://lists.centos.org/mailman/options/centos>, <mailto:centos-request@centos.org?subject=unsubscribe> List-Archive: <http://lists.centos.org/pipermail/centos/> List-Post: <mailto:centos@centos.org> List-Help: <mailto:centos-request@centos.org?subject=help> List-Subscribe: <https://lists.centos.org/mailman/listinfo/centos>, <mailto:centos-request@centos.org?subject=subscribe> X-List-Received-Date: Mon, 29 Aug 2016 22:59:36 -0000 Hi, We are running a cluster under CentOS 6.6. We recently attached a new NAS device, running CentOS 6.8 and rsync'd our user file system to it. We noticed that all the files were owned by nobody (with nobody as the group). We copied over the /etc/passwd and /etc/group files from our front-end server to our NAS server. If we log in to the NAS server we see the files owned by their correct owners. However, doing an ls from the front-end server or any of the compute nodes still shows the files owned by "nobody". We rebooted one of the compute nodes but it still sees the files owned by nobody. Any advice would be greatly appreciated. Thanks -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: phaley(a)mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301

1 0

ipsets/iptables question
by TE Dukes 29 Aug '16

29 Aug '16

Hello, I have ipsets setup with a set of ip address that are badbots that won't comply with robots.txt This is a home server and these are most likely up to no good. I came up with a script to extract ip address from my access_log then another script to take ips and import them into my blacklist set. (see my scripts in the .htaccess thread) I can set these up as cron jobs but I'm not sure about the following: 1) after importing/updating the set, do I need to perform a, ipset save blacklist Since I haven't changed the rule in iptables, do I need to run these? 2) service iptables save 3) service iptables restart Thank!!

1 0

Loaded: not-found (Reason: No such file or directory)
by Kaushal Shriyan 29 Aug '16

29 Aug '16

Hi, I am seeing the below issue. [user~]# systemctl list-unit-files | grep nrpe [user~]# service nrpe status Redirecting to /bin/systemctl status nrpe.service ● nrpe.service * Loaded: not-found (Reason: No such file or directory)* Active: inactive (dead) [user~]# rpm -qa | grep nrpe nrpe-3.0-1.x86_64 nrpe-plugin-3.0-1.x86_64 [user~]#cat /etc/redhat-release *CentOS Linux release 7.2.1511 (Core)* [user~]# Any help will be highly appreciable and please let me know if anyone needs any additional information. Regards, Kaushal

3 2

Gnome weather applet stranded
by isdtor 29 Aug '16

29 Aug '16

The Gnome weather report applet has ceased working on CentOS5/6. http://weather.noaa.gov/ says "This service is no longer available". Are there any good alternatives? I liked the applet as it allowed the use of a custom radar map. As I just discovered, the weather functionality of the CentOS6 Gnome clock applet was using the same service.

10 21

Off Topic: CentOS Public mirror question
by Valeri Galtsev 29 Aug '16

29 Aug '16

Dear All, My apologies for asking my question on less appropriate list. I did ask it on centos-mirror(a)centos.org, but that list is really low traffic (and slow response probably - I only got acknowledgement of my post...). On the other hand, I'm sure there are many public mirror maintainers on this list who may help me with my trouble. Upon replacing faulty machine hosting public mirrors I have noticed that I can not rsync CentOS (all other mirrors do rsync happily as they did on failed box). I probably have missed some announcement, so my apologies for asking what I should know already myself. Which higher tier mirror should I use to rsync CentOS from (including DVDs) to public mirror I maintain? I use probably outdated source to rsync from. Namely, here is my rsync line (in longer cron job): rsync -aqH --exclude .~tmp~/ --exclude .~tmp~ --delete\ msync-dvd.centos.org::CentOS-incdvd /data/mirror/centos - and I'm getting the following error: @ERROR: Unknown module 'CentOS-incdvd' I also tried what CentOS public mirror wiki suggests, and get similar error: rsync -aqH --exclude .~tmp~/ --exclude .~tmp~ --delete\ us-msync.centos.org::CentOS /data/mirror/centos @ERROR: Unknown module 'CentOS' Independent on this error I also have a bit strange answer in DNS resolution of msync-dvd.centos.org: # host msync-dvd.centos.org msync-dvd.centos.org has address 209.44.106.213 Host msync-dvd.centos.org not found: 2(SERVFAIL) I would appreciate any help or pointers. Thanks a lot in advance for all your answers! Valeri ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++

2 1

BIND (named) as secondary and .jnl files
by Walter H. 28 Aug '16

28 Aug '16

Hello, I have two running BINDs in my LAN, one on my router box and one as VM; both are caching DNS servers, and a few zones are on both, on the box as master and on the VM as slave, but how can I cleanup/flush the growing .jnl files; rndc freeze rndc thaw doesn't work as these are not master ... Thanks, Walter

2 1

Kickstart issue with UEFi
by Phil Manuel 28 Aug '16

28 Aug '16

Hi, I have a test system that booted fine using "Legacy Bios” mode and using the following Kickstart snippet configured the disks correctly:- # Clear the Master Boot Record zerombr # Partition clearing information clearpart --all --initlabel # Disk partitioning information part raid.01 --fstype="raid" --ondisk=sda --size=500 part raid.02 --fstype="raid" --grow --ondisk=sda --size=1 part raid.03 --fstype="raid" --ondisk=sdb --size=500 part raid.04 --fstype="raid" --grow --ondisk=sdb --size=1 raid /boot --device=0 --fstype="xfs" --level=RAID1 raid.01 raid.03 raid pv.01 --device=1 --level=RAID1 raid.02 raid.04 For UEFi I changed it to the following:- # Clear the Master Boot Record zerombr # Partition clearing information clearpart --all --initlabel # Disk partitioning information part raid.01 --fstype="raid" --ondisk=sda --size=500 part raid.02 --fstype="raid" --grow --ondisk=sda --size=1 part raid.03 --fstype="raid" --ondisk=sdb --size=500 part raid.04 --fstype="raid" --grow --ondisk=sdb --size=1 raid /boot --device=0 --fstype="xfs" --level=RAID1 raid.01 raid.03 part /boot/efi —fstype=“efi” --grow --maxsize=200 --size=20 raid pv.01 --device=1 --level=RAID1 raid.02 raid.04 The install fails under UEFi due to the fact the partitions are not cleared, and it doesn’t have any space to continue. Is there an extra step I need to do to remove the original partitions before the new layout will work ? Thanks

6 13

CentOS 7 : keyboard shortcut for mouse gesture?
by Nicolas Kovacs 28 Aug '16

28 Aug '16

Hi, I have a CentOS 7 (GNOME) desktop installed as a VirtualBox guest on my Slackware64 14.1 workstation, to fiddle with it. Guest Additions are installed and configured OK, and 3D acceleration is working too. In its default configuration, the GNOME desktop under CentOS shows an "exposé" (I don't know how you call this), a list of all open windows, when you move the mouse cursor to the upper left corner of the screen. When no window is open, you just see the sidebar with the application launchers, and on the right side you see the empty virtual desktops. Is there a keyboard shortcut for this mouse gesture? I'm asking because on my dual-monitor workstation, the CentOS guest is displayed full-screen on my right monitor, and the mouse gesture seems to be ineffective. Thanks, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

2 2

Samba DC NT4 Style is Gone. When AD-DC will enable for default into Centos/RedHat Samba4 packages?
by Dario Lesca 27 Aug '16

27 Aug '16

This recent Microsoft's Patch https://lists.samba.org/archive/samba/2016-August/202197.html disable password change for all server Domain Controller NT4 Style, Samba 3 and 4 included. Then is urgent to enable, into Samba 4 Centos package by default support to AD-DC mode, or release another renamed packages with AD-DC support enable. For now, I must download the samba.src rpm, modify the spec file > sed \ > -e 's/%global with_mitkrb5 1/%global with_mitkrb5 0/' \ > -e 's/%global with_dc 0/%global with_dc 1/' \ > ~/rpmbuild/SPECS/samba.spec then rebuild the package after all update. My question is: There is some hope that in the short this flags are enable by default? Many thanks for your reply -- Dario Lesca (inviato dal mio Linux Fedora 24 Workstation)

1 0

CentOS-announce Digest, Vol 138, Issue 9
by centos-announce-request＠centos.org 27 Aug '16

27 Aug '16

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-2016:1776 Important CentOS 5 java-1.6.0-openjdk Security Update (Johnny Hughes) 2. CESA-2016:1776 Important CentOS 6 java-1.6.0-openjdk Security Update (Johnny Hughes) 3. CESA-2016:1776 Important CentOS 7 java-1.6.0-openjdk Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 26 Aug 2016 14:36:52 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1776 Important CentOS 5 java-1.6.0-openjdk Security Update Message-ID: <20160826143652.GA17670(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1776 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1776.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: d6d0f386a6f9d22a393a247f7cd7c58b1239c6ae7b313828b87fcdfa65a68b1e java-1.6.0-openjdk-1.6.0.40-1.13.12.4.el5_11.i386.rpm 003823d694e9316c0f58b2cef8ec2f1c5a785a0548a5ae82b9c8c00ed42a5e3a java-1.6.0-openjdk-demo-1.6.0.40-1.13.12.4.el5_11.i386.rpm a901afc3d0ab6313a4b1f95e7af4a6d452925643899807365453285232c320db java-1.6.0-openjdk-devel-1.6.0.40-1.13.12.4.el5_11.i386.rpm daf59f8a6ba2bb995a58c9bf836130882508d4cd0df923078e11ba7b622437cd java-1.6.0-openjdk-javadoc-1.6.0.40-1.13.12.4.el5_11.i386.rpm 26112915bd3ce6e56f376abe8d6c7c7c3ec34bd291ab024171941082191c5ab2 java-1.6.0-openjdk-src-1.6.0.40-1.13.12.4.el5_11.i386.rpm x86_64: 7facd58d760041b41707cbc04fea6404e5760aa89a64b09a63d0f642453e601c java-1.6.0-openjdk-1.6.0.40-1.13.12.4.el5_11.x86_64.rpm acdd1a149a650802bab713348efed3cea94c3fa1e4a3eedef0b14dc530f63e11 java-1.6.0-openjdk-demo-1.6.0.40-1.13.12.4.el5_11.x86_64.rpm faa0bb044816096b5c322ed889500fab4226b773add9da74ac3785533a06233b java-1.6.0-openjdk-devel-1.6.0.40-1.13.12.4.el5_11.x86_64.rpm 9098ab7a6fa89b673952660495ff0fe4814ba653bcb36e58d3b40514398fd057 java-1.6.0-openjdk-javadoc-1.6.0.40-1.13.12.4.el5_11.x86_64.rpm ac196f3ec06eb8008d9104d9bb8b27ca9142e2bdaff848053c7ad25f9765656b java-1.6.0-openjdk-src-1.6.0.40-1.13.12.4.el5_11.x86_64.rpm Source: dfc80c864a12dd91aa6b026969da5dfceeafbce0c3ee8862ee8ec892943ddae6 java-1.6.0-openjdk-1.6.0.40-1.13.12.4.el5_11.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: JohnnyCentOS ------------------------------ Message: 2 Date: Fri, 26 Aug 2016 14:45:12 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1776 Important CentOS 6 java-1.6.0-openjdk Security Update Message-ID: <20160826144512.GA47992(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1776 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1776.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 85a42b9dc7548e3f8b86cacd1609fc14bc8e8e519a4ce4858e15d320d09d6c9d java-1.6.0-openjdk-1.6.0.40-1.13.12.6.el6_8.i686.rpm a44a315add63888bdb90fd5c6dec550396d8c6a3ac3daa0dba40f07520927d6c java-1.6.0-openjdk-demo-1.6.0.40-1.13.12.6.el6_8.i686.rpm 358bda472da2634563588274cd6f8f8095dd7af95fc6ecc1b28c6eabcde63a1b java-1.6.0-openjdk-devel-1.6.0.40-1.13.12.6.el6_8.i686.rpm 4365bf6681d15abcb1967eb66c365ea867ed39e9272a6b2babfadbf9dc5faf70 java-1.6.0-openjdk-javadoc-1.6.0.40-1.13.12.6.el6_8.i686.rpm 64b7542290a9531ee58d69027f060fabb9d87bd0a3c1c56856e4993a0b69048c java-1.6.0-openjdk-src-1.6.0.40-1.13.12.6.el6_8.i686.rpm x86_64: 867d64c8e0b0a7ab80aa705b96f64ea8c2a8637374dca25707180cb9fe3a55a8 java-1.6.0-openjdk-1.6.0.40-1.13.12.6.el6_8.x86_64.rpm 3ec19d952f64d6a3b5cdbb5d0012117d842128474f880f621a77f67381e66149 java-1.6.0-openjdk-demo-1.6.0.40-1.13.12.6.el6_8.x86_64.rpm ec5818e8e2670df9b68140febdbcccb1cab99cf016b7fc1f57442bbe03579ac1 java-1.6.0-openjdk-devel-1.6.0.40-1.13.12.6.el6_8.x86_64.rpm e582a9589e7f51391dbb900eb0b9e6d7872e1382a1ab23aa9f41fb64254c5109 java-1.6.0-openjdk-javadoc-1.6.0.40-1.13.12.6.el6_8.x86_64.rpm 05cca14dd0a3ba8fa4e8c794ac83610766104ce9215141148da92730754db124 java-1.6.0-openjdk-src-1.6.0.40-1.13.12.6.el6_8.x86_64.rpm Source: 2ca712c6daf3a2597d52228823cf01e58a77613f07bd201ae1739a32d32090db java-1.6.0-openjdk-1.6.0.40-1.13.12.6.el6_8.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Fri, 26 Aug 2016 15:40:17 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:1776 Important CentOS 7 java-1.6.0-openjdk Security Update Message-ID: <20160826154017.GA60948(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:1776 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-1776.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: f2a27f7b6061bed7fc189feb3b25b63319d8b41f6d0c67c3feebcc297aa7487f java-1.6.0-openjdk-1.6.0.40-1.13.12.5.el7_2.x86_64.rpm b685ba29ba96991483b3120219338e90919708d21b2ac4a4b68100ad022ce381 java-1.6.0-openjdk-demo-1.6.0.40-1.13.12.5.el7_2.x86_64.rpm 0a136da5d7ed5a505effabe1218ff47245c84c4cbb2fa59cfbe5d248dceb4310 java-1.6.0-openjdk-devel-1.6.0.40-1.13.12.5.el7_2.x86_64.rpm 3ec9d367a743952bf34c36152e087e9b071f1d07fa7cac3fc7bed03a2748e559 java-1.6.0-openjdk-javadoc-1.6.0.40-1.13.12.5.el7_2.x86_64.rpm 2eeabee30ab8056b61e4b2f258b973586edc47eb9d23aed27c972f12022bef40 java-1.6.0-openjdk-src-1.6.0.40-1.13.12.5.el7_2.x86_64.rpm Source: e9a9b3b63cdfd7cec648b4893ba5f09c1c3ee68a9e3e9079ad5c67d7aafac10f java-1.6.0-openjdk-1.6.0.40-1.13.12.5.el7_2.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 138, Issue 9 ***********************************************

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss