Hacker News Reader

Comment by megous | Hacker News Reader

Most likley because you stopped the wrong service. You should have stopped the relevant timer service, not the service that the timer starts.

View on HN

> You should have stopped the relevant timer unit, not the service unit that the timer starts.

FTFY. Helps keeping them apart to not use the same word for both ;)

    systemctl disable --now unattended-upgrades.timer;
    systemctl disable --now unattended-upgrades.service

No need to uninstall or mask.

Can you give example code to stop that timer?

Usually, it's the same service name but with .timer at the end instead of .service.

It's the same, but you disable the timer instead of the service. `sudo systemctl stop unattended-upgrades.timer`

It will still start when you next boot up. 'systemctl disable --now unattended-upgrades.timer' will stop it now _and_ remove the symlink that starts it at boot.

Probably better to mask it instead if you don't want it to execute at all

Reply on news.ycombinator.com