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
This commit is contained in:
Basti 2021-05-28 23:36:46 +02:00 committed by GitHub
parent bbf8840fd8
commit bbe277c0db
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 5 additions and 1 deletions

View file

@ -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! **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 ### Countributing

View file

@ -5,7 +5,7 @@ Before=suspend.target
[Service] [Service]
User=%I User=%I
Type=simple Type=forking
Environment=DISPLAY=:0 Environment=DISPLAY=:0
ExecStart=/usr/local/bin/betterlockscreen --lock ExecStart=/usr/local/bin/betterlockscreen --lock
TimeoutSec=infinity TimeoutSec=infinity