418 days and near the end (IT related).

[slodave]

My main Linux server in my house is soon to be retired, it's been running here for close to 9 years. It's been currently up for 418 days. It runs Slackware version 10.0, but very customized. The parts are 10 years old and could probably run for another 10 years, but, it's time to shutdown and turn off and install a new, OK, newer server. The replacement is a PIII 550 with a 9 gig primary HD and 15 gig secondary for web and other stuff.

Although there are 4 HD's in the computer, only two are actually still alive and kicking. The cover hasn't been on for about 4 years .

It runs my firewall (IPTables), primary DNS, Apache web server, NATs WAN and LAN. I have another Linux server that is my sendmail server, secondary DNS, MySQL server, RAID storage and more.

I started with Slackware Linux version 1.0 (1993) and have been with it ever since. I am also familiar with Redhat, Fedora flavors. Well, there's OpenBSD and SCO Unix too.




Computer on left is my dead (water pump died) XP wkstation. Middle is my email, MySQL, etc. server (RedHat). Computer on right is the soon to be retired heart of it all (Slackware).

The current specs are:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 5
model name : Pentium II (Deschutes)
stepping : 1
cpu MHz : 233.866 <-- **** I believe it's actually a 333 running @ 233 ****
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr
bogomips : 466.94

21:09:35 up 418 days, 13:22, 1 user, load average: 0.00, 0.08, 0.14
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
slodave pts/0 192.168.0.240 21:00 0.00s 0.25s 0.03s w

Filesystem Size Used Avail Use% Mounted on
/dev/hda1 6.3G 5.1G 844M 86% /
/dev/hdb2 1.9G 34M 1.8G 2% /compile2
redhat:/mnt/raid 123G 64G 60G 52% /mnt/raid

total used free shared buffers cached
Mem: 250 235 14 0 33 147
-/+ buffers/cache: 54 196
Swap: 196 1 195

[Porsche-O-Phile]

I hear ya. Linux rocks. Currently my server has been running for about three years in its current configuration non-stop (well, actually there are a few days when I shut it down for cleaning or to save power in a power emergency, which happens here occasionally). Rock-solid stable. In some respects I wish I were more into computer/IT stuff like I used to be. Casualty of going back to doing architecture again I guess. After spending all day (most days) doing drafting work on a computer, or e-mail on a computer, or writing specs on a computer or whatever else on a computer, it's hard to get excited about building them/understanding them like I once did in my younger days. . .

Congrats on building/keeping up such a robust system!

[beepbeep]

hmm...on my last job I deployed AD main controller for 250 users running W2k on Fujitsu Siemens RX300 server. It run 24/7 for 5 years, never crashed and nothing ever happened except one disk that died and was hot-plug replaced while running.

It hasn't been rebooted for 450 days and runs AD, printers, backup and all home directory's for medium sized company.

How about that? And yes, it's running Microsoft OS.

[slodave]

On the flip side, the first server we built for the first company I co-started, first ran Windows NT Workstation, then Server. It had to be rebooted at least once a day. In all fairness, there was a hardware problem that was never determined, forcing the reboots, but after throwing Linux on that box, it never crashed again.

I don't know Jeff, I fix problems all day for other people. At night, I cause my own problems and find it relaxing to fix them. Although, daytime issues are Windows based, nights are Linux and more of a hobby these days and to keep me current. I do burn out a couple times a year and since it's how I make my living, I can't get away from it, which puts me in a very bad mood during those periods.

[svandamme]

hmm, Novell once had to go onsite, to help track down a ghost Netware server
customer knew it was there, running,it was maintenance free, just worked, and the IT team lost track of it's location over the years

turns out, somebody had bricked up a wall at some point and the server was behind that wall
somebody must have read a book about security, and took the "secure physical access to the machines" a little bit to serious

[slodave]

Takes firewall to a whole new level.