auter VS needrestart

For your couple of Linux servers, if you have their repositories sorted out, look at auter. Really easy to setup and schedule servers and especially when it's just a few of them.

I'm quite fond of Auter. I've been using it to automate patching of about 250 servers (RHEL, but Auter supports Ubuntu as well). It's quite flexible and easily extendable via its hooks. You can use Ansible or similar to deploy the config and cronjob to all your hosts, and then just sit back and watch it do its thing. No GUI, though.

How about auter? Auter link It's a github project built by people I work with, and it has some very nice configuration options available. We've configured environments that autoreboot for kernel updates but not everything else, options for not patching a group of systems if a different group failed for some reason (to keep from taking down all redundant systems in a patching run), unlimited automation options and scripting. In the dept I'm with now, we use a commercial product but we're really leaning into moving to Ansible. This is because it's easier to manage multiple envs with playbooks, than it would be to write all the customization into scripts for auter (and we're not allowed to completely automate the patching process in the new dept).

That one is fixed by needrestart 3.6 (in F37): https://github.com/liske/needrestart/issues/247

needrestart doesn't understand the Pi kernel file naming scheme so thinks the v7l and v8 are kernel version numbers. You need to tell it that you're only interested in kernel7.img

See also needrestart

I use this to see what I need to restart: https://github.com/liske/needrestart

You'll want tool like needrestart to manage that. My preferred way of doing so is to just shoot me an email so that I can restart the updated service at my own schedule.

You should have a look at needrestart (.deb page). Here's the github page.

https://github.com/liske/needrestart [available via EPEL for RHEL 7/8]