6 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi All,
I want to write a domain specific REST/HTTP server to run on FreeBSD. I have control over both the server side and the primary client intended to consume the service.
My question is: how do you think it should be designed to support multiple connections, given:
It will run on a... (6 Replies)
Discussion started by: LittleCookieMon
6 Replies
2. BSD
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
3. Shell Programming and Scripting
Hi guys, so, I have a server running an sqlite database which is accessed by many client machines working as hardware testers, whenever something fails and needs to be replaced the operator would have to enter the Serial Number of the part being replaced as well as some other data. and... (0 Replies)
Discussion started by: sx3v1l_1n51de
0 Replies
4. UNIX for Dummies Questions & Answers
Ok, I've been shopping around and I've seen some nice one's, but they are either too expensive or they are not 64-bit; I want to be prepared for the future at the right price (under $3,000 with a decent configuration)! :D
Where can I find a good 64-bit desktop or workstation that will run the... (0 Replies)
Discussion started by: Mr. Nice Guy
0 Replies
5. UNIX Desktop Questions & Answers
Hi Every One,
I got a Basic doubts about clients on X-Server environment.
1) First of all what is mend by one client. (as per my understanding one application which is connected to X-server).
2) if i say two clients connected to my X-Server from the same machine, does it mean that two... (0 Replies)
Discussion started by: ps_sureshreddi
0 Replies
6. UNIX for Dummies Questions & Answers
Hello all!
I have been using FreeBSD for years, however, I have colleagues who prefer Linux. For some reason we can never meet eye to eye on what the advantage is from one system to the other.
My question is, can anyone explain what the differences are between both systems in respect to each... (1 Reply)
Discussion started by: Ivo
1 Replies
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)