this post was submitted on 28 Apr 2026
624 points (97.3% liked)
linuxmemes
31219 readers
1591 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Having high uptime is not the flex you think it is
You shouldn't have uptime higher than 60 days
I tried telling this to my manager for years. He saw it as a "X days since we last had a problem and needed to reboot the server" and took pride in it.
We finally shut it down at over 5 years of uptime. Some docker containers had been running for 4 years straight.
Yes, that means what you think it does concerning update policies. Yes, the server and some containers were exposed to the internet. No, the backups were never tested.
Yeah these days a high uptime is a mark of shame, not a badge of honour.
Why, by the way?
If a device hasn't been rebooted in a long time there is a much higher chance of it not coming back after a reboot. This is made worse by the fact that sometimes power loss is unexpected which means that an outage can occur at a bad time.
The other issue is that a high uptime device doesn't usually have the latest updates installed. Delaying updates creates security issues and when you do get around to updating it means that more things get changed at once.
The reverse is that if you really know your stuff you can get away with fewer restarts, or even none. But you pretty much have to know every component and update you run while in that untested state.
This is similar to bugs that go away on a restart. If you don't know why, then you haven't really fixed it, just rolled the dice again hoping it won't reoccur.
As for updates, on regular systems you can do update everything but the kernel. You do have to restart affected services afterwards (often done automatically).
Even on atomic systems you can switcheroo the subvolume underneath a running system.
Unfortunately the kernel is quite major, so that is a valid reason to see the need to update. Definitely not as pressing as say nginx, sshd, or sudo though. Kernel bugs bubbling up to an exposed attack surface is still quite unusual.
Maybe they're kexec-ing.
uptime should be handled by the kernel, so a kexec "soft-reboot" would still reset the uptime.
Modular custom single-program kernel running in a VM live migrated across a cluster?
No security revisions over multiple months?