Re: systemd-inhibit don't work

[Lennart Poettering <lennart@xxxxxxxxxxxxxx>]

On Mo, 10.08.20 15:05, Reindl Harald (h.reindl@xxxxxxxxxxxxx) wrote:

> well, i would expect that the reboot in the scond ssh-session is
> refused.......
>
> [root@master:~]$ /usr/bin/systemd-inhibit --what=shutdown --who=root
> --why="Backup in progress" --mode=block sleep 600
>
> [root@master:~]$ /usr/bin/systemd-inhibit; systemctl reboot
> WHO  UID USER PID COMM            WHAT     WHY                MODE
> root 0   root 569 systemd-inhibit shutdown Backup in progress block
>
> 1 inhibitors listed.
> [root@master:~]$ Connection to master.thelounge.net closed by remote host.
> Connection to master.thelounge.net closed.
> [harry@srv-rhsoft:~]$

Root is almighty on UNIX. This also means it has the privilege to
ignore inhibitors, and thta's what you are seeing here.

There is a github issue filed asking for some mechanism to extend
inhibitors so that root can't trivially override it, but so far this
hasn't been implemented.

Lennart

--
Lennart Poettering, Berlin
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel