mirror of
https://git.proxmox.com/git/fwupd
synced 2025-05-22 09:12:32 +00:00
bf1b876e56
From [Lennart’s answer on systemd-devel][1]: > fwupd.target should not list the various network management solutions, > that is unnecessary, and ordering after network.target should be > sufficient to achieve the same, in a generic fashion. i.e. network > managers should order themselves before network.target, so that > ordering yourself after that automatically orders you after all > implementations at once... So, remove the unneeded targets. As the service unit is not installed/enabled, and instead called by a timer, the system will most probably be online already. [1]: https://lists.freedesktop.org/archives/systemd-devel/2020-March/044205.html "Best practices for starting unit only if network is online" |
||
|---|---|---|
| .. | ||
| 85-fwupd.motd.in | ||
| fwupd-refresh.preset | ||
| fwupd-refresh.service.in | ||
| fwupd-refresh.timer | ||
| meson.build | ||
| README.md | ||
Message of the day integration
Message on the day integration is used to display the availability of updates when connecting to a remote console.
It has two elements:
- Automatic firmware metadata refresh
- Message of the day display
Automatic firmware metadata refresh
This uses a systemd timer to run on a regular cadence. To enable this, run
# systemctl enable fwupd-refresh.timer
Motd display
Motd display is dependent upon the availability of the update-motd snippet consumption service such as pam_motd.