Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
User Journal

Journal grub's Journal: 1000 day uptime 11


Ok, first off: I know "I haev teh l337x0r5 uptime" boasts are lame but this has me happy at some 14-year-old-who-just-installed-linux level:

$ uptime
3:43PM up 1000 days, 16:40, 2 users, load averages: 0.27, 0.06, 0.02

It's an ancient Pentium 166 MMX running FreeBSD 3.3 (OLD!) but has had all services touching the net up to date. The machine is well firewalled off and all packets hitting it are scrubbed with pf.

Look at all that disk space:

$ df -k
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/wd0s1a 119055 34449 75082 31% /
/dev/wd0s1f 2887188 2118030 538183 80% /usr
/dev/wd0s1e 992239 162634 750226 18% /var
procfs 4 4 0 100% /proc

This machine was at an uptime of 683 days but a power failure which lasted long enough that the UPS failed happened 1000 days ago today.

When we moved our offices in the house around I carried this computer while Kim carried the chirping UPS along. Anything to keep the uptime... :)

Funny, other machines I have get upgraded every 6 months (OpenBSD) or every day (Windows) and I don't care about reboots. I also have a newer machine which is ready to drop into service when this one chokes but this old crapbox has a lot of nostalgic value for me. I have no idea why. It's weird to think that this has been running since well before we talked about having kids (our daughter is 18.5 months old now).

What's your lame uptime story? What have you done to keep the uptime going? We all have a story like this to own up to...

This discussion has been archived. No new comments can be posted.

1000 day uptime

Comments Filter:
  • The best I managed with my old web server was a bit over 500 days, but unfortunately the ISP moved its server farm and had to shut it down. I finally retired that server -- a Duron 800 with a heavily patched Red Hat 5.0 system -- last spring. While it used to easily get uptimes of well over 200 days (broken only by kernel upgrades), towards the end it was getting extremely flaky and would only manage a few days before needing a reboot.

    My current hosted server is a Mac mini running Ubuntu, and is doing qui

    • by nizo ( 81281 ) *

      April 09, 2001 (1:28 PM EDT)
      Server 54, Where Are You?

      The University of North Carolina has finally found a network server that, although missing for four years, hasn't missed a packet in all that time. Try as they might, university administrators couldn't find the server. Working with Novell Inc. (stock: NOVL), IT workers tracked it down by meticulously following cable until they literally ran into a wall. The server had been mistakenly sealed behind drywall by maintenance workers.

      Speaking of which, I had to

      • This morning, there I was, tracking down a race condition, when Windows told me it wanted to update. Fine, whatever, "You can continue working while Windows installs updates", right? Except when it finished, it harassed me every five minutes until I gave in and rebooted.

        I've got a Windows VM that's got an uptime of a few months, but that's only because it spent most of that time paused.

        The best part about work is coding. The best part about going home is settling into my Linux desktop. :-) (The worst pa
        • by grub ( 11606 )
          Except when it finished, it harassed me every five minutes until I gave in and rebooted.

          I hate that. Type net stop wuauserv at a command prompt and it kills that annoying message.

          • by nizo ( 81281 ) *
            Holy crap, thank you for that info. That made my day.
            • by grub ( 11606 )
              Heh, no problem.
              I use it enough that I made a .bat file on my desktop which does it. :)
              • by nizo ( 81281 ) *
                Half the time when I am doing click-battle with the server, I worry that the "reboot now" will get clicked accidentally. I submit this stupidity as further proof that Microsoft servers suck stinky donkey balls.
    • Another favorite of mine is from the old keykos operating system [eros-os.org] which is designed to implement continuous persistence so you could cut power to a running system, start it back up again, and be back exactly where it left off with everything still running:

      At the 1990 uniforum vendor exhibition, key logic, inc. found that their booth was next to the novell booth. Novell, it seems, had been bragging in their advertisements about their recovery speed. Being basically neighborly folks, the key logic team suggested the following friendly challenge to the novell exhibitionists: let's both pull the plugs, and see who is up and running first.

      Now one thing Novell is not is stupid. They refused.

      Somehow, the story of the challenge got around the exhibition floor, and a crowd assembled. Perhaps it was gremlins. Never eager to pass up an opportunity, the keykos staff happily spent the next hour kicking their plug out of the wall. Each time, the system would come back within 30 seconds (15 of which were spent in the bios prom, which was embarassing, but not really key logic's fault). Each time key logic did this, more of the audience would give novell a dubious look.

      Eventually, the novell folks couldn't take it anymore, and gritting their teeth they carefully turned the power off on their machine, hoping that nothing would go wrong. As you might expect, the machine successfully stopped running. Very reliable.

      Having successfully stopped their machine, novell crossed their fingers and turned the machine back on. 40 minutes later, they were still checking their file systems. Not a single useful program had been started.

      Figuring they probably had made their point, and not wanting to cause undeserved embarassment, the keykos folks stopped pulling the plug after five or six recoveries.

  • "df -h" all the way!
     
  • I was working in the Netherlands for a while. I stuck my home computer into the server room at the office back in the States. Windows 95 rolled out while I was over there, and all the fanboys started ooohing and aaaahhing over their suddenly "reliable" computers. Reliable compared to MS-DOG, maybe.

    On one forum the guys were bragging about their Win 95 boxes and I just pointed out that I was reading the Usenet on a PC running Linux. And that box was 5000 miles away, and I was pretty sure I wouldn't have to r
    • Heh. On the other side of things, at around the same time I was working at a Web agency, where I was using a Mac (being a design monkey), and most other people there were also using Macs, while one of the two owners used Win95 and thought it was teh bomb. Meanwhile our resident programming god used an early version of SuSE on a build-your-own PC, and I was bemused at how he got excited when he installed KDE and was proud to have a trash can. :-D

      That was my first introduction to Linux, but it apparently di

Those who can, do; those who can't, write. Those who can't write work for the Bell Labs Record.

Working...