This bug was fixed in the package update-motd - 1.10
---
update-motd (1.10) jaunty; urgency=low
* debian/update-motd.cron.d: Fix broken crontab entries, LP: #312809
-- Dustin KirklandMon, 05 Jan 2009 12:51:54
-0600
** Changed in: update-motd (Ubuntu)
Status: In Progres
Thanks for the bug report.
I'm attaching a patch for the Ubuntu package. Note that I have already
committed this change to the upstream Launchpad branch, lp:update-motd.
I'm requesting main sponsorship.
:-Dustin
** Changed in: update-motd (Ubuntu)
Status: Confirmed => In Progress
** At
Contents of update-motd.cron.d from update_motd_1.9:
# /etc/cron.d/update-motd: crontab fragment for update-motd
#
# Running 'update-motd' dynamically generates the /etc/motd with
# a concatenation of output from each script in /etc/update-motd.d/*
*/10 * * * *root[ -x /usr/sbin/update-mo
Package version is 1.9 (jaunty). I also have the */10 rule, but then the
following four rules. I didn't add them myself.
00 * * * * root[ -x /usr/sbin/update-motd ] && /usr/sbin/update-motd
hourly 2>/dev/null
* 06 * * * root[ -x /usr/sbin/update-motd ] && /usr/sbin/update-motd
What version of update-motd are you using? I looked at the source
package, as well as the cron.d entry placed when I installed the current
version (1.8) of the package. It looks as follows:
# /etc/cron.d/update-motd: crontab fragment for update-motd
#
# Running 'update-motd' dynamically generates
** Changed in: update-motd (Ubuntu)
Importance: Undecided => High
Assignee: (unassigned) => Dustin Kirkland (kirkland)
Status: New => In Progress
--
crontab entries are incorrect
https://bugs.launchpad.net/bugs/312809
You received this bug notification because you are a member of U
