Hardware errors often cause system instability hence this is false.
this post was submitted on 10 Dec 2025
1031 points (98.0% liked)
linuxmemes
28397 readers
395 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn, no politics, no trolling or ragebaiting.
- Don't come looking for advice, this is not the right community.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
founded 2 years ago
MODERATORS
How false are we talking? A couple seconds? Minutes?
A lot of windows errors are actually hardware acting up. Such as an aggressive overclock or random issues.
An operating system cannot prevent that
how long since the boss has been asleep so you can finally restart without them calling two seconds later cause they didn't bother reading the scheduled downtime email
Are we not doing kernel upgrades?
Yeah thatβs about the only time I have to do reboots at work which are 99% linux. Well the production ones anyway.
Or the other reason is my lab having power issues due to malfunctioning UPSes, faulty NEMA L6-30 plugs, janky 240v circuit breakers orβ¦ Iβm beginning to think my lab is electrically cursed.
While technically the truth, it can be a hassle to make sure you restart all relevant services after updating a given library.
I just like being able to restart underlying system to take care of any possible straggler without thinking, and the services broadly be provided by multiple systems so the "experience" is starting up through a rolling reboot
Was about to say, "or if you're running Arch, the last time you updated the kernel or systemd version, so probably last week or summit."
Pretty sure everybody is missing the joke. The joke is that Debian packages are so stable and stale that you likely will need a reboot before an update.
Also, it's a joke....please patch your boxes, k?
I've got a patch in my boxers right now.
Oh boxes.
I got obsessed with uptime in the early 2000s, but for my desktop Slackware box. It ran a bunch of servers and services and crap but only for me, not heavy loads of public users. Anyway, I reached 6 years of uptime without a UPS and was aiming for 7 when a power outage got me.
Skill issue. Next time you can open up the computers power supply while itβs running, splice in a second power cable, and attach a UPS without powering down or getting electrocuted.
For legal reasons, /s
Not sure what your signature is supposed to do here but now I have 3rd degree burns and a fireball has engulfed my office wall
But more importantly, did your uptime get reset?
Debian admin here. Even Debian gets regular kernel upgrades that like a reboot afterwards. Security updates are more important than uptime. Also regular testing for clean recovery after a reboot is a must so a power outrage doesn't bring any new surprises with it. Also test your backup restores regularly.
As someone running a UPS on my ubuntu server, "uptime" represents the time since the last kernel release, and not much else.
Novice homelaber here, is this just a case of apt update & upgrade or is there different commands for security and kernel updates? Also whatβs your preferred backup/restore software? Thanks!
Nope it's just apt update & upgrade. Iirc apt tells you when the kernel was updated and needs a reboot as well.
load more comments
(5 replies)
load more comments
(9 replies)
load more comments
(6 replies)
βUptimeβ β aka the anxiety meter for every sysadmin.
Or if you have a UPS and backup generator or a house battery (do these need a UPS as well still?) it will tell you how long since you setup the system.
I would suspect you would still want a UPS. I don't think house "power" setups have the switch over speed even if they're automatic. Most home generator setups are manual not sure about battery setups.
load more comments
(3 replies)
How do I check when the last power outage was if it's connected to a UPS?
Thatβs ridiculous. Itβs much more complicated than that.
You need to check NUT.
Deez? π°πΏοΈ
My father was an HPUX admin that had a server with an uptime of >12 years
I was introduced to homelab by trying to figure out how my uncles setup. It ran for 4 years after he died, 11 years uptime. The estate probate prevented anyone from touching the equipment for the legal fights, and I get a kick out of thinking of how smug he would have been about it.
Heard of tuptime? I've been using it for a while now, I think I like it.
System startups: 151 since 18:00:05 10/11/15 System shutdowns: 137 ok + 13 bad System life: 9yr 223d 1h 27m 47s
Longest uptime: 106d 5h 34m 28s from 14:17:10 26/03/22 Average uptime: 23d 4h 32m 0s System uptime: 99.81% = 9yr 216d 12h 31m 51s
Longest downtime: 4d 23h 30m 48s from 10:36:53 14/09/23 Average downtime: 1h 2m 46s System downtime: 0.19% = 6d 12h 55m 56s
Current uptime: 25d 0h 34m 25s since 20:25:37 15/11/25
Heard of it for the first time (as far as I can remember) a couple days ago, on Lemmy.
TIL, Lemmy's educational.
load more comments
(3 replies)
Does NixOS apply kernel updates live? I can't recall from when I used it.
Mine doesn't. I reboot when I get a new kernel.
step 1: sudo apt install sl
step 2: fuck up
step 3: ???
step 4: profit!!!!
load more comments
(5 replies)
On my Gentoo server, uptime:
- 21:47:56 up 2455 days, 15:09, 1 user, load average: 0.00, 0.01, 0.00
Solid.
Would have been double that by now if not for the fire.
You forgot to say "this is fine", I take it?
Joking aside, I hope you didn't lose anything. Was it a big fire?
Those who manage the dedicated server racks service kept my stuff intact. Thankfully. Just disrupted my uptime.
[User "error" since, has cost me a TB of data. "Error", fearquoted, because it was intentional... probably unnecessary clearing of space, partly regretted since.]
I don't know how big the fire was, happened over 1000 miles away from here.
So, it really was fine. :3
ππ Good to hear
view more: next βΊ