Printable View
It was a tragedy! My workgroup's web / email / print server (it also serves a few files over samba & nfs) crashed after 497 days of uptime. It's running some older version of Mandrake (6.0 I believe). I suppose this proves Steve Ballmer's point that linux is truely a cancer and plague on everything it touches.
...let's see Win NT / 2000 maintain 497 days of uptime running on a puny old K6-200 with 64M of ram and IDE disks!!!
-Bash
Wanna join the Linux Hippy Club? You look like a serious Linux user.
------------------
"There are nights when the wolves are silent and only the moon howls." - George Carlin
SF Linux Hippy Club President
Proud Linux Hippy
Well, my FreeBSD user friend had 2k running on a laptop with 96M of RAM and a P-166 ( i think) for 6 months. Granted, that doesnt come close to 497 days tho.Quote:
Originally posted by Bash:
It was a tragedy! My workgroup's web / email / print server (it also serves a few files over samba & nfs) crashed after 497 days of uptime. It's running some older version of Mandrake (6.0 I believe). I suppose this proves Steve Ballmer's point that linux is truely a cancer and plague on everything it touches.
...let's see Win NT / 2000 maintain 497 days of uptime running on a puny old K6-200 with 64M of ram and IDE disks!!!
-Bash
------------------
------
Pat D.
Visit a music site I write for:
http://www.geocities.com/mjareviews
Quote:
Originally posted by Bash:
It was a tragedy! My workgroup's web / email / print server (it also serves a few files over samba & nfs) crashed after 497 days of uptime. It's running some older version of Mandrake (6.0 I believe). I suppose this proves Steve Ballmer's point that linux is truely a cancer and plague on everything it touches.
...let's see Win NT / 2000 maintain 497 days of uptime running on a puny old K6-200 with 64M of ram and IDE disks!!!
-Bash
Wow... nothing like REALWORLD ACTUAL PROOF that something works...
I am not even sure if Windows 2K HAS been out that long.
------------------
"Given enough time and money..Microsoft will eventually invent a Unix." - ME
Why Yes! I am a proud member of the SF Linux Hippy Club.
It would be an honor. https://www.sharkyforums.com/images/.../2005/06/5.gifQuote:
Originally posted by Digital Froggy:
Wanna join the Linux Hippy Club? You look like a serious Linux user.
-Bash
I have a couple of DNS(secondary) servers running Bind 4 on linux 5.0 that have been running for over 500 days. I have been debating weather to reboot them or just let them go and see how long the will run. They are like a comfortable old freinds: they're always there.
I have been building new DNS servers with Redhat7.1 and am very impressed by the performance gains, so the older bind 4 servers may be updated anyway. Any thoughts?
------------------
BP6 with dual 366@550 and loving it
Couldnt you just let them keep going, but if you had to you could replace them and turn bind off and/or change their IP... unlike WINDOWS you can do that and KEEP them running https://www.sharkyforums.com/images/.../2005/08/2.gifQuote:
Originally posted by PDR60:
I have a couple of DNS(secondary) servers running Bind 4 on linux 5.0 that have been running for over 500 days. I have been debating weather to reboot them or just let them go and see how long the will run. They are like a comfortable old freinds: they're always there.
I have been building new DNS servers with Redhat7.1 and am very impressed by the performance gains, so the older bind 4 servers may be updated anyway. Any thoughts?
They have given you so much, let them die in their own time.
------------------
"Given enough time and money..Microsoft will eventually invent a Unix." - ME
Why Yes! I am a proud member of the SF Linux Hippy Club.
I've never understood the whole uptimes thing myself. 497 days is damn impressive, but that means that you have been running the same kernel for a year and a half.
It opens up a whole range of security issues... I always get worried when working on a box that has been up for more than about 60 days.
True true, but the uptimes are still pretty impressive!
Hehhe, our production Database Server at work which is running MSSQL 7.0, and Win2k Server, has been up for the past 10 months, we haven't touched the thing. I'm interested to see how long it will go...though...we should take it down to install SP2 on it someday...would probably be a good idea.
It reminds me of this wonderful story though: http://content.techweb.com/wire/story/TWB20010409S0012
Quote:
Server 54, Where Are You?
April 9, 2001 (4:28 p.m. EST)
TechWeb News
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.
Oh man, that's great!
I have also heard of a warehouse type place who got a 386 when it was the top of the line and installed linux on it. The machine was just used to enter items into a database and became so grungy after MANY years that the hardware itself failed, but the OS never did. The uptime was around 6 years! Their reaction was "well now that we have to get a new machine, I guess we can get rid of this 1.x kernel we've been using and go with something a little more modern". LOL
------------------
"Software is like sex, it's better when it's free"
--Linus Torvalds
LOL! that's great man heheheQuote:
Originally posted by sourdaisy:
Oh man, that's great!
I have also heard of a warehouse type place who got a 386 when it was the top of the line and installed linux on it. The machine was just used to enter items into a database and became so grungy after MANY years that the hardware itself failed, but the OS never did. The uptime was around 6 years! Their reaction was "well now that we have to get a new machine, I guess we can get rid of this 1.x kernel we've been using and go with something a little more modern". LOL
------------------
I wish I hadn't eaten that gravy packet I found in the parking lot...
nice...hey, I could get Win98 to go without crashing for longer than that. of course, I'd have to never turn the computer on, but still, uptime is uptime.
uhhh, uptime means that the OS has to be running. ;-)Quote:
Originally posted by qwex:
nice...hey, I could get Win98 to go without crashing for longer than that. of course, I'd have to never turn the computer on, but still, uptime is uptime.
I bet win98 could stay up that long, but you wouldnt be able to touch it while it was running. ;-)
------------------
------
Pat D.
Visit a music site I write for:
http://www.geocities.com/mjareviews
That's just funny.Quote:
Originally posted by blppt:
I bet win98 could stay up that long, but you wouldnt be able to touch it while it was running. ;-)
------------------
Size does matter, unless yours is bigger than mine.
Resistance is futile.
Yahoo! Messenger ID: ntfanboy <---- Talk to me.
Nah, Win98 (I think), and definetely Win95 keel over after 50 or so days, because it uses a 32 bit number to store uptime, and keeled over if it somehow managed to stay up that long.
I wasnt even aware that win98 kept track of how long it was up. Kind pointless isnt it? Best i ever did with 98 was 7 days uptime, and i havent gotten close to that ever again. ;-)Quote:
Originally posted by port22:
Nah, Win98 (I think), and definetely Win95 keel over after 50 or so days, because it uses a 32 bit number to store uptime, and keeled over if it somehow managed to stay up that long.
------------------
------
Pat D.
Visit a music site I write for:
http://www.geocities.com/mjareviews
Yeah, even so, you'd have to patch your system because there's a problem with one of the files that'll BSOD if the uptime gets to be 42.7 (?) days. I think this affects win98 as well.Quote:
Originally posted by port22:
Nah, Win98 (I think), and definetely Win95 keel over after 50 or so days, because it uses a 32 bit number to store uptime, and keeled over if it somehow managed to stay up that long.
When I did have windows installed, I never patched it cause its not like I came close to having that long of an uptime anyway. I think I managed to keep it up for over a week and ended up rebooting cause the machine went into suspend mode and wouldn't wake up. OH well, windows seems like its built to be rebooted so often. I have to say, though, that win2000 is much better and I have left it up for the better part of a month before it needed rebooting.
------------------
"Software is like sex, it's better when it's free"
--Linus Torvalds
We could be talking about the same thing...Quote:
Originally posted by sourdaisy:
Yeah, even so, you'd have to patch your system because there's a problem with one of the files that'll BSOD if the uptime gets to be 42.7 (?) days. I think this affects win98 as well.
2^32 = 4294967296
4294967296 ms = 49.7 days
Maybe... Either way, keeping up a leaky OS for that long is bad.
Yup, sure sounds like we are talking about the same thing. I just couldn't remember the exact time before it BSODs. But you are absolutely right, even IF you could get it to run that long, it wouldn't be a great idea.Quote:
Originally posted by port22:
We could be talking about the same thing...
2^32 = 4294967296
4294967296 ms = 49.7 days
Maybe... Either way, keeping up a leaky OS for that long is bad.
------------------
"Software is like sex, it's better when it's free"
--Linus Torvalds