| Subject: Re: I am going to quit when SETI Classic goes down. |
| From: Lars Bausch |
| Date: 24/10/2005, 00:05 |
Hi !
Alonzo wrote:
Why do you not migrate some hosts to boinc and verify the installation
and test the clients on your different platfroms. - For all your
platforms are binaries available.
i didn't know until now that boinc will work behind a proxy server.
this is the main reason.
Proxy or socks as proxy works. But I recommend the use of boinc version
>4.43.
second reason is (not a really big reason): we don't have the password
on our account and our domain has moved (my boss, the subscriber of
this account, don't remember the password), so we can't use the same
account for boinc.
i think we will migrate to boinc when seti classic is closing.
Have you tried to contact the seti admins for help ? - They can help you.
we have 130 clients now. i don't have time to control all by manual
connect :-P
Yes, I understand this problem !
But boinc is harmless, you can start it from a shell script in a while
true loop (boinc client should restarted if it crashs). The boinc client
do all the things automaticly for you, like caching, upload/download
work. If the seti app will abort, the boinc client restart it.
I think with the shell scripts and boinc view it is easy to manage.
If you which, I can mail you my shell script collection, including
start/stop scripts, and a boinc keepalive skript with automaticly
restarting.
I am not shure, but I have seen that setiqueue is now available for
boinc now. - I will search around in the forums.
There is no setiqueue for boinc, but in the forums is boinc view
described as a good alternative to setiqueue.
my goal now is to make 99.999% before classic is closing, but i don't
think that we can get there.
:-) Happy crunching.
greetings from austria
Viele Grüße / Regards
Lars