I’m a bit of noobie, so sometimes it’s a bit of trial and error, but I hope this might point you in the right direction. My credits from the laptop are now being added to my Rosetta Account, but I set up a BOINCstatsBAM account ( Boinc Account Manager), when I also installed the BOINC client software on my main home Windows PC. BOINC was created at the University of California. I assume it is an update that installs automatically. problems with the long - run work units sent out by CPDN and people stopped giving up so quickly. It doesnt work to rename BOINC to BOINC2, then install. In the case of the RP3 & RP4, they updated without having to re-install the software. boinc-client is running but not attached. I’m not sure if the software will be updated in the future to replicate the latest Rasberry Pi GUI. Version numbers are 7.16.6 Ive tried all the steps above and still boinc-manager cannot connect to the boinc-client. This GUI is the same as your screenshot (without the additional buttons at top of screen). I have also connected an old Windows laptop which uses the “Generic x86_64” pre-configured image. I installed boinc-client and boing manager and the manager is not connection to boinc. Originally my software for the RP3 & RP4 didn’t have the additional buttons to change the Account Key, Shutdown or Reboot etc… Am I asking this question in the WRONG place? BOINC manager & client are all installed using YUM.I have a RP3 & RP4 connected using the pre-configured images, which now has the GUI as shown by bira’s screenshot. Why did only my (Fedora) Linux machinesĢ. The advantage of installing BOINC as a daemon on Linux is that it automatically starts when Linux boots and it runs even when no users are logged on. Now, the boinc-client process is running, but when I open the manager, it doesn't connect and no computations are done. I installed boinc-client and boinc-manager packages from the repositories. Reconnect attempts are essentially void, yum REINSTALL is useless, yum ERASE (and rename of home ".BOINC Manager" file) - then reboot/reinstall of boinc-manager and boinc-client is successful but results in the same NON-result that prompted this inquiry in the first place.ġ. I have a machine running Linux Mint 13 (which is basically Ubuntu 12.04 LTS with a different desktop). The several other Fedora machines that ran out of work have all disconnected entirely from the project and all preferences are gone. The BOINC client runs in the boinc group and belongs to that group as well as the video group if you use the gpu. ![]() I would need to pass arguments to but I dont want delay when running from command line. I am guessing I could always add at script that runs in background MyScript & where MyScript is actually the boinc-client with the sleep 300 delay. My Fedora (19/20) machines "not so much" - the FC19 with plenty of packets to work on is just fine. /configure so I am not running that version with the autostart. My Windows machines just sat and waited till this morning's server "fix". Apparently, the SETI servers had issues this Christmas/New Years week or so that resulted in a number of my BOINC clients running out of work. I have ( or rather 'had') BOINC/setiathome running on all my machines, in both Fedora (19 and 20) and Windows instances - whichever the boot choice.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |