boinc_client1
The boinc core client program.
Part of boinc(1).
Usage
boinc [options]
Overview
The BOINC "core client", boinc, is the heart of BOINC. It controls which project applications are run on your computer, downloading "Workunits" and uploading the "Result" files from completed tasks. boinc is usually run in the background, ideally as a daemon. It can then be controlled either by a graphical tool called the BOINC Manager, boincmgr(1), or a command-line tool called boinccmd(1), by means of Remote Proceedure Calls (RPCs) over port 31416.
The BOINC core client can be controlled by command-line options, configuration files, and environment variables. Standard usage is simply to start the client running in the background.
Options
These command-line options for boinc can be used to control how BOINC is started. Once the client has started, you should use a separate program, (boincmgr(1) or boinccmd(1)) which communicates with it by means of Remote Proceedure Calls (RPCs).
- FC
--helpF[0] -
show options
- FC
--versionF[0] -
show version info
- FC
--exit_when_idleF[0] -
exit when there are no results
- FC
--show_projectsF[0] -
show attached projects
- FC--detach_project F[0]URL
-
detach from a project
- FC--reset_project F[0]URL
-
reset (clear) a project
- FC--attach_project F[0]URLFC F[0]key
-
attach to a project
- FC--update_prefs F[0]URL
-
contact a project to update preferences
- FC
--run_cpu_benchmarksF[0] -
run the CPU benchmarks
- FC
--check_all_loginsF[0] -
for idle detection, check remote logins too
- FC
--allow_remote_gui_rpcF[0] -
allow remote GUI RPC connections
- FC--gui_rpc_port F[0]port
-
port for GUI RPCs
- FC
--redirectioF[0] -
redirect stdout and stderr to log files
- FC--dir F[0]path
-
use given dir as BOINC home
- FC
--no_gui_rpcF[0] -
Omits creation of a socket as required for the remote control of the client. Consequently the client cannot be controlled by external tools like GUIs (
boincmgretc.) or the console command tool (boinccmd).
- FC
--daemonF[0] -
run as daemon
- FC
--exit_before_startF[0] -
exit right before starting a job
- FC
--exit_after_finishF[0] -
exit right after finishing a job
- FC
--insecureF[0] -
disable app sandboxing
- FC
--launched_by_managerF[0] -
core client was launched by Manager
- FC
--run_by_updaterF[0] -
set by updater
Access control for gui RPC
By default the core client accepts GUI RPC connections only from programs on the same host, which means that any user on this host can control the core client.
History
- Debian 5.0 (Lenny): the text shown here
- Debian 4.0 (Etch)
-allow_remote_gui_rpc until Debian 4.0 (Etch);
-check_all_logins until Debian 4.0 (Etch);
-daemon until Debian 4.0 (Etch);
-detach_project until Debian 4.0 (Etch);
-dir until Debian 4.0 (Etch);
-exit_when_idle until Debian 4.0 (Etch);
-gui_rpc_port until Debian 4.0 (Etch);
-help until Debian 4.0 (Etch);
-no_gui_rpc until Debian 4.0 (Etch);
-redirectio until Debian 4.0 (Etch);
-reset_project until Debian 4.0 (Etch);
-return_results_immediately until Debian 4.0 (Etch);
-run_cpu_benchmarks until Debian 4.0 (Etch);
-show_projects until Debian 4.0 (Etch);
-update_prefs until Debian 4.0 (Etch);
-version until Debian 4.0 (Etch).