From: Jean-Marc Monnez (monnez.jean-marc@AGORA.MSA.FR)
Date: Mon May 12 2003 - 09:50:22 EDT
Your crontab lines limit the monthes to 5, 6, 8, 9, 11.
That's why 4/27 cannot be a valid date.
-- JMM
-----------------------------
Jean-Marc MONNEZ
MSA / AGORA / ATD
monnez.jean-marc@agora.msa.fr
-----------------------------
Lynn Lacaillade wrote :
> I added the jobs below to my crontab on 4/23. The job didn't run on 4/27 as
> expected and successfully ran on 5/4 as it should have.
>
> THE PROBLEM: It ran at 18:00 on 5/11. The job does not call itself. It
> totally relies on cron to run it when needed.
>
> Has anyone seen this before, or is there a problem with my cron entries?
>
> 0 18 4 5 0 /usr/local/dba/ksh/SbsMonthEnd.ksh BOPA 1
> 0 18 1 6 0 /usr/local/dba/ksh/SbsMonthEnd.ksh BOPA 1
> 0 18 29 6 0 /usr/local/dba/ksh/SbsMonthEnd.ksh BOPA 1
> 0 18 3 8 0 /usr/local/dba/ksh/SbsMonthEnd.ksh BOPA 1
> 0 18 31 8 0 /usr/local/dba/ksh/SbsMonthEnd.ksh BOPA 1
> 0 18 28 9 0 /usr/local/dba/ksh/SbsMonthEnd.ksh BOPA 1
> 0 18 2 11 0 /usr/local/dba/ksh/SbsMonthEnd.ksh BOPA 1
> 0 18 30 11 0 /usr/local/dba/ksh/SbsMonthEnd.ksh BOPA 1
>
> Lynn Lacaillade
> Unix Systems Administrator
> Exchange Administrator
> Ben & Jerry's Homemade, Inc.
> 802-846-1543 x7860
> mailto:lynnl@benjerry.com
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:16:49 EDT