boinc/doc/client_files.html

54 lines
1.9 KiB
HTML

<title>Core client: file structure</title>
<body bgcolor=ffffff>
<h2>Core client: file structure</h2>
<p>
The core client runs in a <b>BOINC home directory</b>.
It creates and uses the following files and directories within the
home directory:
<ul>
<li>
<b>prefs.xml</b>:
The user's latest preferences; see below.
<li>
<b>client_state.xml</b>: a description of the files,
application, workunits and results present on this client.
<li>
Each project has a <b>project subdirectory</b> whose name is an encoded
version of the project's master URL.
This subdirectory contains all files (inputs,
outputs, executables) related to the project.
<li>
<b>slots</b>: this directory contains one subdirectory for each
CPU "slot" (normally there are as many slots as the host has CPUs).
The subdirectories are named 0, 1, ... N-1.
</ul>
<p>
Each result executes in particular slot directory.
The core client creates "soft link" files in the slot directory,
linking to the corresponding files in the project directory.
<h3>Format of prefs.xml</h3>
<p>
This format of prefs.xml is as follows:
<pre>
&lt;preferences>
&lt;prefs_mod_time>1030128387&lt;/prefs_mod_time>
&lt;from_project>http://www.myproject.com/&lt;/from_project>
&lt;from_scheduler>http://server3.myproject.com/cgi-bin/scheduler_cgi&lt;/from_scheduler>
&lt;mod_time>2&lt;/mod_time>
&lt;high_water_days>2&lt;/high_water_days>
&lt;low_water_days>1&lt;/low_water_days>
&lt;project>
&lt;master_url>http://www.myproject.com/&lt;/master_url>
&lt;authenticator>3f7b90793a0175ad0bda68684e8bd136&lt;/authenticator>
&lt;resource_share>1&lt;/resource_share>
&lt;/project>
&lt;project>
&lt;master_url>http://www.project2.com/&lt;/master_url>
&lt;authenticator>3f7b90793a0175ad0bda68684e8bd136&lt;/authenticator>
&lt;resource_share>1&lt;/resource_share>
&lt;/project>
&lt;/preferences>
</pre>