Here's how to contribute your HTCondor pool's spare cycles to Folding@Home. The basic idea is to use HTCondor's "work fetch" mechanism to start the Folding@Home client when you have idle resources. This means you don't have Folding@Home jobs cluttering up your schedulers or in your the accountant, and you don't have to do anything special to preserve your Folding@Home progress. If you wish to run Folding@Home jobs as works submitted to a HTCondor Schedd and tracked by HTCondor's accounting mechanism _this is not the recipe for you_ {subsubsection: Assumptions} *: We assume that you're configuring a Linux execute machine. *: We assume that execute machine already has Folding@Home installed. Many of the ways to install the Folding@Home client on a machine try to configure it to run in the background; you'll want to disable that. *: We assume that =/opt/fah= is a great place to put our Folding@Home bits. {subsubsection: Instructions} 1: Create user named 'backfill' for Folding@Home to run as. 1: Make directories so that Folding@Home can preserve its progress when preempted: create =/opt/fah/slots/slot1=, =/opt/fah/slots/slot2/=, and the like (up to the number of cores on your machine). Make sure that the 'backfill' user can read and write to them (=chown= them appropriately). 1: Create the following files: {file: /opt/fah/fetch_work} #!/bin/bash # extract SlotId from the Machine classad passed on stdin eval `awk '/^SlotID/ {print "export _CONDOR_BACKFILL_SLOTID="$3}'` # build a job classad from a template in the HTcondor config called FAH_JOB condor_config_val -macro '$(FAH_JOB)' {endfile} The following configuration can be changed if you want credit for your contribution. {file: /opt/fah/config.xml} {endfile} 1: If you're using partitionable slots, use {wiki: FoldingAtHomeDynamicSlots this recipe} for your configuration. 1: If you're using static slots, use {wiki: FoldingAtHomeStaticSlots this recipe} for your configuration.