The crontab File Entry Format
A crontab file contains entries for each cron job. Entries are separated by newline characters. Each crontab file entry contains six fields separated by spaces or tabs in the following form:
Sample commands:
A field may be an asterisk (*), which always stands for "first-last".
Ranges of numbers are allowed. Ranges are two numbers separated with a hyphen. The specified range is inclusive. For example, 8-11 for an "hours" entry specifies execution at hours 8, 9, 10 and 11.
Lists are allowed. A list is a set of numbers (or ranges) separated by commas. Examples: "1,2,5,9", "0-4,8-12".
Step values can be used in conjunction with ranges. Following a range with "/" specifies skips of the number's value through the range. For example, "0-23/2" can be used in the hours field to specify command execution every other hour (the alternative in the V7 standard is "0,2,4,6,8,10,12,14,16,18,20,22"). Steps are also permitted after an asterisk, so if you want to say "every two hours", just use "*/2".
Names can also be used for the "month" and "day of week" fields. Use the first three letters of the particular day or month (case doesn't matter). Ranges or lists of names are not allowed.
Cron also offers some special strings:
If you encounter errors from cron job, you should get email from crond. Mots system will send unhandled cron job output by email to root or the corresponding user.
Use:
$ mailx
You can put the condition into the actual crontab command (the percent-syntax needs to be escaped):
See also:
# Minute Hour Day of Month Month Day of Week Command
# (0-59) (0-23) (1-31) (1-12 or Jan-Dec) (0-6 or Sun-Sat)
0 2 12 * 0,6 ls -l > /dev/null
Sample commands:
/sbin/ping -c 1 192.168.0.1 &> /dev/null
/sbin/ping -c 192.168.0.1; ls -la >> /var/log/cronrun
cd /path/to/the/working/dir/; /sbin/ping -c 1 192.168.0.1 &> /dev/null
A field may be an asterisk (*), which always stands for "first-last".
Ranges of numbers are allowed. Ranges are two numbers separated with a hyphen. The specified range is inclusive. For example, 8-11 for an "hours" entry specifies execution at hours 8, 9, 10 and 11.
Lists are allowed. A list is a set of numbers (or ranges) separated by commas. Examples: "1,2,5,9", "0-4,8-12".
Step values can be used in conjunction with ranges. Following a range with "/" specifies skips of the number's value through the range. For example, "0-23/2" can be used in the hours field to specify command execution every other hour (the alternative in the V7 standard is "0,2,4,6,8,10,12,14,16,18,20,22"). Steps are also permitted after an asterisk, so if you want to say "every two hours", just use "*/2".
Names can also be used for the "month" and "day of week" fields. Use the first three letters of the particular day or month (case doesn't matter). Ranges or lists of names are not allowed.
Special stringsCron also offers some special strings:
- stringmeaning@rebootRun once, at startup.@yearlyRun once a year, "0 0 1 1 *".@annually(same as @yearly)@monthlyRun once a month, "0 0 1 * *".@weeklyRun once a week, "0 0 * * 0".@dailyRun once a day, "0 0 * * *".@midnight(same as @daily)@hourlyRun once an hour, "0 * * * *".
Use:
More control of crontab command
Note that the day of a command's execution can be specified by two fields: day of month, and day of week. If both fields are restricted (in other words, they aren't *), the command will be run when either field matches the current time. For example, "38 8 1,15 * 5" would cause a command to be run at 8:38 am on the 1st and 15th of each month, plus every Friday.You can put the condition into the actual crontab command (the percent-syntax needs to be escaped):
0 12 1-7 * * [[ "$(date '+\%a')" = "Mon" ]] && echo "It's Monday"
Or0 12 1-7 * *
if [ "$(date +\%_d)" -le 7 ]; then echo "It's Monday"; fi
The "[[...]]" is a shorthand for IF in bash. The "&&" Ensures the command followed is only Executed if the condition evaluates to TRUE. See also:
Comments
Post a Comment