This optional key causes the job to be started every calendar interval as specified. The semantics are much like crontab(5): Missing attributes are considered to be wildcard. Unlike cron which skips job invocations when the computer is asleep, launchd will start the job the next time the computer wakes up. If multiple intervals transpire before the computer is woken, those events will be coalesced into one event upon waking from sleep.
The list must not be empty and must not contain duplicate entries (attrsets which compare equally).
Since missing attrs become wildcards, an empty attrset effectively means "every minute".
Declarations
Type
null or (submodule) or unique (non-empty (list of (submodule)))Default
nullExample
[
{
Hour = 2;
Minute = 30;
}
]