by very stupid accident - wiped my hard disk clean and had to install linux alone. after several days of configuration, i finally have it working. but i want to be able to run boinc-cp. i have downloaded it and unzipped it. i put it in a folder and try to \'run\' it. (remember i am coming from dos/windows.) do i have to create a makefile? supposedly i have an app called WINE which runs windows apps but i cannot find it. (i am running Suse Linux.) anyways, i hope you can help me. i want to do my part and continue to run cp.

Hi, you just want to download the Linux BOINC client from here:

http://climateapps2.oucs.ox.ac.uk/cpdnboinc/download.php

Then open up a "Terminal" window (i.e. "Xterm") and type in:

gzip -d boinc_4.05*.gz
chmod uog+rx boinc_4.05*
./boinc_4.05*

this will startup the BOINC client, then you attach to "climateprediction.net" and "paste" the authenticator key that should have been emailed to you when you created the "sam michael" account. Then after running benchmarks boinc will download everything for CPDN and hopefully get your model running!

thank you carl for your reply :) this note is for people running Suse Linux. i figured the problems out myself. what you do is extract the downloaded file. then you create a new folder (call it boinc if you want). put the two items into that new folder. then create a newer folder inside that new folder (call it temp if you want). you now have a folder called boinc on your desktop with three items in it. copy the extracted file into temp. rename the file something easy like boink. change the permissions on the file to executable. open a terminal window while you're in temp. cd .. to get to the higher level folder boinc. you are now ready to run the program. type temp/boink and this should set up and run the program. you will have to enter the two input parameters to run the program correctly. these are url and your acct ID. the url is http://climateprediction.net your acct ID is what they emailed you when you set up your acct (the long-___ number they assigned you). happy computing :) ps - don't kill the window or you might kill the program (i don't know if the process stays alive if you do - i just minimized it and let it run).

Closing the window will kill the program. What you can do instead of just running the program is to use nohup and also run the program in the background. But first, if you are in the folder boinc and you want to run boink, you can type:
./boink
This is the same as being up a folder and typing:
boinc/boink

So instead of running:
./boink
You can run:
nohup ./boink > output.log &

The nohup will keep the program running even if you close the terminal window or log out. The ">" will output the data into the output.log file. This will overwrite the file each time you start the client, ">>" will append the new output onto the end of the current file. The "&" will make the job run in the background.

You can then watch the output with:
tail -f output.log
If you want to stop running the client you need to kill the process boink.

> nohup ./boink > output.log &

wow that's awesome, I really learn something new everyday, I never knew of "nohup"!

Another alternative to nohup is screen. You may already have it installed ('man screen'). Simply type "screen" at a command line and you are brought into an interactive session that doesn't go away even after you log off. You can "detach" from the screen by pressing CTRL+A and then D. At any time you can come back to the screen by typing "screen -r" at a command line.

This way, you can terminate boink without killing it.. simply resume the screen, hit CTRL+C (which is caught by the program to clean itself up, I presume), and type "exit" to terminate the screen.

-S.