As the mythtv-status author, my preferred solution is to have mythtv-status run via update-motd.
Just symlink'ing /usr/bin/mythtv-status into /etc/update-motd.d/ isn't the best solution - you won't pick up the configuration settings.
However, the next version of mythtv-status will use a stand along config file which it tries to load, and that'll allow a much cleaner solution to this.
In the meantime, the work around that Stefan gives is probably better (no need to restart cron though). Also, the latest version of mythtv-status (not in Ubuntu yet) checks if motd.new exists before it tries to move it in an attempt to reduce the race condition that is being hit.
Hi,
As the mythtv-status author, my preferred solution is to have mythtv-status run via update-motd.
Just symlink'ing /usr/bin/ mythtv- status into /etc/update-motd.d/ isn't the best solution - you won't pick up the configuration settings.
However, the next version of mythtv-status will use a stand along config file which it tries to load, and that'll allow a much cleaner solution to this.
In the meantime, the work around that Stefan gives is probably better (no need to restart cron though). Also, the latest version of mythtv-status (not in Ubuntu yet) checks if motd.new exists before it tries to move it in an attempt to reduce the race condition that is being hit.
Cheers!