Displaying 20 results from an estimated 200 matches similar to: "CESA-2017:2679 Important CentOS 7 kernel Security Update"
2017 Sep 14
0
CentOS-announce Digest, Vol 151, Issue 3
Send CentOS-announce mailing list submissions to
centos-announce at 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 at centos.org
You can reach the person managing the list at
centos-announce-owner at centos.org
When
2017 Feb 17
3
[Bug 2679] New: ssh mux process (and maybe others) should perhaps cd /
https://bugzilla.mindrot.org/show_bug.cgi?id=2679
Bug ID: 2679
Summary: ssh mux process (and maybe others) should perhaps cd /
Product: Portable OpenSSH
Version: 7.4p1
Hardware: Other
OS: All
Status: NEW
Severity: enhancement
Priority: P5
Component: ssh
Assignee:
2019 Sep 18
0
CEBA-2019:2679 CentOS 7 libvirt BugFix Update
CentOS Errata and Bugfix Advisory 2019:2679
Upstream details at : https://access.redhat.com/errata/RHBA-2019:2679
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
21895646047b35e098755091ef3dfb304bd32e21ed7545cdc16a0795a1c35811 libvirt-4.5.0-23.el7_7.1.x86_64.rpm
2018 Feb 07
2
/dev/md1 => 93% Used. Warning. Disk Filling up. - what would be safe to delete in /boot ?
Hello CentOS users,
in the recent time I keep getting the logwatch warnings from my 2 dedicated
servers running CentOS 7.4.1708.
I guess because of the numerous kernel updates (because of
Spectre+Meltdown) in the near past?
Could someone please suggest me, which files in my /boot partition would be
safe to delete?
I would like to avoid the situation of having to boot the rescue partiton
etc.
2017 Oct 05
0
Missing file in current kernel-devel package
> -----Original Message-----
> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of m.roth at 5-
> cent.us
> Sent: Thursday, October 05, 2017 10:58 AM
> To: CentOS mailing list <centos at centos.org>
> Subject: Re: [CentOS] Missing file in current kernel-devel package
>
> Fred Smith wrote:
> > On Thu, Oct 05, 2017 at 09:56:57AM -0400, m.roth at
2017 Oct 05
0
Missing file in current kernel-devel package
On 10/05/2017 10:17 AM, m.roth at 5-cent.us wrote:
> Albert McCann wrote:
>>> -----Original Message-----
>>> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of m.roth at 5-
>>> cent.us
>>> Sent: Thursday, October 05, 2017 10:58 AM
>>> To: CentOS mailing list <centos at centos.org>
>>> Subject: Re: [CentOS] Missing file in
2017 Oct 05
2
Missing file in current kernel-devel package
Albert McCann wrote:
>> -----Original Message-----
>> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of m.roth at 5-
>> cent.us
>> Sent: Thursday, October 05, 2017 10:58 AM
>> To: CentOS mailing list <centos at centos.org>
>> Subject: Re: [CentOS] Missing file in current kernel-devel package
>>
>> Fred Smith wrote:
>> >
2017 Oct 04
2
C7: kernel-3.10.0-693.2.2, huh?
Ok... I just fully updated a user's machine. And got a kernel panic on
reboot. So, having run into this earlier this year, I tried to reinstall
the kernel.
yum reinstall kernel-3.10.0-693.2.2.el7.x86_64
Installed package kernel-3.10.0-693.2.2.el7.x86_64 (from updates) not
available.
Error: Nothing to do
Huh? Anyone?
mark
2017 Oct 05
3
Missing file in current kernel-devel package
Johnny Hughes wrote:
> On 10/05/2017 10:17 AM, m.roth at 5-cent.us wrote:
>> Albert McCann wrote:
>>>> -----Original Message-----
>>>> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of m.roth at 5-
>>>> cent.us
>>>> Sent: Thursday, October 05, 2017 10:58 AM
>>>> To: CentOS mailing list <centos at centos.org>
2017 Oct 12
3
Kernel crash
Hi everyone,
I updated the kernel from 3.10.0-514.16.1.el7.x86_64
to 3.10.0-693.2.2.el7.x86_64 . While I was following these steps
https://wiki.centos.org/HowTos/Laptops/Wireless/Broadcom (I knew that I
needed to compile again everything) in order to activate WIFI, the laptop
crashed doing
# depmod -a
# modprobe wl
Noting that I replaced (naively) # depmod $(uname -r) from the guide
(stupid
2017 Oct 22
2
Areca RAID controller on latest CentOS 7 (1708 i.e. RHEL 7.4) kernel 3.10.0-693.2.2.el7.x86_64
-----Original Message-----
From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Noam
Bernstein
Sent: Sunday, October 22, 2017 8:54 AM
To: CentOS mailing list <centos at centos.org>
Subject: [CentOS] Areca RAID controller on latest CentOS 7 (1708 i.e. RHEL
7.4) kernel 3.10.0-693.2.2.el7.x86_64
> Is anyone running any Areca RAID controllers with the latest CentOS 7 kernel,
>
2012 Nov 21
1
Conntrackd - fail at startup.
Hi all.
I currently try to start conntrackd to test it.
CentOS release 6.3 (Final)
Linux lb1.local 2.6.32-279.11.1.el6.x86_64 #1 SMP Tue Oct 16 15:57:10 UTC
2012 x86_64 x86_64 x86_64 GNU/Linux
This is a VirtualBox vm.
I try:
/usr/sbin/conntrackd -C /etc/conntrackd/conntrackd.conf -d
My config:
[root at lb1 log]# egrep -v '^\s*#|^$' /etc/conntrackd/conntrackd.conf | less
Sync {
2011 Feb 05
2
Help!!! from R beginner
Hello,
I'm trying to add a column to the following data frame. The new column
will contain "black" when the 5th column(if_TE_related) is
"TE_related", or "orange" when the 4th column is " " (space).
"chromo" "MSU_locus" "end5" "end3" "if_TE_related"
"chr04" "LOC_Os04g01006" 1032
2017 Sep 14
1
vmware player 12.5.7 with CentOS 7.4
hi all - anyone find a way to get vmware player 12.5.7 working with 7.4?
Thanks - everything good with the upgrade except that.
Great job CentOS team!
Jerry
starting vmplayer I get the following:
Note: adwaita is installed.
canberra is installed
No idea what pk is ?
vmplayer
(vmware-modconfig:12595): Gtk-WARNING **: Unable to locate theme engine in
module_path: "adwaita",
2004 Sep 15
0
codec trouble?
Hi everyone!
Situation: when I call from cell phone to a asterisk-connected phone,
all works fine. When I call from the asterisk-connected phone (a Cisco
7960 SIP) to the cell, the connection gets made, but there is no audio
going in either way...
Asterisk reports the following:
Sep 16 08:27:41 WARNING[245775]: chan_sip.c:2679 process_sdp:
Insufficient information for SDP (m = '', c =
2007 Jan 05
0
idle SIP channels problem
I have 2 asterisk servers connected together on internet, when placing one
or two calls, things goes fine, but when placing more calls, i am getting
the below messages on the far end:
Jan 5 17:25:00 ERROR[2679] chan_sip.c: Call from peer 'switch' rejected due
to usage limit of 16
Jan 5 17:25:00 NOTICE[2679] chan_sip.c: Failed to place call for user , too
many calls
I am seeing a lot of
2017 Oct 13
0
Kernel crash
I'm sorry for all this trouble; I followed ElRepo's instructions and now I
have wifi! (someday I will fix bluetooth).
2017-10-12 18:52 GMT-03:00 Diego Farias <dnfarias at uc.cl>:
> By the way, attached is the kernel panic screenshot, apparently it is
> related to cfg80211.
>
> On Oct 12, 2017 5:46 PM, "Diego Farias" <dnfarias at uc.cl> wrote:
>
2017 Oct 22
0
Areca RAID controller on latest CentOS 7 (1708 i.e. RHEL 7.4) kernel 3.10.0-693.2.2.el7.x86_64
Is anyone running any Areca RAID controllers with the latest CentOS 7 kernel, 3.10.0-693.2.2.el7.x86_64? We recently updated (from 3.10.0-514.26.2.el7.x86_64), and we?ve started having lots of problems. To add to the confusion, there?s also a hardware problem (either with the controller or the backplane most likely) that we?re in the process of analyzing. Regardless, we have an ARC1883i, and
2017 Oct 05
3
Missing file in current kernel-devel package
Fred Smith wrote:
> On Thu, Oct 05, 2017 at 09:56:57AM -0400, m.roth at 5-cent.us wrote:
>> Ok, folks,
>>
>> I've identified what my problem is, trying to install the NVidia
>> proprietary drivers: in kernel-devel-3.10.0-514.26.2.el7.x86_64, there
>> is a file
>> /usr/src/kernels/3.10.0-514.26.2.el7.x86_64/include/linux/fence.h
>>
>> It
2012 Jul 04
0
[xen-unstable test] 13460: regressions - FAIL
flight 13460 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/13460/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-pv 18 leak-check/check fail REGR. vs. 13459
test-amd64-amd64-pv 18 leak-check/check fail REGR. vs. 13459
test-amd64-i386-xl 18