With the original Seti command line I am able to run multiple instances for one account as long as each is started in a different sub-directory.

I have been unable to do the equivalent with the BIONC command line. Is it possible? Can someone point me in the right direction to allow this?

Thanks.

Why do you wan't to use more as one instance ? - The boinc client starts a sepereate seti app for each CPU you have, and also caching WUs.

---

You can do this if you really want - just put multiple copies of BOINC in their own directories e.g. /home/boinc1, /home/boinc2 etc.

As Dotsch has already stated, there is no need to do this for SMP machines as the BOINC client is capable of running as many instances of the program as there are CPUs.

Look at your General Preferences under your account and there is a setting for the max number of CPUs BOINC is allowed to utilise.

---

Why do you wan't to use more as one instance ? - The boinc client starts a sepereate seti app for each CPU you have, and also caching WUs.

Maybe some person do not have a flatrate and can stay online all day ;?
In my case one boinc client is ready after nearly 3 hours. Although I have edited my preferences, that it should download WUs for a day, it is ready in such a short time ... :( With the seti1-client I used 3 of them and one boinc-client, so they were ready after 24 hours ... ;) So it is not so expensive to run them ... But now I can only start two clients, every further client just finish immediately with an error message like
"GUI RPC bind failed: -1
gstate.init() failed: -180" ... :(

---

Located somewhere in Galactic Sector ZZ9 Plural Z Alpha

Why do you wan't to use more as one instance ? - The boinc client starts a sepereate seti app for each CPU you have, and also caching WUs.

Maybe some person do not have a flatrate and can stay online all day ;?
In my case one boinc client is ready after nearly 3 hours. Although I have edited my preferences, that it should download WUs for a day, it is ready in such a short time ... :( With the seti1-client I used 3 of them and one boinc-client, so they were ready after 24 hours ... ;) So it is not so expensive to run them ... But now I can only start two clients, every further client just finish immediately with an error message like
"GUI RPC bind failed: -1
gstate.init() failed: -180" ... :(

You can setup the WU cache on the website on the general preferences up to 10 days. So your client connects every 10 days to the boinc servers.

GUI RPC is very problematic with two boinc clients. With luck, the second boinc will connect to the alternate port. But if the bindings will be successfull, you can not manage the second via the gui, because the GUI connects only to the second if the primary not anwsering.

So I recommend you to set your work cache higher.

---

Why do you wan't to use more as one instance ? - The boinc client starts a sepereate seti app for each CPU you have, and also caching WUs.

Maybe some person do not have a flatrate and can stay online all day ;?
In my case one boinc client is ready after nearly 3 hours. Although I have edited my preferences, that it should download WUs for a day, it is ready in such a short time ... :( With the seti1-client I used 3 of them and one boinc-client, so they were ready after 24 hours ... ;) So it is not so expensive to run them ... But now I can only start two clients, every further client just finish immediately with an error message like
"GUI RPC bind failed: -1
gstate.init() failed: -180" ... :(

You can setup the WU cache on the website on the general preferences up to 10 days. So your client connects every 10 days to the boinc servers.

GUI RPC is very problematic with two boinc clients. With luck, the second boinc will connect to the alternate port. But if the bindings will be successfull, you can not manage the second via the gui, because the GUI connects only to the second if the primary not anwsering.

So I recommend you to set your work cache higher.

Thanks, Dotsch, for the quick answer ... :) I have running two clients ATM without any further problem, but if I want to start a 3rd one, I get the above mentioned error message ... :( And two clients are still to fast ... :(
I have changed my prefs to 1.5 day, so I will wait to see, if this helps ... ;)

---

Located somewhere in Galactic Sector ZZ9 Plural Z Alpha

So I recommend you to set your work cache higher.

Thanks, Dotsch, for the quick answer ... :) I have running two clients ATM without any further problem, but if I want to start a 3rd one, I get the above mentioned error message ... :( And two clients are still to fast ... :(
I have changed my prefs to 1.5 day, so I will wait to see, if this helps ... ;)

If you run more than on seti instance, it will slowdown the processing, because seti is very memory and cache intensive. So the processing off two parallel instances will need some more time than two times...
As I have written, there is no need to do this. Let run one instance and set the cache higher, so the boinc client connects if the cache is empty or near empty.

---

Why do you wan't to use more as one instance ? - The boinc client starts a sepereate seti app for each CPU you have, and also caching WUs.

As I have written before: I want to crunch WUs, but want to go online once a day ... ;) I have not enough money to do it more often ... :(

---

Located somewhere in Galactic Sector ZZ9 Plural Z Alpha