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

FAH service Startup on Linux #81

Closed
Hou5e opened this issue Jan 5, 2023 · 0 comments · Fixed by #82
Closed

FAH service Startup on Linux #81

Hou5e opened this issue Jan 5, 2023 · 0 comments · Fixed by #82

Comments

@Hou5e
Copy link
Contributor

Hou5e commented Jan 5, 2023

When you install FAH on Linux, it auto-runs the service, but on a reboot it doesn't. Is the intended behavior to not auto-run on startup? (Linux Mint 21.1 & 19, for FAH v8.1.5 to v8.1.7 didn't auto-start on a reboot)

This is more of a documentation and clarification request for Linux:
There isn't much documentation on how the service should be run, if you do ever reboot Linux.
From this: https://github.com/FoldingAtHome/fah-client-bastet/blob/master/install/lin/fah-client.service
It looks like we should be using:

sudo systemctl start fah-client
sudo systemctl stop fah-client
sudo systemctl restart fah-client

systemctl status --no-pager fah-client

Being run as a service, the data is located at: /var/lib/fah-client and logs go to: /var/log/fah-client/

It has been nice to not need to use 'sudo', and just run 'fah-client' from the home directory. That has worked well for alpha testing.
For documentation; state that fah-client will make the data and log folders in the working directory where it is run from, if it's not being run as a service.

Can that type of info be added and documented on the project README.md pages and in what you see at the end of the command line on an install sudo dpkg -i ./fah-client_8.1.7_amd64.deb?

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

Successfully merging a pull request may close this issue.

1 participant