boinc/doc/client_files.html

52 lines
1.9 KiB
HTML
Raw Normal View History

<title>Core Client: File Structure</title>
<body bgcolor=ffffff>
<h2>Core Client: File Structure</h2>
<p>
The core client runs in a BOINC home directory.
An account file (accounts.xml) must be present in this directory.
The core client
creates and uses the following files and directories within the BOINC
home directory:
<ul>
<li>
<b>client_state.xml</b>: this is an description of the files,
application, workunits and results present on this client.
<li>
Each project has a <b>project subdirectory</b> whose name is the
project's base 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. The core client creates
symbolic links (UNIX) or .lnk files (Windows) in the slot directory,
linking the input, output and executable files to the appropriate files
in the project directory. On UNIX, the core client uses chroot() so that
the application sees the slot directory as the root of its filesystem,
and cannot create or access files outside of it.
<p>
A participant's accounts are described in a <b>preferences file</b>
on each of their hosts.
This file looks like this:
<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;resource_share>1&lt;/resource_share>
&lt;project>
&lt;master_url>http://www.myproject.com/&lt;/master_url>
&lt;authenticator>3f7b90793a0175ad0bda68684e8bd136&lt;/authenticator>
&lt;/project>
&lt;/preferences>
</pre>