How an AutoClient System's Cache Is Updated

An AutoClient system uses consistency checking to keep a cached file system synchronized with its back file system. The following descriptions show how consistency checking is done for an AutoClient system:

• By default, files that are updated in the server's back file systems are updated on the AutoClient system's cached file systems within 24 hours. However, if the update needs to occur sooner, you can use the autosync command. The autosync(1M) command initiates consistency checking that updates (synchronizes) an AutoClient system's cached file systems with its server's back file systems.

  For more information about the autosync command, see Chapter 8, AutoClient Environment Maintenance. You can also refer to the autosync(1M) man page.

• Each time an AutoClient system is booted, the AutoClient system's cached file systems are checked for consistency and updated with its server's back file systems.

Consistency checking for an AutoClient system is different from a system running CacheFS. AutoClient files (/ and /usr) are not likely to change very often, so consistency checking does not need to occur as frequently on an AutoClient system as it does on a system running CacheFS. This reduces traffic on your AutoClient network. See System Administration Guide for detailed information about CacheFS consistency checking.

Also, if you add new files to an AutoClient system, its server's back file systems are updated immediately, because an AutoClient system uses a write-through cache. A write-through cache is one that immediately updates its back file system as data is changed or added to the cache.