boinc 2.9 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News boinc 2.9 (Default branch)
# 1  
Old 12-30-2007
boinc 2.9 (Default branch)

boinc can be used as a console tool to display information about BOINC projects and working units. It can also be used to start or stop BOINC.License: GNU General Public License (GPL)Changes:
The application's user-friendly name is now shown in the project long display. Only the last application of each project is shown in the project short display. The float portion is removed from the credit number in stats.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. BSD

Compiling BOINC/Seti@Home for OpenBSD 5.3 Sparc64

I used to use x86 Linux clients for this years ago, but ceased all activity until last night. I have resurrected an old Sun Blade 100, which used to run Solaris 9, when I first owned it, in the 2003 period, but now is very much alive with 2 gig of new ram, and and extra 10 gig of drive space... (0 Replies)
Discussion started by: RichardET
0 Replies

2. UNIX for Advanced & Expert Users

Has anyone run the linux boinc client on FreeBSD

The reason I ask is because the einstein client in the freash ports is not the current one with boinc. No new work is being assigned. They sugested or asked if I could run boinc 6.10.17 linux in emulation and if so, I would be able to crunch einstein data. so, anyone done the linux emulation of... (0 Replies)
Discussion started by: droolin
0 Replies
Login or Register to Ask a Question
boinc(1)																  boinc(1)

NAME
boinc - The BOINC core client program. SYNOPSIS
boinc [options] DESCRIPTION
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 Re- mote 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). --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 exter- nal 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 con- trol the core client. SEE ALSO
boinccmd(1), boincmgr(1) <http://boinc.berkeley.edu/wiki/Client_configuration_(advanced)> COPYRIGHT
Copyright (C) 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)