1
.\" Unix Manual page for boinc_client
2
.\"======================================================================
3
.\" This file is a part of BOINC. Distribution and/or modifications
4
.\" are allowed under the terms of the Lesser GNU Public License.
5
.\" See the file COPYING for details.
6
.\"======================================================================
7
.\" To view this file without the man command type:
8
.\" 'nroff -man boinc.1 | more'
9
.\" or, on some versions of man, just man -l boinc.1
11
.\" @(#) $Id: boinc_client.1,v 1.1 2007/12/29 16:50:09 myers Exp $
12
.TH boinc_cmd 1 "29 December 2007" "BOINC 5.10" "User Manuals"
26
The BOINC "core client",
28
is the heart of BOINC.
29
It controls which project applications are run on your computer,
30
downloading "Workunits" and uploading the "Result" files from
33
is usually run in the background, ideally as a daemon.
34
It can then be controlled either by a graphical tool
35
called the BOINC Manager,
37
or a command line tool called
39
by means of Remote Proceedure Calls (RPCs) over port 31416.
43
The BOINC core client can be controlled by command-line options,
44
configuration files, and environment variables.
45
Standard usage is simply to start the client running in the
49
.SH CONFIGURATION FILES
51
BOINC uses the following configuration files.
52
You can edit these files before launching
54
to control BOINC in various ways.
57
.I account_<PROJECT-URL>.xml
58
Accounting information for a given project.
59
There will be one for each attached project.
62
.I global_prefs_override.xml
63
Override global preferences
67
Turn log messages on/off by category, and other core client
68
configuration options.
69
These settings can be very useful for troubleshooting problems or debugging.
73
Hosts from which remote GUI RPCs are allowed.
74
If this file does not exist then...?
96
These command-line options for
98
can be used to control how BOINC is started.
99
Once the client has started,
100
you should use a separate program,
104
which communicates with it by means of Remote Proceedure Calls (RPCs).
109
Show these command line options.
113
Show client software version.
117
Show all attached projects.
120
.B --detach_project <URL>
121
Detach from the project associated with the given URL.
124
.B --reset_project <URL>
125
Reset (clear) the project associated with the given URL
128
.B --attach_project <URL> <key>
129
Attach to the project associated with the given URL.
132
is the authenthentication token (account key)
133
of an existing account on the project.
136
.B --update_prefs <URL>
137
Contact the project associated with the given URL
138
to update preferences.
141
.B --run_cpu_benchmarks
142
Run the CPU benchmarks.
145
.B --check_all_logins
146
For idle detection, check remote logins too.
147
When BOINC is set to run when the computer is idle, it usually only
148
checks for user activity from locally logged-in user.
149
This causes it to also check for activity from remote logins.f
152
.B --allow_remote_gui_rpc
153
Allow remote GUI RPC connections.
156
.B --gui_rpc_port <port>
157
Set the port for GUI RPCs.
158
The default, if not otherwise set, is port 31416.
162
Redirect stdout and stderr to log files.
166
Detach from console (Windows only)
170
Use the given directory as the BOINC home (working directory).
174
Do not allow GUI RPCs, don't make socket.
178
Run as daemon, in the background (Unix only).
182
Disable application sandboxing (Unix only).
185
.B --launched_by_manager
186
Indicates that the Core Client was launched by the BOINC Manager.
190
Indicates that the Core Client was launched by the updater.
194
Specify a number of seconds to delay running apps after client startup
195
[New in version 6.1.]
202
uses the following Unix environment variables to control
203
how it deals with web proxies.
211
User name for proxy authentication
215
Password for proxy authentication
218
URL of SOCKS 4 server
222
URL of SOCKS 5 server
226
User name for SOCKS authentication
230
Password for SOCKS authentication
233
.SH DEBUGGING OPTIONS
234
These command line options are usually only of use for
235
troubleshooting or debugging.
239
Exit when there are no more results to process.
242
.B --exit_before_start
243
Exit right before starting a job (useful for debugging).
246
.B --exit_after_finish
247
Exit right after finishing a task (useful for debugging).
251
Don't run performance benchmarks; use fixed numbers instead.
254
.B --exit_after_app_start N
255
Exit about N seconds after first application starts
259
Put client in the background after starting up
262
.B --skip_cpu_benchmarks
263
Don't run CPU benchmarks
266
.B --file_xfer_giveup_period N
267
Specify giveup period for file transfers
270
.B --started_by_screensaver
271
Passed by screensaver when it launches client
284
Revision Number: 5.10.21-18
286
Release Date: 29 Dec 2007