October 06, 2007"> GNU"> ]> Steffen Moeller steffen_moeller@gmx.de Frank Thomas frank@thomas-alfeld.de 2007 University of California &dhdate; &dhbinary; 1 &dhbinary; The BOINC core client program. &dhbinary; options DESCRIPTION &dhbinary; starts a client for communication with the Berkeley Open Infrastructure for Network Computing. For a graphical interface to the BOINC client, use BOINC Manager. For a command-line interface to the BOINC client, use boinc_cmd. OPTIONS A full summary of options is included below. show options show version info exit when there are no results show attached projects contact server when have results detach from a project reset (clear) a project attach to a project contact a project to update preferences run the CPU benchmarks for idle detection, check remote logins too allow remote GUI RPC connections port for GUI RPCs redirect stdout and stderr to log files use given dir as BOINC home 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 (boinc_cmd). run as daemon exit right before starting a job exit right after finishing a job disable app sandboxing core client was launched by Manager 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. SEE ALSO COPYRIGHT Copyright © 2007 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.