Uptime

Post Reply New Topic

Hey guys,

Uptime thread. Post how long your computer has been without a reboot. Also, inlcude your OS.

Laptop: Windows Vista Ultimate SP1 64 bit - 4 days, 17 hours, 10 mins, 2 seconds (with some sleeping from when I take it to class)

Desktop: Currently Off (it's 80 kilometres away currently)

Server: Windows Server 2003 R2 - 6 days, 5 hours, 9 mins. (it's 80 kilometres away too, at home. When I'm here (at college) I adminstrate it remotely).

This main desktop Ubuntu Hardy Heron (because Irritating Ibex doesn't like my old graphics card), up 20.5 days. I reboot (about 3 minutes, to cycle from Apache shutdown, to webserving again) when a new kernel comes up... eventually. It has had one small period of downtime in the last year and a half. (About a day, while I was doing some hardware tinkering with it. A new router was causing me some grief.)

I forget why I rebooted the Acer Aspire One (Ubuntu Intrepid Ibex), but I did so a couple of days ago. (I vaguely think I just clicked on "restart" rather than "suspend" - I should remove that from the menu.) Otherwise, it would have been a week, since the last kernel update, when it takes about half a minute to reboot with a new kernel and be back online.

The other machines I don't generally leave on.

Hm. My MacBook on Leopard has gone about a month without rebooting before. Since I started using Ubuntu, I will shut it off fairly regularly for various reasons, such as I feel like switching to a different OS or the battery is about to die after I have it out in classes. I think I've gone over a week without a reboot for Ubuntu before. Vista I got to last for about 4 days once before I finally gave up and switched my computer back into Ubuntu.

I have Vista. I have gone four or five days on sleep or hibernate. Then some weird things start to happen. I have a rule which applies to any Micro$oft garbage. When weird things start to happen, do a complete re-boot.

ruveyn

My OS/2 Warp server runs for ages without reboot I don't think it has ever made a whole year yet but it must have been pretty close a couple of times. and it usually is rebooted because I'm messing with the configuration.

Electricity costs too much out here IMO, so I just use /sys/class/rtc/rtc0/wakealarm and a bit of bash where appropriate.

My laptop really must be an oddity, it's underpowered for the 32 bit Vista Home Premium on it, but I consistently leave it on for two weeks plus at a time, occasionally longer than a month (hibernating most every night or when I have to go do something). Nine times out of ten, the only reason I shut it down is for installing an update/program or because I accidentally hit "Shut Down" instead of "Hibernate".

Currently been on for: 6 days, 9 hours.

$uptime
08:45:30 up 17 days, 16:37, ...

So time for reboot:

http://kernelnewbies.org/Linux_2_6_29

Nah. The Ubuntu repositories don't move that fast. The Ibexes (Ibices?) are still on 2.6.27 and this Heron is stuck at 2.6.26, for now.

However... the ext4(no journalling) sounds interesting - for the Acer netbook, as I have yet to get around to correcting the mistake I made, last year, of letting it use ext3 on an SSD. It's not a huge deal, to reformat the file system, although I might just need a reboot at some time, during that process. Maybe I'll wait, and when 2.6.29 is on the repositories (the kernel has been available for two days, already!), I'll see if a skip up from ext3 to ext4 makes more sense than the somewhat retrograde (but sensible) step of going back from ext3 to ext2.

I haven't turned off one of my desktops in about a month or maybe a little longer. I turn off my laptop every day. I see no reason to leave it on when it's in my bag.

You must be doing something wrong. My desktop at home has gone for a month (on all the time) on Vista (just over 32 days, IIRC). And my laptop has been "up" (with sleeping when I take it to class) for a few weeks. What usually takes them down is the need to reboot for an Update, or some software install. I very very rarely reboot just for reboot's sake, or because something's gone wrong.