Joined: 14 Oct 99
This is wierd. I had been running seti@home i686 linux on this K6-III-450, 290MB RAM linux box, (no problems, no errors, ran for weeks at a time with no crashes) and then decided with the public announcement of the BOINC launch to switch it to BOINC. All kinds of error messages in the Konsole window after launching BOINC, not enough disk space allocated to download any work, etc., so I copied the BOINC executable to my 80GB-disk-space linux machine and launched BOINC on the K6-III machine, CD'd to the big storage machine, using the executable on that box, over the network. I chmod'ed that directory to open access to avoid across-the-network permission problems, and chmod'ed the executable likewise. I then changed my prefs at seti to allow more disk space usage. That worked ok - didn't get the insufficient disk space allocation error, but it didn't successfully do any work, either, some sort of wierd error that occurred periodically, wasn't very informative, and did not indicate a permission problem like can't create or write to a file, etc. (I closed and then opened a new Konsole window so those errors aren't there now). I then noticed that BOINC then downloaded seti@home for linux and apparently has started running that as a client of BOINC!! But seti@home was already installed, so what's the deal here? If all it's going to do on this machine is run seti@home anyway, what's the point of BOINC? In fact it was more efficient the way I ran it before BOINC, because I had set@home running all the time whereas I set up BOINC to only run when a user was NOT using the computer. I have 10,700+ WUs completed, using several computers, mostly Athlons, both Windows and Linux, and I would like to keep being useful, but right now I'm mostly just frustrated. And I haven't been able to find any docs that would help me understand how this is supposed to work, or how best to optimize settings, and criteria like minimum disk space and minimum ram recommended or required. So far BOINC seems to just be thrashing gobs of status message in the Konsole window and not accomplishing anything much. Seti@home just quietly worked, crunched WUs, no muss no fuss. Was this maybe public-released a bit early? I gather there are also currently some hardware issues at the server level that y'all are rushing to address.
|ID: 1870 ·|
Joined: 2 Jul 99
"I then noticed that BOINC then downloaded seti@home for linux and apparently has started running that as a client of BOINC!! But seti@home was already installed, so what's the deal here?"
|ID: 2074 ·|
©2016 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.