Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#65887 - [foldingathome] config.xml not readable

Attached to Project: Community Packages
Opened by Jonathan Kotta (jpkotta) - Thursday, 19 March 2020, 02:50 GMT
Last edited by Maxime Gauduin (Alucryd) - Saturday, 18 April 2020, 05:23 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Maxime Gauduin (Alucryd)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

FAH expects to write to the config.xml. It spams the logs about once per minute about not being able to write it. I'm not sure if there are adverse effects; it seems to run OK for the first several minutes at least. It tries to write "slots" to config.xml.

I recommend a file in /etc with environment variables, e.g.

# /etc/foldingathome/defaults.env
USER=
TEAM=
SMP=true
GPU=false
EXTRA_ARGS=

and using those in the systemd unit like:

EnvironmentFile=/etc/foldingathome/defaults.env
ExecStart=/usr/bin/FAHClient --user=$USER --team=$TEAM --smp=$SMP --gpu=$GPU $EXTRA_ARGS

The default env file can be like the example: blank user and team are OK, but smp and gpu need to be bools.

FWIW, I made the foldingathome-noroot AUR package. I put a script in there to run `FAHClient --configure` to generate the config.xml, because it seemed like FAH assumed the config.xml was generated that way.
This task depends upon

Closed by  Maxime Gauduin (Alucryd)
Saturday, 18 April 2020, 05:23 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed on AUR, while we get permission.
Comment by Maxime Gauduin (Alucryd) - Thursday, 19 March 2020, 13:51 GMT
Oh, thanks for the heads up. Only watched the logs at start and this didn't come up. I'd rather leave the whole config accessible in its original format (and have it backed up), so I found a compromise. I'm keeping the xml in /etc/foldingathome/ and just copy it in /var/lib/fah in an ExecPreStart stanza, that way fah can write to the copy, and any change to the etc config will be taken into account upon a restart of the service.

Loading...