Provided by: boinc-client_7.0.24+dfsg-1_amd64
boinc - The BOINC core client program.
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.
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). --help show options --version show version info --exit_when_idle exit when there are no results --show_projects show attached projects --detach_project URL detach from a project --reset_project URL reset (clear) a project --attach_project URL key attach to a project --update_prefs URL contact a project to update preferences --run_cpu_benchmarks run the CPU benchmarks --check_all_logins for idle detection, check remote logins too --allow_remote_gui_rpc allow remote GUI RPC connections --gui_rpc_port port port for GUI RPCs --redirectio redirect stdout and stderr to log files --dir path use given dir as BOINC home --no_gui_rpc 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 (boincmgr etc.) or the console command tool (boinccmd). --daemon run as daemon --exit_before_start exit right before starting a job --exit_after_finish exit right after finishing a job --insecure disable app sandboxing --launched_by_manager core client was launched by Manager --run_by_updater 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.
boinccmd(1), boincmgr(1) ⟨http://boinc.berkeley.edu/wiki/Client_configuration_(advanced)⟩
Copyright © 2007-2008 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. April 06, 2008 boinc(1)