"hmm, so OnUnitActiveSec= operates relative to a unit becoming active, but Type=oneshot service units actually never become active, unless you combine them with RemainAfterExit=, hence the confusion...
Type=oneshot units after all do stuff during their start-up and when that's complete they go down again, they never stay up continiously... Hence, combining Type=oneshot with OnUnitActiveSec= can't really work... This is a big underdocumented though"
Which seems relevant, since:
$ cat /lib/systemd/system/motd-news.service
[Unit]
Description=Message of the Day
After=network-online.target
Documentation=man:update-motd(8)
I think this is related to https:/ /github. com/systemd/ systemd/ issues/ 6680, specifically this comment:
"hmm, so OnUnitActiveSec= operates relative to a unit becoming active, but Type=oneshot service units actually never become active, unless you combine them with RemainAfterExit=, hence the confusion...
Type=oneshot units after all do stuff during their start-up and when that's complete they go down again, they never stay up continiously... Hence, combining Type=oneshot with OnUnitActiveSec= can't really work... This is a big underdocumented though"
Which seems relevant, since:
$ cat /lib/systemd/ system/ motd-news. service Message of the Day network- online. target =man:update- motd(8)
[Unit]
Description=
After=
Documentation
[Service] /etc/update- motd.d/ 50-motd- news --force
Type=oneshot
ExecStart=