1boinc(1)                                                              boinc(1)
2
3
4

NAME

6       boinc - The BOINC core client program.
7

SYNOPSIS

9       boinc [options]
10

DESCRIPTION

12       The  BOINC  "core  client",  boinc, is the heart of BOINC.  It controls
13       which project  applications  are  run  on  your  computer,  downloading
14       "Workunits"  and  uploading  the  "Result"  files from completed tasks.
15       boinc is usually run in the background, ideally as  a  daemon.  It  can
16       then be controlled either by a graphical tool called the BOINC Manager,
17       boincmgr(1), or a command-line tool called boinccmd(1), by means of Re‐
18       mote Proceedure Calls (RPCs) over port 31416.
19
20       The  BOINC  core client can be controlled by command-line options, con‐
21       figuration files, and environment variables. Standard usage  is  simply
22       to start the client running in the background.
23

OPTIONS

25       These  command-line  options for boinc can be used to control how BOINC
26       is started. Once the client has started, you should use a separate pro‐
27       gram,  (boincmgr(1) or boinccmd(1)) which communicates with it by means
28       of Remote Proceedure Calls (RPCs).
29
30       --help show options
31
32       --version
33              show version info
34
35       --exit_when_idle
36              exit when there are no results
37
38       --show_projects
39              show attached projects
40
41       --detach_project URL
42              detach from a project
43
44       --reset_project URL
45              reset (clear) a project
46
47       --attach_project URL key
48              attach to a project
49
50       --update_prefs URL
51              contact a project to update preferences
52
53       --run_cpu_benchmarks
54              run the CPU benchmarks
55
56       --check_all_logins
57              for idle detection, check remote logins too
58
59       --allow_remote_gui_rpc
60              allow remote GUI RPC connections
61
62       --gui_rpc_port port
63              port for GUI RPCs
64
65       --redirectio
66              redirect stdout and stderr to log files
67
68       --dir path
69              use given dir as BOINC home
70
71       --no_gui_rpc
72              Omits creation of a socket as required for the remote control of
73              the  client. Consequently the client cannot be controlled by ex‐
74              ternal tools like GUIs (boincmgr etc.) or  the  console  command
75              tool (boinccmd).
76
77       --daemon
78              run as daemon
79
80       --exit_before_start
81              exit right before starting a job
82
83       --exit_after_finish
84              exit right after finishing a job
85
86       --insecure
87              disable app sandboxing
88
89       --launched_by_manager
90              core client was launched by Manager
91
92       --run_by_updater
93              set by updater
94

ACCESS CONTROL FOR GUI RPC

96       By  default  the core client accepts GUI RPC connections only from pro‐
97       grams on the same host, which means that any user on this host can con‐
98       trol the core client.
99

SEE ALSO

101       boinccmd(1), boincmgr(1)
102
103http://boinc.berkeley.edu/wiki/Client_configuration_(advanced)⟩
104
106       Copyright © 2007-2008 University of California.
107
108       Permission  is  granted to copy, distribute and/or modify this document
109       under the terms of the GNU Free Documentation License, Version  1.2  or
110       any  later  version  published by the Free Software Foundation; with no
111       Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
112
113
114
115                                April 06, 2008                        boinc(1)
Impressum