Paul D. Ouderkirk » linux

Server Burn-in

admin — Fri, 06 Mar 2009 23:42:08 +0000

I used to burn-in new servers by having them compile MySQL from source in a loop for 24-48 hours, but let’s face it, that’s not much of a challenge for today’s servers.

You know what is? Building OpenOffice.org.

On Debian Lenny, here’s the shortest path:
# apt-get install build-essential dpkg-dev pbuilder # apt-get source openoffice.org # apt-get build-dep openoffice.org # cd openoffice.org-2.4.1 # debuild -us -uc

On a Sun x4100 with dual Opteron 275s and 8GB RAM, this takes about 5.5 hours, and uses way more disk I/O and memory than a mere MySQL compile.

Run this 4-5 times and you can probably feel pretty safe that your server won’t burst into flames at 3AM the day after you deploy it in production.

Airing of Grievances, part two

admin — Thu, 11 Dec 2008 14:04:59 +0000

Who picked these example cities for timezones in Canada? Dawson *and* Dawson Creek? (populations: 1,327 and 11,811, respectively).

Atikokan?!? (population:3,293) I wasn’t even sure what province this one was in, I had to look it up.

Airing of grievances, part one.

admin — Tue, 11 Nov 2008 20:37:00 +0000

Default install of OpenSUSE 11 (meaning I didn’t explicitly include or exclude any particular software packages during the installation).

Comes with OpenOffice.org, Banshee (media player), F-Spot (like iPhoto) and Firefox.

Not included? A whois client.

OLPC XO-1 /proc/cpuinfo

admin — Thu, 06 Nov 2008 03:51:33 +0000

[olpc@xo-11-42-2b ~]$ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 5 model : 10 model name : Geode(TM) Integrated Processor by AMD PCS stepping : 2 cpu MHz : 430.931 cache size : 128 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu de pse tsc msr cx8 sep pge cmov clflush mmx mmxext 3dnowext 3dnow bogomips : 863.19 clflush size : 32

Chumby /proc/cpuinfo

admin — Thu, 06 Nov 2008 03:41:55 +0000

chumby:~# cat /proc/cpuinfo Processor : ARM926EJ-Sid(wb) rev 4 (v5l) BogoMIPS : 174.89 Features : swp half thumb fastmult edsp java CPU implementer : 0x41 CPU architecture: 5TEJ CPU variant : 0x0 CPU part : 0x926 CPU revision : 4 Cache type : write-back Cache clean : cp15 c7 ops Cache lockdown : format C Cache format : Harvard I size : 16384 I assoc : 4 I line length : 32 I sets : 128 D size : 16384 D assoc : 4 D line length : 32 D sets : 128

Hardware : Freescale MX21ADS Revision : 0000 Serial : 0000000000000000

Progress indicator from dd

admin — Wed, 22 Oct 2008 17:44:14 +0000

Yes, you can get a progress indicator from dd. Here’s the relevant section from the GNU dd manpage:

Sending a USR1 signal to a running `dd’ process makes it print I/O
statistics to standard error and then resume copying.

$ dd if=/dev/zero of=/dev/null& pid=$!
$ kill -USR1 $pid; sleep 1; kill $pid

18335302+0 records in 18335302+0 records out 9387674624 bytes
(9.4 GB) copied, 34.6279 seconds, 271 MB/s