Something unclear about the explanation: systemd-inhibit is not running `sh & disown`, it's running `sh` and `& disown` applies to the systemd-inhibit command.

Something unclear about the explanation: systemd-inhibit is not running `sh & disown`, it's running `sh` and `& disown` applies to the systemd-inhibit command. If you actually daemonized the inner command, systemd-inhibit would release the lock immediately. Cool trick though! I didn't know about systemd-inhibit.