From ArchWiki
Revision as of 16:58, 2 July 2013 by Tm258 (Talk | contribs) (Fixed reference to FAHControl AUR package)

Jump to: navigation, search

From the AUR package page: "Folding@home is a distributed computing project which studies protein folding, misfolding, aggregation, and related diseases." For more information, see [1].


Install foldingathomeAUR from the Arch User Repository.


Run /opt/fah/FAHClient --configure as root to generate a configuration file at /opt/fah/config.xml. (the Arch Linux team number is 45032) Alternately, you can write opt/fah/config.xml by hand and use /opt/fah/sample-config.xml as a reference. With a config file in place, you can start the daemon, check it's status, and make the daemon automatically start at boot time:

# systemctl start foldingathome
$ systemctl status foldingathome
# systemctl enable foldingathome

The graphical way

You can manage the daemon by opening a web browser and heading to http://localhost:7396/. Alternately, you can install fahcontrolAUR and use the FAHControl program.

The daemon can also be controlled remotely. Instructions for doing so are listed in /opt/fah/sample-config.xml. Remember to open firewall ports if necessary.

The terminal way

To see the current progress of foldingathome, simply tail /opt/fah/log.txt.

The behaviour of foldingathome can be customized by editing /opt/fah/config.xml. Some options that can be specified:

  • bigpackets, defines whether you will accept memory intensive work loads. If you have no problem with Folding@home using up more of your RAM, then set this to big. Other settings are normal and small.
  • passkey, to uniquely identify you. Though not needed, it provides some measure of security. For details, see [2]
<passkey v='passkey'/>
  • Slots for CPU or GPU
<slot id='0' type='CPU'/>

Multi-Core CPUs and Folding@home

As of version 7.x, multi-core CPUs no longer require any special configuration. If you are using version 6.x, read on.

A Quick Note On Hyperthreading

If you have a single-core hyperthreading CPU, you may be tempted to follow the multi-core instructions. It is highly recommenced that you do not do this as the Folding@home team prefers fewer results quickly, than more results slowly. There is also a time-limit on work-units, so if it runs slower, your work-units may not be returned in time, and so distributed to another user. If you have one core, run one folding process.

Tango-inaccurate.pngThe factual accuracy of this article or section is disputed.Tango-inaccurate.png

Reason: "Hyperthreading is usually enabled in the BIOS by default, and we recommend that it stays enabled, as the SMP cores can use it to process Work Units faster." [3] (Discuss in Talk:Folding@home#)

Multiple Folding@home Installs

Multiple installations of FAH on a single machine are useless, as in v7, you can use slots for every workload. The software is uniform now for gpu and cpu.

Monitoring Work-Unit Progress

There are several ways of monitoring the progress of your FAH client/s, both on the command line and by GUI.

The FAHControl software distributed by folding at home provides you with efficient means to control remote hosts. Just add another client with the corresponding button "Add" and enter the name, ip address, port and password (if you set one) and hit save. The software should now try to establish a connection to the remote host and show you the progress in a seperate client tab.

In AUR there is silent blades fahmon, which provides a GUI with the ability to watch multiple clients and get info on the work-unit itself. Fahmon has a dedicated site at

On the CLI, you can add a command to your .bashrc , .zshrc or .whateverrc :

fahstat() {
	echo `date`
	cat /opt/fah/FAH_USER/unitinfo.txt   #(replacing FAH_USER first)

Or for multiple clients :

fahstat() {
        echo `date`
        echo "Core 1:";cat /opt/fah/FAH_USER/unitinfo.txt      #(replace FAH_USER first)
        echo "Core 2:";cat /opt/fah2/FAH_USER/unitinfo.txt     #(replace FAH_USER first)

Also, replacing cat with tail -n1 will give just the percentage of work unit complete.

On foldingathome-smp 6.43, the unitinfo.txt file is not placed inside the user folder. The correct directory would be /opt/fah-smp/unitinfo.txt.

External Resources