polkitd on CentOS 7.5

manoj.linux · 10-13-2018, 08:12 AM

Hi,

Please suggest how to disable polkitd on CentOS 7.5?

also would like to know disablng polkit will create issues?

it is taking high CPU utilization.

jsbjsb001 · 10-13-2018, 08:28 AM

Quote:

Originally Posted by manoj.linux

Hi,

Please suggest how to disable polkitd on CentOS 7.5?

Have you done any research about that? It doesn't sound like a good idea to me, sorry.

Quote:

also would like to know disablng polkit will create issues?

Highly likely, yes, it would. Probably some very serious issues too.

Quote:

it is taking high CPU utilization.

Have you tried to find out why? It maybe a bug in either polkitd itself or something else.

I think you need to provide more information.

ondoho · 10-14-2018, 07:14 AM

let's look at it like this:
on my system, polkitd is owned by polkit.
it is a hard requirement only for gconf and udisks2 - both packages i could live without - again, on my system.
it is optional for systemd: "allow administration as unprivileged user"

polkitd is currently not running on my system.

the command

Code:

systemctl --all|grep -iE 'polkit|policy'

does not return anything; so there's no polkitd service.

yes, you should find out why it takes so much cpu.

jsbjsb001 · 10-14-2018, 01:31 PM

I just disabled polkitd in a VM and for those of us who do actually use CentOS... you really don't want to disable it if your system has a GUI, and I'll tell you why; because you won't even get to any graphical login screen. Have a look at the screenshot below...

TB0ne · 10-14-2018, 02:47 PM

Quote:

Originally Posted by manoj.linux

Hi,
Please suggest how to disable polkitd on CentOS 7.5?

also would like to know disablng polkit will create issues? it is taking high CPU utilization.

You should check some of your *MANY* other threads about high CPU/memory usage, and perform some basic troubleshooting. Did you do any research?

This is a known bug, and a patch is being worked on. There is a workaround you can find on the CentOS forums, and on the bug tracker. And you can find both with a simple Google search.

After eleven years, you should know to do basic research first.

MarcosRocha · 09-27-2019, 08:06 AM

In my case it was Docker changing ownership of entire directory. After stopping the container, which was running just a test, the files turned to my ownership automagically.