A cron job is a command your computer runs on a schedule, by itself: a nightly database backup, a weekly log clean-up, a report every morning at nine. You describe the schedule once, in a short pattern of time fields, and the system does the rest.
Cron and cron jobs
Cron is a scheduler that has shipped with Unix-like systems for decades. It runs as a background service (a daemon, usually called cron or crond) that wakes up once a minute, reads its list of jobs and starts every job whose schedule matches the current time.
Each entry in that list is a cron job: a schedule plus the command to run. The list lives in a crontab, short for 'cron table'. Every user has their own, and you manage yours with the crontab command:
crontab -e # edit your crontab
crontab -l # print itCron doesn't care what the command is. It can be a shell script, a Python program or a curl call to an API. That makes it the usual answer to 'this has to happen every day, and nobody should have to remember to do it'.
Reading a cron expression
The schedule is a row of fields separated by spaces, each one a unit of time. The format the video uses has six fields, starting with seconds:
| Position |
|---|
Wondering how this was made? How we make these