[CentOS] bug report and resolved patch for remove_hrtimer in CentOS 6.x
Hi, I happened to meet with a similar issue like https://bugs.centos.org/view.php?id=7051 I found the root cause might be fixed by commit f13d4f979c518119bba5439dd2364d76d31dcd3f. The commit in branch linux-2.6.32-y is 0bd9ac380a44611e953b1657d7f54075b2f77fb0 This issue is existed in centOS 6.6 also any ideas B.R. Justin ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Dropbox on CentOS 6?
Hi, On 12/11/2014 08:55 AM, Niki Kovacs wrote: > Is there a way that > 1. Actually works? > 2. Doesn't include jumping through burning loops? just use the Fedora RPM from Dropbox. It's working fine. The files included and a German posting is at http://chris-blog.net/2014/07/dropbox-unter-centos-installieren/ -- Gruß, Christian ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] print something on console after boot
Looks like you are seeing the codes defined for mingetty rather than agetty. This is what you would expect for a virtual console on CentOS 6 which uses the former. K al ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS-6 Another email related AVC
CentOS-6.6
Postfix-2.11.1 (local)
ClamAV-0.98.5 (epel)
Amavisd-new-2.9.1 (epel)
opendkim-2.9.0 (centos)
pypolicyd-spf-1.3.1 (epel)
/var/log/maillog
Dec 11 16:52:09 inet18 setroubleshoot: SELinux is preventing /usr/bin/perl
from read access on the file online. For complete SELinux messages. run
sealert -l 62006e35-dcc8-4a4f-8e10-9f34757f3a4a
Dec 11 16:52:10 inet18 setroubleshoot: SELinux is preventing /usr/bin/perl
from read access on the file online. For complete SELinux messages. run
sealert -l 62006e35-dcc8-4a4f-8e10-9f34757f3a4a
Dec 11 16:52:10 inet18 setroubleshoot: SELinux is preventing /usr/bin/perl
from read access on the file online. For complete SELinux messages. run
sealert -l 62006e35-dcc8-4a4f-8e10-9f34757f3a4a
Dec 11 16:52:10 inet18 setroubleshoot: SELinux is preventing /usr/bin/perl
from read access on the file online. For complete SELinux messages. run
sealert -l 62006e35-dcc8-4a4f-8e10-9f34757f3a4a
Dec 11 16:52:11 inet18 setroubleshoot: SELinux is preventing /usr/bin/perl
from read access on the file online. For complete SELinux messages. run
sealert -l 62006e35-dcc8-4a4f-8e10-9f34757f3a4a
Dec 11 16:53:28 inet18 setroubleshoot: SELinux is preventing /usr/bin/clamscan
from write access on the directory tmp. For complete SELinux messages. run
sealert -l 1f0d210d-b4e1-4635-8765-f7e913e2bf28
Dec 11 16:53:29 inet18 setroubleshoot: SELinux is preventing /usr/bin/clamscan
from write access on the directory tmp. For complete SELinux messages. run
sealert -l 1f0d210d-b4e1-4635-8765-f7e913e2bf28
Dec 11 16:53:29 inet18 setroubleshoot: SELinux is preventing /usr/bin/perl
from read access on the file online. For complete SELinux messages. run
sealert -l 62006e35-dcc8-4a4f-8e10-9f34757f3a4a
Dec 11 16:58:36 inet18 setroubleshoot: SELinux is preventing /usr/bin/clamscan
from write access on the directory tmp. For complete SELinux messages. run
sealert -l 1f0d210d-b4e1-4635-8765-f7e913e2bf28
Dec 11 16:58:36 inet18 setroubleshoot: SELinux is preventing /usr/bin/perl
from read access on the file online. For complete SELinux messages. run
sealert -l 62006e35-dcc8-4a4f-8e10-9f34757f3a4a
Dec 11 16:58:37 inet18 setroubleshoot: SELinux is preventing /usr/bin/perl
from read access on the file online. For complete SELinux messages. run
sealert -l 62006e35-dcc8-4a4f-8e10-9f34757f3a4a
sealert -l 62006e35-dcc8-4a4f-8e10-9f34757f3a4a
SELinux is preventing /usr/bin/perl from read access on the file online.
* Plugin catchall (100. confidence) suggests ***
If you believe that perl should be allowed read access on the online file by
default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep amavisd /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp
[root@inet18 ~ (master #)]# grep amavisd /var/log/audit/audit.log | audit2allow
#= amavis_t ==
allow amavis_t shell_exec_t:file { read open };
allow amavis_t sysfs_t:file read;
--
*** E-Mail is NOT a SECURE channel ***
James B. Byrnemailto:byrn...@harte-lyne.ca
Harte & Lyne Limited http://www.harte-lyne.ca
9 Brockley Drive vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada L8E 3C3
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
[CentOS] HOWTO Stratum 1 NTP server under CentOS 7
Hello everyone, If anyone is interested, I have created a HOWTO on running a Motorola GPS receiver connected to a CentOS 7 box via serial port (com1), with 1PPS over DCD. The trick here is that CentOS 7 uses systemd and setup was a bit different. Anyway, everything works. The result is a highly accurate NTP server, Stratum 1. Here is the documentation. http://www.maximaphysics.com/Centos_7_GPS_Setup.html Let me know if something does not look right. -George, N2FGX ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5- mount shows a cifs share mounted 4 times!
Hello Gordon, Thursday, December 11, 2014, 6:46:00 PM, you wrote: GM> Specify the local path rather than the source: GM> $ umount /NSA320-music Well well! I'm sure I’ve always unmouted the mount and not the mount point before... mind I think this is the first time I've tried to unmount a remote share rather then something local. -- Best regards, Niamhmailto:ni...@fullbore.co.uk pgpdKdSStv5XN.pgp Description: PGP signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 grub.cfg missing on new install
- Original Message - From: "Gordon Messmer" To: "CentOS mailing list" Cc: "Jeff Boyce" Sent: Thursday, December 11, 2014 9:45 AM Subject: Re: [CentOS] CentOS 7 grub.cfg missing on new install On 12/10/2014 10:13 AM, Jeff Boyce wrote: The short story is that got my new install completed with the partitioning I wanted and using software raid, but after a reboot I ended up with a grub prompt, and do not appear to have a grub.cfg file. ... I initially created the sda[1,2] and sdb[1,2] partitions via GParted leaving the remaining space unpartitioned. I'm pretty sure that's not necessary. I've been able to simply change the device type to RAID in the installer and get mirrored partitions. If you do your setup entirely in Anaconda, your partitions should all end up fine. It may not be absolutely necessary, but it appears to me to be the only way to get to my objective. The /boot/efi has to be on a separate partition, and it can not be on a RAID device. The /boot can be on LVM according to the documentation I have seen, but Anaconda will give you an error and not proceed if it is. Someone pointed this out to me a few days ago, that this is by design in RH and CentOS. And within the installer I could not find a way to put /boot on a non-LVM RAID1 while the rest of my drive is setup with LVM RAID1. So that is when I went to GParted to manually setup the /boot/efi and /boot partitions before running the installer. At this point I needed to copy my /boot/efi and /boot partitions from sda[1,2] to sdb[1,2] so that the system would boot from either drive, so I issued the following sgdisk commands: root# sgdisk -R /dev/sdb1 /dev/sda1 root# sgdisk -R /dev/sdb2 /dev/sda2 root# sgdisk -G /dev/sdb1 root# sgdisk -G /dev/sdb2 sgdisk manipulates GPT, so you run it on the disk, not on individual partitions. What you've done simply scrambled information in sdb1 and sdb2. The correct way to run it would be # sgdisk -R /dev/sdb /dev/sda # sgdisk -G /dev/sdb Point taken, I am going back to read the sgdisk documentation again. I had assumed that this would be a more technically accurate way to copy sda[1,2] to sdb[1,2] rather than using dd as a lot of how-to's suggest. However, you would only do that if sdb were completly unpartitioned. As you had already made at least one partition on sdb a member of a RAID1 set, you should not do either of those things. The entire premise of what you're attempting is flawed. Making a partition into a RAID member is destructive. mdadm writes its metadata inside of the member partition. The only safe way to convert a filesystem is to back up its contents, create the RAID set, format the RAID volume, and restore the backup. Especially with UEFI, there are a variety of ways that can fail. Just set up the RAID sets in the installer. I need some additional explanation of what you are trying to say here, as I don't understand it. My objective is to have the following layout for my two 3TB disks. sda1/boot/efi sda2/boot sda3RAID1 with sdb3 sdb1/boot/efi sdb2/boot sdb3RAID1 with sda3 I just finished re-installing using my GParted prepartitioned layout and I have a bootable system with sda1 and sda2 mounted, and md127 created from sda3 and sdb3. My array is actively resyncing, and I have successfully rebooted a couple of times without a problem. My goal now it to make sdb bootable for the case when/if sda fails. This is the process that I now believe I failed on previously, and it likely has to do with issueing the sgdisk command to a partition rather than a device. But even so, I don't understand why it would have messed with my first device that had been bootable. I then installed GRUB2 on /dev/sdb1 using the following command: root# grub2-install /dev/sdb1 Results: Installing for x86_64-efi platform. Installation finished. No error reported. Again, you can do that, but it's not what you wanted to do. GRUB2 is normally installed on the drive itself, unless there's a chain loader that will load it from the partition where you've installed it. You wanted to: # grub2-install /dev/sdb Yes, I am beginning to think this is correct, and as mentioned above am going back to re-read the sgdisk documentation. I rebooted the system now, only to be confronted with a GRUB prompt. I'm guessing that you also constructed RAID1 volumes before rebooting, since you probably wouldn't install GRUB2 until you did so, and doing so would explain why GRUB can't find its configuration file (the filesystem has been damaged), and why GRUB shows "no known filesystem detected" on the first partition of hd1. If so, that's expected. You can't convert a partition in-place. Looking through the directories, I see that there is no grub.cfg file. It would normally be in the first partition, which GRUB cannot read on your system. So following the guidance I had I issued t
Re: [CentOS] CentOS 5- mount shows a cifs share mounted 4 times!
On 12/11/2014 10:24 AM, Niamh Holding wrote: Thursday, December 11, 2014, 5:23:56 PM, you wrote: GM> The system will mount a GM> filesytem on top of an existing path, including one with another GM> filesystem at the same path. But the mounts are identical- Yeah, that's allowed. GM> They stack, so that you'd need to unmount GM> all four instances. I've tried- umount 10.0.0.253\\niamh umount: \\10.0.0.253\niamh: not mounted Do I need to do more backslash escaping? Specify the local path rather than the source: $ umount /NSA320-music ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5- mount shows a cifs share mounted 4 times!
Hello Gordon, Thursday, December 11, 2014, 5:23:56 PM, you wrote: GM> The system will mount a GM> filesytem on top of an existing path, including one with another GM> filesystem at the same path. But the mounts are identical- 10.0.0.253\\niamh on /NSA320-music type cifs (rw) 10.0.0.253\\niamh on /NSA320-music type cifs (rw) 10.0.0.253\\niamh on /NSA320-music type cifs (rw) 10.0.0.253\\niamh on /NSA320-music type cifs (rw) GM> They stack, so that you'd need to unmount GM> all four instances. I've tried- umount 10.0.0.253\\niamh umount: \\10.0.0.253\niamh: not mounted Do I need to do more backslash escaping? -- Best regards, Niamhmailto:ni...@fullbore.co.uk pgp6WmYDtoRLP.pgp Description: PGP signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] httpd listening only on IPv6 interface on CentOS 7
On 12/11/2014 09:35 AM, Warren Young wrote: Am 11.12.2014 um 04:48 schrieb Warren Young: the stock configuration of Apache only listens for IPv6 connections: As per RFC 3493 (Sections 3.7 and 5.3) an IPv6 socket will accept connections from IPv4 hosts, which will be mapped into the IPv6 address space. We noticed this problem when web browsers would refuse to connect to the server. *Then* we discovered the netstat oddity, and *then* we found that changing the Listen line in httpd.conf fixed it. That leaves me still wanting an explanation for what happened. New guess: there’s a difference between the IPv4 and v6 firewalls, so that changing the Listen line caused Apache to avoid the problem on the v6 side. I don't have a good guess, there. If the client was actually connecting from an IPv4 address, then the IPv4 firewall rules should have applied. At least, that's what my testing indicates. What I can say for sure is that a CentOS 7 system will accept IPv4 http connections if the IPv4 firewall allows that port, or if the firewall is disabled. Whatever problem you faced was caused by post-install configuration. Try making your standard changes incrementally and testing as you go until you can locate the steps where the problem occurs. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 grub.cfg missing on new install
On 12/10/2014 10:13 AM, Jeff Boyce wrote: The short story is that got my new install completed with the partitioning I wanted and using software raid, but after a reboot I ended up with a grub prompt, and do not appear to have a grub.cfg file. ... I initially created the sda[1,2] and sdb[1,2] partitions via GParted leaving the remaining space unpartitioned. I'm pretty sure that's not necessary. I've been able to simply change the device type to RAID in the installer and get mirrored partitions. If you do your setup entirely in Anaconda, your partitions should all end up fine. At this point I needed to copy my /boot/efi and /boot partitions from sda[1,2] to sdb[1,2] so that the system would boot from either drive, so I issued the following sgdisk commands: root# sgdisk -R /dev/sdb1 /dev/sda1 root# sgdisk -R /dev/sdb2 /dev/sda2 root# sgdisk -G /dev/sdb1 root# sgdisk -G /dev/sdb2 sgdisk manipulates GPT, so you run it on the disk, not on individual partitions. What you've done simply scrambled information in sdb1 and sdb2. The correct way to run it would be # sgdisk -R /dev/sdb /dev/sda # sgdisk -G /dev/sdb However, you would only do that if sdb were completly unpartitioned. As you had already made at least one partition on sdb a member of a RAID1 set, you should not do either of those things. The entire premise of what you're attempting is flawed. Making a partition into a RAID member is destructive. mdadm writes its metadata inside of the member partition. The only safe way to convert a filesystem is to back up its contents, create the RAID set, format the RAID volume, and restore the backup. Especially with UEFI, there are a variety of ways that can fail. Just set up the RAID sets in the installer. I then installed GRUB2 on /dev/sdb1 using the following command: root# grub2-install /dev/sdb1 Results: Installing for x86_64-efi platform. Installation finished. No error reported. Again, you can do that, but it's not what you wanted to do. GRUB2 is normally installed on the drive itself, unless there's a chain loader that will load it from the partition where you've installed it. You wanted to: # grub2-install /dev/sdb I rebooted the system now, only to be confronted with a GRUB prompt. I'm guessing that you also constructed RAID1 volumes before rebooting, since you probably wouldn't install GRUB2 until you did so, and doing so would explain why GRUB can't find its configuration file (the filesystem has been damaged), and why GRUB shows "no known filesystem detected" on the first partition of hd1. If so, that's expected. You can't convert a partition in-place. Looking through the directories, I see that there is no grub.cfg file. It would normally be in the first partition, which GRUB cannot read on your system. So following the guidance I had I issued the following commands in grub to boot the system. grub# linux /vmlinuz -3.10.0-123.el7.x86_64 root=/dev/sda2 ro grub# initrd /initramfs-3.10.0-123.el7.x86_64.img grub# boot Unfortunately the system hung on booting, with the following information in the "journalctl" file: # journalctl Not switching root: /sysroot does not seem to be an OS tree. /etc/os-release is missing. On your system, /dev/sda2 is "/boot" not the root filesystem. Your "root=" arg should refer to your root volume, which should be something like "root=/dev/mapper/vg_jab-hostroot". dracut may also need additional args to initialize LVM2 volumes correctly, such as "rd.lvm.lv=vg_jab/hostroot". If you had encrypted your filesystems, it would also need the uuid of the LUKS volume. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] httpd listening only on IPv6 interface on CentOS 7
On Dec 11, 2014, at 3:10 AM, Alexander Dalloz wrote: > Am 11.12.2014 um 04:48 schrieb Warren Young: >> >> the stock configuration of Apache only listens for IPv6 connections: > > No, that's just the way it is displayed for apache. In fact the service > listens on IPv4 as well (given we speak about the default configuration with > `Listen 80'). > > Easy to verify. We noticed this problem when web browsers would refuse to connect to the server. *Then* we discovered the netstat oddity, and *then* we found that changing the Listen line in httpd.conf fixed it. That leaves me still wanting an explanation for what happened. New guess: there’s a difference between the IPv4 and v6 firewalls, so that changing the Listen line caused Apache to avoid the problem on the v6 side. I guess we’ll just keep an eye out when we build our next EL7 box... ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 5- mount shows a cifs share mounted 4 times!
On 12/11/2014 09:02 AM, Niamh Holding wrote: How can this happen? There's nothing really abnormal about that. The system will mount a filesytem on top of an existing path, including one with another filesystem at the same path. They stack, so that you'd need to unmount all four instances. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS 5- mount shows a cifs share mounted 4 times!
Hello, How can this happen? mount -l /dev/sda3/ on type ext4 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/sda1 on /boot type ext4 (rw) /dev/sdb1 on /music type ext3 (rw) /dev/mapper/VolGroup00-LogVol00 on /fedora type ext3 (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) 10.0.0.3:/backup on /backup type nfs (rw,addr=10.0.0.3) /etc/named on /var/named/chroot/etc/named type none (rw,bind) /etc/named.rfc1912.zones on /var/named/chroot/etc/named.rfc1912.zones type none (rw,bind) /etc/rndc.key on /var/named/chroot/etc/rndc.key type none (rw,bind) /usr/lib64/bind on /var/named/chroot/usr/lib64/bind type none (rw,bind) /etc/named.iscdlv.key on /var/named/chroot/etc/named.iscdlv.key type none (rw,bind) /etc/named.root.key on /var/named/chroot/etc/named.root.key type none (rw,bind) 10.0.0.253:/i-data/48e5a222/nfs/music on /thecus-music type nfs (rw,addr=10.0.0.253) 10.0.0.253:/i-data/48e5a222/nfs/fedora on /thecus-backup type nfs (rw,addr=10.0.0.253) 10.0.0.253\\niamh on /NSA320-music type cifs (rw) 10.0.0.253\\niamh on /NSA320-music type cifs (rw) 10.0.0.253\\niamh on /NSA320-music type cifs (rw) 10.0.0.253\\niamh on /NSA320-music type cifs (rw) 10.0.0.253\\fedora on /NSA320-fedora type cifs (rw) -- Best regards, Niamh mailto:ni...@fullbore.co.uk ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 grub.cfg missing on new install
- Original Message - From: "Ned Slider" To: Cc: Sent: Wednesday, December 10, 2014 8:53 PM Subject: Re: [CentOS] CentOS 7 grub.cfg missing on new install On 10/12/14 18:13, Jeff Boyce wrote: Greetings - The short story is that got my new install completed with the partitioning I wanted and using software raid, but after a reboot I ended up with a grub prompt, and do not appear to have a grub.cfg file. So here is a little history of how I got here, because I know in order for anyone to help me they would subsequently ask for this information. So this post is a little long, but consider it complete. . . . trim . . . I then installed GRUB2 on /dev/sdb1 using the following command: root# grub2-install /dev/sdb1 Results: Installing for x86_64-efi platform. Installation finished. No error reported. The upstream docs (see below) seem to suggest 'grub2-install /dev/sdb' rather than /dev/sdb1 (i.e, installing to the device rather than a partition on the device). I don't know if this is the cause of your issue. I rebooted the system now, only to be confronted with a GRUB prompt. Thinking that this is a good opportunity to for me to learn to rescue a system since I am going to need to understand how to recover from a disk or raid failure, I started researching and reading. It takes a little bit of work to understand what information is valuable when a lot of it refers to GRUB (not GRUB2) and doesn't make reference to UEFI booting and partitions. I found this Ubuntu wiki as a pretty good source https://help.ubuntu.com/community/Grub2/Troubleshooting#Search_.26_Set I found the upstream documentation for grub2 to be useful: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/ch-Working_with_the_GRUB_2_Boot_Loader.html Included is a procedure for completely reinstalling grub2 which might help you recover. . . . trim . . . Ned, thanks for your insight. I feel like I have been sleeping with that RH7 document the last day or so trying to understand what I messed up and how to recover, I just didn't reference it in my post. Your conclusion about grub2-install being directed to the partition rather than the device may be correct, and is about the only little detail that I see that may have been wrong. The weird thing is that the installation should have put everything in the proper place on the primary drive, and my grub2-install command is being directed at putting it on the secondary drive. That is what is confusing me as the proper grub files should have been on the primary drive, allowing me to boot from there. It would have been nice if I had happened to check for the grub files before the failed reboot, or immediately after the installation. I think at this point I am going to not try and recover, but just re-install from scratch. I have gained enough knowledge in the past few days learning about grub that at least I know the general process and how to get started, but at this point I want to make sure I have a good clean system on the initial install. Thanks to others who at least took the time to read my long post. Jeff ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] print something on console after boot
On Wed, December 10, 2014 17:51, Gordon Messmer wrote: > On 12/10/2014 12:47 PM, Dan Hyatt wrote: >> I've a virtual instance and I need to know its IP address after it has >> finished booting up, to know where to ssh into it. I've tried adding >> "ip -4 addr > /dev/tty0" to rc.local, but that obviously doesn't work, >> because the login prompt overwrites everything I do. > > The easy answer would be: don't fight the login prompt. "agetty" writes > the contents of /etc/issue to the console before the login prompt. If > /etc/issue contains "\4" then agetty will print the IPv4 address to the > console. > > See the man page for agetty, and update /etc/issue. > > I find that CentOS-6 evidently does not support \; nor many of the /etc/issue flags defined in man 1 agetty: /etc/issue CentOS release 6.6 (Final) Kernel \r on an \m Test: b:\b d:\d s:\s l:\l m:\m n:\n o:\o O:\O r:\r t:\t u:\u 0:\0 4:\4 6:\6 login: CentOS release 6.6 (Final) Kernel 2.6.32-504.1.3.el6.centos.plus.x86_64 on an x86_64 Test: b: d:09:19 on Thursday, 11 December 2014 s:Linux l:7 m:x86_64 n:vhost04.hamilton.harte-lyne.ca o: O: r:2.6.32-504.1.3.el6.centos.plus.x86_64 t:09:19 on Thursday, 11 December 2014 u: 0: 4: 6: For ease in analysis (note that flags \0, \4, and \6 are not defined in agetty): b: d:09:19 on Thursday, 11 December 2014 s:Linux l:7 m:x86_64 n:vhost04.hamilton.harte-lyne.ca o: O: r:2.6.32-504.1.3.el6.centos.plus.x86_64 t:09:19 on Thursday, 11 December 2014 u: 0: 4: 6: Is there some configuration issue of which I am unaware? Where is the flag \4 usage defined? -- *** E-Mail is NOT a SECURE channel *** James B. Byrnemailto:byrn...@harte-lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS-announce Digest, Vol 118, Issue 7
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org
You can reach the person managing the list at
centos-announce-ow...@centos.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."
Today's Topics:
1. CESA-2014:1971 Important CentOS 7 kernel Security Update
(Johnny Hughes)
2. CESA-2014:1976 Important CentOS 7 rpm SecurityUpdate
(Johnny Hughes)
3. CEEA-2014:1980 CentOS 7 systemd Enhancement Update (Johnny Hughes)
--
Message: 1
Date: Wed, 10 Dec 2014 12:48:13 +
From: Johnny Hughes
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2014:1971 Important CentOS 7 kernel
SecurityUpdate
Message-ID: <20141210124813.ga47...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Security Advisory 2014:1971 Important
Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-1971.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
0ba4633c95c00c8c0e680e4ba25a7d86b814997e770ec969b13786e7dc293edb
kernel-3.10.0-123.13.1.el7.x86_64.rpm
9394409a1a2198f722c5413405cab3a02ff9f3e84a4b7ebbc79bfd4d33a9c1bf
kernel-abi-whitelists-3.10.0-123.13.1.el7.noarch.rpm
c1fccd2c7a95dae3ccd3b4d3970c96fcda48c7fe21c8a7e8580dd19171c51278
kernel-debug-3.10.0-123.13.1.el7.x86_64.rpm
b694c8adb48d481617db3056c34dd455962bf48994ebd5ac7339d5169842766d
kernel-debug-devel-3.10.0-123.13.1.el7.x86_64.rpm
fa1622aaa604897b79cd7e468b9d99c81c4e9b2c94c24ebacb6f94070907f579
kernel-devel-3.10.0-123.13.1.el7.x86_64.rpm
5db912400deea9b97dcbfb113d5dc67e47c6f04f763cdc28615f9eb7cf74c59d
kernel-doc-3.10.0-123.13.1.el7.noarch.rpm
198ad46ad016f25e59c0d96daf207feaaf214c90e41c33e03324141f4d485c7e
kernel-headers-3.10.0-123.13.1.el7.x86_64.rpm
ddb99325960b064fb283c5a2dbc505b8a452663d00bbd6e6247150c53a834e18
kernel-tools-3.10.0-123.13.1.el7.x86_64.rpm
bc0c7bde959031b02fe76e4ff4016d61bb0db6bc6cb15fe5bf7b858814539eaa
kernel-tools-libs-3.10.0-123.13.1.el7.x86_64.rpm
ac5b1b0066d71d38f2a5e2a231b6b81603dfd4f16c314d8eb94738550f4b2af1
kernel-tools-libs-devel-3.10.0-123.13.1.el7.x86_64.rpm
1221821e953c8c6122b87ca9878ef3fe69dac93243061e13fb6f8756a313fc0d
perf-3.10.0-123.13.1.el7.x86_64.rpm
2ad0cf510727c006412e2ca1c944e0e47fb6cfb6c24a2bb86d3e6cbf61cc51b4
python-perf-3.10.0-123.13.1.el7.x86_64.rpm
Source:
264dd245a168050e3c8cf54adf892827786fd07a03f55cc45e6b9fdb46486354
kernel-3.10.0-123.13.1.el7.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
--
Message: 2
Date: Wed, 10 Dec 2014 12:49:42 +
From: Johnny Hughes
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2014:1976 Important CentOS 7 rpm
SecurityUpdate
Message-ID: <20141210124942.ga48...@n04.lon1.karan.org>
Content-Type: text/plain; charset=us-ascii
CentOS Errata and Security Advisory 2014:1976 Important
Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-1976.html
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
42d0d9d8c43646be6bb73af2645e7e7d00613ffbd7281a167e938e13254d838d
rpm-4.11.1-18.el7_0.x86_64.rpm
3718d08372462fb7670e87dd49c55ccd3ba241c9c99b849478fcba4783f78102
rpm-apidocs-4.11.1-18.el7_0.noarch.rpm
4cb5f67b92322653529f9c2c4f21756e4500c4c009c8d7e76a9ef29fa92e8d52
rpm-build-4.11.1-18.el7_0.x86_64.rpm
6d0cd4d0e424f21e6f51b89a9eb81b42c6d36824e16d8ff839f442c5504e081b
rpm-build-libs-4.11.1-18.el7_0.i686.rpm
5414fe17e10dc2032fb7dd007f983acdee938c21c9352351e9c8a1529e990275
rpm-build-libs-4.11.1-18.el7_0.x86_64.rpm
e9e3de0f85d9f06931ea379c9c0b9da041468986f4c6e96029c8ae918ab44db5
rpm-cron-4.11.1-18.el7_0.noarch.rpm
e8f8a8be3445672da00e8c2a687b902981c6ea453bc3e87b6d0e83b9a93b6b94
rpm-devel-4.11.1-18.el7_0.i686.rpm
5e9ad78b8bbb20470671e3575657468c7db209156600b5502d06e3055e9a9808
rpm-devel-4.11.1-18.el7_0.x86_64.rpm
b1cad417e97633e8989ffbc62512f9b51323d3adfe3f87455dd40df0cfc43ffd
rpm-libs-4.11.1-18.el7_0.i686.rpm
44fe1c44040cd329c58ae73a02c778715f8bf1528bfc7fd6a18eac2c0bc0dfd2
rpm-libs-4.11.1-18.el7_0.x86_64.rpm
16fd2ef83d8b529c171275273dfb52a68605557ad8aad56e6f56ca2481bfd0d6
rpm-python-4.11.1-18.el7_0.x86_64.rpm
03ddda6f66ed8a65c43f2fddc6f3d9475d5891dd264cb6bff83a3707e953b36a
rpm-sign-4.11.1-18.el7_0.x86_64.rpm
Source:
7d5bbcb466c84459731a4830945d454ffbcf14b773fd318594d29e73fdde5052
rpm-4.11.1-18.el7_0.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.free
Re: [CentOS] Dropbox on CentOS 6?
> -Original Message- > From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On > Behalf Of Niki Kovacs > Sent: den 11 december 2014 11:32 > To: CentOS mailing list > Subject: Re: [CentOS] Dropbox on CentOS 6? > > Le 11/12/2014 10:58, Liam O'Toole a écrit : > > That procedure works for me up to and including 6.6. It would indeed be > > helpful if the OP listed the particular problems they encountered. > > I guess my mistake was to hunt down a Dropbox RPM package in various > third-party repos. I'll try the command-line procedure that's advertised > on the Dropbox site. > > Thanks everybody for your answers, Remember you can install already downloaded rpm's with yum as well, it'll download any dependencies you're possibly missing that Dropbox requires. ;-) -- //Sorin ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Dropbox on CentOS 6?
Le 11/12/2014 10:58, Liam O'Toole a écrit : That procedure works for me up to and including 6.6. It would indeed be helpful if the OP listed the particular problems they encountered. I guess my mistake was to hunt down a Dropbox RPM package in various third-party repos. I'll try the command-line procedure that's advertised on the Dropbox site. Thanks everybody for your answers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'église - 30730 Montpezat Web : http://www.microlinux.fr Mail : i...@microlinux.fr Tél. : 04 66 63 10 32 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] httpd listening only on IPv6 interface on CentOS 7
Am 11.12.2014 um 04:48 schrieb Warren Young: I’ve held off reporting this since I thought it might just be some kind of fluke, but I’ve seen it now on three different boxes. The symptom is that the stock configuration of Apache only listens for IPv6 connections: $ netstat -na | grep :80.*LISTEN tcp6 0 0 :::80 :::*LISTEN No, that's just the way it is displayed for apache. In fact the service listens on IPv4 as well (given we speak about the default configuration with `Listen 80'). Easy to verify. You should see a second line there for IPv4, but you don't: tcp0 0 0.0.0.0:80 0.0.0.0:* LISTEN The stock httpd.conf file just says “Listen 80” which is documented as listening on both IPv4 and IPv6. [1] You’re supposed to need to go out of your way to get it to listen on just one or the other, but somehow CentOS 7’s Apache manages it. Since I only need IPv4, I’ve managed to hack it into working by changing that line in /etc/httpd/conf/httpd.conf to: Listen 0.0.0.0:80 Why do I need to do this? [1] https://httpd.apache.org/docs/2.4/mod/mpm_common.html#listen Alexander ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Dropbox on CentOS 6?
On 2014-12-11, Sorin Srbu wrote: >> -Original Message- From: >> centos-boun...@centos.org >> [mailto:centos-boun...@centos.org] On >> Behalf Of Niki Kovacs Sent: den 11 december 2014 08:55 To: >> centos@centos.org Subject: [CentOS] >> Dropbox on CentOS 6? >> >> I just spent a couple of unnerving hours trying to make Dropbox work >> on CentOS 6.6. >> >> Is there a way that >> >> 1. Actually works? >> >> 2. Doesn't include jumping through burning loops? > > The procedure described on https://www.dropbox.com/install?os=lnx has > worked for me on several occasions before on CentOS 6.0 >> 6.5. > Haven't done it on 6.6 yet, but I doubt it'd be any different. > > What problems have you run into?? That procedure works for me up to and including 6.6. It would indeed be helpful if the OP listed the particular problems they encountered. -- Liam ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] get /full/path/filename.ext from filename.ext
On 12/10/2014 04:02 PM, Dan Hyatt wrote: I don't know if this is of interest as an alternative. I did find a cool functionality called locate and updatedb Updatedb creates the database of your files, locate does superfast searches. It essentially does a superfast "find" on your root filesystem, giving you the fully qualified path of all hits. You can create db's on your other filessytems. The problem is that it can get stale, but you can update it before doing your searches. Plus it gives you a fully qualified path name with the results. So if you need to do a set of searches on a filesystem (or whole system) run updatedb on each target filesystem to create the db for that filesystem. then use locate to search each filesystem "db"... it takes seconds like ls instead of minutes like findthe more files in the FS, the quicker the searches compared to other tools. the best part is you can run the db's when your systems are quiet, and the databases use minimal diskspace. Dan, Thanks for responding. I've been using those two utilities for a long time, and they are indispensable. But they don't solve the issue I'm having. Consider the case where there are multiple files with the same name but different paths. Also, it takes quite a while for the data used by those utilities to update, much too long for an interactive script. On 12/9/2014 2:57 PM, ken wrote: This should be simple, but it's not, unless I'm forgetting something. Writing a script, an arg is a filename. So fname=$1 But I want that expanded to include the full path and filename, not just what is given as the arg on the command line. E.g., if the user's cwd is /home/joe/a/b/c/ and he specifies ../x/file-a.ext then the function/utility should transform that into the absolute path with filename: /home/joe/a/b/x/file-a.ext In the simplest scenario, the answer would be $PWD/file-a.ext, but that would by no means cover a portion of the possible scenarios. You'd think this functionality would be included already in one or another linux utility. It's kinda like the complement to the 'basename' utility. I've looked into the dark corners of ls, stat, file, bash, type, find, and a few other linux standards, but nothing seems to do this. Any gurus out there know the utility which does this? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Dropbox on CentOS 6?
Hello Andrew, On Thu, 11 Dec 2014 09:45:45 +0100 Andrew Holway wrote: > FYI It works for me on Centos 7 when I used it last week. Me too, no problem here. Regards, > On 11 December 2014 at 09:04, Sorin Srbu wrote: > > > > -Original Message- > > > From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On > > > Behalf Of Niki Kovacs > > > Sent: den 11 december 2014 08:55 > > > To: centos@centos.org > > > Subject: [CentOS] Dropbox on CentOS 6? > > > > > > I just spent a couple of unnerving hours trying to make Dropbox work on > > > CentOS 6.6. > > > > > > Is there a way that > > > > > > 1. Actually works? > > > > > > 2. Doesn't include jumping through burning loops? > > > > The procedure described on https://www.dropbox.com/install?os=lnx has > > worked for me on several occasions before on CentOS 6.0 >> 6.5. > > Haven't done it on 6.6 yet, but I doubt it'd be any different. > > > > What problems have you run into?? > > -- > > //Sorin > > ___ > > CentOS mailing list > > CentOS@centos.org > > http://lists.centos.org/mailman/listinfo/centos > > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos -- wwp pgpcM5J4QMAwB.pgp Description: OpenPGP digital signature ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Dropbox on CentOS 6?
FYI It works for me on Centos 7 when I used it last week. On 11 December 2014 at 09:04, Sorin Srbu wrote: > > -Original Message- > > From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On > > Behalf Of Niki Kovacs > > Sent: den 11 december 2014 08:55 > > To: centos@centos.org > > Subject: [CentOS] Dropbox on CentOS 6? > > > > I just spent a couple of unnerving hours trying to make Dropbox work on > > CentOS 6.6. > > > > Is there a way that > > > > 1. Actually works? > > > > 2. Doesn't include jumping through burning loops? > > The procedure described on https://www.dropbox.com/install?os=lnx has > worked for me on several occasions before on CentOS 6.0 >> 6.5. > Haven't done it on 6.6 yet, but I doubt it'd be any different. > > What problems have you run into?? > -- > //Sorin > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Dropbox on CentOS 6?
> -Original Message- > From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On > Behalf Of Niki Kovacs > Sent: den 11 december 2014 08:55 > To: centos@centos.org > Subject: [CentOS] Dropbox on CentOS 6? > > I just spent a couple of unnerving hours trying to make Dropbox work on > CentOS 6.6. > > Is there a way that > > 1. Actually works? > > 2. Doesn't include jumping through burning loops? The procedure described on https://www.dropbox.com/install?os=lnx has worked for me on several occasions before on CentOS 6.0 >> 6.5. Haven't done it on 6.6 yet, but I doubt it'd be any different. What problems have you run into?? -- //Sorin ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
