Linux Vixie Cron vs. Modern Schedulers
Standard Unix (Vixie) cron uses 5 fields. However, as cloud computing evolved, scheduling requirements became more precise, leading to non-standard implementations with 6 or 7 fields.
AWS CloudWatch / EventBridge
AWS cron syntax uses 6 fields: `cron(Minutes Hours Day-of-month Month Day-of-week Year)`. Notably, AWS requires that you cannot specify `*` in both the Day-of-month and Day-of-week fields simultaneously. One must be replaced with a question mark `?` to indicate 'no specific value'.
Quartz Scheduler (Java / Spring)
The Quartz scheduler uses 7 fields, adding a seconds field at the very beginning and an optional year field at the end. This allows for sub-minute precision, which standard cron cannot achieve.
systemd Timers: The Modern Linux Alternative
On modern Linux systems, systemd timers (`.timer` units coupled with `.service` units) are rapidly replacing standard cron jobs. They offer massive advantages for sysadmins:
1. **Monotonic Timers**: Timers can run tasks relative to boot time (`OnBootSec=`) or service activation, rather than relying on strict calendar time (`OnCalendar=`).
2. **Detailed Logging**: Console output from triggered services is captured automatically in `journald`, eliminating the need to pipe output to `/var/log/syslog` manually.
3. **Resource Control**: Jobs triggered by systemd can be heavily throttled using cgroups to prevent background tasks from starving the CPU of foreground applications.