🌟🎀 uptime check ✨🌈💖
22:09:13 up 9 days, 12:29, 2 users, load average: 0.03, 0.05, 0.11EDIT: wait why does it say 2 users though 😳
EDIT: wait why does it say 2 users though
Sorry about that, won’t happen again
“Shutdown off”
It’s an alias for “sudo shutdown now”.
If you don’t have a UPS, just use a suicide cable to energize the circuit while it is disconnected at the breaker.
(/s, if the term suicide cable wasn’t enough of a hint; don’t actually do this)
i know the OP was about server, but just curious how long is every one’s uptime on laptop / desktop?
I’ve had a year or two. But kernel updates make reboots. My FreeBSD boxes are much more long-lived than Linux because kernel updates
but just curious how long is every one’s uptime on laptop / desktop?
Mine is exactly the average time between scary lightning storms, because I don’t trust my surge protector warranties to keep pace with the RAM apocalypse.
I turn my desktop and laptop of when not in use.
Anything between 5 minutes and 5 days, including those numbers as well. The more you approach the midpoint between those 2 numbers, the odds of that being near my uptime are lower
Ironically, this was one of the primary reasons I have a UPS on everything. The uptime must grow.
shutdown off
In English, that’s “shut down”.
deleted by creator
“Shutdown off”
“Openup on’t”
All your base distribution are belong to
Do y’all not reboot after kernel/firmware updates?
I don’t follow CVEs: when was the last time a remotely exploitable kernel bug was a concern? Ignoring the fact that this is a home server and they likely care about uptime a lot more than exploitation on their LAN.
Generally I expect kernel bugs to be LPEs so updating user space would probably be sufficient for most home servers
Hmm, not my proudest moment.
16:09:15 up 1031 daysPrivate server, though.
Almost 44 days last year before I needed to reboot for an update:
part of the reason to use Debian is it doesn’t really need to be updated, at least not very often
It needs to be updated at least several times a year…
depends on your use case
home automation server that doesn’t connect to the internet? nah
media server that only occasionally gets connected to the internet? maybe
anything else that regularly connects to the internet, definitely
You should install updates regardless
if it’s working and there’s no security risk, why?
(I mean, I actually agree with you, I update even normally airgapped machines because them not being updated feels wrong)
Software these days will always need security patches
What’s more is that the longer you put off updating the more things will be changed when you do end up updating.
Even if there are no security risks to mitigate, updates can bring bug fixes and, god forbid, new features once in a while.
New features on Debian isn’t something that would make it into the repository. Bug fixes might but only if security relevant.
I’ve been running the same AIX kernel since 1993, and my ftp server is still running fine. I don’t know what the rest of these assholes are complaining about.
Prefect response.
I can’t guess exaclty which sarcastic high fantasy themed poster, mug or t-shirt warns others away from which exact kind of action that wastes your time, but I’m confident it is present near your primary work space. (Since tone is hard in text - this assumption is meant to convey a general revernce for you and the various roles you probably fill in your communities!)
up… date? what does that mean?
Say what now?
Rolling distros don’t need to
You absolutely do need to reboot
Laughs in kexec
It is way easier to just reboot
Ah, this brings back memories of flashing Android with various kernels and ROMs.
They absolutely do. There’s nothing special about them vs normal distros. Hell rolling ones probably get new kernels more often and you can only live patch so much. Some updates just hard need a reboot to take effect.
Just because you updated packages , doesnt mean those new ones are in use. Not sure what apt has, but with zypper you do a zypper ps -s and it shows you what installed packages are waiting on a reboot or service restart before they are in play… Otherwise kernel is just accessing old package libraries.
Are you sure? I’ve used Fedora Workstation and Fedora Server, I had to reboot. And Cannonical charges money for this feature in Ubuntu.
The UPS will keep it running long enough to switch to another power source.
I’m guessing OP probably doesn’t have a petrol/diesel generator handy :p
An extension cord running to another room would be enough if the minor electrical work only needs a circuit to be switched off.
My UPS just runs on a lead battery. It lasts long enough to run my router and server for a few minutes and cost less than 100€.
I got it when we had electrical issues and using the ironing board would trip the main fuse.
Yeah, I was thinking a UPS wouldn’t hold a load up long enough to do electrical work, but I guess it depends on the nature of what needs to be done
If one is not enough just daisy chain two or three of them.
(Don’t do this)
We had some very large UPSes at work that would be able to keep a server up for hours, but they’re also so heavy it would probably cause the floor in my living room to collapse :p
Having high uptime is not the flex you think it is
You shouldn’t have uptime higher than 60 days
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.
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.
Maybe they’re kexec-ing.
uptime should be handled by the kernel, so a kexec “soft-reboot” would still reset the uptime.
Well proxmox is based on Debian so it’s technically included in the original meme
Yes
Shitting down & spinning shit up is something I still practice more often than restoring backups (I don’t run test instances).
I too practice shitting down.
But do you not then spin that shit right up again??
Just wear rubber boots and gloves and leave the electricity on
I was vacuuming and accidentally pulled the cord on a 3 month uptime.
My current uptime has survived 2 power outages that lasted about 10 minutes each.
small uninterruptible power supply could be pretty useful
