search for: youjr

Displaying 5 results from an estimated 5 matches for "youjr".

Did you mean: you'r
2016 Feb 17
2
New glibc for CentOS-6 and CentOS-7 and CVE-2015-7547
...ut SystemD .. I assume c7. In c7 .. there is a symlink to /etc/sysctl.d/99-sysctl.conf to /etc/sysctl.conf Have you verified your sysctl.conf actually contains those settings still. Your best bet on CentOS-7 is to create a new file in /etc/sysctl.d/ called something like 99-postgres.conf and put youjr mods in there. That way it will never change. Also .. verify all the files in /etc/sysctl.d/ and /etc/sysctl.conf are set to this label for selinux: unconfined_u:object_r:etc_t:s0 See this for labeling: red.ht/1ooTpiI But, /etc/sysctl.conf should still work in centos-7. -------------- next par...
2016 Feb 17
0
New glibc for CentOS-6 and CentOS-7 and CVE-2015-7547
...c7 .. there is a symlink to /etc/sysctl.d/99-sysctl.conf to > /etc/sysctl.conf > > Have you verified your sysctl.conf actually contains those settings still. > > Your best bet on CentOS-7 is to create a new file in /etc/sysctl.d/ > called something like 99-postgres.conf and put youjr mods in there. > That way it will never change. > > Also .. verify all the files in /etc/sysctl.d/ and /etc/sysctl.conf are > set to this label for selinux: > > unconfined_u:object_r:etc_t:s0 > > See this for labeling: > red.ht/1ooTpiI > > But, /etc/sysctl.conf...
2016 Feb 17
2
New glibc for CentOS-6 and CentOS-7 and CVE-2015-7547
...ink to /etc/sysctl.d/99-sysctl.conf to >> /etc/sysctl.conf >> >> Have you verified your sysctl.conf actually contains those settings still. >> >> Your best bet on CentOS-7 is to create a new file in /etc/sysctl.d/ >> called something like 99-postgres.conf and put youjr mods in there. >> That way it will never change. >> >> Also .. verify all the files in /etc/sysctl.d/ and /etc/sysctl.conf are >> set to this label for selinux: >> >> unconfined_u:object_r:etc_t:s0 >> >> See this for labeling: >> red.ht/1ooTpiI...
2016 Feb 17
1
New glibc for CentOS-6 and CentOS-7 and CVE-2015-7547
> The easy answer is yes .. glibc requires so many things to be restarted, > that is the best bet. Or certainly the easiest. > > Note: in CentOS 7, there is also a kernel update which is rated as > Important .. so you should boot to that anyway: > https://lists.centos.org/pipermail/centos-announce/2016-February/021705.html > > Here is a good link to figure out what to
2016 Feb 17
4
New glibc for CentOS-6 and CentOS-7 and CVE-2015-7547
On 02/17/2016 07:08 AM, Michael H wrote: > On 17/02/16 13:01, Johnny Hughes wrote: >> I normally just let the daily announce post to this list show what >> is available for updates, but there is a CVE (CVE-2015-7547) that >> needs a bit more attention which will be on today's announce list >> of updates. >> >> We released a new glibc yesterday for