| |
Outline
Using the "Task Scheduler" can be any script, program or document to run at a scheduled time most convenient. Popular talk is the time to execute a script program.
Common uses
Off Timer
Regularly check for updates
Timing system configuration, database, backup log
Regularly clean up junk files
Detecting whether installed
# Crontab
-bash: crontab: command not found
Execute crontab command if the message command not found, it indicates not installed.
start installation
# Yum -y install vixie-cron
Loaded plugins: fastestmirror, refresh-packagekit, security
Existing lock /var/run/yum.pid: another copy is running as pid 25960.
Another app is currently holding the yum lock; waiting for it to exit ...
The system automatically upgrades may be running, yum in the locked state.
You can turn off mandatory yum process:
#rm -f /var/run/yum.pid
Then you can use the yum.
# Yum -y install vixie-cron
Loaded plugins: fastestmirror, refresh-packagekit, security
Determining fastest mirrors
* Base: mirrors.btte.net
* Extras: mirrors.sina.cn
* Updates: mirrors.sina.cn
base | 3.7 kB 00:00
extras | 3.4 kB 00:00
extras / primary_db | 32 kB 00:00
updates | 3.4 kB 00:00
updates / primary_db | 1.9 MB 00:07
Setting up Install Process
Resolving Dependencies
-> Running transaction check
---> Package cronie.x86_64 0: 1.4.4-15.el6 will be installed
-> Processing Dependency: dailyjobs for package: cronie-1.4.4-15.el6.x86_64
-> Processing Dependency: / usr / sbin / sendmail for package: cronie-1.4.4-15.el6.x86_64
-> Running transaction check
---> Package cronie-anacron.x86_64 0: 1.4.4-15.el6 will be installed
-> Processing Dependency: crontabs for package: cronie-anacron-1.4.4-15.el6.x86_64
---> Package sendmail.x86_64 0: 8.14.4-9.el6 will be installed
-> Processing Dependency: procmail for package: sendmail-8.14.4-9.el6.x86_64
-> Running transaction check
---> Package crontabs.noarch 0: 1.10-33.el6 will be installed
---> Package procmail.x86_64 0: 3.22-25.1.el6_5.1 will be installed
-> Finished Dependency Resolution
Dependencies Resolved
================================================== ======================
Package Arch Version Repository Size
================================================== ======================
Installing:
cronie x86_64 1.4.4-15.el6 base 74 k
Installing for dependencies:
cronie-anacron x86_64 1.4.4-15.el6 base 31 k
crontabs noarch 1.10-33.el6 base 10 k
procmail x86_64 3.22-25.1.el6_5.1 base 162 k
sendmail x86_64 8.14.4-9.el6 base 716 k
Transaction Summary
================================================== ======================
Install 5 Package (s)
Total download size: 994 k
Installed size: 2.1 M
Downloading Packages:
(1/5): cronie-1.4.4-15.el6.x86_64.rpm | 74 kB 00:00
(2/5): cronie-anacron-1.4.4-15.el6.x86_64.rpm | 31 kB 00:00
(3/5): crontabs-1.10-33.el6.noarch.rpm | 10 kB 00:00
(4/5): procmail-3.22-25.1.el6_5.1.x86_64.rpm | 162 kB 00:00
(5/5): sendmail-8.14.4-9.el6.x86_64.rpm | 716 kB 00:00
-------------------------------------------------- -------------------------------------------------- ----------------------------
Total 1.3 MB / s | 994 kB 00:00
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Installing: procmail-3.22-25.1.el6_5.1.x86_64 1/5
Installing: sendmail-8.14.4-9.el6.x86_64 2/5
Installing: cronie-1.4.4-15.el6.x86_64 3/5
Installing: crontabs-1.10-33.el6.noarch 4/5
Installing: cronie-anacron-1.4.4-15.el6.x86_64 5/5
ERROR: dbus.proxies: Introspect error on: 1.2513: / org / freedesktop / PackageKit: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply Possible causes include:. The remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Unable to send message to PackageKit
Verifying: crontabs-1.10-33.el6.noarch 1/5
Verifying: cronie-anacron-1.4.4-15.el6.x86_64 2/5
Verifying: sendmail-8.14.4-9.el6.x86_64 3/5
Verifying: cronie-1.4.4-15.el6.x86_64 4/5
Verifying: procmail-3.22-25.1.el6_5.1.x86_64 5/5
Installed:
cronie.x86_64 0: 1.4.4-15.el6
Dependency Installed:
cronie-anacron.x86_64 0: 1.4.4-15.el6 crontabs.noarch 0: 1.10-33.el6 procmail.x86_64 0: 3.22-25.1.el6_5.1 sendmail.x86_64 0: 8.14.4-9.el6
Complete!
View command help
crontab does not support the option -help -h or the like, but it can still view the command help
# Crontab -h
crontab: invalid option - h
crontab: usage error: unrecognized option
usage: crontab [-u user] file
crontab [-u user] [-e | -l | -r]
(Default operation is replace, per 1003.2)
-e (edit user's crontab)
-l (list user's crontab)
-r (delete user's crontab)
-i (prompt before deleting user's crontab)
-s (selinux context) 1
You can also use info crontab command to view detailed help information.
cron service providers to set the cron crontab command service, the following are some of the parameters and description of this command:
crontab -u // set a user's cron service, usually root user needs this parameter when executing this command
crontab -l // list the details of a user cron services
crontab -r // not delete a user's cron service
crontab -e // edit a user's cron service
For example, set the root view their own cron: crontab -u root -l
For another example, root you want to delete the cron setting fred: crontab -u fred -r
In the editing cron service, edit the contents of some of the formats and conventions, enter: crontab -u root -e
Enter vi edit mode, edit the content must meet the following format: / 1 * * * ls >> /tmp/ls.txt
Service state control
/ Sbin / service crond start // Start Service
/ Sbin / service crond stop // Close Service
/ Sbin / service crond restart // restart the service
/ Sbin / service crond reload // reload the configuration
/ Sbin / service crond status // View Status
Or use
# Service crond start
# Service crond stop
# Service crond restart
# Service crond reload
# Service crond status
boot
You can use this service to start automatically when the system starts:
At the end of /etc/rc.d/rc.local script plus:
/ Sbin / service crond start
Cron is now inside the service has been in the process, we can use this service up. |
|
|
|