mirror of https://github.com/BOINC/boinc.git
edit
parent
8c6336741c
commit
def43fb005
|
@ -37,7 +37,7 @@ and save it in your [BOINC Data directory](BOINC_Data_directory) or project dire
|
|||
|
||||
### General configuration
|
||||
|
||||
The ```cc_config.xml``` file has the format:
|
||||
The``cc_config.xml` file has the format:
|
||||
```xml
|
||||
<cc_config>
|
||||
<options>
|
||||
|
@ -51,7 +51,7 @@ The ```cc_config.xml``` file has the format:
|
|||
|
||||
#### Options
|
||||
|
||||
The ```<options>``` section contains settings that control the behavior of
|
||||
The `<options>` section contains settings that control the behavior of
|
||||
the BOINC client.
|
||||
Default values will be used for any options not specified.
|
||||
|
||||
|
@ -97,19 +97,19 @@ Specify a coprocessor, such as an FPGA or a GPU not known to BOINC
|
|||
(i.e. not NVIDIA, AMD, or Intel).
|
||||
The elements are:
|
||||
|
||||
```<count>```: the number of coprocessor instances.
|
||||
`<count>`: the number of coprocessor instances.
|
||||
|
||||
```<device_nums>```: their device numbers (default 0, 1, ...).
|
||||
`<device_nums>`: their device numbers (default 0, 1, ...).
|
||||
|
||||
```<peak_flops>```
|
||||
their the peak FLOPS (or IOPS for integer processors) per instance.
|
||||
`<peak_flops>`:
|
||||
the peak FLOPS (or IOPS for integer processors) per instance.
|
||||
|
||||
If ```<non_gpu/>``` is specified, the coprocessor is not treated as a GPU;
|
||||
If `<non_gpu/>` is specified, the coprocessor is not treated as a GPU;
|
||||
e.g. "Suspend GPU" does not affect it.
|
||||
|
||||
You can use this in combination with the [Anonymous platform](Anonymous_platform) mechanism,
|
||||
in which case the name given in ```<type>``` must match that in the
|
||||
```<coproc>``` element in ```app_info.xml```.
|
||||
in which case the name given in `<type>` must match that in the
|
||||
`<coproc>` element in `app_info.xml`.
|
||||
Or projects can offer app versions that use the coprocessor,
|
||||
with an appropriate plan class specification.
|
||||
The coprocessor description is passed in scheduler RPC requests.
|
||||
|
@ -532,7 +532,7 @@ selecting ''Event Log Diagnostic Flags'' from the ''Advanced'' menu or
|
|||
by pressing ''CTRL+Shift+F'' simultaneously on the keyboard in either the Advanced
|
||||
View or the Simple View (''Command+Shift+F'' on a Macintosh.)
|
||||
|
||||
You can enable or disable each type in the <tt><log_flags></tt> section.
|
||||
You can enable or disable each type in the `<log_flags>` section.
|
||||
For example, to see messages about CPU scheduling,
|
||||
edit cc_config.xml so that it contains:
|
||||
```xml
|
||||
|
@ -545,14 +545,13 @@ edit cc_config.xml so that it contains:
|
|||
If you edit the file while BOINC is running,
|
||||
the changes will take effect only if you select the
|
||||
**Advanced / Read config file** menu item.
|
||||
(Note: some changes in the <options> section take effect only when you restart the BOINC client).
|
||||
(Note: some changes in the `<options>` section take effect only when you restart the BOINC client).
|
||||
|
||||
The flags within <tt><log_flags></tt> are used to selectively turn different types of messages on and off
|
||||
(<tt><tag>0</tag></tt> for off, <tt><tag>1</tag></tt> for on).
|
||||
The flags within `<log_flags>` are used to selectively turn different types of messages on and off
|
||||
(`<tag>0</tag>` for off, `<tag>1</tag>` for on).
|
||||
The following messages are enabled by default:
|
||||
|
||||
<dl><dt>
|
||||
|
||||
**\<task>**
|
||||
</dt>
|
||||
<dd>
|
||||
|
@ -903,17 +902,17 @@ The file format:
|
|||
[<report_results_immediately/>]
|
||||
</app_config>
|
||||
```
|
||||
The app name (in ```<name>``` and ```<app_name>``` elements) is case insensitive.
|
||||
The app name (in `<name>` and `<app_name>` elements) is case insensitive.
|
||||
|
||||
|
||||
Each ```<app>``` element specifies parameters for a given application.
|
||||
Each `<app>` element specifies parameters for a given application.
|
||||
Its elements are:
|
||||
|
||||
```xml
|
||||
<name>
|
||||
```
|
||||
short name of the application as found in the corresponding
|
||||
```<name>xxxxx</name>``` element in your client_state.xml file.
|
||||
`<name>xxxxx</name>` element in your client_state.xml file.
|
||||
|
||||
```xml
|
||||
<max_concurrent>
|
||||
|
@ -936,8 +935,8 @@ For example, .5 means that two jobs of this application can run at once on a sin
|
|||
```
|
||||
The number of CPU instances (possibly fractional) used by GPU versions of this app.
|
||||
|
||||
Each ```<app_version>``` element specifies parameters for a given app version;
|
||||
it overrides ```<app>```.
|
||||
Each `<app_version>` element specifies parameters for a given app version;
|
||||
it overrides `<app>`.
|
||||
Its elements are:
|
||||
|
||||
```xml
|
||||
|
@ -974,7 +973,7 @@ A limit on the number of running jobs for this project.
|
|||
```
|
||||
If set, report this project's completed tasks immediately.
|
||||
|
||||
If you remove ```app_config.xml```, or change any of its entries,
|
||||
If you remove `app_config.xml`, or change any of its entries,
|
||||
you must reset the project (or restart the client)
|
||||
in order to restore the proper values.
|
||||
|
||||
|
|
Loading…
Reference in New Issue