hi there, I\'m highly proud of beeing betatester again ...

is ist right, that the project, once started, runing in foregrond?
I had to shut down the boinc-client to run it again with screen.
there i wondered: it began to compute at 01.12.1810 again. shouldn\'t it resume at the point it was canceled?

that\'s all for the moment.

nice work ... that\'s what i was expecting about CP @ boinc @ linux-commandline :p

thanks ... the poor time, my gateway was unemployed is over now.

Hi, Gandhi,

The Model falls back to the last Checkpoint when stopped/restarted. That occurs every 144 TimeSteps. (It pays to wait until after a 144-TS boundary to shut down, especially if crunching two models on a HT P4 CPU.)

Linux version is only on Command Line, so nothing to run in foreground...? (I keep mine on a separate KDE Desktop -- hidden and out of harm's way.)

Screen? Are you running in Windoze -- or running ./viz?

________________________________________________
Washing one's hands of the conflict between the powerful and the powerless means to side with the powerful, not to be neutral.
-- Paulo Freire (1921-1997), educator, author.

> Hi, Gandhi,
>
> The Model falls back to the last Checkpoint when stopped/restarted. That
> occurs every 144 TimeSteps. (It pays to wait until after a 144-TS boundary to
> shut down, especially if crunching two models on a HT P4 CPU.)

ok, i thought something in this way.
>
> Linux version is only on Command Line, so nothing to run in foreground...? (I
> keep mine on a separate KDE Desktop -- hidden and out of harm's way.)

no, the gatway hasn't even x-free installed ;p
he's got no monitor and no keyboard - because of this i use it by SecureCRT from my windows-box.
>
> Screen? Are you running in Windoze -- or running ./viz?

I've unzipped the arcive and ran the executable.
from this moment on, the process was in foreground. as i closed the terminal, the process died.
i opened a new one, and ran the executable by "screen" (

thats all, by the way

... the program still runing in its own terminal, everything is fine :)

hi,

as for running as a daemon I found a script on the predictor-site:
http://predictor.scripps.edu/client.php#cmdline
which worked after some modifications for me (inserted log to file, etc.)
There's also a thread listing more options in the Seti-forum:
http://setiweb.ssl.berkeley.edu/forum_thread.php?id=142