Projects that use trickle-up messages will also need to have a trickle-up handler. 'Boinc' happily doing things for a while - then it tries to look for a domain socket, doesn't find it - tries to connect to port 60. Typically, this mechanism is used to run work handling daemons. Describe the bug A clear and concise description of what the bug is. If you're running multiple instances of a daemon on one host, you must specify this.ĭaemons are executed in a directory tmp_hostname/ (not bin/).ĭaemons are started when you run the bin/start script,Īnd killed (by a SIGHUP signal) when you run bin/stop. Defaults to the program name followed by '.pid'. Name of file used to store the process ID (in the pid_HOSTNAME directory). If you're running multiple instances of a daemon on one host, you must specify this. Defaults to the program name followed by '.log'. Name of output file (in the log_HOSTNAME directory). Note: won't work you must specify a number. If set to 1, don't print a message at project startup about this daemon. The default is the project's main host, as specified in config.xml. You can then start the BOINC Manager from the pull-down menu Applications -> System Tools -> BOINC Manager. Starting BOINC After the installation is finished, the client is started automatically. Specifies the host on which the daemon should run. sudo aptitude install boinc-client See also the page Stop or start BOINC daemon after boot for helpful commands for controlling the client. Must be a program in the project's bin/ directory. Your project's daemons are described in its config.xml file, with elements of the form: Daemons are server programs that normally run continuously.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |