Without BOINC

IronBits:

The graphics run as a seperate thread which simply does nothing as long as you don't chose to show them by opening the window or running the screensaver. On Linux the graphics code isn't even loaded when it can't be run (due to lack of libs etc) and silently dies when it doesn't get a connection to an X server without affecting the "worker" thread (science code).

Current Linux and Mac clients are command line clients only. The command line client is also part of the Windows bundle. Install BOINC on one (frontend) machine, attach it to the projects you want to, then zip up the client "boinc_cli.exe" and the "account_(project_url).xml" files, distribute this zip to the farm and start the clients remotely. No graphical interface is needed. The messages are written to files stderr.txt and stdout.txt, so these can also be monitored remotely.

There is no single config file, but you can assign parts of the farm to different projects by chosing which account files are in the bundle and end up in the directory where you run the client. Look into the account file once you created one by attaching to a project - the structure is simple enough so you can clone and modify them yourself for the projects you want to run.

BM