beta.foldingathome.org - settings & capabilities with 8.x #249
Replies: 8 comments 2 replies
-
I believe issue 1 has been designed by request from us. For starters GPUs, especially in Linux are problematic, and even in Windows if user unknown to them, installs fahclient with MS pre-installed GPU driver, which has no real functionality except to display desktop, automatic GPU enablement and start will waste a lot of WUs before user catches on it. |
Beta Was this translation helpful? Give feedback.
-
It may not matter for these issues, but for alpha clients, you should use |
Beta Was this translation helpful? Give feedback.
-
Your issues would be solved by using persistent fah client data directories that are uniquely used when spinning up a container. It is important that folding finishes and pauses before a container exits, because the v8 client will dump current work if it detects a machine id change. |
Beta Was this translation helpful? Give feedback.
-
See also #216 |
Beta Was this translation helpful? Give feedback.
-
To send commands by script after a container v8 client starts, this may be helpful: See also #119 |
Beta Was this translation helpful? Give feedback.
-
I'll clarify my hopes and intentions. I do not want to change any default out of the box behavior - I completely understand where you're coming from with the perspective of the new or average F@H user. I am the exception, not the norm. I'm seeking what is, may be, or will be possible. I don't think the original Q's were addressed but just know that for areas that aren't the default - can it instead be configured via the config.xml or the C&C portal via a future 'global setting'. Today with 7.x - (with drivers, packages, and a pre-made config.xml automatically loaded on system first boot) - my F@H clients roar away without any manual intervention - it's what has allowed me to be in the top 100. |
Beta Was this translation helpful? Give feedback.
-
Normally, your config.xml will only need account-token to use all the global account settings and be controllable by remote Web Control. See #214 |
Beta Was this translation helpful? Give feedback.
-
Do you use the v7 exit-when-done option? |
Beta Was this translation helpful? Give feedback.
-
Currently on latest alpha 8.3.17
headless builds - in my scenario the workers are ephemeral - they will spin up brand new each time and are deleted automatically when there's resource exhaustion in the hosting environment.
When adding a worker, I noticed the following:
In 7.x these were set as part of the config.xml
Questions:
Beta Was this translation helpful? Give feedback.
All reactions