Date: Sat, 17 Nov 2001 20:08:00 -0800 From: Kent Stewart <kstewart@owt.com> To: Anthony Atkielski <anthony@atkielski.com> Cc: FreeBSD Questions <freebsd-questions@FreeBSD.ORG> Subject: Re: Mysterious boot during the night Message-ID: <3BF73420.2040806@owt.com> References: <20011117130052.B7072@mars.thuis> <020e01c16f42$14885c10$0a00000a@atkielski.com> <20011117015632.B87944@xor.obsecurity.org> <02a001c16f53$215323b0$0a00000a@atkielski.com> <3BF63DB1.1070008@owt.com> <02a701c16f5e$a9cb0c70$0a00000a@atkielski.com> <020e01c16f42$14885c10$0a00000a@atkielski.com> <20011117015632.B87944@xor.obsecurity.org> <02a001c16f53$215323b0$0a00000a@atkielski.com> <3BF63DB1.1070008@owt.com> <20011118102106.C72712@monorchid.lemis.com> <3BF71585.6090104@owt.com> <034a01c16fd9$f5e75750$0a00000a@atkielski.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Anthony Atkielski wrote: > Kent writes: > > >>Most of the people I know run setiathome >>in a script. >> > > I have a user account set up with setiathome as its shell. You login, and SETI > runs until you interrupt the program. It seemed secure. > I also login in to run setiathome but then I start a script called runseti # and it starts with what ever you supply instead of the #. This allowed me to capture all of the state.sah's before I ship them to Berkeley. I can go back and look at the peaks and what ever. I was using the processing times to compare systems. I concatentate the finished state.sah on to the end of a file called result.log. When it gets above 400KB and I notice it, I rename it and gzip it to make it smaller. There is quite a large difference between wu's but after you have run around a 100 or so, things start leveling out. I have two P-II 400s that process with a 10% difference in rate. I saw the 10% at 100 wus and it was very close to the same rate when they had each processed 1000 wus. Never did figure out why they are different. I assume one mb was faster than the other and eventually stopped being curious. Some time ago, I tried overclocking a Celeron 300a and found that building XFree86-3.x.x and running setiathome was too much and cooked the Celeron. The build required several hours. I could do build worlds just fine but the build of XFree86 stressed the system more. Kent -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://users.owt.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ 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?3BF73420.2040806>