Please note that you need to restart daemons that are still using old
library versions or reboot the whole machine.
you can use command 'lsof +c0 -d DEL | awk 'NR==1 || /libc-/ {print
$2,$1,$4,$NF}' | column -t' to check what daemons are still using old
version of library.
--
Eero
2016-02-20 7:30 GMT+02:00 jdow <j...@earthlink.net>:
> # rpm -qa | grep glibc
> glibc-2.12-1.166.el6_7.7.x86_64
> glibc-2.12-1.166.el6_7.7.i686
> glibc-utils-2.12-1.166.el6_7.7.x86_64
> glibc-common-2.12-1.166.el6_7.7.x86_64
> glibc-devel-2.12-1.166.el6_7.7.x86_64
> glibc-headers-2.12-1.166.el6_7.7.x86_64
>
> Already installed with updates as of a day or so ago.
>
> {^_^}
>
> On 2016-02-19 17:49, Kenny Noe wrote:
>
>> Yes..... Follow these instructions.
>>
>> http://www.thegeekstuff.com/2016/02/glibc-patch-cve-2015-7547/
>>
>> --Kenny
>>
>> Thanks
>>
>> --Kenny
>>
>> On Fri, Feb 19, 2016 at 8:33 PM, ToddAndMargo <toddandma...@zoho.com
>> <mailto:toddandma...@zoho.com>> wrote:
>>
>> Hi All,
>>
>> Are we affected by this?
>>
>>
>> http://www.infoworld.com/article/3033862/security/patch-now-unix-bug-puts-linux-android-and-ios-systems-at-risk.html
>>
>> -T
>>
>>
>> --
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> Computers are like air conditioners.
>> They malfunction when you open windows
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>>
>>
