Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

maybe change default config path? #17

Closed
cj360 opened this issue Apr 26, 2019 · 2 comments
Closed

maybe change default config path? #17

cj360 opened this issue Apr 26, 2019 · 2 comments

Comments

@cj360
Copy link

cj360 commented Apr 26, 2019

This may just be an issue from the aur not this script, so if this should be on the aur's page not here let me know.

In this script's case since the install dir is the default config location, it seems bad that its looking for a config among /usr/bin. On the other hand, it seems weird to ask the person that made the aur package to change the original script. Just a nitpick really not actually a problem if I just cloned the repo.

@nan0s7
Copy link
Owner

nan0s7 commented Apr 29, 2019

Yeah this can't really be helped unless the default path is forced to be somewhere in the users home directory. It does suit that the default config location is the install location because the main script has no sense of what the default values should be.

But of course that is why there's an option to run the script with a config path command line option.

@ReneHollander
Copy link
Contributor

In the new AUR package the config is located in /etc/nfancurve.conf. The provided systemd user unit will use that config.

Just beware, enabling the nfancurve.service does not start it at boot. I am still trying to get it to work, but running systemd --user start nfancurve.service works fine.

@cj360 cj360 closed this as completed Aug 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants