What the expression does

* * * * * matches every minute of every hour of every day of every month. The command runs 1,440 times per day, at the first second of each minute.

All five fields are wildcards, so every field matches every value on every evaluation. There is no hidden step value and no restriction: this is the most frequent schedule standard cron can express.

When this schedule is useful

  • A lightweight health check that must notice a dead service within one minute.
  • A queue or spool directory drain that is cheap when empty.
  • Shipping buffered log lines during an incident, temporarily.
  • Testing a new cron installation: if this line does not run, the daemon is the problem.

Nearby expressions worth knowing

Small changes to one field produce very different schedules. These variants are the ones people usually want when they search for this cadence:

  • Every 2 minutes: */2 * * * * — 720 runs per day; still frequent.
  • Every 5 minutes: */5 * * * * — A common compromise for polling.
  • Every 10 minutes: */10 * * * * — Often enough for cache refreshes.
  • Once an hour: 0 * * * * — The sane default for most recurring jobs.
cron
*/2 * * * *        # Every 2 minutes
*/5 * * * *        # Every 5 minutes
*/10 * * * *       # Every 10 minutes
0 * * * *          # Once an hour

Timezone, load and edge cases

Cron evaluates this expression in the timezone of the daemon, not the timezone of the person who wrote it. If the server runs UTC, a schedule that looks like a morning job can fire in the middle of the local night. Select the server timezone in the next-run preview and compare the wall-clock time before deploying.

A job that takes 70 seconds will overlap with the next invocation. Use flock or a scheduler that prevents concurrency.

Many servers firing at the same moment create a thundering herd against shared databases. Add a random offset with a wrapper script if needed.

Every run can send mail when output is not redirected, which is how inboxes fill up at 3 AM.

If the schedule runs more often than you expect, check whether day-of-month and day-of-week are both restricted — Vixie cron treats that combination as OR, not AND.

Verify it before shipping

  • Run the expression through the explainer and read the English sentence once.
  • Check the next five run times in the server's timezone, not your laptop's.
  • Execute the command manually with the same user and environment cron will use.
  • Redirect stdout and stderr to a log file, and include a timestamp in each line.