Apple Software Update

Infobox Software
name = Software Update



caption =
developer = Apple Inc.
latest_release_version = 3.0.3 (180.2)
latest_release_date = 2007
operating_system = Mac OS X
Windows
genre = System Utility
license = Proprietary
website = [http://www.apple.com/macosx/upgrade/softwareupdates.html apple.com/macosx/upgrade/
softwareupdates.htm]

Software Update is a software tool by Apple Inc. that installs the latest version of Apple software on computers running Mac OS X. It was originally introduced to Mac users in Mac OS 9. A Windows version has been available since the introduction of iTunes 7, under the name "Apple Software Update". Software Update automatically informs users of new updates. It is part of the CoreServices in OS X, found at /System/Library/CoreServices/Software Update.app, or by choosing Software Update from the Apple menu. Software Update can be set to check for updates daily, weekly, monthly, or not at all; in addition, it can download and store the associated .pkg file (the same type used by Installer) to be installed at a later date and maintains a history of installed updates.

Software Updates consist of incremental updates of the Mac OS and its applications, Security Updates, device drivers and firmware updates. All software updates require a password, as with all consequential system changes. Some updates require a system restart. Starting with Mac OS X 10.5, updates that require a reboot log out the user prior to installation and automatically restart the computer when complete; in earlier versions, the updates are installed, but critical files are not replaced until the next system startup.

Command line

All of Software Update's features are available through the command-line program softwareupdate.

The command line usage for softwareupdate in Mac OS X 10.5 is:Using this tool, it is fairly straightforward for lab administrators to automatically install incoming updates by adding a cron job:
softwareupdate --install --all
(or just --recommended to be more cautious). You may want to set the job to run only every few days to give yourself a chance to jump in with an --ignore if a particular update is reported to have issues by early adopters. If running as a cron job, it is probably also a good idea to avoid running the update while a user is logged in, especially since some updates require reboot to take effect. (softwareupdate does not reboot automatically, it merely displays a warning on its standard output if a reboot is necessary.) Remote administrators may also be interested in also using the cURL and installer command line utilities to set up their own software update system.