Multi boinc manager update#

is the peak FLOPS (or IOPS for integer processors) per instance. specify a coprocessor, such as an FPGA or a GPU not known to BOINC (i.e. platform_name Specify an alternate platform name, to be included in scheduler requests. 0|1 If 1, allow GUI RPCs from any remote host (see Controlling BOINC remotely). Each must run in a different data directory. 0|1 Allow multiple BOINC clients to run on a single host. Useful on grids where disk gets wiped after each run.

Multi boinc manager update#

(default values will be used for any options not specified):Ġ|1 If 1, abort jobs and update projects when client exits. The section contains settings that control the behavior of BOINC To create or edit the file, use a text editor such as Notepad,Īnd save it in your BOINC Data directory or project directory. If the file is absent, the default configuration is used. The configuration is read from: cc_config.xml, nvc_config.xml, and (for each project) app_config.xml. When using the example, delete the square brackets. Note: square brackets in examples indicate optional parts. Some parameters can be controlled using different mechanisms

Environment variables (mainly for Unix).

Command-line options (mainly for Unix).There are three configuration mechanisms: They are also written to the file stdoutdae.txt (Windows) or to standard output (Unix). These messages appear in the Event Log of the BOINC Manager The BOINC client can be configured to control its behaviorĪnd to produce more detailed log messages.