If not given, exclude all GPUs of the given type. specifies the number of the GPU to exclude (0.63). Don't use the given GPU for the given project. Requires a client restart, but does not cancel already downloaded jobs. 0|1 If set, exempt non-CPU-intensive tasks from suspension in most cases. This flag also suppresses a periodic fetch of a project list from. If this flag is set, this behavior is suppressed. 0|1 To determine if a physical network connection exists, the client occasionally contacts a highly-available web site (). Use it if you need to modify files locally for some reason. If this flag is set, this check is skipped. 0|1 Normally, the size of application and input files are compared with the project-supplied values after the files are downloaded, and just before starting an application. 0|1 If enabled, the client won't attach to new projects. NAME use the given name to identify this computer on project web sites. The coprocessor description is passed in scheduler RPC requests. Or so projects can offer app versions that use the coprocessor, with an appropriate plan class specification. In which case the name given in must match that in the element in app_info.xml. You can use this in combination with the Anonymous platform mechanism, If is specified, the coprocessor is not treated as a GPU e.g. 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.
Boinc config file 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.
0 kommentar(er)
