In the first article in this series, I explained how a great many background activities in macOS, including […]
launchd
Rather than using cron or launchd, many background services in macOS are now run using Centralized Task Scheduling (CTS). This is how it works.
What’s the quickest way to tear down all user apps and services? Or to force a restart? The answer is in the command tool launchctl.
When you want software to run automatically each time you Mac starts up, there are several ways of doing that. Here’s your choice.
Scheduling background activities like making backups has moved from cron to launchd, and now to a more complex system. This has reduced the reliability of macOS and made it harder to support.
New release lets you save and re-open activity configurations in simple plist files, and fixes a couple of annoying bugs.
Background activities scheduled by third-party software currently use launchd, and run the risk of affecting the user. Would GCD be a better choice of dispatcher?
An experimental tool to let you schedule background tasks of your own, which are managed by Grand Central Dispatch. First alpha release.
The aim is to be able to run commands at regular intervals using GCD rather than launchd. Here are details of the code and resulting log entries, casting light on how GCD works.
Despite its documentation vanishing, it’s clear that GCD does a lot more than provide an easy way to concurrency for app developers.
The Eclectic Light Company 