You can alter the following aspects of the Cache Manager configuration to achieve different levels of performance on different client machines:
· Disk or Memory Cache: You can direct the Cache Manager to use machine memory instead of disk space for caching.
· Chunk Size and Number: You can use several options with dfsd to alter the default size and number of chunks that compose a cache. With a disk cache, each chunk is called a V file; with a memory cache, each chunk is represented by a block of memory. The size and number of chunks can be modified to take advantage of fast networks or to compensate for slow networks.
· Cache Location: The standard cache location (dcelocal/var/adm/dfs/cache) can be changed to take advantage of greater space availability on other partitions.
· Cache Size: The cache size influences how often the Cache Manager contacts File Server machines across the network. Increasing the cache size results in better performance because fewer cross-network calls are necessary.
· File Server and FL Server Preferences: The Cache Manager maintains entries that contain the machine specifications (either host names or IP addresses) and preference ranks for File Servers and FL Servers. A File Server entry's rank determines that Cache Manager's preference for electing to access replicas at that address over replicas that are available through other network connections. Similarly, an FL Server entry's rank determines the Cache Manager's preference for querying the FLDB through a particular address. You can specify preferences for both types of server machines to bias the Cache Manager's selection process. A File Server or FL Server will normally have up to four entries in a Cache Managers preference list, with each entry having a separate machine specification.
· The setuid Status: By default, the Cache Manager does not allow setuid programs from filesets to execute with setuid permission. You can enable setuid programs from specific filesets to execute with setuid permission; setgid programs on a fileset are enabled and disabled along with setuid programs.
· Device File Status: By default, the Cache Manager does not honor device files stored in filesets. You can instruct the Cache Manager to recognize device files from specific filesets.
· Cached File Versions: The DFS token mechanism guarantees that the Cache Manager uses the most current versions of files and directories. You can also force the Cache Manager to discard the versions you are using and fetch new versions from the File Server machine.
· Unstored Data: If the Cache Manager cannot contact a File Server machine to write data to it, it keeps the unstored data in the cache. It then continues to attempt to contact the File Server machine until it can store the data. You can list all of the data the Cache Manager cannot store, and you can force the Cache Manager to discard the data rather than to continue to try to contact unavailable File Server machines.
· RPC Authentication Levels: The Cache Manager and File Server default authentication levels are such that communications default to the packet integrity RPC authentication level. You can set two sets of initial RPC authentication levels and minimum RPC authentication levels; one set governs communications with File Servers in the local cell, while the second set governs communications with File Servers in foreign cells.
Note: You must issue the commands described in this topic at a console or terminal of the machine being configured; you cannot specify a different machine name to be used with these commands. Some of the commands require that you log in as root, while others require no privileges; the necessary privileges are indicated with each command. All of the files mentioned in this topic are local files.