Re: Timed Events

The fifth field in the crontab is the day of week:

*     *     *   *    *        command to be executed
-     -     -   -    -
|     |     |   |    |
|     |     |   |    +----- day of week (0 - 6) (Sunday=0)
|     |     |   +------- month (1 - 12)
|     |     +--------- day of month (1 - 31)
|     +----------- hour (0 - 23)
+------------- min (0 - 59)
[download]

No need to check the day again in the code.

($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord
}map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,
[download]

Comment on Re: Timed Events Select or Download Code

Replies are listed 'Best First'.
Re^2: Timed Events by MidLifeXis (Monsignor) on Dec 10, 2015 at 18:07 UTC
To follow up on this a bit -- if you include the date in your code as well as in the execution control, you now have to update your code if it is necessary to run this off schedule, if the schedule changes, if an execution failed, etc. Split your concerns. Have the app do what it does well, and have cron control when it runs. --MidLifeXis	[reply]
Re^3: Timed Events by PilotinControl (Pilgrim) on Dec 11, 2015 at 14:22 UTC
All three answers were great. It is an older server which needs replaced however management says just to let it run and when it dies tend to it then. So using the day of the week instead of relying on the crontab for the day will be more reliable as the machine likes to hiccup especially on weekends and it sends the internal date and time off....and especially when the power goes out for a longer period of time than the UPS allows for. Thanks again!	[reply]