gilles/asusctl
1
0
Fork 0
mirror of https://gitlab.com/asus-linux/asusctl.git synced 2026-02-06 00:15:04 +01:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #16 from shoenig/daemon-reload

Browse Source 
Add note about daemon-reload in README
This commit is contained in:
Luke Jones
2020-06-10 16:30:31 +12:00
committed by GitHub
parent d53cef8268 182ea89417
commit d0fe8488bd
1 changed files with 7 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@@ -72,6 +72,12 @@ $ sudo systemctl start rog-core.service
$ sudo systemctl enable rog-core.service $ sudo systemctl enable rog-core.service
``` ```
If you are upgrading from a previous installed version, you will also need to reload service files.
```
$ sudo systemctl daemon-reload
```
You may also need to activate the service for debian install. If running Pop!_OS, I suggest disabling `system76-power` You may also need to activate the service for debian install. If running Pop!_OS, I suggest disabling `system76-power`
gnome-shell extension, or at least limiting use of the power-management parts as `rog-core` lets you set the same things gnome-shell extension, or at least limiting use of the power-management parts as `rog-core` lets you set the same things
(one or the other will overwrite pstates). I will create a shell extension at some point similar to system76, but using (one or the other will overwrite pstates). I will create a shell extension at some point similar to system76, but using
@@ -105,7 +111,7 @@ You can find the thingimajig [here](https://aur.archlinux.org/packages/rog-core/
## Updating ## Updating
Occasionally I might break things for you by tweaking or changing the config file layout. Usually this will mean you Occasionally I might break things for you by tweaking or changing the config file layout. Usually this will mean you
need to remove `/etc/rog-core.conf' and restart the daemon to create a new one. You *can* back up the old one and copy need to remove `/etc/rog-core.conf` and restart the daemon to create a new one. You *can* back up the old one and copy
settings back over (then restart daemon again). settings back over (then restart daemon again).
## Use ## Use