This adds ownership of the two directories /run/motd.d and /usr/lib/motd.d and two motd files /run/motd and /usr/lib/motd, which completes ownership of the default motd paths that PAM is now using [1]. Tested installation using the RPM on the fedora/29-cloud-base Vagrant box built in COPR: https://copr-be.cloud.fedoraproject.org/results/rfairley/add-motd-directories/fedora-29-x86_64/00836610-filesystem/, and works as expected.
The /run/motd and /usr/lib/motd files are treated like config files, but I'm thinking it makes sense to keep them in filesystem rather than setup if the motd.d directories are here. To include the files, I needed to add a stub file as a source for each (run.motd and usr-lib.motd) - I appreciate any suggestions for other approaches.
I noticed https://src.fedoraproject.org/rpms/filesystem has a specfile one release higher than this is currently, can also open the PR there if needed.
This adds ownership of the two directories /run/motd.d and /usr/lib/motd.d and two motd files /run/motd and /usr/lib/motd, which completes ownership of the default motd paths that PAM is now using [1]. Tested installation using the RPM on the
fedora/29-cloud-baseVagrant box built in COPR: https://copr-be.cloud.fedoraproject.org/results/rfairley/add-motd-directories/fedora-29-x86_64/00836610-filesystem/, and works as expected.The
/run/motdand/usr/lib/motdfiles are treated like config files, but I'm thinking it makes sense to keep them in filesystem rather than setup if the motd.d directories are here. To include the files, I needed to add a stub file as a source for each (run.motdandusr-lib.motd) - I appreciate any suggestions for other approaches.I noticed https://src.fedoraproject.org/rpms/filesystem has a specfile one release higher than this is currently, can also open the PR there if needed.
[1] https://github.com/linux-pam/linux-pam/pull/69