'\" -*- coding: us-ascii -*-
.if \n(.g .ds T< \\FC
.if \n(.g .ds T> \\F[\n[.fam]]
.de URL
\\$2 \(la\\$1\(ra\\$3
..
.if \n(.g .mso www.tmac
.TH boinc 1 "April 06, 2008" "" ""
.SH NAME
boinc \- The BOINC core client program.
.SH SYNOPSIS
'nh
.fi
.ad l
\fBboinc\fR \kx
.if (\nx>(\n(.l/2)) .nr x (\n(.l/5)
'in \n(.iu+\nxu
[\fIoptions\fR]
'in \n(.iu-\nxu
.ad b
'hy
.SH DESCRIPTION
The BOINC "core client", \fBboinc\fR, 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. \fBboinc\fR is usually run in the background, ideally as a
daemon. It can then be controlled either by a graphical tool called the
BOINC Manager, \fBboincmgr\fR(1), or a command-line tool called
\fBboinccmd\fR(1), by means of Remote Proceedure Calls (RPCs) over port
31416.
.PP
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.
.SH OPTIONS
These command-line options for \fBboinc\fR can be used to control
how BOINC is started. Once the client has started, you should use a
separate program, (\fBboincmgr\fR(1) or \fBboinccmd\fR(1)) which communicates
with it by means of Remote Proceedure Calls (RPCs).
.TP 
\*(T<\fB\-\-help\fR\*(T>
show options
.TP 
\*(T<\fB\-\-version\fR\*(T>
show version info
.TP 
\*(T<\fB\-\-exit_when_idle\fR\*(T>
exit when there are no results
.TP 
\*(T<\fB\-\-show_projects\fR\*(T>
show attached projects
.TP 
\*(T<\fB\-\-detach_project \fR\*(T>\fIURL\fR 
detach from a project
.TP 
\*(T<\fB\-\-reset_project \fR\*(T>\fIURL\fR 
reset (clear) a project
.TP 
\*(T<\fB\-\-attach_project \fR\*(T>\fIURL\fR\*(T<\fB \fR\*(T>\fIkey\fR 
attach to a project
.TP 
\*(T<\fB\-\-update_prefs \fR\*(T>\fIURL\fR 
contact a project to update preferences
.TP 
\*(T<\fB\-\-run_cpu_benchmarks\fR\*(T>
run the CPU benchmarks
.TP 
\*(T<\fB\-\-check_all_logins\fR\*(T>
for idle detection, check remote logins too
.TP 
\*(T<\fB\-\-allow_remote_gui_rpc\fR\*(T>
allow remote GUI RPC connections
.TP 
\*(T<\fB\-\-gui_rpc_port \fR\*(T>\fIport\fR 
port for GUI RPCs
.TP 
\*(T<\fB\-\-redirectio\fR\*(T>
redirect stdout and stderr to log files
.TP 
\*(T<\fB\-\-dir \fR\*(T>\fIpath\fR
use given dir as BOINC home
.TP 
\*(T<\fB\-\-no_gui_rpc\fR\*(T>
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 (\fBboincmgr\fR etc.) or the console
command tool (\fBboinccmd\fR).
.TP 
\*(T<\fB\-\-daemon\fR\*(T>
run as daemon
.TP 
\*(T<\fB\-\-exit_before_start\fR\*(T>
exit right before starting a job
.TP 
\*(T<\fB\-\-exit_after_finish\fR\*(T>
exit right after finishing a job
.TP 
\*(T<\fB\-\-insecure\fR\*(T>
disable app sandboxing
.TP 
\*(T<\fB\-\-launched_by_manager\fR\*(T>
core client was launched by Manager
.TP 
\*(T<\fB\-\-run_by_updater\fR\*(T>
set by updater
.SH "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.
.SH "SEE ALSO"
\fBboinccmd\fR(1), \fBboincmgr\fR(1)
.PP
.URL http://boinc.berkeley.edu/wiki/Client_configuration_(advanced) ""
.SH COPYRIGHT
Copyright \(co 2007-2008 University of California.
.PP
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.