# Cronjob for curator
**URL:** https://discuss.elastic.co/t/cronjob-for-curator/56585
**Category:** Elasticsearch
**Created:** [July 28, 2016, 7:38am UTC](https://discuss.elastic.co/t/cronjob-for-curator/56585 "2016-07-28T07:38:01Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Kennedy\_Kan1](https://discuss.elastic.co/u/Kennedy_Kan1)
#### Post date: [July 28, 2016, 7:38am UTC](https://discuss.elastic.co/t/cronjob-for-curator/56585/1 "2016-07-28T07:38:02Z")
I have installed ELK and the latest curator 4.0. I would like to made it regularly run with cronjob in linux.
1. I have installed .curator at the linux home, i.e. `cd~`.
2. I have typed `crontab -e`.
3. I input the following statement `* * * * * /.curator curator action.yml`
Is this setting right? How should I check if it is running or not?
---
### Author:  [@javanna](https://discuss.elastic.co/u/javanna)
#### Post date: [July 28, 2016, 11:16am UTC](https://discuss.elastic.co/t/cronjob-for-curator/56585/2 "2016-07-28T11:16:20Z")
I think this is a generic answer on testing crontab instead of waiting for them to run the next time? If so there are multiple places where similar questions around crontab were asked and answered., for instance [http://unix.stackexchange.com/questions/42715/how-can-i-make-cron-run-a-job-right-now-for-testing-debugging-without-changing](http://unix.stackexchange.com/questions/42715/how-can-i-make-cron-run-a-job-right-now-for-testing-debugging-without-changing) . Otherwise it is a matter of looking at your system logs to figure out whether the crontab is running successfully.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 10:32pm UTC](https://discuss.elastic.co/t/cronjob-for-curator/56585/3 "2017-07-05T22:32:10Z")