Introduction to the crontab command for executing scheduled tasks in centos

1. Start and Stop Cron

Since cron is a built-in service in Linux, you can use the following method to start and close the service:

/Sbin/service crond start // start the service
/Sbin/service crond stop // close the service
/Sbin/service crond restart // restart the service
/Sbin/service crond reload // reload the configuration

2. cron configuration file

2.1 global configuration file

Crontab contains cron. Hourly, cron. daily, cron. Weekly, cron. Monthly, cron. d and crontab and cron. deny files under the/etc directory.

Cron. daily is a job executed once a day, cron. weekly is a job executed once a week. cron. monthly is a job executed once a month, cron. hourly is a job executed every hour. cron. D is a task automatically and periodically required by the system, but it is not executed by hour, by day, by week, by month, so it is placed under this directory.

The/etc/crontab file is generally as follows:

01 *** root run-parts/etc/cron. Hourly
02 4 *** root run-parts/etc/cron. daily
22 4 ** 0 root run-parts/etc/cron. Weekly
42 4 1 ** root run-parts/etc/cron. Monthly

We can add the required cron job to this file.

The/etc/cron. deny file is used to control which users are not allowed to use crontab.

2.2 user configuration file

Each user has his own cron configuration file, which can be edited through crontab-E. Generally, after the cron configuration file is saved and exited, the system automatically stores the file in the/var/spool/cron/directory. The file is named after the user name.

The Linux Cron service reads all the content under/var/spool/cron,/etc/crontab,/etc/cron. d every minute.

3. cron Command Format

Crontab [-u user] File
Crontab [-u user] {-L |-r |-e}

-U: Specifies a user.

-E: Execute the text editor to set the user (current user or specified user) time table. The specified text editor is vi.
-R: delete a user time table.
-L: list the user time table.

4. Cron File Format

* *** Command
Hour, day, month, and week commands

The 1st column indicates minute 1 ~ 59, represented by * or */1 per minute
The first column indicates the hour 1 ~ 23 (0 indicates 0 points)
The 3rd column indicates the date 1 ~ 31
The 4th column indicates the month 1 ~ 12
The Identification Number of column 5th is from day of the week to day ~ 6 (0 indicates Sunday)
6th columns of commands to run

5. cron file usage instructions

5.1 General situation

When F1 is *, the program is executed every minute, when F2 is *, the program is executed every hour, and so on.

* ***/Bin/usershell: Execute/bin/usershell every minute
When F1 is a-B, it indicates that execution is performed from the minute a to the minute B. When F2 is a-B, it indicates that execution is performed from the hour a to the hour B, and so on.

0-12 *****/bin/usershell is executed every minute from 0 to 12 minutes every day/bin/usershell
When F1 is */N, it indicates that execution is performed every n minutes. If F2 is */N, it indicates that execution is performed every n hours, and so on.

**/2 ***/bin/usershell is executed every two hours every day./bin/usershell
When F1 is a, B, c ,... a, B, C ,... execute in minutes. F2 is a, B, c ,... a, B, c... execute in hours, and so on.

* 1, 3, 5, 7 ***/bin/usershell execute/bin/usershell once every 3, 3, 4, 7 every day

5.2. Conflict Logic

The date can be set to monthly or weekly. If two segments conflict, the command of the sixth segment will be executed when any one of the segments matches, for example

"30 4*5", will run on the first and 15th of every month plus every Friday at AM.

5.3. symbol "%"

"%" In the cron file has the function of "ending command line", "line feed", and "redirection". If the special function of "%" is not required, escape using escape characters.

5.4. @ reboot

This does not need to be understood, in order to achieve the purpose of running after the boot, and only run once, in addition to this, it cannot be achieved through the first five segment settings.

@ Annually.

As for @ yearly, @ monthly, and so on, you can use the preceding five sections to set them.

 

Then I wroteSmall ExampleThe following test is performed:

UseCrontab-eEdit the content as follows:

*/2 ***** echo "I am crontab">/home/Zhang/Hello

In this way, I am crontab will be written to the hello file every two minutes.

I wrote a script task myself. sh to run the task directly. sh can be run, but it will run after it is added to crontab. Then I checked the solution on the Internet and finally solved it. Let's take a look at the task I originally wrote. sh script:

#! /Bin/sh

Java-jar offergateway. biz. offer-1.0-SNAPSHOT.jar

Crontab scheduled tasks are written as follows:

* ***/Task. Sh

Later, I checked the Internet and said that to run crontab, you must use the absolute path. Then I changed all the paths to the absolute path.

In the crontab execution environment variable, there is no environment variable set by the corresponding user. You need to manually set the environment variable to make it take effect. So I changed the above script:

#! /Bin/sh

./Etc/profile

Java-Jar/home/Zhang/offergateway. biz. offer-1.0-SNAPSHOT.jar

Crontab is also changed to absolute path:

* *** Sh/home/Zhang/task. Sh

Haha, it's successful ~~ Happy ~~

From: http://li200429.iteye.com/blog/1608758

Introduction to the crontab command for executing scheduled tasks in centos