# Description: Enable service provided by daemon. # Short-Description: Start daemon at boot time Linux seems not user-friendly at all, and to be a huge learning curve. Anyway, I gave up, and a very flaky XP-64 is running again. Maybe there is a problem because I installed Kali & BOINC on my C2D lappie, where it did download WCG tasks, but BOINC didn't like swapping machines. Though the machine was online & could surf the net, BOINC would do nothing except say "Update requested by user" when urged. Got the libsso problem with the Berkeley BOINC 7.0.64, but apt-get fetched & installed 7.0.27 from the supplied repositories. While it was offline, stuck in my 16G USB stick that's got Kali installed. Thought it was hardware, but it eventually responded to a repair reinstall of XP - PITA. Had a first dabble with BOINC on Linux a few days ago when my 2600K with XP-64 crashed. (Had a user a/c on the 2nd machine in the continent to run genuine Unix - version 6 on DEC PDP-11/70) BTW, lots of this Linux stuff is mumbo-jumbo to me, though I've used and administered *nix systems in the past. ? ( none 200M 0 2G 0% /var/lib/boinc-client/slots <- ) In your `df -h`output, the "Size" of the ramdisc is shown as 200M not 2G. (Link?) Do you periodically suspend BOINC and copy a snapshot of the data onto non-volatile storage, or does the RAMdisc driver automatically do journalling onto a n-v medium? Only downside is (was) you'd lose all your data every time you restart, and I've already fixed that issue.Can't see the fix, but I haven't been following this topic.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |