secureplatform cron - Revision history

Nighthawk: /* crontab file examples */

2013-07-18T00:45:01Z

‎crontab file examples

Nighthawk at 00:44, 18 July 2013

2013-07-18T00:44:48Z

Nighthawk: Created page with "root crons configured by running '''crontab -e''' at expert prompt cron file will be save to... /var/spool/cron/root category:sysadmin"

2013-07-18T00:39:57Z

Created page with "root crons configured by running '''crontab -e''' at expert prompt cron file will be save to... /var/spool/cron/root category:sysadmin"

New page

root crons configured by running '''crontab -e''' at expert prompt

cron file will be save to...
/var/spool/cron/root

[[category:sysadmin]]

@@ Line 26: / Line 26: @@
 * * * * /usr/local/bin/cron.hourly.sh
 4 * * * /usr/local/bin/cron.daily.sh
 4 * * 0  /usr/local/bin/cron.weekly.sh
 4 1 * * /usr/local/bin/cron.monthly.sh
 [[category:sysadmin]]

← Older revision		Revision as of 00:44, 18 July 2013
Line 4:		Line 4:
	/var/spool/cron/root		/var/spool/cron/root

		+
		+	== cron file format ==
		+
		+	Each line in the /etc/crontab file represents a job and has the following format:
		+	minute hour day month dayofweek command
		+
		+	minute — any integer from 0 to 59
		+
		+	hour — any integer from 0 to 23
		+
		+	day — any integer from 1 to 31 (must be a valid day if a month is specified)
		+
		+	month — any integer from 1 to 12 (or the short name of the month such as jan or feb)
		+
		+	dayofweek — any integer from 0 to 7, where 0 or 7 represents Sunday (or the short name of the week such as sun or mon)
		+
		+	command — the command to execute (the command can either be a command such as ls /proc >> /tmp/proc or the command to execute a custom script)
		+
		+
		+	== crontab file examples ==
		+
		+	01 * * * * /usr/local/bin/cron.hourly.sh
		+	02 4 * * * /usr/local/bin/cron.daily.sh
		+	22 4 * * 0 /usr/local/bin/cron.weekly.sh
		+	42 4 1 * * /usr/local/bin/cron.monthly.sh
	[[category:sysadmin]]		[[category:sysadmin]]