![]() This can be done thus:īoinc_cmd -host localhost -passwd -get_state You'll probably want to edit this file so that it contains the password you want to use.īoinc_client will need to be restarted for this change to take effect. boinc_client will have invented a random password (to protect the connection to the boinc_client daemon and is nothing at all to do with project passwords) and put it into /var/lib/boinc-client/gui_rpc_auth.cfg. The first stumbling block is that (for security reasons) boinc_cmd should not be authorized to connect to the daemon initially. Why not try it! When it works, you'll see lots of information about the projects you are (or are not) running but it's likely not to work just yet. The first command you should use should be These will need to be consulted when troubleshooting. By default, the output from boinc_client is piped to log files in /var/lib/boinc-client/ ( stdoutdae.txt and stderrdae.txt). When working from the command line only, this means using boinc_cmd to communicate with the boinc_client service.īoinc_cmd can be a little frustration to work with, the man page needs a volunteer to step up and the feedback from the command is minimalistic. The package installs boinc_client as a daemon service running under user boinc. Successfully running BOINC from the command line may take a little work. Unfortunately, when it doesn't work because of failed X authorization, it does not report the error back to boinc_cmd or boinc_mgr, and the only trace of the error is in some log file in the result directory /var/lib/boinc-client/slots/. Then, the "Show graphics" button in boincmgr, or the -result . graphics_window option to boinc_cmd, will actually work. This will only give access to the "boinc" user that boinc_client runs as. If you're concerned about security a more limited version of the above is It is a bad idea on multi-user machines, so don't do it there. This is generally safe on single-user machines, though not ideal. Your X display can be made accessible to all local UNIX socket connections, including the ones from BOINC, by running The X display needs to be accessible to the BOINC graphics processes in order to see the interesting graphics for, e.g., and it isn't by default. Graphics are supported, but they won't show up by default. Thus, the following is only useful for very old version of boinc.) (Graphics processes seem to be forked from boincmgr now, with user's uid instead of boinc-client's uid, so it works by default. Make sure to have shut down the system-wide boinc_client by invoking "/etc/init.d/boinc-client stop" when debugging. This page has some detailed instructions how to run gdb. After its installation run boinc_client with the GNU Debugger gdb. ![]() Such are distributed with the boinc-dbg package. This only works for binaries that were compiled with the -g debug flag and are not stripped. A backtrace lists the functions that were called. SPARC and PowerPCs, some users have reported core dumps of the boinc client. The web site of the project features entries for each result which may be indicative of one problem or the other.Įxperiencing core dumps - how to get a backtrace with gdb That is performed by the binary downloaded dynamically by that client. The boinc-client installed by the Debian package does not perform the actual computation. The submitted results are not all 100% identical when run on different machines. If this is fewer than 10 in 100 times then this may be some physiological behaviour. Please note some information on this page may be out of date, and in need of updating.Įverything works fine but some submissions get evaluated as erroneous ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |