Re: cron bug?



Jeff Hyman typed (on Wed, Jan 30, 2008 at 01:23:05PM -0500):
| Am I missing something, or is this a bug in cron?
| OSR5.0.6
|
| COMMAND can be whatever.
| # grep COMMAND /usr/spool/cron/crontabs

Don't be typing "/usr/spool./cron" as part of any command, it's living on
the edge. You could do:

crontab -l | grep pattern


| ./root:18 13 23 01 1,2,3,4,5 exec COMMAND
| ^^^^^^^^^--- over-rides Jan 23 13:18

No "over-riding:" is occuring. Read the crontab man page. The
command will run every Mon Tue Wed Thu Fri, AND ALSO Saturday or
Sunday providing the date is Jan 23.

that day
| ./root:18 13 23 01 * exec COMMAND
| ^^^^^^^^^--- Works as expected, does NOT run
| except Jan 23, 13:18

What's the purpose of the "exec" ?

--
JP
.



Relevant Pages

  • SUMMARY: cron entry: nth day of every month?
    ... cron can not handle this with its own syntax. ... 21st but "command" only runs if the output of the "date" command ... What I would suggest is rather than embedding the logic in each script ... The answer is it is _not_ possible to control it only with crontab ...
    (Tru64-UNIX-Managers)
  • Re: Cron job question
    ... > From: root@somedomain.nl (Cron Daemon) ... You've made the classic mistake of confusing the system crontab ... extra column defining which user ID the command should be run as. ... any new cron jobs for any user (including root) and leave the system ...
    (freebsd-questions)
  • Re: [opensuse] Re: cron problems
    ... The exception is when your crontab line starts ... your ipdetect cron job really works, you might want to turn off job start ... Your crontab syntax itself is OK, ... userid in it, before the command, has just the command. ...
    (SuSE)
  • Re: Running DBI, ODBC in the crontab
    ... Run the following lines in both the command line and crontab: ... Any of the paths that are missing in cron ... This communication is issued by UBS AG or an affiliate by the ...
    (perl.dbi.users)
  • Re: [SLE] rsync log
    ... If you type kcron you should get the ... What this means is the non-error output from a command like rsync prints ... the standard output of a cron job is emailed ... kcron is just a GIU way to specify your crontab ...
    (SuSE)