|
CrontabExpression
Description of the crontab format and expressions
Featured A crontab expression are a very compact way to express a recurring schedule. A single expression is composed of 5 space-delimited fields: MINUTES HOURS DAYS MONTHS DAYS-OF-WEEK Each field is expressed as follows:
The table below lists the valid values for each field:
Two fields also accept named values in English: MONTHS and DAYS-OF-WEEKS. So you can use names like January, February, March and so on for MONTHS and Monday, Tuesday, Wednesday and so on for DAYS-OF-WEEK. The names are not case-sensitive and you can even use short forms like Jan, Feb, Mar or Mon, Tue, Wed. In fact, at the moment, the parser in NCrontab will use the first match that it finds. Consequently, if you specify just the letter J for the month, then it will be interpreted as January since it occurs before the months June and July. If you specify Ju, then June will be assumed for the same reason. However, you should stick to either the 3 letter abbreviations or the full name since that is the norm among cron implementations. Finally, you can also mix numerical and named values, as in Jan,Feb,3,4,May,Jun,6. | ||||||||||||||||||
Cool project. Would it be possible to specify a timezone offset with the cron expression? So if I wanted to run a script on a remote server with timezone offset of +2 hours, every hour starting at the half hour with the initial start time of 1630 local time, I would like the server to compensate and change the expression accordingly to start at 1430.
This is a simple example.
Cool indeed :) Many thanks to developers. Could you please add "YEARS" part after DAYS-OF-WEEK?
Does '#' valid here as it represented in http://en.wikipedia.org/wiki/Cron ?