Re: [CentOS] Updating microcode_ctl froze Centos7

On Mon, 2020-06-15 at 22:25 +0200, Robin Lee wrote: > On Fri, 2020-06-12 at 09:20 +0200, Robin Lee wrote: > > Today when I ran yum update two packages came up microcode_ctl > > and unbound-libs. The updating process went fine until it > > outputted > > > > R

Re: [CentOS] Updating microcode_ctl froze Centos7

On Fri, 2020-06-12 at 09:20 +0200, Robin Lee wrote: > Today when I ran yum update two packages came up microcode_ctl > and unbound-libs. The updating process went fine until it outputted > > Running transaction > Updating : 2:microcode_ctl-2.1-61.6.el7_8.x86_64 > >

Re: [CentOS] Updating microcode_ctl froze Centos7

On Sun, 2020-06-14 at 17:39 +0100, Phil Perry wrote: > yum --enablerepo=\* clean all Thanks, that worked ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Updating microcode_ctl froze Centos7

On Fri, 2020-06-12 at 09:20 +0200, Robin Lee wrote: > Today when I ran yum update two packages came up microcode_ctl > and unbound-libs. The updating process went fine until it outputted > > Running transaction > Updating : 2:microcode_ctl-2.1-61.6.el7_8.x86_64 > >

Re: [CentOS] Updating microcode_ctl froze Centos7

On Fri, 2020-06-12 at 10:24 +0200, Tru Huynh wrote: > On Fri, Jun 12, 2020 at 09:20:34AM +0200, Robin Lee wrote: > > Today when I ran yum update two packages came up microcode_ctl > > and unbound-libs. The updating process went fine until it > > outputted > &g

[CentOS] Updating microcode_ctl froze Centos7

Today when I ran yum update two packages came up microcode_ctl and unbound-libs. The updating process went fine until it outputted Running transaction Updating : 2:microcode_ctl-2.1-61.6.el7_8.x86_64 then it just froze. I could no longer ssh to the machine and the console was just blank. I

Re: [CentOS] Centos7 & Selinux & Tor

On Tue, 2018-10-23 at 14:54 -0400, Daniel Walsh wrote: > Most likely this is tor running as root and trying to access this > file. I'm trying to start tor using 'systemctl start tor' and I haven't touched any systemd file. What I get in the logs when I try to start is polkitd[1097]: Registered

Re: [CentOS] Centos7 & Selinux & Tor

On Sun, 2018-10-14 at 20:13 +0200, Robin Lee wrote: > I've just encountered a problem starting tor. When I do 'systemctl > start tor' it fails and I get selinux errors in the log. There was > suggestion to do full auditing with 'auditctl -w /etc/shadow -p w'. > Which I did

Re: [CentOS] Centos7 & Selinux & Tor

On Sun, 2018-10-14 at 20:13 +0200, Robin Lee wrote: > I've just encountered a problem starting tor. When I do 'systemctl > start tor' it fails and I get selinux errors in the log. I explored this a bit further. I moved away the /var/lib/tor/hidden_service directory. Then I started tor a

[CentOS] Centos7 & Selinux & Tor

I've just encountered a problem starting tor. When I do 'systemctl start tor' it fails and I get selinux errors in the log. There was suggestion to do full auditing with 'auditctl -w /etc/shadow -p w'. Which I did and it gave the following type=PROCTITLE msg=audit(1539540150.692:60570):

Re: [CentOS] An m4 question

On Sat, Sep 17, 2016 at 1:05 AM, wrote: > Does anyone know what, if any, the limits are in m4 on the length of > strings, such as in defines? > > That is, if I were to do > define('LINUX', 'machine1, machine2,...machine120...') > > Is there a limit to how many I could put in

Re: [CentOS] RPM perl requirements woes

On Thu, May 12, 2016 at 11:14 PM, Anand Buddhdev wrote: > Dear CentOS hive mind, > > I'm trying to package up a perl module into an RPM for easy deployment. > I want it to be as self-contained as possible (to avoid version issues > with perl modules in base or EPEL). So in my

Re: [CentOS] How to setup own i686 buildenv for CentOS7

Thanks! Best regards! On Mon, Sep 7, 2015 at 12:12 PM, Peter <pe...@pajamian.dhs.org> wrote: > On 09/07/2015 02:32 PM, Robin Lee wrote: > > Can you re-paste this cfg? The url is outdated. > > I'll paste mine in here for posterity (altered to remove my private > repos

Re: [CentOS] How to setup own i686 buildenv for CentOS7

official and unsupported. RedHat does not > support 32bit in EL7. > > HTH > Lucian > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > > - Original Message - > > From: "Robin Lee" <robinlee.s...@gm

Re: [CentOS] build c7 packages for i686 using mock

Hi, Here's how my epel-7-i386.cfg mock file looks like: http://fpaste.org/164110/19877702/raw/ Do note the 32bit packages are unofficial and unsupported. RedHat does not support 32bit in EL7. HTH Lucian Nux! n...@li.nux.ro 12/30/14 to CentOS On Fri, Jan 30, 2015 at 10:38 AM, Peter

[CentOS] How to setup own i686 buildenv for CentOS7

Hi, all! How to setup own i686 mock for CentOS7? Or, is there any public i686 repo for CentOS7? I found i686 repo available in internal CentOS building environment, from a root.log from a mock build result[1]. [1]

Re: [CentOS] How to setup own i686 buildenv for CentOS7

. HTH Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - From: Robin Lee robinlee.s...@gmail.com To: centos@centos.org Sent: Monday, 29 December, 2014 16:27:33 Subject: [CentOS] How to setup own i686 buildenv for CentOS7 Hi