@reboot in system crontab ignores (some) valid sh command syntax
Bug #308341 reported by
Daniel Richard G.
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cron (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: cron
This concerns cron 3.0pl1-104+ubuntu5 in Intrepid.
/etc/cron.d/blah:
--------
SHELL = /bin/sh
@reboot root a=/tmp/cron1.out; echo foo >$a
@reboot root true; a=/tmp/cron2.out; echo foo >$a
--------
For some reason---when the system (and cron) start up---the first command fails to execute, but the second one succeeds. The syslog doesn't even mention the first command; cron just silently ignores it.
This does not occur when the event time is specified with the normal five-field syntax, nor in user crontabs.
Related branches
CVE References
To post a comment you must log in.
I'm still seeing this on Karmic (3.0pl1- 106ubuntu3) , and in a user crontab to boot.