diff options
| author | Basti <mail@sebastian-sellmeier.de> | 2021-05-28 23:36:46 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-05-28 23:36:46 +0200 |
| commit | bbe277c0db5cd11069770a8d95705bf85b288684 (patch) | |
| tree | e6c74d577b3bbaac73a6b48897b2acb96fc06f6d | |
| parent | bbf8840fd863e9e94805424c45447d2d89f2aa98 (diff) | |
Fix #217 - Change systemd-service type to forking (#224)
Besides user-feedback I've found many resources showing that it is one common way to use forking here.
I've also found the option "--nofork" for i3lock-color but I'm unsure of the side-effects (https://github.com/i3/i3lock/issues/109)
as it was the less popular solution.
https://gist.github.com/victorhaggqvist/603125bbc0f61a787d89
https://github.com/Raymo111/i3lock-color/issues/174#issuecomment-687149213
https://gist.github.com/Raymo111/91ffd256b7aca6a85e8a99d6331d3b7b
| -rw-r--r-- | README.md | 4 | ||||
| -rw-r--r-- | system/betterlockscreen@.service | 2 |
2 files changed, 5 insertions, 1 deletions
@@ -236,6 +236,10 @@ systemctl disable betterlockscreen@$USER **Hint:** The systemd-unit expects betterlockscreen to be installed in "/usr/local/bin", so maybe you want to check or change this! +Resources and more informations: + * https://gist.github.com/Raymo111/91ffd256b7aca6a85e8a99d6331d3b7b + * https://github.com/Raymo111/i3lock-color/issues/174#issuecomment-687149213 + --- ### Countributing diff --git a/system/betterlockscreen@.service b/system/betterlockscreen@.service index b9ad6fb..5bc8505 100644 --- a/system/betterlockscreen@.service +++ b/system/betterlockscreen@.service @@ -5,7 +5,7 @@ Before=suspend.target [Service] User=%I -Type=simple +Type=forking Environment=DISPLAY=:0 ExecStart=/usr/local/bin/betterlockscreen --lock TimeoutSec=infinity |