Re: cron bug?

Jeff Hyman typed (on Wed, Jan 30, 2008 at 04:24:45PM -0500):
| Not completely understanding man cron,
| I now understand:
|
| Your command will run if it is Jan 23rd **OR** if it is M-T-W-T-F.
|
| Correct?
| Then why would the "*" (which represents ALL the days of the week)
| not reproduce the same results?

Again see the man page:

To specify days by only one field, the other field should be set
to `` * '' (for example, 0 0 * * 1 would run a command only on
Mondays).


--
JP
.

Relevant Pages

  • Re: cron bug?
    ... I should have thought of doing 'man crontabs' instead of 'man cron'. ... Jeff H ...
    (comp.unix.sco.misc)
  • Re: A reply to Marvin Minsky.
    ... in my understanding. ... and not over specify the behavior. ... And the result is the creation of a handful of "names" for typical behaviors ... the theoretical foundation in which it was built. ...
    (comp.ai.philosophy)
  • Re: A reply to Marvin Minsky.
    ... in my understanding. ... and not over specify the behavior. ... And the result is the creation of a handful of "names" for typical behaviors ... the theoretical foundation in which it was built. ...
    (comp.ai.philosophy)
  • Re: Crontab issues
    ... If you specify both a day in the month and a day of week, ... the crontab entry will be run on ... Dillon's Cron, of course, which mirrors classic Unix crontab ... I was getting permission denied error. ...
    (alt.os.linux)
  • Re: Crontab issues
    ... If you specify both a day in the month and a day of week, ... the crontab entry will be run on the ... Dillon's Cron, of course, which mirrors classic Unix crontab format. ... I was getting permission denied error. ...
    (alt.os.linux)