motd-news.timer trigger motd-news.service even if disable
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
base-files (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Hello, guys, how are you?
I notice motd-news.timer activate motd-news.service even when motd-new.service disable.
I follow this doc's from UBUNTU:
https:/
/etc/default/
It's not working too…
When you reboot the server and put
sudo systemctl status motd-news.service
Service look dead. (disable)
but he got trigger by motd-news.timer after 10 - 20 minutes (screenshot):
https:/
if you look on the screenshot, you will see:
TriggeredBy: ● motd-news.timer
I can disable the motd-news.timer service, but i don't know if it will affect other services of UBUNTU.
Anyway It's still a bug, even if i disable the timer service, it's not should be this way.
Happened on 2 Different machines of UBUNTU 22.04 (Google Cloud Platform)
Be happy for your recommendation before i disable the motd-new.timer with systemctl.
Changed in base-files (Ubuntu): | |
status: | Expired → New |
The /etc/default/ motd-news file is read by the /etc/update- motd.d/ 50-motd- news script which is launched by motd-news.service. It is normal that setting the option in this file will not stop motd-news.service from running - however, it makes the script a no-op that does not access the network.
Are you seeing the motd-news.service access the network and make changes to files when ENABLED=0 is set? This is what is guaranteed by https:/ /ubuntu. com/legal/ motd.
You are free to disable the timer service as well if that is your preference. The documentation tells users how to disable the service without having to know systemd service interfaces.