crontab entries are incorrect
Bug #312809 reported by
Daniel Swarbrick
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-motd (Ubuntu) |
Fix Released
|
High
|
Dustin Kirkland |
Bug Description
Binary package hint: update-motd
Somebody needs to do a bit of basic sysadmin reading.
* 06 * * * root [ -x /usr/sbin/
The above entry will execute every minute, daily, from 06:00 until 06:59.
* * * * 1 root [ -x /usr/sbin/
The above entry will execute every every minute of every hour on Mondays.
* * 1 * * root [ -x /usr/sbin/
And the above entry will execute every minute of every hour, on the first day of every month.
Related branches
Changed in update-motd: | |
assignee: | nobody → kirkland |
importance: | Undecided → High |
status: | New → In Progress |
To post a comment you must log in.
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 the /etc/motd with
# a concatenation of output from each script in /etc/update-motd.d.
*/10 * * * * root [ -x /usr/sbin/ update- motd ] && /usr/sbin/ update- motd 2>/dev/null
Which runs every ten minutes.
Looking through the changelog, I don't see any mention of changes being made to the timing through releases. That does not appear to be the crontab installed with the package -- looks like someone wrote their own.