Should work in Condor version: 7.2 -When Condor is not busy running jobs from users, you may want it to run some other backfill task. Condor provides special support for backfilling with BOINC. However, the built-in support assumes that BOINC can decide for itself how many tasks to run in order to fill the idle cpus on a multi-cpu/core machine. At this time (BOINC 6.4), there is no such capability in BOINC. Therefore, the built-in support for BOINC is only really capable of backfilling a single slot. (If you set it up, Condor may show multiple slots in the backfill state, but in fact only a single instance of BOINC will be running and it will be running a configurable but constant number of work units in parallel--typically just one.) +When Condor is not busy running jobs from users, you may want it to run some other backfill task. Condor provides special support for backfilling with BOINC. However, the built-in support assumes that BOINC can decide for itself how many tasks to run in order to fill the idle cpus on a multi-cpu/core machine. At this time (BOINC 6.4), there is no such capability in BOINC. Therefore, the built-in support for BOINC is only really capable of backfilling a single slot. (If you set it up, Condor may show multiple slots in the backfill state, but in fact only a single instance of BOINC will be running and it will be running a statically configured number of work units in parallel--typically just one.) To get around that problem, there is a different way to configure Condor to run BOINC backfill (or any other type of backfill task). It uses the startd's fetch-work hook to run one instance of the backfill task per idle Condor slot. Here is an example configuration:
