So, you never update the kernel?
@NullPointerException @yesman debian never updates it
My father was an HPUX admin that had a server with an uptime of >12 years
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.
My home generator is automatic but you still need an ups because the transfer switch and power on process for the generator isn’t instant. Takes like 10-30 seconds depending on how cold it is and how recently I serviced the generator.
You also ideally need a higher quality ups that can handle the shitty power coming from a generator, although the overall ups doesn’t need to be as “hefty” as a result. My ups is the kind that has extra filtering and stabilization of incoming power. My old ups was a cheaper cyberpower and it died after a few months of generator usage (we lose power here roughly every 4-6 weeks, thus the auto generator). The cheaper cyberpower would be fine in the majority of home circumstances tbh otherwise.
Battery should be automatic, but yeah not certain how quick the switchover is. At least you could go for the smallest capacity UPS there is as long as it can manage the wattage you are going with.
Are we not doing kernel upgrades?
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.”
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?
At some point when I am less busy again I think I am gonna swap back to a debian based system because my experience on arch and red hat systems just hasnt been as good (this may be because I started on Debian based systems and keep trying to use commands that dont work on the other ones out of muscle memory)
I get bored every so often and move all the important stuff to an external drive or a separate internal one and completely change my os
I am on manjaro but I have also run arch, red hat, void, mint, Debian, Ubuntu and a bunch of others that I either put on laptops or something similar as messing around with devices
Tails and slitaz have to be my favorite to run from a USB but peppermint isn’t the worst
I just did the contrary. Moved from debian to arch. After the update to trixie my network stack completely died somehow, so I’m going back to arch.
I have had minimal issues from my manjaro desktop but I just dont like it as much as my mint based systems because everything feels wrong and I can barely remember how to update my graphics drivers on manjaro vs mint where I am confident I could run my entire system mostly command line from installs to updates and random other shit that I just can’t remember how to do through arch systems because I dont run them as hard for some reason
Why type
uptimewhenwis sufficient?What the hell!?
?
“Uptime” — aka the anxiety meter for every sysadmin.
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.
Huh. Only 11 days on the Raspberry Pi I’m using as a “desktop system” right now. (Arch Linux Arm, btw… though Arch Linux Arm sucks now-a-days.)
Let’s check my RPi-based NAS:
[tootsweet@mynasserver ~]$ uptime 19:56:07 up 212 days, 18:43, 4 users, load average: 0.16, 0.04, 0.01Also not as long as I’d have guessed.
My RPi uptime on one project will never exceed 4 hours.
I’ve got a cron job set to reboot my Raspberry Pi every 4 hours because I wrote a crappy Python app that continuously creates objects during operation that I would have to recreate, but I can’t delete the originals, or rather, I can delete the original parent but the child survives and keeps its memory allocation. So a full reboot with autolaunch of the application on boot is my ugly janky workaround. Its a cosmetic application, nothing critical. Its just a colorful display of data metrics.
I can hear the horror and gnashing of teeth of real developers as they read this.
As a real developer…
I just remember that airplanes have “reboot the plane every 51 days” to prevent an overflow from crashing the plane in their maintenance manuals
So, like, yours can be improved, but it’s not safety critical like other reboot requirements…
I’m a sysadmin and I’m weeping, gnashing my teeth and rending my garments. 😆 And I’ve never done anything janky like that. Ever.
Oh, there’s even more jank in this thing than the reboot workaround described above!
I have 3 windows displaying different metrics on this display powered by the RPi. Because of the animation of each metric rendered on the display, higher value metrics will consume more CPU. Since each is a separate process, the animation in the displays would be different for each window by without any modifications. So to make each of the 3 display’s animations operate at the same relative speed, I do a calculation of how the number of objects being displayed for the metric, then add an amount of invisible (well, black on black) objects to each window so to equal a fixed amount of the animation speed I want resulting in each window having the exact same number of objects and the animations move at the same speed.
This works surprisingly well. The only time I have to monkey with the fixed value is if I’m using it on faster or slower Raspberry Pis. For example, I’ll have a lower number of final fixed objects for an RPi 3 rather than a higher number of fixed final objects for a faster RPi 4.
“If it works, it ain’t stupid.” ;)
- Uptime : up 2 weeks, 5 days, 2 hours, 7 minutes
Had to reboot due to Jellyfin weirdness, It’s not happened since so maybe it was patched whatever happened.
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
How do I check when the last power outage was if it’s connected to a UPS?
Interesting. LMDE seems to be more like MS Windows in that things like kernel updates insist on a reboot, and certain other things are easiest restarted with a reboot too, for example, X.Org changes.
I’m sure there’s still a way to bootstrap a new kernel on the bare metal without needing to reboot, likewise for restarting X.Org, but I foresee problems with any programs and daemons that were children of the original processes. For example, convincing them not to exit when their parent does and then getting them to play nice under a new session.
I mean, I guess you could just not update, or have a long period where they’re unnecessary and that’d work too. That could well be what this meme is getting at. Can confirm sessions (caveat: with standby and hibernate) that have lasted well over a month.
But this all raises the question: Does anyone actually not reboot when system changes happen, and what’s the workflow for bootstrapping without rebooting there?
I don’t get why are you talking about LMDE under a meme about Debian
Because LMDE stands for Linux Mint Debian Edition
Yeah but it’s Linux mint debian edition, not Debian
LMDE is mostly just the apps and visual config. It is verg close to regular Debian. I know for a fact it is basically just regular Debian because I have distromorphed it into Kicksecure several times, which only works on Debian.
