The crontab program might have various names, like
sudo apt search -n ^cron
Once installed, search for the service name, and start it.
sudo systemctl list-unit-files | grep cron
sudo systemctl enable –now cron
You can edit your crontab with:
39 */3 * * * /usr/bin/updatedb
* * * * *
These five points refer to:
minute hour day month weekday
So ‘3pm every Sunday’ would be:
0 15 * * 7
Here ‘Sunday’ is indicated by “7”, and ‘3pm’ is ’the 15th hour’. The minute is ‘0’ (i.e. ‘0 minutes past three pm’).
Doing the same thing, but only in February, would be:
0 15 * 2 7
Executing something requires the full path to where it is, so you cannot simply use
apt update -y, because cron does not know where
Instead, find out where it is:
type -P apt
Then put that into the crontab:
sudo crontab -e
40 */3 * * * /usr/bin/apt update -y
This will run
apt update -y as root every 3 hours, at 40 minutes past the hour, e.g. 00:40, 03:40, 06:40.
You can execute a script as root by putting it into a directory, instead of in the tab. Look at the available cron directories:
Testing with runparts
Run-parts runs all executable scripts in a directory.
$HOME to crontab to use scripts.
HOME=/home/user, then you can use syntax like this:
0 * * * * $HOME/.scripts/myScript.sh
Remember to test the script by executing that line first:
You can also add your regular path to your crontab as a variable (see example below). If you’re using vim as the editor, just run this at the top of your crontab:
The crontab files are in
/var/spool/cron/, so you can backup or restore them.
HOME=/home/user PATH=/usr/condabin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/user/.local/bin:/home/user/.scripts/:/home/user/.local/bin:/home/user/.scripts/ 1 0 1 * * /usr/bin/mkdir -p $HOME/arc/$(date +%Y/%m) 18 0 1 */3 * $HOME/.scripts/mail-clean.sh * * * * * ping -c 1 home || mail-pull.sh 50 18 * * * /usr/bin/timeout 30m /usr/bin/syncthing