# uptime
20:03:59 up 792 days, 6:35, 1 user, load average: 0.66, 0.34, 0.29

# uptime
23:38:08 up 875 days, 10:09, 2 users, load average: 0.00, 0.00, 0.00

# uptime
20:33:24 up 914 days, 7:04, 1 user, load average: 0.04, 0.01, 0.00

# uptime
05:55:06 up 955 days, 16:26, 1 user, load average: 0.12, 0.04, 0.01

# uptime
17:24:09 up 966 days, 3:55, 1 user, load average: 0.02, 0.01, 0.00

My server is already 966 days up and ready to hit the1000 days target, then

> Hello, maintenance is required for one or more of your Linodes' physical hosts. [...] your Linode(s) will experience a brief interruption while the host is rebooted.

No!!!!!!!!!! :blobcathissing:


Seriously though, chasing uptime is cool but really not a good idea. It often hides serious boot misconfiguration. Who needs to write a boot script when the service you manually started 300 days ago is still running? Until the reboot day comes and everything explodes. Perhaps we even need to have mandatory reboot days in every month.

· · Web · 5 · 6 · 4

@niconiconi I patch & reboot quarterly, no exceptions.

I also patch & reboot if needed for security updates.

@niconiconi Personally, I consider that three months is a good uptime to reboot. That’s practical because htop add a (!) to the uptime when it’s over 100 days :D

@niconiconi I heard some servers would have broken physical components that are only relied on during boot time, so it runs like a zombie just fine in several years until it doesn't for good and all. the ultimate trap 🤣

Sign in to participate in the conversation

cybrespace: the social hub of the information superhighway jack in to the mastodon fediverse today and surf the dataflow through our cybrepunk, slightly glitchy web portal support us on patreon or liberapay!