mythtv-status could run as the mythtv daemon user, but does the mythtv daemon user have the config.xml file? (I'm not running 0.21 yet, so can't check).
As Björn points out you can't just have the cron job run the init script as the mythtv user due to needing to write to /etc/motd, but the init script could run mythtv-status as the mythtv user.
Why have the init.d script? So that on system bootup the motd is set correctly rather than having to wait for the cronjob to run.
I'd still prefer to see MythTV.pm fixed. This would solve this and some other problems. Given the way that I'm using MythTV.pm, it has no need what so ever to contact the database, so config.xml is not actually required for the current user case. I can tell MythTV.pm where the host is (because mythtv-status knows), but this patch is unlikely to hit the 0.21-fixes branch.
mythtv-status could run as the mythtv daemon user, but does the mythtv daemon user have the config.xml file? (I'm not running 0.21 yet, so can't check).
As Björn points out you can't just have the cron job run the init script as the mythtv user due to needing to write to /etc/motd, but the init script could run mythtv-status as the mythtv user.
Why have the init.d script? So that on system bootup the motd is set correctly rather than having to wait for the cronjob to run.
I'd still prefer to see MythTV.pm fixed. This would solve this and some other problems. Given the way that I'm using MythTV.pm, it has no need what so ever to contact the database, so config.xml is not actually required for the current user case. I can tell MythTV.pm where the host is (because mythtv-status knows), but this patch is unlikely to hit the 0.21-fixes branch.