~whynothugo/systemd-lock-handler

Wait for PrepareForSleep(false) before re-inhibiting
Automatically restart service on failure
Check error of releasing lock
readme: add some useful links
Fix freeze when starting a unit
Fix bogus formatting sytax
Make the aliasing explicit

Some go tools get confused otherwise.
b4d0ee51 — Hugo Osvaldo Barrera 2 years ago
Update README example to be safer

Only unlocks the session if swaylock exits cleanly
Block until targets are reached

And expand docs on how to make sure the locker is ready before the
target is reached.
Inhibit sleeping to ensure we have time to react

This is still imperfect; see linked article for additional upcoming
changes in v3.0.0.
cf57f51c — Hugo Osvaldo Barrera 2 years ago
Add builds badge to README
6656b23f — Hugo Osvaldo Barrera 2 years ago
Run builds on CI
2c61db38 — Hugo Osvaldo Barrera 2 years ago v2.3.0
Fix lock services not stopping after waking up
b57596ac — Hugo Osvaldo Barrera 2 years ago
Run in session.slice

From systemd.special(7):

> session.slice
>   All essential services and applications required for the session should use
>   this slice. These are services that either cannot be restarted easily or where
>   latency issues may affect the interactivity of the system and applications.
>   This includes the display server, screen readers and other services such as
>   DBus or XDG portals. Such services should be configured to be part of this
>   slice by adding Slice=session.slice to their unit files.
4920bb3f — Hugo Osvaldo Barrera 2 years ago
Include a changelog
a0b3cec8 — Hugo Osvaldo Barrera 2 years ago
Improve the README
Next