How do I set up seti clients to run on dual cpus?

[zodder]

I know this must have been answered a thousand times, but I've downloaded and installed the service things from Sukhoi's excellent thread and I'm not sure if that's all I need to do. The services are running, but I don't see any way to check what's going on. I know this sounds like a pretty n00b question from a guy whos crunched more than 10K, but I'm clueless. Thanks, folks.

 

[networkman]

Some folks may suggest you use SetiDriver; personally, I use a mixture of SetiQueue and SetiSpy.

But since your question seems geared to running SETI as a service, the only things I can think of would be have to each client in it's own directory, and then as part of the parameters for executing the client, you'd specify which cpu to run it on. On my dual-cpu boxes, I have the cmd-line parameters something like:

seti1.exe -verbose -cpu 1 -proxy 192.168.1.40:5517

Where seti1.exe is the Seti Client, the "-verbose" echos output back to the screen, the "-cpu 1" specifies which cpu to run on, and the "-proxy 192.168.1.40:5517" points to the local SetiQueue that I have setup in my house.

So on my 2nd cpu, I'd simply change the parameters to reflect "-cpu 2"; since I use SetiSpy to track my local progress, I don't bother to use the "-verbose" parameter, and if you're going to be running Seti as a service anyway, you probably wouldn't want that parameter anyway.

Hope this helps!

 

[Baldy18]

If the install uses seti driver then just add the line "-cpu 2" to the setidriver.cfg file.

[EDIT] That of course would be in a dual processor machine. If the machine has more processors then use the appropriate number of CPUs.

 

[IJump]

SetHide also handles multiple processors. It detects the processors and runs the appropriate number of clients.... Plus it has some tracking built in....

 

[zodder]

I don't necessarily have to run them as a service. It's my home server, so I don't have to hide it. I guess I'm looking for the easiest way to make this happen and still be able to keep track of what's happening.

 

[Smoke]

SetiDriver and set Maximum Processes to "2".

 

[zodder]

As always, Smokeball, you rock. Thanks buddy.

 

[Rattledagger]

Ehm, if you're using the -cpu-switch to the seti.exe, remember that the numbering starts at 0.

Since I'm using setiqueue, I've never looked into setidriver and the likes, so the numbering here can be different.

 

[networkman]

Hmm.. that's interesting.. I've been using -cpu 1 and -cpu 2 for over a year and a half now and all of the processors are crunching exactly as they should.

 

[SoulAssassin]

<< Hmm.. that's interesting.. I've been using -cpu 1 and -cpu 2 for over a year and a half now and all of the processors are crunching exactly as they should.

>>



Interesting...have you tried killing one and making sure it runs on the right cpu, killing the other, etc...it definitely should be 0 and 1 for a dual box in my experience.