![]() ![]() launched_by_manager core client was launched by Managerīy 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Ĭopyright © 2007-2008 University of California. exit_after_finish exit right after finishing a job exit_before_start exit right before starting a job ( boincmgr etc.) or the console command tool ( boinccmd). Consequently the client cannot be controlled by external tools like GUIs no_gui_rpc Omits creation of a socket as required for the remote control of the client. redirectio redirect stdout and stderr to log files allow_remote_gui_rpc allow remote GUI RPC connections check_all_logins for idle detection, check remote logins too run_cpu_benchmarks run the CPU benchmarks update_prefs URL contact a project to update preferences attach_project URL key attach to a project reset_project URL reset (clear) a project ![]() detach_project URL detach from a project exit_when_idle exit when there are no results ( boincmgr(1) or boinccmd(1)) which communicates with it by means of Remote Proceedure Calls (RPCs). Once the client has started, you should use a separate program, These command-line options for boinc can be used to control how BOINC is started. The BOINC core client can be controlled by command-line options, configuration files, and environment variables. Graphical tool called the BOINC Manager, boincmgr(1), or a command-line tool called boinccmd(1), by means of Remote Proceedure Calls (RPCs) over boinc is usually run in the background, ideally as a daemon. Uploading the "Result" files from completed tasks. It controls which project applications are run on your computer, downloading "Workunits" and ![]() The BOINC "core client", boinc, is the heart of BOINC. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |