feat: boinc config files examples

This commit is contained in:
Michele Cereda
2023-05-29 01:16:54 +02:00
parent 5b8cfdbc68
commit 0f0cb94fcf
5 changed files with 119 additions and 0 deletions

View File

@@ -0,0 +1,21 @@
<!--
${BOINC_DATA_DIR}/projects/${PROJECT}/app_config.xml
Configurtion file for specific applications or app versions.
See https://boinc.berkeley.edu/wiki/Client_configuration#Project-level_configuration
for a complete list of all the available options.
-->
<app_config>
<project_max_concurrent>
<!-- Limit the number of running jobs for this project. -->
3
</project_max_concurrent>
<report_results_immediately>
<!--
Report jobs to the project server as soon as they are finished.
Satisfies the inbuilt 60 second delay from the completion of the
result's upload.
-->
1
</report_results_immediately>
</app_config>

View File

@@ -0,0 +1,65 @@
<!--
${BOINC_DATA_DIR}/cc_config.xml
Configurtion file for the BOINC core client.
See https://boinc.berkeley.edu/wiki/Client_configuration#Client_configuration
for a complete list of all the available options.
-->
<cc_config>
<options>
<!-- Avoid storing more than the minimum required data on disk. -->
<abort_jobs_on_exit>
<!-- Abort jobs and update projects when the client exits. -->
1
</abort_jobs_on_exit>
<fetch_minimal_work>
<!-- Fetch only one job per device. -->
1
</fetch_minimal_work>
<report_results_immediately>
<!--
Report jobs to the project server as soon as they are finished.
Satisfies the inbuilt 60 second delay from the completion of the
result's upload.
-->
1
</report_results_immediately>
<!--
Act as if the host had N CPUs.
Zero means to use the actual number of CPUs.
Intented to simulate more CPUs than effectively available. Use the
computing preferences to limit CPU usage instead.
-->
<ncpus>4</ncpus>
<!-- Don't accept jobs for specific devices. -->
<dont_use_vbox>1</dont_use_vbox>
<!--
0 is the first GPU for the vendor.
1 is the second, and so on.
-->
<ignore_intel_dev>0</ignore_intel_dev>
<ignore_nvidia_dev>0</ignore_nvidia_dev>
<!--
Allow GUI RPCs from *any* remote host.
See https://boinc.berkeley.edu/wiki/Controlling_BOINC_remotely.
-->
<allow_remote_gui_rpc>1</allow_remote_gui_rpc>
</options>
<log_flags>
<!-- Already on by default. -->
<task>1</task>
<file_xfer>1</file_xfer>
<sched_ops>1</sched_ops>
</log_flags>
</cc_config>

View File

@@ -0,0 +1,16 @@
<!--
${BOINC_DATA_DIR}/global_prefs_override.xml
Configurtion file for the BOINC core client that can be used to override global
preferences locally.
See http://boinc.berkeley.edu/trac/wiki/PrefsOverride and
https://boinc.berkeley.edu/wiki/Global_prefs_override.xml for a complete list
of all preferences which can be overridden.
-->
<global_preferences>
<cpu_usage_limit>100</cpu_usage_limit>
<max_cpus>1024</max_cpus>
<max_ncpus_pct>90</max_ncpus_pct>
<run_if_user_active>0</run_if_user_active>
<suspend_cpu_usage>40</suspend_cpu_usage>
</global_preferences>

View File

@@ -0,0 +1 @@
yourPasswordHere

View File

@@ -0,0 +1,16 @@
################################################################################
# ${BOINC_DATA_DIR}/remote_hosts.cfg
#
# This file contains a list of hostnames or IP addresses (one per line). Those
# are the remote hosts that are allowed to connect and to control the local
# BOINC core client via GUI RPCs.
# Lines beginning with a # or a ; are treated like comments and will be
# ignored.
################################################################################
#host.example.com
#192.168.0.180
alfredo.lan
magic.local
192.168.1.10