[systemd-devel] systemd-inhibit don't work
Lennart Poettering
lennart at poettering.net
Mon Aug 10 13:37:15 UTC 2020
On Mo, 10.08.20 15:05, Reindl Harald (h.reindl at thelounge.net) wrote:
> well, i would expect that the reboot in the scond ssh-session is
> refused.......
>
> [root at master:~]$ /usr/bin/systemd-inhibit --what=shutdown --who=root
> --why="Backup in progress" --mode=block sleep 600
>
> [root at 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 at master:~]$ Connection to master.thelounge.net closed by remote host.
> Connection to master.thelounge.net closed.
> [harry at 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
More information about the systemd-devel
mailing list