Re: Burn Testing
cd /usr/ports make all install :-) On 5/24/05, Gaby vanhegan [EMAIL PROTECTED] wrote: On 24 May 2005, at 16:00, Gaby vanhegan wrote: Is there a similar burn-testing app that I can run on OpenBSD to test the stability of the machines over a 12 day period? I should have mentioned that there will be a prize* for the most creative suggestion. Gaby. *There is no actual prize -- Junkets for bunterish lickspittles since 1998! [EMAIL PROTECTED] http://weblog.vanhegan.net
Re: Burn Testing
On 25 May 2005, at 05:34, Sean Brown wrote: On May 24, 2005 9:43 am, Gaby vanhegan wrote: On 24 May 2005, at 16:00, Gaby vanhegan wrote: Is there a similar burn-testing app that I can run on OpenBSD to test the stability of the machines over a 12 day period? I should have mentioned that there will be a prize* for the most creative suggestion. What about simply using stress from ports? This turned out to be the simplest suggestion, and therefore wins a special prize*. What I actually did in the end was: for x in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 do stress --cpu 12 --io 8 --vm 4 --hdd 4 --timeout 14400 sleep 60 echo Test: $x: completed `date` | mail -s stress test $x [EMAIL PROTECTED] sleep 60 done The sleep 60 lets the load drop back to normal, so the MTA will accept connections again, then it gives it 60 seconds to deliver the email before it kicks off again. Repeat that every 4 hours for the next four days. Gaby *There is no actual prize. -- Junkets for bunterish lickspittles since 1998! [EMAIL PROTECTED] http://weblog.vanhegan.net
Re: Burn Testing
* Gaby vanhegan [EMAIL PROTECTED] [050526 17:31]: Ouch ;-) for x in `jot 24 1` is better I think ;-) I tried to use seq, but it wasn't there. Quick to write the numbers than search the man page... /usr/ports/misc/sh-utils if you want (g)seq, but jot is fine.
Re: Burn Testing
On 26 May 2005, at 18:27, Oliver J. Morais wrote: * Gaby vanhegan [EMAIL PROTECTED] [050526 17:31]: Ouch ;-) for x in `jot 24 1` is better I think ;-) I tried to use seq, but it wasn't there. Quick to write the numbers than search the man page... /usr/ports/misc/sh-utils if you want (g)seq, but jot is fine. So, why is there no seq in OpenBSD? I can see that jot fills the gap nicely, and I presume it takes the functionality of some other old gnu apps also? -- Junkets for bunterish lickspittles since 1998! [EMAIL PROTECTED] http://weblog.vanhegan.net
Re: Burn Testing
On 26 May 2005, at 13:53, Gaby vanhegan wrote: This turned out to be the simplest suggestion, and therefore wins a special prize*. What I actually did in the end was: Sorry for replying to my own post, but it seems related. These systems, being SMP systems are using the bsd.mp kernel. I wanted to have the system boot into bsd.mp by default and I did this by: # mv /bsd /bsd.up # mv /bsd.mp /bsd And I can tell it which one to boot into at the boot prompt: boot wd0a:/bsd.up or boot wd0a:/bsd I would have preferred to do this by telling it to boot bsd.mp rather than shuffling files around. I read boot.conf and boot man pages but was none the wiser. How do I point the bootloader at a specific kernel? Gaby -- Junkets for bunterish lickspittles since 1998! [EMAIL PROTECTED] http://weblog.vanhegan.net
Re: Burn Testing
On Thu, 26 May 2005, Gaby vanhegan wrote: On 26 May 2005, at 13:53, Gaby vanhegan wrote: This turned out to be the simplest suggestion, and therefore wins a special prize*. What I actually did in the end was: Sorry for replying to my own post, but it seems related. These systems, being SMP systems are using the bsd.mp kernel. I wanted to have the system boot into bsd.mp by default and I did this by: # mv /bsd /bsd.up # mv /bsd.mp /bsd And I can tell it which one to boot into at the boot prompt: boot wd0a:/bsd.up or boot wd0a:/bsd I would have preferred to do this by telling it to boot bsd.mp rather than shuffling files around. I read boot.conf and boot man pages but was none the wiser. How do I point the bootloader at a specific kernel? set image bsd.mp -Otto
Re: Burn Testing
On Thu, May 26, 2005 at 07:09:21PM +0100, Gaby vanhegan wrote: On 26 May 2005, at 18:27, Oliver J. Morais wrote: * Gaby vanhegan [EMAIL PROTECTED] [050526 17:31]: Ouch ;-) for x in `jot 24 1` is better I think ;-) I tried to use seq, but it wasn't there. Quick to write the numbers than search the man page... /usr/ports/misc/sh-utils if you want (g)seq, but jot is fine. So, why is there no seq in OpenBSD? I can see that jot fills the gap nicely, and I presume it takes the functionality of some other old gnu apps also? I'd guess from the (g) prefix that it's a licensing issue. -- 46. If an advisor says to me My liege, he is but one man. What can one man possibly do?, I will reply This. and kill the advisor. --Peter Anspach's list of things to do as an Evil Overlord
Re: Burn Testing
On Tue, May 24, 2005 at 04:00:20PM +0100, Gaby vanhegan wrote: I have acquired some second-hand dual processor servers with the intention of putting OpenBSD with on them. I have put Debian on one of them and FreeBSD on another, and am pounding them as hard as I can with setiathome to see if they fall over. [EMAIL PROTECTED] touches pretty narrow parts of the system, doesn't it? CPU-bound in userland with little kernel interaction AFAIK...perhaps not the best thing to judge real-world stability by. Is there a similar burn-testing app that I can run on OpenBSD to test the stability of the machines over a 12 day period? Besides maybe some memory access, does running [EMAIL PROTECTED] really show system stability any more than the following shell script shows system stability? while true; do done; I would think running an endless 'make build' loop would be a better indicator than [EMAIL PROTECTED], and thats not to say its necessarily a good indicator ...
Re: Burn Testing
On May 24, 2005, at 11:43 AM, Gaby vanhegan wrote: On 24 May 2005, at 16:00, Gaby vanhegan wrote: Is there a similar burn-testing app that I can run on OpenBSD to test the stability of the machines over a 12 day period? I should have mentioned that there will be a prize* for the most creative suggestion. In that case, I revise my answer. Build -current nonstop, On a self-mounted NFS share, Over a looped-to-self VPN session with 2048-bit keys. :) -- Jason Dixon DixonGroup Consulting http://www.dixongroup.net
Re: Burn Testing
On Tuesday 24 May 2005 11:00, Gaby vanhegan wrote: Hi, I have acquired some second-hand dual processor servers with the intention of putting OpenBSD with on them. I have put Debian on one of them and FreeBSD on another, and am pounding them as hard as I can with setiathome to see if they fall over. Is there a similar burn-testing app that I can run on OpenBSD to test the stability of the machines over a 12 day period? Gaby Building the world is a great test of hardware. Once you've done that, you could build all the packages, another test which has proven to me that hardware I thought was good, was bad. On my 1.7G package builder it takes about 74 hours to build them all, and all of OpenBSD takes about 2:20. You might have to do that several times depending on the speed of your processor. I've never done a package build on an mp system so I don't know the details of that, but I can't imagine that isn't a good test. --STeve Andre'
Re: Burn Testing
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gaby vanhegan Sent: Tuesday, May 24, 2005 11:43 AM To: misc@openbsd.org Subject: Re: Burn Testing On 24 May 2005, at 16:00, Gaby vanhegan wrote: Is there a similar burn-testing app that I can run on OpenBSD to test the stability of the machines over a 12 day period? I should have mentioned that there will be a prize* for the most creative suggestion. Thermite. Ok, maybe try replicating what was done here: http://www.feyrer.de/NetBSD/gmcgarry/
Re: Burn Testing
On Tue, May 24, 2005 at 04:00:20PM +0100, Gaby vanhegan wrote: I have acquired some second-hand dual processor servers with the intention of putting OpenBSD with on them. I have put Debian on one of them and FreeBSD on another, and am pounding them as hard as I can with setiathome to see if they fall over. Is there a similar burn-testing app that I can run on OpenBSD to test the stability of the machines over a 12 day period? Try blogbench: http://blogbench.pureftpd.org/ It stresses a lot your hardware and your OS, and if often triggers kernel panics if something is wrong.
Re: Burn Testing
Gaby vanhegan wrote: On 24 May 2005, at 16:00, Gaby vanhegan wrote: Is there a similar burn-testing app that I can run on OpenBSD to test the stability of the machines over a 12 day period? I should have mentioned that there will be a prize* for the most creative suggestion. Gaby. *There is no actual prize Run john. It really uses CPU. -- Adam Papai Digital Influence Inc. E-mail: [EMAIL PROTECTED] Phone: +36 30 33-55-735
Re: Burn Testing
At 11:41 AM 5/24/05, Niall O'Higgins wrote: On Tue, May 24, 2005 at 04:00:20PM +0100, Gaby vanhegan wrote: I have acquired some second-hand dual processor servers with the intention of putting OpenBSD with on them. I have put Debian on one of them and FreeBSD on another, and am pounding them as hard as I can with setiathome to see if they fall over. [EMAIL PROTECTED] touches pretty narrow parts of the system, doesn't it? CPU-bound in userland with little kernel interaction AFAIK...perhaps not the best thing to judge real-world stability by. Is there a similar burn-testing app that I can run on OpenBSD to test the stability of the machines over a 12 day period? Besides maybe some memory access, does running [EMAIL PROTECTED] really show system stability any more than the following shell script shows system stability? while true; do done; [EMAIL PROTECTED] writes only about 4K to disk once per minute per process. Minimal network traffic to receive work units (240K) send results as required (about 4-12 times per process per day depending on cpu speed).
Re: Burn Testing
What about running [EMAIL PROTECTED] on the openbsd box? I do not test it, but some googling returns interesting urls: http://www.mwjr.btinternet.co.uk/seti/description.html http://setiathome.ssl.berkeley.edu/unix.html On Tue, 24 May 2005 16:00:20 +0100 Gaby vanhegan [EMAIL PROTECTED] wrote: Hi, I have acquired some second-hand dual processor servers with the intention of putting OpenBSD with on them. I have put Debian on one of them and FreeBSD on another, and am pounding them as hard as I can with setiathome to see if they fall over. Is there a similar burn-testing app that I can run on OpenBSD to test the stability of the machines over a 12 day period? Gaby -- Junkets for bunterish lickspittles since 1998! [EMAIL PROTECTED] http://weblog.vanhegan.net -- Perceive that which cannot be seen with the eye. - Miyamoto Musashi - Francisco de Borja Lspez Rmo ([EMAIL PROTECTED]) Csdigo23 - Secure Network Solutions http://www.codigo23.net / http://www.e-shell.org
Re: Burn Testing
On May 24, 2005 9:43 am, Gaby vanhegan wrote: On 24 May 2005, at 16:00, Gaby vanhegan wrote: Is there a similar burn-testing app that I can run on OpenBSD to test the stability of the machines over a 12 day period? I should have mentioned that there will be a prize* for the most creative suggestion. What about simply using stress from ports? Gaby. *There is no actual prize -- Junkets for bunterish lickspittles since 1998! [EMAIL PROTECTED] http://weblog.vanhegan.net
