- cross-posted to:
- linux_memes@programming.dev
- cross-posted to:
- linux_memes@programming.dev
cross-posted from: https://swg-empire.de/post/3428368
Though you still have to suspend by yourself when you’re done.
cross-posted from: https://swg-empire.de/post/3428368
Though you still have to suspend by yourself when you’re done.
Though you still have to suspend by yourself when you’re done.
Does
ExecPost=systemctl suspend
work ?
Probably.
But what if the timer triggered during normal operation? Then your computer would suddenly suspend on its own and you wouldn’t know why.
I’ve already made a feature request to only run when the system is suspended.
Until then I’ll look at when the system woke up and if that was less than a minute ago turn off the display and suspend after everything is done.
Doing God’s work …
Can’t you just suspend with another timer that calls
Unit=suspend.target
?Yes, do that a minute after everything else started but run the services themselves with
systemd-inhibit
(another nice thing I didn’t know exists) so that it only goes back to sleep when the last service is done.