Date: Wed, 04 Aug 1999 08:11:44 -0700 From: Kent Stewart <kstewart@3-cities.com> To: Allen Cleveland <allenc@mindsieve.com> Cc: Dutch Collins <dutch@charm.net>, freebsd-questions@FreeBSD.ORG Subject: Re: SETI@home error Message-ID: <37A85830.1DA2C817@3-cities.com> References: <3.0.5.32.19990804012031.00800bd0@mindsieve.com> <3.0.5.32.19990804020752.007fb100@mindsieve.com> <37A7DB91.FC256FC5@charm.net> <37A7E7D9.B41C30A9@3-cities.com> <37A7EA9F.74102312@charm.net> <3.0.5.32.19990804041814.0080c100@mindsieve.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Allen Cleveland wrote: > > At 12:55 AM 8/4/99 -0700, Kent Stewart wrote: > > > > > >Dutch Collins wrote: > >> > >> Kent Stewart wrote: > >> > > >> > No! You only create one account. I have four machines running it and > > >> Yep on the single account, went to web site to download the 1.3 version. > >> It all worked fine and it crunching numbers now. I am running it in a > >> terminal (kvt) so it is out of the way. I do not know how KDE will affect > >> it, not much I guess. This old 486/100 does hufF_and_puff a bit. > >> > >> Based on this configuration I do not have a clue on the bad header problem. > > >I'm also running it from an x-window and It doesn't seem to matter. It > >is also the machine doing my dial out. I didn't even nice it. That is > > I've posted my question to the alt.sci.seti newsgroup. If I knew what was > happening when the client looks at the work unit to evaluate the work unit, > I might be able to figure out whats causing the error :/ > > More info: the fbsd box has a tiny monitor, so I'm not using any gui. > Perhaps I'm missing something that needs to be on the system to check the > work unit correctly? > > Now that the client is installed and runs as nobody, can anyone tell me how > to start it again? What I have done is create an alias called "seti", which places me in the proper directory and then I type "./setiathome". It has been around long enough that I usually type "!105". If I want to stop it, I type ^C and it stops. You restart it and it continues where it left off. The only problem is doing the 2 teraflops of calculations required for each WU. On anything less than a Pentium 400 class machine, that can be a long time. It doesn't stress a machine like a build world does but it keeps your system running at 100% for days. It is very memory sensitive. A computer with PC100 memory has the clear advantage in processing speed when compared to a machine with slower memory. You can also gain insight in to how much a pretty display costs when you compare a command line run on FreeBSD or NT to the Windows GUI version. The command line version for NT and FreeBSD process the data at basically the same rate on systems with the same speed of memory. The GUI adds a factor of 2.5x to the time require to process a WU. Compare a PC100 memoried system to a PC66 memoried system and the PC66 system takes 1.5 times long to process a WU. A Celeron 433 is susposed to have an advantage because the cache is full speed where as a P-II or P-III cache runs a half speed. This is definitly not true with setiathome because you are memory bound and the calculation depends on how fast you can access data, which is dependant on the speed of the real memory and not cache. A P-III 450 slowly pulls away from a P-II 400 but both run away from a Celeron 433. It wouldn't surprise me if a single P-II 400 would out caclulate a dual Celeron'ed system with the slower memory. I'm curious but not curious enough to build such a system. The readme for Unix tells how to add setiathome to your crontab, which sets it up to run automatically in the background with a good nice value. You can also use it to create a new login and other triva. For example, you can stop_after_process or stop_after_xfer. You can also stop after the WU is sent to Berkeley. These are all discussed in the README.TXT. I'm tracking CPU usage and stop_after_process and appeand the result.txt to a result.log and then I continue the loop. I'm only doing this to the Windows NT command line version right now but it wouldn't be any big deal to create a shell script with a loop that would do the same thing for FreeBSD. Kent > > Lastly: Thanks to Dutch Collins and Kent Stewart for the many quick replies! You're welcome. From the statistics there are a lot of us running it and we just happened to still be up at the time. > > -- > Allen Cleveland allenc@mindsieve.com > There is no try. Do, or do not do, but no try. -Yoda > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- Kent Stewart Richland, WA mailto:kstewart@3-cities.com http://www.3-cities.com/~kstewart/index.html SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37A85830.1DA2C817>