Systemd runsvdir service overhaul #16
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I'll get this merged tomorrow, thanks and sorry for the delay. |
|
This looks like a reasonable fix for #22 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The service is named
runsvdir, notrunsvdir-start. The latter was simply a shell script to run the former. The new systemd service file has been renamed to this service and incorporates the functionality ofrunsvdir-start. Please note, the PATH variable is set via a more canonical method: sbin > bin, and local > usr > /. The PATH that has been set into runsvdir-start was insane.Relevant to Linux, the OOMKiller is effectively disabled for the
runsvdirprocess. This is quite important.