--On Thursday, August 30, 2018 4:17 AM + Turritopsis Dohrnii Teo En
Ming wrote:
43. Go to the main Apache web server configuration directory:
cd /etc/httpd/conf
44. Edit the main Apache web server configuration file:
sudo nano httpd.conf
45. Append the following code to the end of
> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of TE Dukes
> Sent: Thursday, August 30, 2018 6:36 PM
> To: 'CentOS mailing list'
> Subject: Re: [CentOS] Mail has quit working
>
>
>
> > -Original Message-
> > From: CentOS
> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Gordon
> Messmer
> Sent: Thursday, August 30, 2018 6:23 PM
> To: centos@centos.org
> Subject: Re: [CentOS] Mail has quit working
>
> On 08/29/2018 06:54 PM, TE Dukes wrote:
> > Added back the IPV6 to
On 08/29/2018 06:54 PM, TE Dukes wrote:
Added back the IPV6 to /etc/hosts a couple days ago for grins and giggles.
No longer getting IPV6 errors in logwatch for bind. Everything working.
I think removing my ISP's nameservers from /etc/resolv.conf was the fix.
I just caught up on the thread.
On 08/30/2018 01:11 AM, wwp wrote:
I well know that to match "1.foo-named", I should use `ls*foo*`
(trailing *) and I'm sure that you know that `ls *foo` matches
1.foo.
I didn't. Given a better description of what you're trying to do, I see
that the bash's behavior has changed.
I also
On Aug 29, 2018, at 23:17, Turritopsis Dohrnii Teo En Ming
wrote:
>
> sudo /usr/sbin/apachectl start
On CentOS 7 you really should run:
$ sudo systemctl start httpd.service
That way the service is managed by systemd and gets the appropriate cgroups and
contexts. You also do nothing to
>
>> Am 30.08.2018 um 17:24 schrieb Simon Matter :
>>
>>> Am 30.08.2018 um 06:37 schrieb Simon Matter :
> Since the update from kernel-2.6.32-754.2.1.el6.x86_64
> to kernel-2.6.32-754.3.5.el6.x86_64 I can not boot my
> KVM guests anymore!? The workstation panics immediately!
>
> Am 30.08.2018 um 17:24 schrieb Simon Matter :
>
>> Am 30.08.2018 um 06:37 schrieb Simon Matter :
>>>
Since the update from kernel-2.6.32-754.2.1.el6.x86_64
to kernel-2.6.32-754.3.5.el6.x86_64 I can not boot my
KVM guests anymore!? The workstation panics immediately!
> Am 30.08.2018 um 06:37 schrieb Simon Matter :
>>
>>> Since the update from kernel-2.6.32-754.2.1.el6.x86_64
>>> to kernel-2.6.32-754.3.5.el6.x86_64 I can not boot my
>>> KVM guests anymore!? The workstation panics immediately!
>>>
>>> I would not have expected this behavior now (last phase of
Stephen John Smoogen wrote:
> On Thu, 30 Aug 2018 at 05:41, Leon Fauster via CentOS
> wrote:
>>
>>> There goes a cheap and reliable VM dev machine :-/
>>
>> No way. Should all IT departments trash a big percentage of there
>> hardware now?
> I am going to say from chip and OEM manufacturers view
On Thu, 30 Aug 2018 at 05:41, Leon Fauster via CentOS
wrote:
>
>
>
> > There goes a cheap and reliable VM dev machine :-/
>
>
> No way. Should all IT departments trash a big percentage of there hardware
> now?
>
>
I am going to say from chip and OEM manufacturers view points: yes. For at
least
On onsdag 29 augusti 2018 kl. 20:19:22 EEST Alvin Starr wrote:
> So in this case do the VM's need to be protected from each other or are
> they all inside a safe controlled network.
No, the environment is quite controlled.
What need to be achieved is that IF someone steal the image
for one or
> >>> Does some one have problems related to KVM with
> >>> kernel-2.6.32-754.3.5.el6.x86_64 ??
> >>
> >> Yes, the exact same thing happened here, and I suspect it is related to
> >> older cpus that don't get any Spectre/Meltdown updates.
> >
> >
> > Thanks for the feedback. I' was assuming that
Am 30.08.2018 um 06:37 schrieb Simon Matter :
>
>> Since the update from kernel-2.6.32-754.2.1.el6.x86_64
>> to kernel-2.6.32-754.3.5.el6.x86_64 I can not boot my
>> KVM guests anymore!? The workstation panics immediately!
>>
>> I would not have expected this behavior now (last phase of OS).
>>
>
> Am 30.08.2018 um 10:54 schrieb isdtor :
>
>>
>> Leon Fauster via CentOS writes:
>>> Since the update from kernel-2.6.32-754.2.1.el6.x86_64
>>> to kernel-2.6.32-754.3.5.el6.x86_64 I can not boot my
>>> KVM guests anymore!? The workstation panics immediately!
>>>
>>> I would not have expected
Am 30.08.2018 um 10:54 schrieb isdtor :
>
> Leon Fauster via CentOS writes:
>> Since the update from kernel-2.6.32-754.2.1.el6.x86_64
>> to kernel-2.6.32-754.3.5.el6.x86_64 I can not boot my
>> KVM guests anymore!? The workstation panics immediately!
>>
>> I would not have expected this
Leon Fauster via CentOS writes:
> Since the update from kernel-2.6.32-754.2.1.el6.x86_64
> to kernel-2.6.32-754.3.5.el6.x86_64 I can not boot my
> KVM guests anymore!? The workstation panics immediately!
>
> I would not have expected this behavior now (last phase of OS).
> It was very robust
On 30.08.2018 03:11, Johnny Hughes wrote:
> On 08/29/2018 05:17 PM, Ian Mortimer wrote:
>> On Wed, 2018-08-29 at 19:20 +0200, Ulf Volmer wrote:
>>
>>> i'm running bind on an up to date CentOS 6.10 and missing the bind
>>> update from the announcement above.
>>
>> I looked for them yesterday on AU
Hi Gordon,
On Wed, 29 Aug 2018 17:59:58 -0700 Gordon Messmer
wrote:
> On 08/29/2018 09:22 AM, wwp wrote:
> > On Wed, 29 Aug 2018 08:27:06 -0700 Gordon Messmer om> wrote:
> >> On 08/28/2018 11:33 PM, wwp wrote:
> >>>- it doesn't expand *foo whereas there are *foo-named files in curre
Hello Mark,
On Wed, 29 Aug 2018 15:20:45 -0700 (PDT) Mark Milhollan
wrote:
> On Wed, 29 Aug 2018, wwp wrote:
>
> >while bash completion was working great to me in CentOS6, since I'm
> >using C7 I spend my day stuck on completion not working the way it
> >should.
>
> Since you don't want
When we consolidated all CentOS Distro builders in a new centralized
setup, covering all arches (so basically x86_64, i386, ppc64le, ppc64,
aarch64 and armhfp those days), we wanted also to add redundancy where
it was possible to.
The interesting "SecureBoot" corner case came on the table and we
21 matches
Mail list logo
