Running scripts on a fixed timeschedule (cron): Difference between revisions
Jump to navigation
Jump to search
(Created page with " == Using crontab == With crontab you can run jobs on a fixed timeschedule. This means that you can e.g. download some data every day. To start an edit with '''crontab -l'...") |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 2: | Line 2: | ||
== Using crontab == | == Using crontab == | ||
With crontab you can run jobs on a fixed | With crontab you can run jobs on a fixed time schedule. | ||
This means that you can e.g. download some data every day. | This means that you can e.g. download some data every day. | ||
To start an edit | To start an edit use '''crontab -l''' , the info on how that file should look can be found by using '''man 5 crontab'''. | ||
Be aware of the following : | Be aware of the following : | ||
The scripts will run on the login node, so do not use a lot of resources | The scripts will run on the login node, so do not use a lot of resources. | ||
The crontab entry will be wiped upon reboot | The crontab entry will be wiped upon reboot ! | ||
Latest revision as of 15:24, 20 October 2020
Using crontab
With crontab you can run jobs on a fixed time schedule.
This means that you can e.g. download some data every day.
To start an edit use crontab -l , the info on how that file should look can be found by using man 5 crontab.
Be aware of the following :
The scripts will run on the login node, so do not use a lot of resources. The crontab entry will be wiped upon reboot !