Fix #217 - Change systemd-service type to forking #224
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update:
Fix #217 - Change systemd-service type to forking
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 (i3/i3lock#109)
as it was the less popular solution.
https://gist.github.com/victorhaggqvist/603125bbc0f61a787d89
Raymo111/i3lock-color#174 (comment)
https://gist.github.com/Raymo111/91ffd256b7aca6a85e8a99d6331d3b7b
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://gist.github.com/victorhaggqvist/603125bbc0f61a787d89
https://www.jvt.me/posts/2019/12/03/lock-before-suspend-systemd/
https://michaelabrahamsen.com/posts/systemd-suspend-i3lock/