I did the following...
1.) Testing if we have the same situation as in the workaround was discribed.
=> Yes we have.
$ grep 10 /etc/cron.d/mythtv-status /etc/cron.d/update-motd
/etc/cron.d/mythtv-status:*/10 * * * * root [ -x
/etc/init.d/mythtv-status ] && /etc/init.d/mythtv-status reload > /dev/null
/etc/cron.d/update-motd:*/10 * * * * root [ -x /usr/sbin/update-motd ] &&
/usr/sbin/update-motd 2>/dev/null
2.) Backing up the cronjob for mythtv-status. => It is now in the userhome.
$ sudo mv /etc/cron.d/mythtv-status ~/
3.) Adding mythtv-status to update-motd. => Workaround is in place.
$ cd /etc/update-motd.d/
$ sudo ln -s /usr/bin/mythtv-status 50-mythtv-status
4.) Activating the changes for cron. => Workaround is activated.
$ sudo /etc/init.d/cron restart
5.) Testing if Workaround does its job. => mythtv-status isn't in the crontable
anymore.
$ grep 10 /etc/cron.d/mythtv-status /etc/cron.d/update-motd
grep: /etc/cron.d/mythtv-status: No such file or directory
/etc/cron.d/update-motd:*/10 * * * * root [ -x
/usr/sbin/update-motd ] && /usr/sbin/update-motd 2>/dev/null
6.) Waiting for ten minutes getting an E-Mail.
=> No E-Mail.
7.) Testing if mythtv-status does its job by "ssh mythbuntu-machine".
=> Everything all right.
--
cronjob for mythtv-status send's me many mails after upgrade to jaunty
https://bugs.launchpad.net/bugs/379500
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
