N Maximum number of lines to display in BOINC Manager's Event Log window (default 2000, 0 means no limit). 0|1 If set, run the client in a mode where its CPU, disk, and memory usage has lower priority than other processes. By default, devices in /dev/tty*, /dev*, and /dev/pts/* are checked for activity. path (Unix) Ignore TTY devices starting with 'path' in checking if the system is idle. Example: 0 will ignore the first NVIDIA GPU in the system. N Ignore (don't use) a specific NVIDIA GPU. N Ignore (don't use) a specific Intel GPU. 0|1 Set this flag to use HTTP 1.0 instead of 1.1 (this may be needed with some proxies). bps An HTTP transfer is considered idle if its transfer rate is below this many bits per second. Valid parameters are: basic, digest, gss-negotiate, ntlm (Setting of particular importance for World Community Grid to facilitate SSL/HTTPS communications) seconds Abort HTTP transfers if idle for this many seconds default 300. auth_method When authenticating against a proxy server use a specific authentication method. 0|1 When updating a project, request work even if not highest priority project. 0|1 Fetch one job per device (see -fetch_minimal_work). 0|1 Exit when all tasks finished (see -exit_when_idle). important.exe BOINC will suspend use of GPUs whenever the executable is running. Multiple applications can be specified: place each filename.exe on a separate line. įilename.exe BOINC will suspend computing whenever the executable is running (e.g., a game). If you want to exclude the GPU use for all projects, look at the, and options further down. If you change GPU exclusions, you must restart the BOINC client for these changes to take effect. If specified, only tasks for that app are excluded. the element within the element in client_state.xml). specifies the short name of an application (i.e. is required if your computer has more than one type of GPU otherwise it can be omitted. 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. (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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |