Folding Forum

/etc/systemd/system/fahclient.service [Unit] Description=Folding@Home V7 Client Documentation=https://folding.stanford.edu/home/the-software/ After=network.target [Service] User=fahclient Group=users WorkingDirectory=/var/lib/fahclient ExecStart=/usr/bin/FAHClient /etc/fahclient/config.xml KillMode=...

calxalot wrote:Is it safe to use
Restart=always
again?

Yes, actually. It now works with Restart=always.

Likely just a permissions problem with the fahclient home folder, or log.txt. It might be that the working directory is not correct. Try adding WorkingDirectory=/var/lib/fahclient to the service. That worked, and folding on the GPU works. mintaka:/etc/systemd/system # systemctl start fahclient.serv...

The latest after I removed restart=always. I suspect that it is trying to store the log.txt where it does not have access. It does not use /var/lib/fahclient/log.txt

If I tried your modified version of the systemd service I am unable to start FAClient. mintaka:/etc/systemd/system # systemctl start fahclient.service mintaka:/etc/systemd/system # systemctl status fahclient.service fahclient.service - Folding@Home V7 Client Loaded: loaded (/etc/systemd/system/fahcl...

Running the following command spawns two instances of FAHClient /usr/bin/FAHClient /etc/fahclient/config.xml --run-as fahclient --pid-file=/var/lib/fahclient/fahclient.pid --daemon sverrem@mintaka:~> ps -aux | grep FAH fahclie+ 2740 0.0 0.0 21097356 6916 ? Ssl 20:10 0:02 /usr/bin/FAHClient /etc/fahc...

I thought the same, but at least run the exact same command that init script does. ExecStart=/usr/bin/FAHClient /etc/fahclient/config.xml --run-as fahclient --pid-file=/var/lib/fahclient/fahclient.pid --daemon I was also thinking about ExecStop that would send finished data before killing the proces...

I created the following systemd service [Unit] Description=Folding@Home V7 Client Documentation=https://folding.stanford.edu/home/the-software/ After=network.target [Service] PIDFile=/var/lib/fahclient/fahclient.pid User=fahclient Group=users ExecStart=/etc/init.d/FAHClient start ExecStop=/etc/init....

Looks like someone already has written a systemd service for FAHClient.
https://gist.github.com/lopezpdvn/81397197ffead57c2e98
However all this does is proxy to the init script /etc/init.d/FAHClient. A better solution would be a pure systemd service.

If OpenSUSE favors systemd services, you might convert to that and share your work. :) That is true, but it can also run init scripts such as /etc/init.d/FAHClient. I believe Fedora also uses systemd now, but I am not so sure about RedHat or CentOS which I believe still uses init. Though the latest...

calxalot wrote:Does OpenSUSE have the start-stop-daemon command?

Does not look like it. It is a utility mostly seen on Debian/Ubuntu. However looks like Fedora does have it.

My modified /etc/init.d/FAHClient OPTS+="$EXTRA_OPTS " OPTS+="--run-as $USER " OPTS+="--pid " OPTS+="--pid-file=$PID " OPTS+="--service " #OPTS+="--daemon " Considering that --daemon is short for --pid --service --respawn --log='' --fork I ...

Both instances has root as group, fahclient:root

I am able now to run FAClient as a service and have access to the GPU. I had to modify the /etc/inid.d/FAHClient and remove the option --daemon. However, even though it can detect CUDA I still get "Bad platformId size". Seems like the problem is when root is starting the FAHClient service....

As I am having trouble folding on GPU I must start the FAClient manually on the command line. Starting the service as root makes the GPU unavailable.
I have only started one instance, but it seems to go well. I did not use the flag --daemon though.