On 4/14/21 2:22 AM, Simon Matter wrote:
On 4/13/21 11:36 PM, Chris Schanzle via CentOS wrote:
> On 4/13/21 5:00 PM, Frank Cox wrote:
>> On Tue, 13 Apr 2021 22:29:26 +0200
>> Simon Matter wrote:
>>
>>> You could try running strace on the hanging process so see what it's
This is an automated email from the git hooks/post-receive script.
rbowen pushed a change to branch master
in repository centos/centos.org.
from cf58c01 Regenerate meeting ics file
add 9ea6b6f Update instructions about subscribe vs import
No new revisions were added by this update.
On Apr 14, 2021, at 12:18 PM, mark mailto:m.r...@5-cent.us>>
wrote:
I'm reading a story linked to from slashdot, and I see FreeBSD is vulnerable.
Has anyone looked at CentOS?
Someone surely has. Figure out what CVEs are involved (e.g.
https://threatpost.com/namewreck-bugs-businesses/165385/),
I'm reading a story linked to from slashdot, and I see FreeBSD is
vulnerable. Has anyone looked at CentOS?
mark
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
This is an automated email from the git hooks/post-receive script.
rbowen pushed a change to branch master
in repository centos/centos.org.
from ed0f312 Apostrophes
add cf58c01 Regenerate meeting ics file
No new revisions were added by this update.
Summary of changes:
On 4/14/21 10:17 AM, Johnny Hughes wrote:
On 4/12/21 9:56 AM, Valeri Galtsev wrote:
On 4/12/21 8:34 AM, Johnny Hughes wrote:
On 4/11/21 11:32 AM, Kenneth Porter wrote:
I'm yum updating some CentOS 7 systems today and got this error. Two
systems (so far) seem to have rebooted fine. Should
On 4/12/21 9:56 AM, Valeri Galtsev wrote:
>
>
> On 4/12/21 8:34 AM, Johnny Hughes wrote:
>> On 4/11/21 11:32 AM, Kenneth Porter wrote:
>>> I'm yum updating some CentOS 7 systems today and got this error. Two
>>> systems (so far) seem to have rebooted fine. Should I worry?
>>>
>>> error: file
On Wed, 14 Apr 2021, Leon Fauster via CentOS wrote:
On 14.04.21 06:40, Frank Cox wrote:
This doesn't work:
Host *
ForwardX11 yes
host jeff
ForwardX11 no
IMHO - first win. It should be
Host jeff
ForwardX11 no
Host *
ForwardX11 yes
I think that's right. My ssh config has what amounts to
CentOS Errata and Security Advisory 2021:0742 Important
Upstream details at : https://access.redhat.com/errata/RHSA-2021:0742
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
Hello
As I said a couple of weeks ago in response to Niki I have been using ProxMox
almost from the beginning ;).
No "enterprise" version. And backup is one of the reasons for that. NFS on NAS
as a backup target is really nice, even one time quicker than backup to local
storage (NAS with
Hi everyone.
I decided to go container with Centos Stream, but I keep having
errors about "unknow capability: CAP_PERFMON". I tried minikube, as
well as standard podman and toolbox container creation:
$ toolbox create --distro fedora --release 34 --container test3
$ toolbox create --distro rhel
On 14.04.21 06:40, Frank Cox wrote:
This doesn't work:
Host *
ForwardX11 yes
host jeff
ForwardX11 no
IMHO - first win. It should be
Host jeff
ForwardX11 no
Host *
ForwardX11 yes
--
Leon
___
CentOS mailing list
CentOS@centos.org
PS: Yes, it finally works, I just saw it in the log file :)
On 4/14/21 9:00 AM, hw wrote:
On 2/27/21 3:40 AM, Jonathan Billings wrote:
On Feb 26, 2021, at 17:16, hw wrote:
Ejabberd is supposed to expire files when they are older than
desired, and selinux prevents it. How can I solve this
On 3/28/21 7:36 PM, Frank Cox wrote:
On Sun, 28 Mar 2021 13:14:16 -0400
Matthew Miller wrote:
Is this a home network or a business one?
It's a really basic setup "routers from Staples" (dlink and tplink brands I
think) plugged into the ISP's modems.
You're right that you generally can't
On 2/27/21 3:40 AM, Jonathan Billings wrote:
On Feb 26, 2021, at 17:16, hw wrote:
Ejabberd is supposed to expire files when they are older than desired, and
selinux prevents it. How can I solve this problem other than by disabling
selinux or by deleting the files manually?
It’s possible
>>> On 4/13/21 11:36 PM, Chris Schanzle via CentOS wrote:
On 4/13/21 5:00 PM, Frank Cox wrote:
> On Tue, 13 Apr 2021 22:29:26 +0200
> Simon Matter wrote:
>
>> You could try running strace on the hanging process so see what it's
>> doing.
> [frankcox@mutt temp]$ rsync
>> On 4/13/21 11:36 PM, Chris Schanzle via CentOS wrote:
>>> On 4/13/21 5:00 PM, Frank Cox wrote:
On Tue, 13 Apr 2021 22:29:26 +0200
Simon Matter wrote:
> You could try running strace on the hanging process so see what it's
> doing.
[frankcox@mutt temp]$ rsync -avv
> On 4/13/21 11:36 PM, Chris Schanzle via CentOS wrote:
>> On 4/13/21 5:00 PM, Frank Cox wrote:
>>> On Tue, 13 Apr 2021 22:29:26 +0200
>>> Simon Matter wrote:
>>>
You could try running strace on the hanging process so see what it's
doing.
>>> [frankcox@mutt temp]$ rsync -avv ../temp/
18 matches
Mail list logo
