Created
February 14, 2019 11:41
-
-
Save int0x33/af9be6855a89d3723bdc2f3a3915a9ff to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # Edit this file to introduce tasks to be run by cron. | |
| # | |
| # Each task to run has to be defined through a single line | |
| # indicating with different fields when the task will be run | |
| # and what command to run for the task | |
| # | |
| # To define the time you can provide concrete values for | |
| # minute (m), hour (h), day of month (dom), month (mon), | |
| # and day of week (dow) or use '*' in these fields (for 'any').# | |
| # Notice that tasks will be started based on the cron's system | |
| # daemon's notion of time and timezones. | |
| # | |
| # Output of the crontab jobs (including errors) is sent through | |
| # email to the user the crontab file belongs to (unless redirected). | |
| # | |
| # For example, you can run a backup of all your user accounts | |
| # at 5 a.m every week with: | |
| # 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/ | |
| # | |
| # For more information see the manual pages of crontab(5) and cron(8) | |
| # | |
| # m h dom mon dow command | |
| * * * * * /root/clearlogs |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment