Heard from someone on my "team" and decided to look in to starting up again. Poking around I downloaded the latest app. Interesting, it wiped out all the stuff that was in /Applications/Folding@home, and left an uninstall and another link. Opening that was interesting. It seems I can start/stop it from that page. It also somehow shows me the logo of the team I was on years ago. There was a log-in button, but when I put my email and passkey, it barfed. Said login failed with a "DB Login not found." I tried the forgot password but it barfed there with the same message. What do I do about this? Are there any benefits to actually logging in there... and if I try setting up a new account, will it know what am I am connected with? It seems to already know so I assume some pref was there that it connected with.
AND I'd really like to know how this runs without any sign of an app, or any "Login Item" setting?
Welcome back! A lot has changed in the net client. Check out https://foldingathome.org/guides/v8-4-client-guide/, in paticular the parts about creating an account (with user name and passphrase) and the account settings (with the user name and passkey you used in the past).
Ryzen 9800X3D / RTX 4090 / Windows 11
Ryzen 5600X / RTX 3070 Ti / Ubuntu 22.04
Ryzen 5600 / RTX 3060 Ti / Windows 11
You do not need to create an account to fold, but it does provide the ability to log in from any system or browser and monitor and control your folding system(s).
The v8 client will read from a v7 config.xml file at install or startup and use many but not all of its settings for the system. So whatever username, passkey, or team settings will carry over.
Thanks for quick replies... funny, I looked back on my backups and could not find that v7 config.xml file. Chances are the last time I folded was even before the v7. Am I correct that FAHViewer and FAHControl are totally deprecated? As long as somehow it seems to remember which team I am on!
Oh, I still like to know exactly how this is actually running on my machine, like what mechanism.
paulcons wrote: ↑Tue Mar 04, 2025 9:43 pm
Thanks for quick replies... funny, I looked back on my backups and could not find that v7 config.xml file. Chances are the last time I folded was even before the v7. Am I correct that FAHViewer and FAHControl are totally deprecated? As long as somehow it seems to remember which team I am on!
Oh, I still like to know exactly how this is actually running on my machine, like what mechanism.
On macOS, the client runs as a service at boot time via launchd. There is a plist that defines this
/Library/LaunchDaemons/org.foldingathome.client.plist
Though unsupported, earlier versions of v8 did work on the iMac I used to have running for testing on 10.12.6. But its power supply failed a while ago after 10+ years and I haven't taken the time to swap in a replacement I have from a parts iMac.
calxalot wrote: ↑Tue Mar 04, 2025 10:50 pm
On macOS, the client runs as a service at boot time via launchd. There is a plist that defines this
/Library/LaunchDaemons/org.foldingathome.client.plist
Still confused... no such plist but I seem to have a org.foldingathome.fahclient.plist. Created and modified 11/2024. Can't say that I really did anything that month. In there I found a "/Library/Application Support/FAHClient" string. In that folder I don't see anything that I recognize as any kind of executable. I poured through Login Item & Extensions but could find nothing in there related to FAH. Looked at a page for launchd as I'm not intimately knowing that much about it... I looked at all the areas it said stuff was located and could not find anything related to FAH (that I recognized). DID find a lot of very old cruft in those locations, referring to stuff I haven't used in years and would have no interest anymore... someday I'll maybe try and clean some of that out. Still a mystery to me and I think I have above the average how things work in macOS.
Oh, just looked at Activity Monitor. Holy smoke I had no idea how so man y thing are always "running." BUT I could not find anything that saw related to FAH, although there was so much there, I could have missed something,
In Activity Monitor just enter fah as a search string in the upper right. That will show just the processes for F@h, and maybe some other process if it happens to include fah in the process name.
The location for the .plist file given by calxalot was almost correct, he just left "fah" out of the name. You found the correct file. No executable for fah-client in either location, it is installed somewhere else that I would have to look up, been a while since I dug that far down. That location is the reason you have to use the supplied Uninstaller if you wanted to remove the client from your Mac, it is not just a drag to the Trash from the Applications folder.
What is located in the /Library/Application Support/FAHClient folder are the log files - current and saved recent ones, a work folder, and a folder of the folding cores downloaded to process WUs. That last folder will contain the only other executables connected to F@h. As your Mac will only process CPU WUs, there will be a FahCore_a8 and possibly a FahCore_a9. Those are downloaded by the client as needed to process a WU, the client will download a new version if the WU calls for one.
There shouldn't be anything located in Login Items for F@h as best as I recall. There might have been for very early versions of the v7 client and the long out of use v6 client. But at some point early on in the development of the v7 client the approach of running the client in the background basically as a service under an unprivileged account was put in place. It gets started and possibly stopped by launchd based on the instructions and locations specified in the .plist file.
Login not found." I tried the forgot password but it barfed there with the same message. What do I do about this? Are there any benefits to actually logging in there... and if I try setting up a new account, will it know what am I am connected with? It seems to already know so I assume some pref was there that it connected with.