I go months some times without powering down my Slackware powered Macbook.

From powerout to powerout

I live in a rural area. All it takes is a lightning strike somewhere near a power line to cause a momentary fluctuation in power, and my system goes down.

Shortest uptime I can recall; about one hour.
Longest uptime: about 11 months.

If that really is a desktop and not a server, you get the "McCann Rude Gesture for Shameless Waste of Natural Resources"!

Used to be, I would never shut down the system, unless I had a kernal update.

But with today’s power hungry CPU’s, I simply can't afford the power bill to keep 3 100watt systems up 24/7.

So they get shutdown when not in active use.

I forgot about power cuts as they cause fewer issues with my desktop uptime since, as stated above, I power it down regularly. However, when I have had machines turned on all the time the maximum time I had between power cuts was around 6 months.

I forgot hibernate -- I can't hibernate my desktop as it seems to cause issues.

I have been a Linux Desktop user for over 10 years. Fedora, Mint, Ubuntu, and finally settled on ZorinOS. For the 10 years, I have NEVER had a system shut-down, crash or otherwise disabled. EXCEPT for when I broke something by "tinkering". No problem, just reinstall. To my knowledge, I have never had a security breech or hack into system or application. Thanks to all the developers who make Linux such a great OS!! I have developed web sites using PHP, Apache2, MySQL in ZorinOS environment. No problems, great response time.

1 members found this post helpful.

I suspend (sleep) it several times a day and at the end of the day to save power with almost instant wake-up. If it is powered up and 15 minutes elapses with no user logged in, it automatically goes to sleep. Every few days I shutdown or reboot it.

If, by uptime, you mean how long has this same computer been operating without failures causing major component replacements, the answer is one thing. If it means how long has this computer been running without significant downtime (2 to 5 hours) for software upgrades, then the answer is quite different.
Answer to the first contingency; over 5 years, due primarily to frequent full backups to separate hard drive. Hard drive fails, boot to the backup, and replace the failed drive.... downtime of less than 30 minutes.
Answer to the second contingency; over 3 years, due primarily to testing potential upgrades or operating system changes extensively on a separate drive before actually making any change.... downtime of less than 10 minutes.

Just to say that I use clonezilla and fsarchiver to do full backups of my machines on a weekly basis ... rolling release generates a lot of updates, so I like to be able to restore/recover only having to deal with up to a week's worth of changes. My main workstation is used as a server for the other smaller machines.
The only places I do Microsoft is with Wine and Virtualbox...

I turn mine off every day (desktop and laptops)!

Less than a day for my laptop; also, I often use suspension to RAM during the day (but I usually shutdown for the night), and never use hibernation.
Boot/shutdown time is just so short that it's not inconvenient at all unless I'm in a hurry and I have lots of stuff open.

I think this thread refers to the uptime command in Linux.

11 minutes

Desktop at home (OpenSUSE 13.2) reboots only when security or kernel fixes are to be installed. Avarage uptime about two months. This desktop is also my web-server.

Desktop at work (OpenSUSE 13.1) reboots on the same arguments, but with more "care", as it also hosts workspace for those poor co-workers that use Windows and sometime may be spoiled using a real OS

Laptop uptime is on average below 48 hours: it reboots on every kernel or security patch available (OpenSUSE TumbleWeed). If restarting X is enough to prevent a reboot, I use that.

Which of those is my main Linux Desktop? They all serve a different purpose and I use them all equally spread over time.