> The documentation tells users how to disable the service without having to know systemd service interfaces.
Which is: > /etc/default/motd-news has an ENABLED=1 setting that if set to 0 will turn off this functionality. And this is not working, as reported by Nadav. My modt keep getting errors when i run commend "systemctl status" too. Mine is: $ sudo systemctl status motd-news.service à motd-news.service - Message of the Day Loaded: loaded (/lib/systemd/system/motd-news.service; static) Active: failed (Result: exit-code) since Sun 2023-09-24 12:40:01 EDT; 6h ago TriggeredBy: â motd-news.timer Docs: man:update-motd(8) Process: 375394 ExecStart=/etc/update-motd.d/50-motd-news --force (code=exited, status=203/EXEC) Main PID: 375394 (code=exited, status=203/EXEC) CPU: 9ms Sep 24 12:40:01 lplat systemd[1]: Starting Message of the Day... Sep 24 12:40:01 lplat systemd[375394]: motd-news.service: Failed to locate executable /etc/update-motd.d/50-motd-news: Permission> Sep 24 12:40:01 lplat systemd[375394]: motd-news.service: Failed at step EXEC spawning /etc/update-motd.d/50-motd-news: Permissio> Sep 24 12:40:01 lplat systemd[1]: motd-news.service: Main process exited, code=exited, status=203/EXEC Sep 24 12:40:01 lplat systemd[1]: motd-news.service: Failed with result 'exit-code'. Sep 24 12:40:01 lplat systemd[1]: Failed to start Message of the Day. $ sudo journalctl -u motd-news.service Aug 17 16:57:01 . systemd[1]: Starting Message of the Day... Aug 17 16:57:01 . systemd[1]: motd-news.service: Main process exited, code=exited, status=203/EXEC Aug 17 16:57:01 . systemd[1]: motd-news.service: Failed with result 'exit-code'. Aug 17 16:57:01 . systemd[1]: Failed to start Message of the Day. Aug 18 01:35:30 . systemd[52283]: motd-news.service: Failed to locate executable /etc/update-motd.d/50-motd-news: Permission denied Aug 18 01:35:30 . systemd[1]: Starting Message of the Day... Aug 18 01:35:30 . systemd[52283]: motd-news.service: Failed at step EXEC spawning /etc/update-motd.d/50-motd-news: Permission denied Aug 18 01:35:30 . systemd[1]: motd-news.service: Main process exited, code=exited, status=203/EXEC Aug 18 01:35:30 . systemd[1]: motd-news.service: Failed with result 'exit-code'. Aug 18 01:35:30 . systemd[1]: Failed to start Message of the Day. . . . $ ls -l /etc/update-motd.d/50-motd-news -rw-r--r-- 1 root root 5023 2021-10-15 06:06 /etc/update-motd.d/50-motd-news How did you disable the timer, Nadav? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/2022825 Title: motd-news.timer trigger motd-news.service even if disable Status in base-files package in Ubuntu: Incomplete 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://ubuntu.com/legal/motd /etc/default/motd-news has an ENABLED=1 setting that to 0 for disable. 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://ibb.co/yXTpzGq 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2022825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp