home *** CD-ROM | disk | FTP | other *** search
- ;
- ; This is a sample CRONTAB file, the event file used by NazCron. You
- ; will find that it will serve no function other than to show you how
- ; to construct a CRONTAB file.
- ;
-
- ;
- ; You can include comments in a CRONTAB file by typing a semi-colon in
- ; column one of the line you wish to be interpreted as a comment.
- ; You can also leave blank lines to make the file easier to read.
- ;
-
- ;
- ; NazCron events are in the format:
- ;
- ; [eventname] min hour day month weekday command
- ;
- ; [eventname] is not required, but if present must begin with an
- ; alphabetic character.
- ; min,hour,day, month and weekday must be numeric or contain asterisks.
- ; command must be a CLI command, or the CLI execution format of any
- ; program. All necessary parameters must be provided.
- ;
-
- ;
- ; Next is the simple form of a NazCron event.
-
- * * * * * Date >ram:cron.date1
-
- ; With asterisks in each of the time positions, this command will be
- ; executed every minute as long as NazCron is active.
-
-
- ;
- ; This command will be executed every hour on the hour:
- 0 * * * * Date >ram:cron.date2
-
- ;
- ; This will be executed every hour on the hour and at 10 and 20 minutes
- ; after the hour as well as every minute from 30 to 59:
- 0,10,20,30-59 * * * * Date >ram:cron.date3
-
- ;
- ; This is a named event; it can be accessed from ARexx. This is other-
- ; wise the essentially same as the first example above.
- UselessEvent * * * * * Date >ram:cron.date4
-
- ;
- ; Examine this:
- 0 0 13 10 5 Date >ram:cron.date5
-
- ; It will be executed at midnight on October 13th ONLY in those years
- ; when this is a Friday the 13th.
- ;
-
- ;
- ; And now for an error:
- 0 * 30 2 * Date >ram:cron.date6
-
- ; Since this is requesting execution on February 30th, it will never be
- ; executed. There is no reasonableness test done on the time values
- ; you code, you have to be careful about stuff like this.
-
- ; Good Luck
-