rtnpro added a new comment to an issue you are following: `` @walters

I created an issue[1] to work on migrating from cron to systemd.

Regarding the first run of ``motdgen-cache-updateinfo``, I am not a big fan of it being run from the PAM stack. That's why I have a workaround in place.

## Use cases ### Installing fedora-motd manually User can run ``/usr/bin/motdgen`` manually post install to cache update details. Hence, in subsequent runs, neither ``atomic`` or ``dnf`` update info will be checked. May be we can run ``/usr/bin/motdgen`` post install. Also, another way is to start ``motdgen.service`` or enable it at boot. So, ``atomic`` and ``dnf`` commands won't be run at all from the PAM stack, because it has already been run, post install or at system boot.

### Enabling fedora-motd in images We can enable ``motdgen.service`` at system boot. This will execute ``atomic`` and ``dnf`` commands only during first boot and cache the results. This will result in displaying the motd data from the cached update info result.

@walters what do you think? Is this workaround good enough?

[1]: https://github.com/rtnpro/motdgen/issues/8 ``

To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/160