On 4/14/23 22:06, Andre Robatino wrote:
I just tried masking/reinstalling just now and it didn't restart. I experienced
it before with a systemd update so it might require that. But masking is
definitely not 100% effective.
Masking should be 100% effective. It changes files in /etc which sho
If it is still relevant - There is a file /etc/cockpit/disallowed-users which
in my case has one entry: root.
Try to comment it out if you need root access. Not discussing here security
implications of this change.
Leon
___
users mailing list -- users
On F37, masking was the first thing I tried. Then after a systemd update, I
noticed it was running again, even though it was still masked (verified by
"systemctl status systemd-oomd" which showed it both running and masked at the
same time).
___
users
On Sat, Apr 15, 2023 at 1:05 PM Andre Robatino
wrote:
>
> On F37, masking was the first thing I tried. Then after a systemd update, I
> noticed it was running again, even though it was still masked (verified by
> "systemctl status systemd-oomd" which showed it both running and masked at
> the s
I don't know enough about systemd to think that's even a bug - I had assumed it
was normal behavior. In any case the bug that was forcing me to disable the OOM
killer ( https://bugzilla.redhat.com/show_bug.cgi?id=2177722 ) has been fixed
so I'm not disabling it anymore.
_
On Sat, Apr 15, 2023 at 3:48 PM Andre Robatino
wrote:
>
> I don't know enough about systemd to think that's even a bug - I had assumed
> it was normal behavior. In any case the bug that was forcing me to disable
> the OOM killer ( https://bugzilla.redhat.com/show_bug.cgi?id=2177722 ) has
> been
