What the expression does

0 0 * * 6,0 runs at midnight on Saturday and Sunday: two runs per week, on the weekend days.

The weekday field is a list of 6 (Saturday) and 0 (Sunday). A list is a union, so both days match. Writing 6-7 also works in many implementations because 7 is accepted as Sunday, but 6,0 is the most portable form.

When this schedule is useful

  • Full backups that would be too slow during the week.
  • Database maintenance, reindexing or compaction.
  • Weekend batch imports and reconciliation.
  • Low-traffic experiments and report generation.

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:

  • Weekend mornings at 10:00: 0 10 * * 6,0 — A more humane maintenance window.
  • Saturday only: 0 0 * * 6 — One run per week.
  • Sunday only: 0 0 * * 0 — Traditional weekly slot.
  • Friday night through Sunday: 0 22 * * 5-7 — Only if 7 is supported as Sunday.
cron
0 10 * * 6,0       # Weekend mornings at 10:00
0 0 * * 6          # Saturday only
0 0 * * 0          # Sunday only
0 22 * * 5-7       # Friday night through Sunday

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 Saturday job that overruns into Monday can block the weekday schedule. Bound the runtime and use a lock.

If day-of-month is also restricted, OR semantics apply and the job may run midweek. Keep day-of-month as *.

DST changes often happen on Sunday mornings; a 00:00 weekend job can be skipped or duplicated.

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.