⚡
fasttools.me
Run Cron Job Every Saturday (0 0 * * 6)
Weekend Maintenance • Saturday Midnight

Run Cron Job Every Saturday (0 0 * * 6)

Schedule weekly cron jobs running every Saturday at midnight (0 0 * * 6). Visual syntax breakdown, upcoming run timetable, and weekend scripts.

Direct Answer Definition

To run a cron job every Saturday at midnight in Linux, use the expression 0 0 * * 6. The 6 in the fifth position represents Saturday. The job fires once per week at midnight as the weekend begins.

POSIX Cron Expression (5-Field)
Valid Syntax
Natural Language Schedule

Runs at minute 0, hour 0, day *, month *, weekday 6

Standard Schedule PresetsClick to load

Interactive 5-Field Workbench

Adjust individual cron segments in real time with instant two-way synchronization.

1. Minute0
0 – 59
2. Hour0
0 – 23 (24h)
3. Day of Month*
1 – 31
4. Month*
1 – 12 (Jan – Dec)
Select Month
5. Day of Week6
0 – 6 (Sun – Sat)
Select Day

Next 5 Scheduled Executions

Real-time schedule timetable projected forward from current timestamp.

12026-10-09 18:00:00 UTC
in 1d 8h
22026-10-16 18:00:00 UTC
in 8d 8h
32026-10-23 18:00:00 UTC
in 15d 8h
42026-10-30 18:00:00 UTC
in 22d 8h
52026-11-06 18:00:00 UTC
in 29d 8h

Crontab Command Snippet

Enter your executable command or script path to generate the full crontab configuration line.

Ready to paste in `crontab -e`0 0 * * 6 curl -fsS https://example.com/cron-job
Runs in system timezone or explicit TZ variablePOSIX Spec
Advertisement
Sponsored Developer Space
Cron Field Syntax Mapping

Field-by-Field Breakdown of `0 0 * * 6`

PositionField NameAllowed ValuesValue in `0 0 * * 6`Evaluation Meaning
1Minute0 – 5900 (At minute 0)
2Hour0 – 2300 (At midnight / 00:00)
3Day of Month1 – 31** (Every day of the month: 1-31)
4Month1 – 12** (Every month: 1-12)
5Day of Week0 – 6 (Sun-Sat)66 (Saturday only)
Technical Engineering Analysis

Saturday Deep Maintenance Strategy

Saturday midnight (0 0 * * 6) is the preferred slot for long-running database maintenance, disk defragmentation, full filesystem antivirus scans, and massive data warehouse backfills.

By launching deep batch processes at Saturday midnight, systems have an entire 48-hour weekend buffer to complete resource-intensive operations before Monday morning business traffic begins.

POSIX cron designates 6 as Saturday. You can also write 0 0 * * SAT on modern Linux distributions.

Real-World Server Implementations

Common Production Scenarios for `0 0 * * 6`

Case 01

PostgreSQL Database Reindex & Vacuum Full

Rebuilds all indexes across the database cluster and compacts physical disk storage during zero-traffic weekend windows.

/usr/bin/vacuumdb --all --full --analyze
Case 02

Filesystem Malware & Antivirus Scan

Runs ClamAV full-system virus scans across server root directories and uploads audit reports to security teams.

/usr/bin/clamscan -r /var/www --quiet --log=/var/log/clamav.log
Case 03

Cold Storage Cloud Archive Sync

Transfers week-old raw server access logs to compressed Amazon S3 Glacier archives for long-term SOC2 compliance.

/usr/local/bin/sync_s3_glacier_weekly.sh
Operational Traps & Failure Modes

Production Gotchas When Running `0 0 * * 6`

  • Job Run Duration: If a Saturday vacuum takes 30 hours, it could encroach into Sunday night traffic. Monitor runtime metrics.
  • Weekend Unattended Errors: A failing Saturday cron job can leave systems degraded for the entire weekend without on-call alerting.
  • Backup Drive Capacity: Ensure external backup storage has adequate free space before kicking off large weekend dumps.

Frequently Asked Questions About `0 0 * * 6`

Can I use SAT instead of 6?

Yes, 0 0 * * SAT is completely valid in modern crontabs.

How do I schedule a Saturday job for 3 AM?

Set minute to 0 and hour to 3: 0 3 * * 6 /path/to/script.sh.

What is the difference between 0 0 * * 6 and 0 0 * * 0?

0 0 * * 6 runs on Saturday, while 0 0 * * 0 runs on Sunday.

Related Cron Schedule Generators