Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #229959
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: "Service restarts being deferred" |
| Date | 2020-12-24 02:30 +0100 |
| Message-ID | <BpnC1-1NK-3@gated-at.bofh.it> (permalink) |
| References | (3 earlier) <BnQIa-1bQ-5@gated-at.bofh.it> <Bo9rr-4s3-3@gated-at.bofh.it> <BoQZr-64V-11@gated-at.bofh.it> <Bpg7v-5Db-1@gated-at.bofh.it> <Bphdg-6gj-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed 23 Dec 2020 at 20:31:09 (+0200), Andrei POPESCU wrote: > On Mi, 23 dec 20, 18:28:43, Jesper Dybdal wrote: > > > > If a server is truly unattended, then it needs unattended-upgrades to > > somehow manage to restart services that it has upgraded. > > And if there are good reasons why these specific services cannot simply be > > restarted directly by unattended-upgrades without a reboot (as the bug > > reports referenced above indicate), then it would seem natural to me to use > > the existing mechanism to get a reboot done after upgrading. That mechanism > > works fine after for instance a kernel upgrade. > > > > Requiring manual intervention to restart an upgraded service would defeat > > the purpose of unattended-upgrades. > > > > > But I would also ask how the system is to determine a scheduled time > > > or occasion to restart services/reboot the system. What criteria, as > > > sysadmin, do you currently use to make those decisions for yourself? > > > > The existing mechanism used after kernel upgrades does it just fine. > > I'm guessing when the mechanism was designed it didn't even consider the > possibility of services that can't be safely restarted, so it's limited > to the kernel. Wich mechanism? I'm now not sure that the OP picked up on Kushal Kumaran's pointing out the abilities of needrestart. > It's probably possible to extend unattended-upgrades to consider > services in addition to kernel upgrades, (with some sort of > include/exclude mechanism) though this needs to be programed. > > You could start by filing a (wishlist) bug. I think you would be reinventing needrestart. I get the impression¹ that unattended-upgrades does the business of downloading and installing updates, with configuration limited to (roughly) when, circumstances (eg AC power), autoremoving and rebooting. OTOH needrestart has fine-grained configuration at the level of individual services, and can list or restart them (automatically or interactively), and it provides hooks for any other sort of decision-making exercise, hence my question above about the OP's criteria. One might assume that even a "truly unattended" system is sending some sort of notification to a sysadmin somewhere, and so that too is configurable in needrestart. ¹ I don't use unattended-upgrades myself, but just a cron job to download potential candidates and notify me. Cheers, David.
Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread
"Service restarts being deferred" Jesper Dybdal <jd-debian-user@dybdal.dk> - 2020-12-19 16:40 +0100
Re: "Service restarts being deferred" Dan Ritter <dsr@randomstring.org> - 2020-12-19 17:20 +0100
Re: "Service restarts being deferred" Jesper Dybdal <jd-debian-user@dybdal.dk> - 2020-12-19 18:40 +0100
Re: "Service restarts being deferred" Kushal Kumaran <kushal@locationd.net> - 2020-12-19 21:10 +0100
Re: "Service restarts being deferred" Jesper Dybdal <jd-debian-user@dybdal.dk> - 2020-12-20 17:10 +0100
Re: "Service restarts being deferred" David Wright <deblis@lionunicorn.co.uk> - 2020-12-22 15:40 +0100
Re: "Service restarts being deferred" Jesper Dybdal <jd-debian-user@dybdal.dk> - 2020-12-23 18:30 +0100
Re: "Service restarts being deferred" Andrei POPESCU <andreimpopescu@gmail.com> - 2020-12-23 19:40 +0100
Re: "Service restarts being deferred" David Wright <deblis@lionunicorn.co.uk> - 2020-12-24 02:30 +0100
csiph-web