Fixed systemd unit file to activate after thermald, if it exists. #34
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
|
late but done :) |
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 Before= directive can only be specified in the [Unit] section, as documented in the systemd.unit manpage.
The Before= (and After=) directive(s) only define the ordering of activated units, which is orthogonal to the dependency of units; that's defined through the Wants= and Requires= directives, so I've added the Wants=thermald.service directive to activate thermald.service when asus-fan.service is activated. Without this change, thermald.service does not start when asus-fan.service is activated; it's simply ordered to start before asus-fan.service if it is activated through some other mechanism.