Re: Unattended Upgrades Ran Anyway.
On Sun 10 Dec 2023 at 11:00:37 (-0700), Charles Curley wrote:
> On Sun, 10 Dec 2023 16:11:44 +0000
> Michael Kjörling <2695bd53d63c@ewoof.net> wrote:
>
> > On 10 Dec 2023 08:49 -0700, from charlescurley@charlescurley.com
> > (Charles Curley): [...]
> >
> > Exactly how did you "shut down" unattended-upgrades?
> >
>
> root@chaffee:/etc/dhcp# systemctl stop unattended-upgrades.service
> root@chaffee:/etc/dhcp# systemctl status unattended-upgrades.service
> ● unattended-upgrades.service - Unattended Upgrades Shutdown
> Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; vendor preset: enabled)
> Active: inactive (dead) since Sat 2023-12-09 19:06:51 MST; 6s ago
> Docs: man:unattended-upgrade(8)
> Process: 540 ExecStart=/usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal (code=exited, status=0/SUCCESS)
> Main PID: 540 (code=exited, status=0/SUCCESS)
> CPU: 1.661s
>
> Oct 09 02:02:20 chaffee systemd[1]: Started Unattended Upgrades Shutdown.
> Dec 09 19:06:42 chaffee systemd[1]: Stopping Unattended Upgrades Shutdown...
> Dec 09 19:06:51 chaffee systemd[1]: unattended-upgrades.service: Succeeded.
> Dec 09 19:06:51 chaffee systemd[1]: Stopped Unattended Upgrades Shutdown.
> Dec 09 19:06:51 chaffee systemd[1]: unattended-upgrades.service: Consumed 1.661s CPU time.
> root@chaffee:/etc/dhcp#
Why is the service loaded, enabled and enabled then? Don't you need
to disable or mask it? Presumably it sits there, dead, all day
normally, and pops up at an appropriate time.
Cheers,
David.
Reply to: