6 ms·
Most likley because you stopped the wrong service. You should have stopped the relevant timer service, not the service that the timer starts.
by megous 3y ago
Most likley because you stopped the wrong service. You should have stopped the relevant timer service, not the service that the timer starts.
- bsd_source 3y ago[flagged]
- esbeeb 3y agoCan you give example code to stop that timer?
- Timber-6539 3y agoUsually, it's the same service name but with .timer at the end instead of .service.
- KAMSPioneer 3y agoIt's the same, but you disable the timer instead of the service. `sudo systemctl stop unattended-upgrades.timer`
- yrro 3y agoIt 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.
- jbverschoor 3y agoProbably better to mask it instead if you don't want it to execute at all
- tux2bsd 3y ago[dead]
- 3np 3y ago> 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.