On Thu, Apr 1, 2021 at 4:19 PM Davide Cavalca via CentOS-docs <
centos-docs@centos.org> wrote:
> Hi,
>
> I tried adding MichelSalim to the ACL for
> SpecialInterestGroup/Hyperscale, but it fails because "You can't change
> ACLs on this page since you have no admin rights on it!". Could you
>
Hi,
I tried adding MichelSalim to the ACL for
SpecialInterestGroup/Hyperscale, but it fails because "You can't change
ACLs on this page since you have no admin rights on it!". Could you
please add him, or even better give me admin right on the page so I can
maintain the ACL myself? My account is
On Mar 26, 2021, at 7:08 AM, Warren Young wrote:
>
> Is anyone else getting this on dnf upgrade?
>
> [MIRROR] sssd-proxy-2.3.0-9.el8.x86_64.rpm: Interrupted by header callback:
> Server reports Content-Length: 9937 but expected size is: 143980
The short reply size made me think to try a
> All relevant logging is centralised to a server cluster running Graylog.
... and, because I forgot to mention it: Yes, that server cluster has a
"persistent data" device.
Regards,
Peter.
___
CentOS mailing list
CentOS@centos.org
Hi Simon,
> Whenever I read such things I'm wondering, what about things like log
> files? Do you call them OS files or persistent data? How do you back'em up
> then?
I don't.
All relevant logging is centralised to a server cluster running Graylog.
Regards,
Peter.
On 3/29/21 1:28 PM, Matthew Saltzman wrote:
> My CentOS 8 Stream installation is fully current. I did
>
>sudo debuginfo-install libgcc libstdc++
>
> but the response I get is
>
>Could not find debuginfo package for the following installed packages:
>libgcc-8.4.1-1.el8.x86_64,
Hi,
I'm upgrading our request tracker from Centos 7 to 8 and found some
unexpected SELINUX issues with procmail. Even after I create a policy which
allows all denied operations, procmail is still not allowed to run a perl
script (in my case rt-mailgate). I get the following error in the procmail
> Hi Niki,
>
> I'm using a similar approach like Stephen's, but with a kink.
>
> * Kickstart all machines from a couple of ISOs, depending on the
> requirements (the Kickstart process is controlled by Ansible)
> * Machines that have persistent data (which make up about 50% in average)
> have at
Hi Niki,
I'm using a similar approach like Stephen's, but with a kink.
* Kickstart all machines from a couple of ISOs, depending on the requirements
(the Kickstart process is controlled by Ansible)
* Machines that have persistent data (which make up about 50% in average) have
at least two
9 matches
Mail list logo