similar to: CESA-2017:0036 Important CentOS 6 kernel Security Update

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

On Thu, Mar 28, 2019 at 9:24 AM Gianluca Cecchi <gianluca.cecchi at gmail.com> wrote: > > > 1) In CentOS 6 we have the classical SysV service > file: /etc/rc.d/init.d/kdump > > Supposing you have just installed 2.6.32-642.13.1.el6.x86_64 kernel > > [snip] > > and at the end it runs this command if it doesn't find one: > $MKDUMPRD $kdump_initrd

On Thu, Mar 28, 2019 at 6:55 AM wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn> wrote: > > -----Original Messages----- > > From: "Benjamin Hauger" <hauger at noao.edu> > > Sent Time: 2019-03-28 01:31:40 (Thursday) > > To: wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn>, centos at centos.org > > Cc: > > Subject: Re: [CentOS] How to specify

I have a KVM vm running CentOS-6.8 on a host also running CentOS-6.8. This instance is used for occasional development projects which require segregation. Thus it is seldom accessed. At some point in the recent past this guest developed an issue with starting. Specifically these messages were found in the system log files: /var/log/messages-20170312:Mar 10 16:31:06 vhost04 kernel: dracut:

> -----Original Messages----- > From: "Gianluca Cecchi" <gianluca.cecchi at gmail.com> > Sent Time: 2019-03-28 16:59:19 (Thursday) > [...] > The command line fo CentOS 6 clearly misses the kernel version to build > initrd file for, so the correct command should be: > > /sbin/mkdumprd -d -f > "/boot/initrd-2.6.32-642.13.1.el6.x86_64kdump.img"

Hello, I was checking my configuration regarding DNS while I was reading https://wiki.samba.org/index.php/BIND9_DLZ_DNS_Back_End#New_DNS_Entries_Are_Not_Resolvable and I found that private/sam.ldb.d/ and private/dns/sam.ldb.d/ are different # ls -lai /usr/local/samba/private/sam.ldb.d/ 2760569 -rw-------. 1 root root 16400384 Oct 24 08:28 CN%3DCONFIGURATION,DC%3DAPAM-AD,DC%3DAPAM,DC%3DIT.ldb

On Tue, 24 Oct 2017 09:01:16 +0200 Giuseppe Arvati via samba <samba at lists.samba.org> wrote: > Hello, > > I was checking my configuration regarding DNS > while I was reading > https://wiki.samba.org/index.php/BIND9_DLZ_DNS_Back_End#New_DNS_Entries_Are_Not_Resolvable > > and I found that private/sam.ldb.d/ and private/dns/sam.ldb.d/ > are different > > # ls

On Mon, 6 Nov 2017 15:27:13 +0100 Giuseppe Arvati via samba <samba at lists.samba.org> wrote: > Hello, > I recently set up a new software to backup samba share. > This software ( https://github.com/borgbackup/borg ) run on file > server as root cron script during the night and save file on external > NAS. > > The problem I have is that for each file copied from >

On 06/20/2017 04:08 AM, Charles Lepple wrote: > [...] > It does not get a length for method 1, so it moves on to method 2, which gets a length, but fails to get the rest of the descriptor. This is what is happening to lsusb, too (tries to fetch 549 bytes, gets only 9). and is there anything I can do to fix, short of hoping to receive an updated unbroken firmware for the UPS from a support

Hai Giuseppe, ( and +What Rowland said.. ) Samba4 ADDC (you name it file server?) Nas with the storage. ( and is this one domain joined? If yes, post the smb.conf also from this one. ) Burg run the cron script on the Samba server over which protocol? Ssh, then your in trouble. This one is also not resolved, so we need more info about the setup. > > [2017/11/06 14:58:04.826444, 5]

Aaaargggg.... The S-1-5-18 AND sid S-1-5-32-544 did not resolve. But sid S-1-5-32-544 first not then later on it works.? Sorry about the noice, but that one i wanted to point out also. I hate it when im almost done with typing and mr Penny comes first. ;-) :-p Greetz, Louis > > > > > -----Oorspronkelijk bericht----- > > Van: samba [mailto:samba-bounces at

Any word on this update for CentOS 6? This one seems pretty bad if it's a remote exploit. -- Matt Phelps System Administrator, Computation Facility Harvard - Smithsonian Center for Astrophysics mphelps at cfa.harvard.edu, http://www.cfa.harvard.edu ---------- Forwarded message ---------- From: Red Hat Errata Notifications <errata at redhat.com> Date: Tue, Jan 10, 2017 at 5:19 PM

Hello, I recently set up a new software to backup samba share. This software ( https://github.com/borgbackup/borg ) run on file server as root cron script during the night and save file on external NAS. The problem I have is that for each file copied from samba share to external NAS, winbindd log an error such this to samba.log.winbindd and /var/log/messages [2017/11/06 11:05:16.747449, 0]

What do you mean? Wouldn't the kernel version always be the actual running version of the kernel that was booted? Ben On 3/26/19 6:16 PM, wuzhouhui wrote: >> -----Original Messages----- >> From: "Benjamin Hauger" <hauger at noao.edu> >> Sent Time: 2019-03-27 00:15:21 (Wednesday) >> To: centos at centos.org >> Cc: >> Subject: Re: [CentOS]

On 06/20/2017 02:27 AM, Charles Lepple wrote: > On Jun 19, 2017, at 10:45 AM, Manuel Wolfshant wrote: >> #lsusb -vvv -d 0463:ffff >> >> Bus 002 Device 012: ID 0463:ffff MGE UPS Systems UPS > ... >> HID Device Descriptor: >> bLength 9 >> bDescriptorType 33 >> bcdHID 1.10