The run-parts call is now handled by the pam_motd module (C program).
It's run against everything in /etc/update-motd.d at login.
Quickly-running scripts just get run on every login.
Ones that take a long time to run (updates-available,
upgrade-available), or ones who's information doesn't expire quickly
should cache their data in /var/run and background an update when it
determines that it's data is stale.
The /etc/update-motd.d/00-header script prints /etc/motd.tail if it
exists. As far as I can tell, motd.tail should really be empty on
most modern Lucid systems, and should now only be used for the Admin
to manually jam some information in the MOTD.
The run-parts call is now handled by the pam_motd module (C program).
It's run against everything in /etc/update-motd.d at login.
Quickly-running scripts just get run on every login.
Ones that take a long time to run (updates-available,
upgrade-available), or ones who's information doesn't expire quickly
should cache their data in /var/run and background an update when it
determines that it's data is stale.
The /etc/update- motd.d/ 00-header script prints /etc/motd.tail if it
exists. As far as I can tell, motd.tail should really be empty on
most modern Lucid systems, and should now only be used for the Admin
to manually jam some information in the MOTD.