I’m not sure if we are allowed to refer to AI’s here now, but for what it is worth, Grok 3 beta agrees with you. (I’ve been rebooting periodically for years, also.)
1 Like
I’m not a moderator, but as far as I’m concerned, anything AI-related is welcomed provided it’s acknowledged as such. 
1 Like
Genuine question: Do automated updates restart processes that are linked (statically or dynamically) to patched libraries (glibc comes to mind as a fairly pervasive one), or that are themselves patched?
I never bother rebooting anything unless I have to. No reason to. Why bother giving myself more chores and busywork unnecessarily?
I reboot with updates, after major clean-ups, and if I’m away for a few days, but mostly I reboot when it is acting strangely - nothing specific, but sometimes I can tell like things are just off: slow reaction times, keying errors, unexpected results… it’s hard to define but I just can feel it. And no, I don’t mean indexing/backup/updating.
“When in doubt, reboot first.”
1 Like
I thought they were restarted but I might be wrong. I know there’s clever tricks with daemons like sshd so you don’t get dropped/locked out. I do occasionally restart apache and mariadb if the memory usage looks weird (I wrote a Scriptable widget to keep an eye on server stats from my phone).
1 Like