Update (7 february 2012): if you run this on a busy server, you might want to run. Update (9 December 2010): added requirement for curl. If you are running 64 bit Linux and 64 bit BOINC then you might have a problem with projects that issue 32 bit applications rather than 64 bit applications. To avoid restarting your computer at the end of installation (the forced reboot seems totally useless), you can just delete the file named RebootPending.txt in BOINC’s folder. On a side note, I just installed BOINC into Windows 7 too. Two command-line management tools are available: boinccmd and boinc. Now, of course, you might want to configure the thing to run at start up, or even as a service, but this is getting out of the scope of this post, and there are actually some guides available for that, here are some pointers: Install boinc-nox to use BOINC on a headless system. boinccmd -project_attach cee742fga12345b123ab27e51bb6d5c4Īnd that’s it… I don’t understand why noone at BOINC took the time to write down those instructions clearly. The result is: you have to (re-) install the video driver after each Linux update, to re-establish the link between them. The video driver - especially the special bits of the driver we use for computing - stops working. Attach a project and your user key to the client using boinccmd, for instance: If you update Linux (by itself), that linkage gets broken.It communicates with a running client using. Detach the screen (CTRL+A, CTRL+D) or open another terminal. The BOINC command tool (boinccmd) provides a command line interface to control a running BOINC client (boinc(1)).(NB: depending on your Linux version, you may need to install curl, for instance on Ubuntu: apt-get install curl) Launch a screen ( screen), inside which you’ll run run_client (.Navigate to the newly created subfolder BOINC ( cd BOINC).I use the standard Linux distribution version of the manager/client. I have browsed through the client source a couple times to glean more information about the testing being done to arrive at a FOUND GPU. Get the BOINC client (for instance, wget ). I have encountered this several times on Linux systems and I have been able to 'guess' why the BOINC client is not able to find the GPU.Note your account key (you’ll need it later).For the example, I’ll be creating an account at Quantum Monte Carlo Home by University of Muenster (Germany). ![]() Create an account for the project you want.I recently tried to install it on a Linux server, and got lots of trouble figuring out how to configure it using only the command line: as a definitely mainstream program, they seem to revolve around their GUI and the documentation for the command line, although not inexistent, isn’t of much help when it comes to simply configuring the software… So here’s a complete step-by-step guide (even included the properly documented parts) to get it started: If you get it working, it'd be great if you can share info as others might like to follow in your footsteps.BOINC is a large distributed computing project, or more accurately, a piece of software used by a bunch of distributed computing projects. Please post back with more info if you continue to have TurnKey specific issues and I'll do my best to help out. Please keep in mind that TurnKey v15.x is based on Debian 9/Stretch. It looks like the BOINC forums are here if you need BOINC specific assistance. I suspect that the daemon config will be in /etc/default/boinc-client and the rest of the BOINC config will likely be found in /etc/boinc-client. You may need to adjust some of the config. ![]() To start it right now, try this: systemctl start rvice So if you've installed BOINC from the Debian repos (as it sounds like you have) you should only need to run something like this (to make is auto start on boot): systemctl enable rvice Seeing as systemd is becoming standard across most Linux distros, they may even already include a service file to support running it as a daemon? Actually, a quick look through their source code and I discovered a file that appears to be a systemd '.service' file. The XML formats are documented in GuiRpcProtocol. Other BOINC projects run about the same on each OS. TN-Grid runs like 30 faster vs Windows, Universehome (BHSpin) is like 50-60 faster vs Windows, when WCG has a project running on AutoDock Vina it's also around 50 faster on Linux, etc. These RPCs send XML request and reply messages over a TCP connection. Some projects benefit from switching to Linux 64-Bit. This enables the development of GUI (graphical user interface) programs. However, I am fairly familiar with systemd which would be the best way to daemonize BOINC (or any other application you wish to run as a service these days.). The BOINC client provides a set of RPCs (remote procedure calls) for control and state interrogation. I did have a play many years ago, but haven't investigated recently. That's an awesome idea! TBH, I have limited experience with BOINC.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |