I think that command is showing you the total number of hours the system has been running, not the uptime - so it could have been rebooted for patching
[Edit] - Slightly pedantically, it's the number of hours one of the disks has been powered up
That's right. We've got 4 bog standard 750G WD Caviar Blues in a software RAID array in that machine, all powered up for 11+ years, none of which appear to have caught any errors during that time. Pretty amazing.
The OS has been updated and the box rebooted for kernel updates a number of times over the years.
Yes I suspected as much. So really this is bragging about continuous power for 11 years. Which is impressive.
I never saw anyone measure uptime in that way before. But it make a lot more sense than measuring the OS uptime.
Re:Ask HN: Does anyone still use IRC?
by anfractuosity on Friday June 07, 2019 @05:00AM
(#20122829)
I've never used them, but there does appear to be solutions such as kpatch, to patch a kernel whilst running.
That's only intended to be a band-aid until you can do a reboot without heavily impacting users. Say your monthly maintenance isn't for another two weeks, but there's a kernel vulnerability that's very worrisome. You may be able to kpatch it, but you do still need to do a reboot later.
Because when has it ever been patched? You know vulnerabilities in IRC clients do exist. That's why we were always told to not irc with root back in the days of BitchX.