What are the penalties in staying with Monterey, if you choose not to upgrade to Ventura, or your Mac isn’t supported? Please report serious bugs we should know about.
Content Caching
When a downloaded update fails to install, that failure isn’t reported back to either local Content Caching server or Apple’s software update servers. Reliable feedback is important.
Over the last month, several security updates pushed by Apple have caused problems with Content Caching servers. Why?
Update failed to install.
What do you do next? Just try to download it again? What if you’re running a local Content Caching server?
The macOS 12.1 update is the smallest x.1 update since High Sierra 10.13.1 in October 2017, over four years ago. How come it has bucked the trend in Big Sur?
Content Caching server originated in 2005, as a feature in Mac OS X Server, which sold Xserves. Time Machine came in 2007, to support Time Capsules. Those legacies are so different, though.
Details of how the Content Caching server handles a cache macOS security data update, and both client and server handle an App Store update.
Using Activity Monitor and command tools to assess performance of a content caching server, and diagnosing problems from the log.
Big Sur updates have far exceeded those of Mojave or Catalina, and are set to total well over 40 GB. Prospects for security updates are no better, with a high carbon footprint.
Those who are cautious and like to wait before updating are in a quandary: it is better to risk updating now, or your Mac falling victim to malware?
The Eclectic Light Company 