You should include a path to your command, since cron runs with an extensively cut-down environment. You won't have all the environment variables you have in your interactive shell session.
It's a good idea to specify an absolute path to your script/binary, or define PATH in the crontab itself. To help debug any issues I would also redirect stdout/err to a log file.
You forgot a
*
,and you've too many fields, and it's the hour you need to care aboutThis means every 6th hour starting from 0, i.e. at hour 0, 6, 12 and 18 Which you could write as
crontab every 6 hours is a commonly used cron schedule.
Try:
. * has to
You should include a path to your command, since cron runs with an extensively cut-down environment. You won't have all the environment variables you have in your interactive shell session.
It's a good idea to specify an absolute path to your script/binary, or define PATH in the crontab itself. To help debug any issues I would also redirect stdout/err to a log file.
This will be the perfect way to say 6hrs a day.
Your command puts for 6 mins!