Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #264566
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Unattended Upgrades Ran Anyway. |
| Date | 2023-12-10 23:30 +0100 |
| Message-ID | <HJAtb-cHCC-3@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <HJwpz-cFfG-3@gated-at.bofh.it> <HJyrn-cGqF-11@gated-at.bofh.it> <HJyUq-cGAA-19@gated-at.bofh.it> <HJz46-cGE3-19@gated-at.bofh.it> <HJznr-cGZU-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Sun, Dec 10, 2023 at 02:10:43PM -0700, Charles Curley wrote: > On Sun, 10 Dec 2023 14:51:48 -0600 > David Wright <deblis@lionunicorn.co.uk> wrote: > > > I think it might be worth googling and reading "three levels of off" > > (with the quotes). > > > > 1. You can stop a service. That simply terminates the running > > instance of the service and does little else. If due to some form > > of activation (such as manual activation, socket activation, bus > > activation, activation by system boot or activation by hardware > > plug) the service is requested again afterwards it will be > > started. Stopping a service is hence a very simple, temporary and > > superficial operation. > > Thanks. I will disable as well. Disable *what*? Disabling a .service unit which is triggered by a timer event isn't going to stop it from running. *Masking* a .service would prevent it from running when requested by a timer event. Apart from that, you'd have to remove the timer event. However you do that. I've never used systemd timers yet.
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Unattended Upgrades Ran Anyway. Charles Curley <charlescurley@charlescurley.com> - 2023-12-10 17:00 +0100
Re: Unattended Upgrades Ran Anyway. Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-12-10 17:20 +0100
Re: Unattended Upgrades Ran Anyway. Charles Curley <charlescurley@charlescurley.com> - 2023-12-10 19:10 +0100
Re: Unattended Upgrades Ran Anyway. David Wright <deblis@lionunicorn.co.uk> - 2023-12-10 21:20 +0100
Re: Unattended Upgrades Ran Anyway. Charles Curley <charlescurley@charlescurley.com> - 2023-12-10 21:50 +0100
Re: Unattended Upgrades Ran Anyway. David Wright <deblis@lionunicorn.co.uk> - 2023-12-10 22:00 +0100
Re: Unattended Upgrades Ran Anyway. Charles Curley <charlescurley@charlescurley.com> - 2023-12-10 22:20 +0100
Re: Unattended Upgrades Ran Anyway. Greg Wooledge <greg@wooledge.org> - 2023-12-10 23:30 +0100
Re: Unattended Upgrades Ran Anyway. Charles Curley <charlescurley@charlescurley.com> - 2023-12-11 00:20 +0100
Re: Unattended Upgrades Ran Anyway. Max Nikulin <manikulin@gmail.com> - 2023-12-11 03:50 +0100
Re: Unattended Upgrades Ran Anyway. Max Nikulin <manikulin@gmail.com> - 2023-12-10 18:00 +0100
Re: Unattended Upgrades Ran Anyway. Charles Curley <charlescurley@charlescurley.com> - 2023-12-10 19:20 +0100
Re: Unattended Upgrades Ran Anyway. Stefan Monnier <monnier@iro.umontreal.ca> - 2023-12-10 18:30 +0100
Re: Unattended Upgrades Ran Anyway. Dan Ritter <dsr@randomstring.org> - 2023-12-10 22:10 +0100
Re: Unattended Upgrades Ran Anyway. songbird <songbird@anthive.com> - 2023-12-11 02:20 +0100
csiph-web