BOINC Command Line

[drezha]

I want to run command line on my linux rig.

I've setup all the projects on it so far so I was wondering if the following command would work and what others that run if command line have.

Been using http://boinc.berkeley.edu/trac/wiki/BoincCmd as a guide...

My command I want to use is:-

boinc_cmd --read_global_prefs_override

Also what happens if I run another command, like

boinc_cmd --get_results

when the first command is already running?

[vaughan]

Could you run your second command from another Terminal session then close it when you have the answer you want?

[drezha]

The first command wont run.

I get an error saying cant connect to localhost, connection refused.

[LeBo]

The first command wont run.

I get an error saying cant connect to localhost, connection refused.

Make sure you have already started the client with the command "./boinc" from BOINC directory, then make sure you start boinc_cmd from the same directory. Also make sure you use the password command also

[drezha]

Ah I see.

Didn't know I had to start ./boinc. That would explain it. And would also answer my question above about the commands.

[Brucifer]

uhmmm.................... what are you really trying to do here?

When on the extremely rare occasions that I run boinc on a linux system, it's usually a gutted linux system without X installed. And I don't follow the "factory" recommended way of setting boinc up either. I run separate directories for whatever boinc project I want to run. That way if I'm running something that isn't my cough, choke, gasp, "favorite" boinc project and all of a sudden my really cough, choke, favorite boinc project comes up with a whole bunch of new work units, then I just quite my non-favorite one, and change directories over to my cough, choke, favorite one and fire it off. And this way too, if I want to detach from a project, I don't run any chances of hosing up the installation for other projects. About the only downer I can see is that if a person is in to the cross-boinc stats thing, that might be a problem. But then I don't worry about that since I don't go in for those long signature files with every boinc stat is the world in them.

example:

/home/user/wcg/BOINC
or
/home/user/seti/BOINC

I also don't use any of the boinc_cmd stuff. I just fire boinc off with the ./boinc command in the directory and let it go. Control-C to stop. Less overhead and all. Can still issue the important commands without using the boinc_cmd thing.

Clear as mud?

[cicide]

I run my linux systems all command line (no X on them, plus they are remote so I ssh into them). I use the run_client script provided, and I add the option that allows remote gui access. Then I start boinc like this:

nohup ./run_client > /dev/null &

run_client is just a script that executes ./boinc with some options.

-Chris

[drezha]

uhmmm.................... what are you really trying to do here?

Run without the overhead of the GUI. And if I can use BOINC with no GUI, then I can turn the X server off and run the entire server with no GUI giving no graphics overhead, something that would come in useful on this system. (low power CPU, shared memory for gfx)

I thought the startup command was boinc_cmd --read_global_prefs_override but if it's ./boinc, as long as it uses the overriding preferences on the PC, I dont mind. (I control BOINC from each PC, makes it easier for me)

[Brucifer]

I use the home setup on the project site, so I can just use the ./boinc command. but if you want to locally over-ride those setting I see why you are using the boinc_cmd method.

[drezha]

Got it working now.

Just got to figure how to turn off the X server...