MacAT and Scheduled Tasks on a Mac

Somewhere in the history of every platform sits the problem of the job that must run when nobody is watching: the overnight backup, the four hourly export, the Monday morning report. On unix machines the answer was cron, a scheduler older than the Mac itself. On classic Mac servers there was no cron, and MacAT, published from this domain by MacSOS of Sydney, brought cron style scheduling to the platform. Its copyright line runs from 1999 to 2019, which makes it one of the quiet long distance runners of Mac software.

What a scheduler has to do

A task scheduler answers three questions: what runs, when, and what happens if it fails. The what is a command, a script or an application. The when is the interesting part: fixed times of day, intervals, days of the week, and the logic that decides whether a job that was missed while the machine was off should catch up or wait for its next slot. The failure handling is what separates a scheduler from an alarm clock: output needs to be captured somewhere a person will read it, a job must not start a second copy while the first is still running, and the log must say what happened at three in the morning without anyone having been there. Unix administrators had all of this in cron and its logs; the classic Mac had none of it, which was the gap MacAT filled.

What MacAT offered a Mac server room

MacAT presented the administrator with a list of scheduled tasks, the software's published material describing slots for dozens of them, and let each one carry its own timing rule. It aimed at the machines that ran file sharing, print queues and early web services in offices and schools, the Mac servers that did real work while running an operating system with no command line underneath. For the people who kept those machines alive, a scheduler meant the backup ran at two in the morning whether or not anyone remembered, and the maintenance scripts that no one wanted to run by hand at lunchtime ran at night instead. It was sold as shareware at 39 US dollars, registered and unlocked by payment, in the standard bargain of the era that the shareware history describes.

How unix scheduling arrived on the Mac

The deeper change came when Apple rebuilt the Mac on a unix foundation. Mac OS X shipped with a proper command line, and with it the question of which scheduler to use. Early releases offered cron for compatibility, but the system's own answer became launchd, which started in the Tiger era and still runs every modern Mac: it is the first process the kernel starts, it launches the rest of the system, and its agents and daemons double as the native way to schedule work. A launchd job is declared in a property list file stating the program to run and the timing rules, kept calm by the system across sleep and restart. Apple's own developer documentation for creating launchd jobs is the primary reference, and the patient reader can go a long way with it.

What a modern Mac user should reach for

The honest advice is layered. If the job is a personal routine, renaming files, resizing images, moving downloads, the Shortcuts app is the friendliest place to build it, and a shortcut can be scheduled without touching anything deeper. Shortcuts arrived on the Mac with macOS Monterey in 2021, and it inherited the automation ideas Automator had carried since 2005; the guide to automating everyday work on a Mac sorts these options by the job each suits. If the job is a system level routine, cleaning caches, rotating logs, running a maintenance script, launchd is the correct tool, and a wrapper app that writes the property list for you is a reasonable way to learn it. If the job is a single command run now and then, the Terminal does it directly, and the first hour with it is covered in the Terminal basics guide.

What the old tool still teaches

Two lessons survive from the MacAT era. The first is that a schedule you never verify is a rumour: the checklist habit is to check the log after the first night, not after the first disaster, which is the same discipline the backup guide preaches for restores. The second is that the best scheduled job is boring: one script, one purpose, output written where someone reads it. Administrators who wrote thirty seven small tasks in 1999 were doing what launchd users do now, and the design held because the problems held. Even the modern failure modes rhyme with the old ones: a laptop asleep at the scheduled minute, a job whose second copy piles onto the first, a log that grows unattended until it is the biggest file on the disk.

Where the record lives

The dates and pricing here come from the software's published pages as preserved in public web archives, reachable for any reader through the Internet Archive's captures of this domain. MacAT was a product of MacSOS, whose twenty year history is told in the story of this domain, alongside the SyBrowser database browser that shared the catalogue. This magazine publishes the record for what it teaches; the tools to schedule work today come from Apple, and they cost nothing beyond the Mac you already own.