Skip to content
This repository has been archived by the owner on Apr 7, 2021. It is now read-only.

Fix not being able to start service because temperature not yet available #27

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Fix not being able to start service because temperature not yet available #27

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8227461
Fix not being able to start because driver unavailable
May 3, 2020
2aa6e98
Change to restart on failure
Jun 7, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions amdgpu-fancontrol.service
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,9 @@
Description=amdgpu-fancontrol

[Service]
Type=simple
ExecStartPre=/bin/sleep 5
ExecStart=/usr/bin/amdgpu-fancontrol
Restart=on-failure
RestartSec=5

[Install]
WantedBy=multi-user.target
WantedBy=default.target
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this necessary? Setting the restart properties does not require changing the WantedBy property, right? The ArchWiki says default.target is usually a symlink to graphical.target which is different from multi-user.target.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe default.target is a bit more common for these type of services. Happy to change it back if @grmat expresses interest in merging this.