Re: general squawk about unattended-upgrade
On Wed 16 Nov 2022 at 15:55:37 (-0500), gene heskett wrote:
> On 11/16/22 14:17, Charles Curley wrote:
> > On Wed, 16 Nov 2022 13:03:20 -0500 gene heskett wrote:
> >
> > > Please relay to the devs that this utility is dangerous, and needs the
> > > ability to scan the system for stuff that cannot be interrupted, and
> > > exit quietly if it finds one of the un-interruptables running.
Who knows whether a process is interruptible or restartable—You.
> > Did you have Unattended-Upgrade::Automatic-Reboot set to true? If so,
> > set it to false. Similarly
> > Unattended-Upgrade::Automatic-Reboot-WithUsers.
> >
> > You can file a bug report yourself.
I only see a rant, not a bug.
> > You could also write a wrapper for octoprint which disables
> > unattended-upgrades, runs octopprint, then enables unattended-upgrades.
Why would you need unattended-upgrades on a system that runs processes
for a month solid, when they're designed to run daily through to about
weekly. It doesn't seem to make any more sense then running your
internet browser on a machine that's running a rt kernel on account of
the rapidity with which it has to service interrupts.
> With my luck and systemd doing as it DW pleases, what guarantee do I
> have that systemd won't re-enable it? At one point long ago WE were
> masters of our machines, now Leonard thinks he is master of all & WE
> don't count or care.
WTF has that got to do with the price of fish?
Or has some sort of kick-Lennart timer expired on your system?
Ah, no, it's just deflecting the blame.
Cheers,
David.
Reply to: