Jan Allan Andersen wrote:

I'm running BOINC (4.13) in a terminal window under Linux, running SETI2,
LHC and CP.
When BOINC is switching from one project to another, it's leaving a WU in
memory - Does that mean, that if I am closing down the terminal window,
maybe even leaving my Linux (sometimes I have to use windows), the result
left in memory will be lost?

When you close down your terminal window, normally all processes for that window are terminated also. If you want a process to continue, you must ensure that all text output is redirected to log files, and that you have "detach"ed the process.

Better is to run boinc from a script or as a service. "Howto"s for these have been posted on the s@h boinc forum.

See:
http://noether.vassar.edu/~myers/help/boinc/unix.html

I run a secure scripted variation whereby boinc is run under a restricted user id just for boinc. I use (one way) read-only group access to then see what's happening.


All the boinc clients save checkpoints so that if they are interrupted, they can roll back to a recently saved point. Leaving the processes in memory saves wasting CPU time that would otherwise be lost by rolling back.

Not a big problem in regards til SETI2 and LHC, both it is in regards to CP.

CP especially should be kept in memory!

BTW; Is the linux BOINC client crunshing faster than the windows client?

At the moment for s@h, quite a bit faster if you believe the screams from the Windows users. I suspect that some OS interaction is causing problems. The s@h developers are looking into whether the problems are real and what to fix.


(On linux, you could try using Wine (;-))

Happy crunchin',
Martin