--- /dev/null
+# Copyright 2009, Secure Endpoints Inc.
+# All Rights Reserved.
+#
+# Redistribution and use in source and binary forms, with or without
+# modification, are permitted provided that the following conditions are met:
+#
+# - Redistributions of source code must retain the above copyright notice,
+# this list of conditions and the following disclaimer.
+# - Redistributions in binary form must reproduce the above copyright notice,
+# this list of conditions and the following disclaimer in the documentation
+# and/or other materials provided with the distribution.
+# - Neither the name of Secure Endpoints Inc. nor the names of its contributors
+# may be used to endorse or promote products derived from this software without
+# specific prior written permission from Secure Endpoints Inc..
+#
+# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+# AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
+# TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
+# PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER
+# OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
+# EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
+# PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
+# PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
+# LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
+# NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+# SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+
+!INCLUDE ..\..\..\src\config\NTMakefile.$(SYS_NAME)
+!INCLUDE ..\..\..\src\config\NTMakefile.version
+
+!IFNDEF CYGWIN
+CYGWIN = c:/cygwin
+!ENDIF
+!IFNDEF DOCBOOK_XSL
+DOCBOOK_XSL = $(CYGWIN)/usr/share/docbook-xsl
+!ENDIF
+XSLTPROC = xsltproc.exe
+HTML_XSL = $(DOCBOOK_XSL)/html/chunk.xsl
+HTML_PARMS = --param navig.graphics 1 --stringparam navig.graphics.path ../
+CHM_XSL = $(DOCBOOK_XSL)/htmlhelp/htmlhelp.xsl
+
+XMLSRCS = \
+ auagd000.xml \
+ auagd005.xml \
+ auagd006.xml \
+ auagd007.xml \
+ auagd008.xml \
+ auagd009.xml \
+ auagd010.xml \
+ auagd011.xml \
+ auagd012.xml \
+ auagd013.xml \
+ auagd014.xml \
+ auagd015.xml \
+ auagd016.xml \
+ auagd017.xml \
+ auagd018.xml \
+ auagd019.xml \
+ auagd020.xml \
+ auagd021.xml \
+ auagd022.xml \
+ auagd023.xml \
+ auagd024.xml \
+ auagd025.xml \
+ auagd026.xml
+
+index.html: $(XMLSRCS)
+ @echo Building OpenAFS Administrator Guide in HTML format
+ $(XSLTPROC) $(HTML_PARMS) $(HTML_XSL) auagd000.xml
+
+htmlhelp.chm: $(XMLSRCS)
+ @echo Building OpenAFS Administrator Guide in HTML Help format
+ $(XSLTPROC) $(CHM_XSL) auagd000.xml
+ -hhc.exe htmlhelp.hhp
+ $(DEL) *.html
+ $(DEL) *.hh?
+ $(DEL) *.chw
+
+install: htmlhelp.chm index.html
+
+clean::
+ $(DEL) *.html
+ $(DEL) htmlhelp.chm
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<HTML
-><HEAD
-><TITLE
->Managing the NFS/AFS Translator</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="AFS Administration Guide"
-HREF="book1.html"><LINK
-REL="PREVIOUS"
-TITLE="Managing Administrative Privilege"
-HREF="c32432.html"><LINK
-REL="NEXT"
-TITLE="Using AFS Commands"
-HREF="a33826.html"></HEAD
-><BODY
-CLASS="appendix"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->AFS Administration Guide: Version 3.6</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="c32432.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="a33826.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="appendix"
-><H1
-><A
-NAME="HDRWQ595"
-></A
->Appendix A. Managing the NFS/AFS Translator</H1
-><P
->The NFS(R)/AFS(R) Translator enables users working on NFS client machines to access, create and remove files stored in AFS.
- This chapter assumes familiarity with both NFS and AFS.</P
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="HDRWQ596"
->Summary of Instructions</A
-></H1
-><P
->This chapter explains how to perform the following tasks by using the indicated commands:</P
-><DIV
-CLASS="informaltable"
-><A
-NAME="AEN33058"
-></A
-><TABLE
-BORDER="0"
-FRAME="void"
-CLASS="CALSTABLE"
-><COL
-WIDTH="70*"><COL
-WIDTH="30*"><TBODY
-><TR
-><TD
->Mount directory on translator machine</TD
-><TD
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->mount</B
-></SPAN
-></TD
-></TR
-><TR
-><TD
->Examine value of <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->@sys</B
-></SPAN
-> variable</TD
-><TD
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs sysname</B
-></SPAN
-></TD
-></TR
-><TR
-><TD
->Enable/disable reexport of AFS, set other parameters</TD
-><TD
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs exportafs</B
-></SPAN
-></TD
-></TR
-><TR
-><TD
->Assign AFS tokens to user on NFS client machine</TD
-><TD
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs</B
-></SPAN
-></TD
-></TR
-></TBODY
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="HDRWQ598"
->Overview</A
-></H1
-><P
->The NFS/AFS Translator enables users on NFS client machines to access the AFS filespace as if they are working on an AFS
- client machine, which facilitates collaboration with other AFS users.</P
-><P
->An <SPAN
-CLASS="emphasis"
-><I
-CLASS="emphasis"
->NFS/AFS translator machine</I
-></SPAN
-> (or simply <SPAN
-CLASS="emphasis"
-><I
-CLASS="emphasis"
->ltranslator machine</I
-></SPAN
->) is a machine
- configured as both an AFS client and an NFS server: <UL
-><LI
-><P
->Its AFS client functionality enables it to access the AFS filespace. The Cache Manager requests and caches files
- from AFS file server machines, and can even maintain tokens for NFS users, if you have made the configuration changes that
- enable NFS users to authenticate with AFS.</P
-></LI
-><LI
-><P
->Its NFS server functionality makes it possible for the translator machine to export the AFS filespace to NFS client
- machines. When a user on an NFS client machine mounts the translator machine's <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
->
- directory (or one of its subdirectories, if that feature is enabled), access to AFS is immediate and transparent. The NFS
- client machine does not need to run any AFS software.</P
-></LI
-></UL
-></P
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="HDRWQ599"
->Enabling Unauthenticated or Authenticated AFS Access</A
-></H2
-><P
->By configuring the translation environment appropriately, you can provide either unauthenticated or authenticated access
- to AFS from NFS client machines. The sections of this chapter on configuring translator machines, NFS client machines, and AFS
- user accounts explain how to configure the translation environment appropriately. <UL
-><LI
-><P
->If you configure the environment for unauthenticated access, the AFS File Server considers the NFS users to be the
- user <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->anonymous</B
-></SPAN
->. They can access only those AFS files and directories for which the
- access control list (ACL) extends the required permissions to the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->system:anyuser</B
-></SPAN
-> group.
- They can issue only those AFS commands that do not require privilege, and then only if their NFS client machine is a
- system type for which AFS binaries are available and accessible by the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->system:anyuser</B
-></SPAN
->
- group. Such users presumably do not have AFS accounts.</P
-></LI
-><LI
-><P
->If you configure the environment for authenticated access, you must create entries in the AFS Authentication and
- Protection Databases for the NFS users. The authentication procedure they use depends on whether the NFS client machine
- is a supported system type (one for which AFS binaries are available): <UL
-><LI
-><P
->If AFS binaries are available for the NFS client machine, NFS users can issue the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->klog</B
-></SPAN
-> command on the NFS client machine. They can access the filespace and issue AFS
- commands to the same extent as authenticated users working on AFS client machines.</P
-></LI
-><LI
-><P
->If AFS binaries are not available for the NFS client machine, NFS users must establish a connection with the
- translator machine (using the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->telnet</B
-></SPAN
-> utility, for example) and then issue the
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->klog</B
-></SPAN
-> and <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs</B
-></SPAN
-> commands on the translator machine
- to make its Cache Manager use the tokens correctly while users work on the NFS client. They can access the AFS
- filespace as authenticated users, but cannot issue AFS commands. For instructions, see <A
-HREF="a33047.html#HDRWQ612"
->Authenticating on Unsupported NFS Client Machines</A
->.</P
-></LI
-></UL
-></P
-></LI
-></UL
-></P
-></DIV
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="HDRWQ600"
->Setting the AFSSERVER and AFSCONF Environment Variables</A
-></H2
-><P
->If you wish to enable your NFS users to issue AFS commands, you must define the AFSSERVER and AFSCONF environment
- variables in their command shell. This section explains the variables' function and outlines the various methods for setting
- them.</P
-><P
->Issuing AFS commands also requires that the NFS client machine is a supported system type (one for which AFS binaries
- are available and accessible). Users working on NFS client machines of unsupported system types can access AFS as
- authenticated users, but they cannot issue AFS commands. It is not necessary to define the AFSSERVER and AFSCONF variables for
- such users. For instructions on using the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs</B
-></SPAN
-> command to obtain authenticated access on
- unsupported system types, see <A
-HREF="a33047.html#HDRWQ612"
->Authenticating on Unsupported NFS Client Machines</A
->. </P
-><DIV
-CLASS="sect3"
-><H3
-CLASS="sect3"
-><A
-NAME="HDRWQ601"
->The AFSSERVER Variable</A
-></H3
-><P
->The AFSSERVER variable designates the AFS client machine that performs two functions for NFS clients: <UL
-><LI
-><P
->It acts as the NFS client's <SPAN
-CLASS="emphasis"
-><I
-CLASS="emphasis"
->remote executor</I
-></SPAN
-> by executing AFS-specific system calls on its
- behalf, such as those invoked by the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->klog</B
-></SPAN
-> and <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->tokens</B
-></SPAN
->
- commands and by many commands in the AFS suites.</P
-></LI
-><LI
-><P
->Its stores the tokens that NFS users obtain when they authenticate with AFS. This implies that the remote
- executor machine and the translator machine must be the same if the user needs authenticated access to AFS.</P
-></LI
-></UL
-></P
-><P
->The choice of remote executor most directly affects commands that display or change Cache Manager configuration, such
- as the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs getcacheparms</B
-></SPAN
->, <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs getcellstatus</B
-></SPAN
->, and <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs setcell</B
-></SPAN
-> commands. When issued on an NFS client, these commands affect the Cache Manager on the
- designated remote executor machine. (Note, however, that several such commands require the issuer to be logged into the
- remote executor's local file system as the local superuser <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->root</B
-></SPAN
->. The ability of NFS client
- users to log in as <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->root</B
-></SPAN
-> is controlled by NFS, not by the NFS/AFS Translator, so setting the
- remote executor properly does not necessarily enable users on the NFS client to issue such commands.)</P
-><P
->The choice of remote executor is also relevant for AFS commands that do not concern Cache Manager configuration but
- rather have the same result on every machine, such as the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs</B
-></SPAN
-> commands that display or set
- ACLs and volume quota. These commands take an AFS path as one of their arguments. If the Cache Manager on the remote
- executor machine mounts the AFS filespace at the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
-> directory, as is conventional for AFS
- clients, then the pathname specified on the NFS client must begin with the string <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
-> for
- the Cache Manager to understand it. This implies that the remote executor must be the NFS client's primary translator
- machine (the one whose <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
-> directory is mounted at <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
->
- on the NFS client). </P
-></DIV
-><DIV
-CLASS="sect3"
-><H3
-CLASS="sect3"
-><A
-NAME="Header_672"
->The AFSCONF Variable</A
-></H3
-><P
->The AFSCONF environment variable names the directory that houses the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->ThisCell</B
-></SPAN
-> and
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->CellServDB</B
-></SPAN
-> files to use when running AFS commands issued on the NFS client machine. As on
- an AFS client, these files determine the default cell for command execution.</P
-><P
->For predictable performance, it is best that the files in the directory named by the AFSCONF variable match those in
- the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/usr/vice/etc</B
-></SPAN
-> directory on the translator machine. If your cell has an AFS directory
- that serves as the central update source for files in the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/usr/vice/etc</B
-></SPAN
-> directory, it is
- simplest to set the AFSCONF variable to refer to it. In the conventional configuration, this directory is called <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs/</B
-></SPAN
->cellname<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/common/etc</B
-></SPAN
->.</P
-></DIV
-><DIV
-CLASS="sect3"
-><H3
-CLASS="sect3"
-><A
-NAME="Header_673"
->Setting Values for the Variables</A
-></H3
-><P
->To learn the values of the AFSSERVER and AFSCONF variables, AFS command interpreters consult the following three
- sources in sequence: <OL
-TYPE="1"
-><LI
-><P
->The current command shell's environment variable definitions</P
-></LI
-><LI
-><P
->The <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->.AFSSERVER</B
-></SPAN
-> or <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->.AFSCONF</B
-></SPAN
-> file in the
- issuer's home directory</P
-></LI
-><LI
-><P
->The <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/.AFSSERVER</B
-></SPAN
-> or <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/.AFSCONF</B
-></SPAN
-> file in the NFS
- client machine's root (<SPAN
-CLASS="emphasis"
-><I
-CLASS="emphasis"
->/</I
-></SPAN
->) directory. If the client machine is diskless, its root directory can
- reside on an NFS server machine.</P
-></LI
-></OL
-></P
-><P
->(Actually, before consulting these sources, the NFS client looks for the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->CellServDB</B
-></SPAN
->
- and <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->ThisCell</B
-></SPAN
-> files in its own <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/usr/vice/etc</B
-></SPAN
-> directory. If
- the directory exists, the NFS client does not use the value of the AFSCONF variable. However, the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/usr/vice/etc</B
-></SPAN
-> directory usually exists only on AFS clients, not NFS clients.)</P
-><P
->As previously detailed, correct performance generally requires that the remote executor machine be the NFS client's
- primary translator machine (the one whose <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
-> directory is mounted at the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
-> directory on the NFS client). The requirement holds for all users accessing AFS from the NFS
- client, so it is usually simplest to create the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->.AFSSERVER</B
-></SPAN
-> file in the NFS client's root
- directory. The main reason to create the file in a user's home directory or to set the AFSSERVER environment variable in the
- current command shell is that the user needs to switch to a different translator machine, perhaps because the original one
- has become inaccessible.</P
-><P
->Similarly, it generally makes sense to create the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->.AFSCONF</B
-></SPAN
-> file in the NFS client's
- root directory. Creating it in the user's home directory or setting the AFSCONF environment variable in the current command
- shell is useful mostly when there is a reason to specify a different set of database server machines for the cell, perhaps
- in a testing situation.</P
-></DIV
-></DIV
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="HDRWQ602"
->Delayed Writes for Files Saved on NFS Client Machines</A
-></H2
-><P
->When an application running on an AFS client machine issues the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->close</B
-></SPAN
-> or <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fsync</B
-></SPAN
-> system call on a file, the Cache Manager by default performs a synchronous write of the data to
- the File Server. (For further discussion, see <A
-HREF="c667.html#HDRWQ33"
->AFS Implements Save on Close</A
-> and <A
-HREF="c21473.html#HDRWQ418"
->Enabling Asynchronous Writes</A
->.)</P
-><P
->To avoid degrading performance for the AFS users working on a translator machine, AFS does not perform synchronous
- writes for applications running on the translator machine's NFS clients. Instead, one of the Cache Manager daemons (the
- maintenance daemon) checks every 60 seconds for chunks in the cache that contain data saved on NFS clients, and writes their
- contents to the File Server. This does not guarantee that data saved on NFS clients is written to the File Server within 60
- seconds, but only that the <SPAN
-CLASS="emphasis"
-><I
-CLASS="emphasis"
->maintenance daemon</I
-></SPAN
-> checks for and begins the write of data at that
- interval.</P
-><P
->Furthermore, AFS always ignores the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fsync</B
-></SPAN
-> system call as issued on an NFS client. The
- call requires an immediate and possibly time-consuming response from the File Server, which potentially causes delays for
- other AFS clients of the File Server. NFS version 3 automatically issues the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fsync</B
-></SPAN
-> system
- call directly after the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->close</B
-></SPAN
-> call, but the Cache Manager ignores it and handles the
- operation just like a regular <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->close</B
-></SPAN
->.</P
-><P
->The delayed write mechanism means that there is usually a delay between the time when an NFS application issues the
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->close</B
-></SPAN
-> or <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fsync</B
-></SPAN
-> system call on a file and the time when the
- changes are recorded at the File Server, which is when they become visible to users working on other AFS client machines
- (either directly or on its NFS clients). The delay is likely to be longer than for files saved by users working directly on an
- AFS client machine.</P
-><P
->The exact amount of delay is difficult to predict. The NFS protocol itself allows a standard delay before saved data
- must be transferred from the NFS client to the NFS server (the translator machine). The modified data remains in the
- translator machine's AFS client cache until the maintenance daemon's next scheduled check for such data, and it takes
- additional time to transfer the data to the File Server. The maintenance daemon uses a single thread, so there can be
- additional delay if it takes more than 60 seconds to write out all of the modified NFS data. That is, if the maintenance
- daemon is still writing data at the time of the next scheduled check, it cannot notice any additional modified data until the
- scheduled time after it completes the long write operation.</P
-><P
->The Cache Manager's response to the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->write</B
-></SPAN
-> system call is the same whether it is issued
- on an AFS client machine or on an NFS client of a translator machine: it records the modifications in the local AFS client
- cache only.</P
-></DIV
-></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="HDRWQ603"
->Configuring NFS/AFS Translator Machines</A
-></H1
-><P
->To act as an NFS/AFS translator machine, a machine must configured as follows: <UL
-><LI
-><P
->It must be an AFS client. Many system types supported as AFS clients can be translator machines. To learn about
- possible restrictions in a specific release of AFS, see the <SPAN
-CLASS="emphasis"
-><I
-CLASS="emphasis"
->IBM AFS Release Notes</I
-></SPAN
->.</P
-></LI
-><LI
-><P
->It must be an NFS server. The appropriate number of NFS server daemons (<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->nfsd</B
-></SPAN
-> and
- others) depends on the anticipated NFS client load.</P
-></LI
-><LI
-><P
->It must export the local directory on which the AFS filespace is mounted, <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
-> by
- convention.</P
-></LI
-></UL
-></P
-><P
->If users on a translator machine's NFS clients are to issue AFS commands, the translator machine must also meet the
- requirements discussed in <A
-HREF="a33047.html#HDRRMTSYS"
->Configuring the Translator Machine to Accept AFS Commands</A
->.</P
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="Header_676"
->Loading NFS and AFS Kernel Extensions</A
-></H2
-><P
->The AFS distribution for system types that can act as NFS/AFS Translator machines usually includes two versions of the
- AFS kernel extensions file, one for machines where the kernel supports NFS server functionality, and one for machines not
- using NFS (the latter AFS kernel extensions file generally has the string <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->nonfs</B
-></SPAN
-> in its name).
- A translator machine must use the NFS-enabled version of the AFS extensions file. On some system types, you select the
- appropriate file by moving it to a certain location, whereas on other system types you set a variable that results in
- automatic selection of the correct file. See the instructions in the <SPAN
-CLASS="emphasis"
-><I
-CLASS="emphasis"
->IBM AFS Quick Beginnings</I
-></SPAN
-> for
- incorporating AFS into the kernel on each system type.</P
-><P
->On many system types, NFS is included in the kernel by default, so it is not necessary to load NFS kernel extensions
- explicitly. On system types where you must load NFS extensions, then in general you must load them before loading the AFS
- kernel extensions. The <SPAN
-CLASS="emphasis"
-><I
-CLASS="emphasis"
->IBM AFS Quick Beginnings</I
-></SPAN
-> describes how to incorporate the AFS initialization
- script into a machine's startup sequence so that it is ordered correctly with respect to the script that handles NFS.</P
-><P
->In addition, the AFS extensions must be loaded into the kernel before the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->afsd</B
-></SPAN
-> command
- runs. The AFS initialization script included in the AFS distribution correctly orders the loading and <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->afsd</B
-></SPAN
-> commands.</P
-></DIV
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="HDRRMTSYS"
->Configuring the Translator Machine to Accept AFS Commands</A
-></H2
-><P
->For users working on a translator machine's NFS clients to issue AFS commands, the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-rmtsys</B
-></SPAN
-> flag must be included on the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->afsd</B
-></SPAN
-> command which initializes
- the translator machine's Cache Manager. The flag starts an additional daemon (the <SPAN
-CLASS="emphasis"
-><I
-CLASS="emphasis"
->remote executor</I
-></SPAN
->
- daemon), which executes AFS-specific system calls on behalf of NFS clients. For a discussion of the implications of NFS users
- issuing AFS commands, see <A
-HREF="a33047.html#HDRWQ600"
->Setting the AFSSERVER and AFSCONF Environment Variables</A
->.</P
-><P
->The instructions in the IBM AFS Quick Beginnings for configuring the Cache Manager explain how to add options such as
- the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-rmtsys</B
-></SPAN
-> flag to the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->afsd</B
-></SPAN
-> command in the AFS
- initialization script. On many system types, it is simplest to list the flag on the line in the script that defines the
- OPTIONS variable. The <SPAN
-CLASS="emphasis"
-><I
-CLASS="emphasis"
->remote executor daemon</I
-></SPAN
-> does not consume many resources, so it is simplest to add it
- to the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->afsd</B
-></SPAN
-> command on every translator machine, even if not all users on the machine's NFS
- clients issue AFS commands.</P
-></DIV
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="HDRWQ604"
->Controlling Optional Translator Features</A
-></H2
-><P
->After an AFS client machine is configured as a translator machine, it by default exports the AFS filespace to NFS
- clients. You can disable and reenable translator functionality by using the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs exportafs</B
-></SPAN
->
- command's <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-start</B
-></SPAN
-> argument. The command's other arguments control other aspects of translator
- behavior. <UL
-><LI
-><P
->The <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-convert</B
-></SPAN
-> argument controls whether the second and third (<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->group</B
-></SPAN
-> and <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->other</B
-></SPAN
->) sets of UNIX mode bits on an AFS file or
- directory being exported to NFS are set to match the first (<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->owner</B
-></SPAN
->) mode bits. By
- default, the mode bits are set to match.</P
-><P
->Unlike AFS, NFS uses all three sets of mode bits when determining whether a user can read or write a file, even
- one stored in AFS. Some AFS files possibly do not have any <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->group</B
-></SPAN
-> and <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->other</B
-></SPAN
-> mode bits turned on, because AFS uses only the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->owner</B
-></SPAN
-> bits
- in combination with the ACL on the file's directory. If only the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->owner</B
-></SPAN
-> mode bits are
- set, NFS allows only the file's owner of the file to read or write it. Setting the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-convert</B
-></SPAN
-> argument to the value <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->on</B
-></SPAN
-> enables other users to access
- the file in the same manner as the owner. Setting the value <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->off</B
-></SPAN
-> preserves the mode bits
- set on the file as stored in AFS.</P
-></LI
-><LI
-><P
->The <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-uidcheck</B
-></SPAN
-> argument controls whether tokens can be assigned to an NFS user
- whose local UID on the NFS client machine differs from the local UID associated with the tokens on the translator
- machine. By default, this is possible.</P
-><P
->If you turn on UID checking by setting the value <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->on</B
-></SPAN
->, then tokens can be assigned
- only to an NFS user whose local UID matches the local UID of the process on the translator machine that is assigning the
- tokens. One consequence is that there is no point in including the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-id</B
-></SPAN
-> argument to the
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs</B
-></SPAN
-> command: the only acceptable value is the local UID of the command's issuer, which
- is the value used when the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-id</B
-></SPAN
-> argument is omitted. Requiring matching UIDs in this way
- is effective only when users have the same local UID on the translator machine as on NFS client machines. In that case,
- it guarantees that users assign their tokens only to their own NFS sessions. For instructions, see <A
-HREF="a33047.html#HDRWQ612"
->Authenticating on Unsupported NFS Client Machines</A
->.</P
-><DIV
-CLASS="note"
-><BLOCKQUOTE
-CLASS="note"
-><P
-><B
->Note: </B
->Turning on UID checking also prevents users on supported NFS clients from using the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->klog</B
-></SPAN
-> command to authenticate on the NFS client directly. They must authenticated and use the
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs</B
-></SPAN
-> command on the translator machine instead. This is because after the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->klog</B
-></SPAN
-> command interpreter obtains the token on the NFS client, it passes it to the Cache
- Manager's remote executor daemon, which makes the system call that stores the token in a credential structure on the
- translator machine. The remote executor generally runs as the local superuser <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->root</B
-></SPAN
->,
- so in most cases its local UID (normally zero) does not match the local UID of the user who issued the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->klog</B
-></SPAN
-> command on the NFS client machine.</P
-><P
->On the other hand, although using the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs</B
-></SPAN
-> command instead of the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->klog</B
-></SPAN
-> command is possibly less convenient for users, it eliminates a security exposure: the
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->klog</B
-></SPAN
-> command interpreter passes the token across the network to the remote executor
- daemon in clear text mode.</P
-></BLOCKQUOTE
-></DIV
-><P
->If you disable UID checking by assigning the value <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->off</B
-></SPAN
-> , the issuer of the
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs</B
-></SPAN
-> command can assign tokens to a user who has a different local UID on the NFS
- client machine, such as the local superuser <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->root</B
-></SPAN
->. Indeed, more than one issuer of the
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs</B
-></SPAN
-> command can assign tokens to the same user on the NFS client machine. Each time a
- different user issues the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs</B
-></SPAN
-> command with the same value for the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-id</B
-></SPAN
-> argument, that user's tokens overwrite the existing ones. This can result in unpredictable
- access for the NFS user.</P
-></LI
-><LI
-><P
->The <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-submounts</B
-></SPAN
-> argument controls whether users on the NFS client can mount AFS
- directories other than the top-level <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
-> directory. By default, the translator does
- not permit these submounts.</P
-><P
->Submounts can be useful in a couple of circumstances. If, for example, NFS users need to access their own AFS home
- directories only, then creating a submount to it eliminates the need for them to know or enter the complete path.
- Similarly, you can use a submount to prevent users from accessing parts of the filespace higher in the AFS hierarchy
- than the submount.</P
-></LI
-></UL
-></P
-></DIV
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="Header_679"
->To configure an NFS/AFS translator machine</A
-></H2
-><P
->The following instructions configure the translator to enable users to issue AFS commands. Omit Step <A
-HREF="a33047.html#LIWQ605"
->6</A
-> if you do not want to enable this functionality. <OL
-TYPE="1"
-><LI
-><P
->Become the local superuser <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->root</B
-></SPAN
-> on the machine, if you are not already, by
- issuing the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->su</B
-></SPAN
-> command. <PRE
-CLASS="programlisting"
-> % <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->su root</B
-></SPAN
->
- Password: <<VAR
-CLASS="replaceable"
->root_password</VAR
->>
-</PRE
-></P
-></LI
-><LI
-><P
->Configure the NFS/AFS translator machine as an NFS server, if it is not already. Follow the instructions provided
- by your NFS supplier. The appropriate number of NFS server daemons (such as <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->nfsd</B
-></SPAN
->)
- depends on the number of potential NFS clients.</P
-></LI
-><LI
-><P
->Configure the NFS/AFS translator machine as an AFS client, if it is not already. For the most predictable
- performance, the translator machine's local copies of the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/usr/vice/etc/CellServDB</B
-></SPAN
-> and
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/usr/vice/etc/ThisCell</B
-></SPAN
-> files must be the same as on other client machines in the
- cell.</P
-></LI
-><LI
-><P
-><A
-NAME="LITRANS-MOUNTFILE"
-></A
->Modify the file that controls mounting of directories on the machine by remote
- NFS clients. <UL
-><LI
-><P
->On systems that use the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/etc/exports</B
-></SPAN
-> file, edit it to enable export of the
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
-> directory to NFS clients. You can list the names of specific NFS client
- machines if you want to provide access only to certain users. For a description of the file's format, see the NFS
- manual page for <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->exports(5)</B
-></SPAN
->.</P
-><P
->The following example enables any NFS client machine to mount the machine's <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
->, <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/usr</B
-></SPAN
->, and <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/usr2</B
-></SPAN
->
- directories:</P
-><PRE
-CLASS="programlisting"
-> /afs
- /usr
- /usr2
-</PRE
-></LI
-><LI
-><P
->On system types that use the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->share</B
-></SPAN
-> command, edit the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/etc/dfs/dfstab</B
-></SPAN
-> file or equivalent to include <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->share</B
-></SPAN
->
- instructions that enable remote mounts of the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
-> directory. Most distributions
- include the binary as <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/usr/sbin/share</B
-></SPAN
->. The following example commands enable
- remote mounts of the root ( <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/</B
-></SPAN
-> ) and <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
->
- directories. To verify the correct syntax, consult the manual page for the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->share</B
-></SPAN
->
- command. <PRE
-CLASS="programlisting"
-> share -F nfs -o rw -d "root" /
- share -F nfs -o rw -d "afs gateway" /afs
-</PRE
-></P
-></LI
-></UL
-></P
-></LI
-><LI
-><P
->Edit the machine's AFS initialization file to invoke the standard UNIX <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->exportfs</B
-></SPAN
->
- command after the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->afsd</B
-></SPAN
-> program runs. On some system types, the modifications you made
- in Step <A
-HREF="a33047.html#LITRANS-MOUNTFILE"
->4</A
-> are not enough to enable exporting the AFS filespace via the
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
-> directory, because the resulting configuration changes are made before the
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->afsd</B
-></SPAN
-> program runs during machine initialization. Only after the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->afsd</B
-></SPAN
-> program runs does the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
-> directory become the mount point
- for the entire AFS filespace; before, it is a local directory like any other.</P
-></LI
-><LI
-><P
-><A
-NAME="LIWQ605"
-></A
->Modify the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->afsd</B
-></SPAN
-> command in the AFS initialization file to
- include the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-rmtsys</B
-></SPAN
-> flag.</P
-><P
->For system types other than IRIX, the instructions in the <SPAN
-CLASS="emphasis"
-><I
-CLASS="emphasis"
->IBM AFS Quick Beginnings</I
-></SPAN
-> for
- configuring the Cache Manager explain how to add the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-rmtsys</B
-></SPAN
-> flag, for example by
- adding it to the line in the script that defines the value for the OPTIONS variable.</P
-><P
->On IRIX systems, the AFS initialization script automatically adds the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-rmtsys</B
-></SPAN
->
- flag if you have activated the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->afsxnfs</B
-></SPAN
-> configuration variable as instructed in the
- <SPAN
-CLASS="emphasis"
-><I
-CLASS="emphasis"
->IBM AFS Quick Beginnings</I
-></SPAN
-> instructions for incorporating AFS extensions into the kernel. If the
- variable is not already activated, issue the following command.</P
-><PRE
-CLASS="programlisting"
-> # <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/etc/chkconfig -f afsxnfs on</B
-></SPAN
->
-</PRE
-></LI
-><LI
-><P
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->(Optional)</B
-></SPAN
-> Depending on the number of NFS clients you expect this machine to
- serve, it can be beneficial to add other arguments to the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->afsd</B
-></SPAN
-> command in the machine's
- initialization file, such as the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-daemons</B
-></SPAN
-> argument to set the number of background
- daemons. See <A
-HREF="c21473.html"
->Administering Client Machines and the Cache Manager</A
-> and the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->afsd</B
-></SPAN
-> reference page in the <SPAN
-CLASS="emphasis"
-><I
-CLASS="emphasis"
->IBM AFS Administration Reference</I
-></SPAN
->.</P
-></LI
-><LI
-><P
->Reboot the machine. On many system types, the appropriate command is <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->shutdown</B
-></SPAN
->;
- consult your operating system administrator's guide. <PRE
-CLASS="programlisting"
-> # <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->shutdown</B
-></SPAN
-> appropriate_options
-</PRE
-></P
-></LI
-></OL
-></P
-></DIV
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="Header_680"
->To disable or enable Translator functionality, or set optional features</A
-></H2
-><OL
-TYPE="1"
-><LI
-><P
->Become the local superuser <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->root</B
-></SPAN
-> on the machine, if you are not already, by issuing
- the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->su</B
-></SPAN
-> command. <PRE
-CLASS="programlisting"
-> % <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->su root</B
-></SPAN
->
- Password: <<VAR
-CLASS="replaceable"
->root_password</VAR
->>
-</PRE
-></P
-></LI
-><LI
-><P
->Issue the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs exportafs</B
-></SPAN
-> command. <PRE
-CLASS="programlisting"
-> # <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs exportafs nfs</B
-></SPAN
-> [<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-start</B
-></SPAN
-> {<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->on</B
-></SPAN
-> | <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->off</B
-></SPAN
->}} ] [<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-convert</B
-></SPAN
-> {<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->on</B
-></SPAN
-> | <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->off</B
-></SPAN
->}]
- [<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-uidcheck</B
-></SPAN
-> {<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->on</B
-></SPAN
-> | <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->off</B
-></SPAN
->}] [<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-submounts</B
-></SPAN
-> {<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->on</B
-></SPAN
-> | <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->off</B
-></SPAN
->}]
-</PRE
-> <DIV
-CLASS="variablelist"
-><DL
-><DT
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-start</B
-></SPAN
-></DT
-><DD
-><P
->Disables translator functionality if the value is <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->off</B
-></SPAN
-> or reenables it if
- the value is <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->on</B
-></SPAN
->. Omit this argument to display the current setting of all
- parameters set by this command.</P
-></DD
-><DT
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-convert</B
-></SPAN
-></DT
-><DD
-><P
->Controls the setting of the second and third (<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->group</B
-></SPAN
-> and <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->other</B
-></SPAN
->) sets of UNIX mode bits on AFS files and directories as exported to NFS clients If
- the value is <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->on</B
-></SPAN
->, they are set to match the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->owner</B
-></SPAN
->
- mode bits. If the value is <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->off</B
-></SPAN
->, the bits are not changed. If this argument is
- omitted, the default value is <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->on</B
-></SPAN
->.</P
-></DD
-><DT
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-uidcheck</B
-></SPAN
-></DT
-><DD
-><P
->Controls whether issuers of the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs</B
-></SPAN
-> command can specify a value for its
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-id</B
-></SPAN
-> argument that does not match their AFS UID: <UL
-><LI
-><P
->If the value is <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->on</B
-></SPAN
->, the value of the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-id</B
-></SPAN
-> argument must match the issuer's local UID.</P
-></LI
-><LI
-><P
->If the value is <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->off</B
-></SPAN
->, the issuer of the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs</B
-></SPAN
-> command can use the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-id</B
-></SPAN
-> argument to assign
- tokens to a user who has a different local UID on the NFS client machine, such as the local superuser
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->root</B
-></SPAN
->.</P
-></LI
-></UL
-></P
-><P
->If this argument is omitted, the default value is <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->off</B
-></SPAN
->.</P
-></DD
-><DT
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-submounts</B
-></SPAN
-></DT
-><DD
-><P
->Controls whether the translator services an NFS mount of any directory in the AFS filespace other than the
- top-level <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
-> directory. If the value is <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->on</B
-></SPAN
->,
- such submounts are allowed. If the value is off, only mounts of the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
->
- directory are allowed. If this argument is omitted, the default value is <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->off</B
-></SPAN
->.</P
-></DD
-></DL
-></DIV
-></P
-></LI
-></OL
-></DIV
-></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="HDRWQ606"
->Configuring NFS Client Machines</A
-></H1
-><P
->Any NFS client machine that meets the following requirements can access files in AFS via the NFS/AFS Translator. It does
- not need to be configured as an AFS client machine. <UL
-><LI
-><P
->It must NFS-mount a translator machine's <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
-> directory on a local directory, which
- by convention is also called <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
->. The following instructions explain how to add the
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->mount</B
-></SPAN
-> command to the NFS client machine's <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/etc/fstab</B
-></SPAN
->
- file or equivalent.</P
-><P
->The directory on which an NFS client mounts the translator's machine's <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
->
- directory can be called something other than <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
->. For instance, to make it easy to
- switch to another translator machine if the original one becomes inaccessible, you can mount more than one translator
- machine's <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
-> directory. Name the mount <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
-> for the
- translator machine that you normally use, and use a different name the mount to each alternate translator machine.</P
-><P
->Mounting the AFS filespace on a directory other than <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
-> introduces another
- requirement, however: when issuing a command that takes an AFS pathname argument, you must specify the full pathname,
- starting with <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
->, rather than a relative pathname. Suppose, for example, that a
- translator machine's AFS filespace is mounted at <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs2</B
-></SPAN
-> on an NFS client machine and you
- issue the following command to display the ACL on the current working directory, which is in AFS:</P
-><PRE
-CLASS="programlisting"
-> % <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs listacl .</B
-></SPAN
->
-</PRE
-><P
->The <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs</B
-></SPAN
-> command interpreter on the NFS client must construct a full pathname before
- passing the request to the Cache Manager on the translator machine. The AFS filespace is mounted at <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs2</B
-></SPAN
->, so the full pathname starts with that string. However, the Cache Manager on the translator
- cannot find a directory called <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs2</B
-></SPAN
->, because its mount of the AFS filespace is called
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
->. The command fails. To prevent the failure, provide the file's complete pathname,
- starting with the string <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
->.</P
-></LI
-><LI
-><P
->It must run an appropriate number of NFS client <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->biod</B
-></SPAN
-> daemons, which improve
- performance by handling pre-reading and delayed writing. Most NFS vendors recommend running four such daemons, and most
- NFS initialization scripts start them automatically. Consult your NFS documentation.</P
-></LI
-></UL
-></P
-><P
->To enable users to issue AFS commands, the NFS client machine must also be a supported system type (one for which AFS
- binaries are available) and able to access the AFS command binaries. The <SPAN
-CLASS="emphasis"
-><I
-CLASS="emphasis"
->IBM AFS Release Notes</I
-></SPAN
-> list the
- supported system types in each release.</P
-><P
->In addition, the AFSSERVER and AFSCONF environment variables must be set appropriately, as discussed in <A
-HREF="a33047.html#HDRWQ600"
->Setting the AFSSERVER and AFSCONF Environment Variables</A
->.</P
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="Header_682"
->To configure an NFS client machine to access AFS</A
-></H2
-><DIV
-CLASS="note"
-><BLOCKQUOTE
-CLASS="note"
-><P
-><B
->Note: </B
->The following instructions enable NFS users to issue AFS commands. Omit Step <A
-HREF="a33047.html#LIWQ608"
->5</A
-> and Step
- <A
-HREF="a33047.html#LIWQ609"
->6</A
-> if you do not want to enable this functionality.</P
-></BLOCKQUOTE
-></DIV
-><OL
-TYPE="1"
-><LI
-><P
->Become the local superuser <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->root</B
-></SPAN
-> on the machine, if you are not already, by issuing
- the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->su</B
-></SPAN
-> command. <PRE
-CLASS="programlisting"
-> % <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->su root</B
-></SPAN
->
- Password: <<VAR
-CLASS="replaceable"
->root_password</VAR
->>
-</PRE
-></P
-></LI
-><LI
-><P
->Configure the machine as an NFS client machine, if it is not already. Follow the instructions provided by your NFS
- vendor. The number of NFS client (<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->biod</B
-></SPAN
->) daemons needs to be appropriate for the expected
- load on this machine. The usual recommended number is four.</P
-></LI
-><LI
-><P
->Create a directory called <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
-> on the machine, if one does not already exist, to
- act as the mount point for the translator machine's <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
-> directory. It is acceptable to
- use other names, but doing so introduces the limitation discussed in the introduction to this section. <PRE
-CLASS="programlisting"
-> # <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->mkdir /afs</B
-></SPAN
->
-</PRE
-> </P
-></LI
-><LI
-><P
-><A
-NAME="LIWQ607"
-></A
->Modify the machine's file systems registry file (<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/etc/fstab</B
-></SPAN
->
- or equivalent) to include a command that mounts a translator machine's <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
-> directory. To
- verify the correct syntax of the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->mount</B
-></SPAN
-> command, see the operating system's <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->mount(5)</B
-></SPAN
-> manual page. The following example includes options that are appropriate on many system
- types. <PRE
-CLASS="programlisting"
-> mount -o hard,intr,timeo=300 translator_machine:/afs /afs
-</PRE
-></P
-><P
->where <DIV
-CLASS="variablelist"
-><DL
-><DT
-><SAMP
-CLASS="computeroutput"
->hard</SAMP
-></DT
-><DD
-><P
->Indicates that the NFS client retries NFS requests until the NFS server (translator machine) responds. When
- using the translator, file operations possibly take longer than with NFS alone, because they must also pass
- through the AFS Cache Manager. With a soft mount, a delayed response from the translator machine can cause the
- request to abort. Many NFS versions use hard mounts by default; if your version does not, it is best to add this
- option.</P
-></DD
-><DT
-><SAMP
-CLASS="computeroutput"
->intr</SAMP
-></DT
-><DD
-><P
->Enables the user to use a keyboard interrupt signal (such as <<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->Ctrl-c</B
-></SPAN
->>) to break the mount when the translator machine is inaccessible. Include this
- option only if the <SAMP
-CLASS="computeroutput"
->hard</SAMP
-> option is used, in which case the connection does not
- automatically break off when a translator machine goes down.</P
-></DD
-><DT
-><SAMP
-CLASS="computeroutput"
->timeo</SAMP
-></DT
-><DD
-><P
->Sets the maximum time (in tenths of seconds) the translator can take to respond to the NFS client's request
- before the client considers the request timed out. With a hard mount, setting this option to a high number like
- 300 reduces the number of error messages like the following, which are generated when the translator does not
- respond immediately. <PRE
-CLASS="programlisting"
-> NFS server translator is not responding, still trying
-</PRE
-></P
-><P
->With a soft mount, it reduces the number of actual errors returned on timed-out requests.</P
-></DD
-><DT
-><VAR
-CLASS="replaceable"
->translator_machine</VAR
-></DT
-><DD
-><P
->Specifies the fully-qualified hostname of the translator machine whose <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
->
- directory is to be mounted on the client machine's <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
-> directory.</P
-></DD
-></DL
-></DIV
-></P
-><DIV
-CLASS="note"
-><BLOCKQUOTE
-CLASS="note"
-><P
-><B
->Note: </B
->To mount the translator machine's <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
-> directory onto a directory on the NFS
- client other than <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs</B
-></SPAN
->, substitute the alternate directory name for the second instance
- of <SAMP
-CLASS="computeroutput"
->/afs</SAMP
-> in the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->mount</B
-></SPAN
-> command.</P
-></BLOCKQUOTE
-></DIV
-></LI
-><LI
-><P
-><A
-NAME="LIWQ608"
-></A
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->(Optional)</B
-></SPAN
-> If appropriate, create the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/.AFSSERVER</B
-></SPAN
-> file to set the AFSSERVER environment variable for all of the machine's users. For a
- discussion, see <A
-HREF="a33047.html#HDRWQ600"
->Setting the AFSSERVER and AFSCONF Environment Variables</A
->. Place a single
- line in the file, specifying the fully-qualified hostname of the translator machine that is to serve as the remote
- executor. To enable users to issue commands that handle tokens, it must be the machine named as translator_machine in Step
- <A
-HREF="a33047.html#LIWQ607"
->4</A
->.</P
-></LI
-><LI
-><P
-><A
-NAME="LIWQ609"
-></A
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->(Optional)</B
-></SPAN
-> If appropriate, create the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/.AFSCONF</B
-></SPAN
-> file to set the AFSCONF environment variable for all of the machine's users. For a
- discussion, see <A
-HREF="a33047.html#HDRWQ600"
->Setting the AFSSERVER and AFSCONF Environment Variables</A
->. Place a single
- line in the file, specifying the name of the directory where the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->CellServDB</B
-></SPAN
-> and <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->ThisCell</B
-></SPAN
-> files reside. If you use a central update source for these files (by convention, <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs/</B
-></SPAN
->cellname<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/common/etc</B
-></SPAN
->), name it here.</P
-></LI
-></OL
-></DIV
-></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="HDRWQ610"
->Configuring User Accounts</A
-></H1
-><P
->There are no requirements for NFS users to access AFS as unauthenticated users. To take advantage of more AFS
- functionality, however, they must meet the indicated requirements. <UL
-><LI
-><P
->To access AFS as authenticated users, they must of course authenticate with AFS, which requires an entry in the
- Protection and Authentication Databases.</P
-></LI
-><LI
-><P
->To create and store files, they need the required ACL permissions. If you are providing a home directory for storage
- of personal files, it is conventional to create a dedicated volume and mount it at the user's home directory location in
- the AFS filespace.</P
-></LI
-><LI
-><P
->To issue AFS commands, they must meet several additional requirements: <UL
-><LI
-><P
->They must be working on an NFS client machine of a supported system type and from which the AFS command
- binaries are accessible.</P
-></LI
-><LI
-><P
->Their command shell must define values for the AFSSERVER and AFSCONF environment variables, as described in
- <A
-HREF="a33047.html#HDRWQ600"
->Setting the AFSSERVER and AFSCONF Environment Variables</A
->. It is often simplest to
- define the variables by creating <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/.AFSSERVER</B
-></SPAN
-> and <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/.AFSCONF</B
-></SPAN
-> file in the NFS client machine's root directory, but you can also either set the
- variables in each user's shell initialization file (<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->.cshrc</B
-></SPAN
-> or equivalent), or
- create files called <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->.AFSSERVER</B
-></SPAN
-> and <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->.AFSCONF</B
-></SPAN
-> in
- each user's home directory.</P
-></LI
-><LI
-><P
->They must have an entry in the AFS Protection and Authentication Databases, so that they can authenticate if
- the command requires AFS privilege. Other commands instead require assuming the local <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->root</B
-></SPAN
-> identity on the translator machine; for further discussion, see <A
-HREF="a33047.html#HDRWQ601"
->The AFSSERVER Variable</A
->.</P
-></LI
-><LI
-><P
->Their PATH environment variable must include the pathname to the appropriate AFS binaries. If a user works on
- NFS client machines of different system types, include the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->@sys</B
-></SPAN
-> variable in the
- pathname rather than an actual system type name.</P
-></LI
-></UL
-></P
-></LI
-></UL
-></P
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="Header_684"
->To configure a user account for issuing AFS commands</A
-></H2
-><OL
-TYPE="1"
-><LI
-><P
->Create entries for the user in the Protection and Authentication Databases, or create a complete AFS account. See
- the instructions for account creation in <A
-HREF="c24913.html"
->Creating and Deleting User Accounts with the uss Command
- Suite</A
-> or <A
-HREF="c27596.html"
->Administering User Accounts</A
->.</P
-></LI
-><LI
-><P
-><A
-NAME="LIWQ611"
-></A
->Modify the user's PATH environment variable to include the pathname of AFS binaries, such as
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs/</B
-></SPAN
->cellname<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/</B
-></SPAN
->sysname<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/usr/afsws/bin</B
-></SPAN
->. If the user works on NFS client machines of different system types, considering
- replacing the specific sysname value with the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->@sys</B
-></SPAN
-> variable. The PATH variable is
- commonly defined in a login or shell initialization file (such as the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->.login</B
-></SPAN
-> or <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->.cshrc</B
-></SPAN
-> file).</P
-></LI
-><LI
-><P
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->(Optional)</B
-></SPAN
-> Set the AFSSERVER and AFSCONF environment variables if appropriate. This
- is required if the NFS client machines on which the user works do not have the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/.AFSSERVER</B
-></SPAN
-> and <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/.AFSCONF</B
-></SPAN
-> files in their root directories, or if
- you want user-specific values to override those settings.</P
-><P
->Either define the variables in the user's login or shell initialization file, or create the files <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->.AFSSERVER</B
-></SPAN
-> and <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->.AFSCONF</B
-></SPAN
-> files in the user's home directory.</P
-><P
->For the AFSSERVER variable, specify the fully-qualified hostname of the translator machine that is to serve as the
- remote executor. For the AFSCONF variable, specify the name of the directory where the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->CellServDB</B
-></SPAN
-> and <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->ThisCell</B
-></SPAN
-> files reside. If you use a central update
- source for these files (by convention, <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs/</B
-></SPAN
->cellname<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/common/etc</B
-></SPAN
->), name it here.</P
-></LI
-><LI
-><P
->If the pathname you defined in Step <A
-HREF="a33047.html#LIWQ611"
->2</A
-> includes the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->@sys</B
-></SPAN
-> variable, instruct users to check that their system name is defined correctly before they
- issue AFS commands. They issue the following command: <PRE
-CLASS="programlisting"
-> % <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs sysname</B
-></SPAN
->
-</PRE
-></P
-></LI
-></OL
-></DIV
-></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="HDRWQ612"
->Authenticating on Unsupported NFS Client Machines</A
-></H1
-><P
->The <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs</B
-></SPAN
-> command enables users to authenticate with AFS when they are working on NFS
- clients of unsupported system types (those for which AFS binaries are not available). This enables such users to access the AFS
- file tree to the same extent as any other AFS user. They cannot, however, issue AFS commands, which is possible only on NFS
- client machines of supported system types.</P
-><P
->To authenticate on an unsupported system type, establish a connection to the translator machine (using a facility such as
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->telnet</B
-></SPAN
->), and issue the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->klog</B
-></SPAN
-> command to obtain tokens for all
- the cells you wish to contact during the upcoming NFS session. Then issue the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs</B
-></SPAN
-> command,
- which stores the tokens in a credential structure associated with your NFS session. The Cache Manager uses the tokens when
- performing AFS access requests that originate from your NFS session.</P
-><P
->More specifically, the credential structure is identified by a process authentication group (PAG) number associated with a
- particular local UID on a specific NFS client machine. By default, the NFS UID recorded in the credential structure is the same
- as your local UID on the translator machine. You can include the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-id</B
-></SPAN
-> argument to specify an
- alternate NFS UID, unless the translator machine's administrator has used the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs exportafs</B
-></SPAN
->
- command's <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-uidcheck</B
-></SPAN
-> argument to enable UID checking. In that case, the value of the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-id</B
-></SPAN
-> argument must match your local UID on the translator machine (so there is not point to including the
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-id</B
-></SPAN
-> argument). Enforcing matching UIDs prevents someone else from placing their tokens in your
- credential structure, either accidentally or on purpose. However, it means that your cell's administrators must set your local
- UID on the NFS client to match your local UID on the translator machine. It also makes it impossible to authenticate by issuing
- the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->klog</B
-></SPAN
-> command on supported NFS clients, meaning that all NFS users must use the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs</B
-></SPAN
-> command. See <A
-HREF="a33047.html#HDRWQ604"
->Controlling Optional Translator Features</A
->.</P
-><P
->After issuing the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs</B
-></SPAN
-> command, you can begin working on the NFS client with
- authenticated access to AFS. When you are finished working, it is a good policy to destroy your tokens by issuing the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs</B
-></SPAN
-> command on the translator machine again, this time with the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-unlog</B
-></SPAN
->
- flag. This is simpler if you have left the connection to the translator machine open, but you can always establish a new
- connection if you closed the original one.</P
-><P
->If your NFS client machine is a supported system type and you wish to issue AFS commands on it, include the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-sysname</B
-></SPAN
-> argument to the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs</B
-></SPAN
-> command. The remote executor daemon on the
- translator machine substitutes its value for the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->@sys</B
-></SPAN
-> variable in pathnames when executing AFS
- commands that you issue on the NFS client machine. If your PATH environment variable uses the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->@sys</B
-></SPAN
-> variable in the pathnames for directories that house AFS binaries (as recommended), then setting
- this argument enables the remote executor daemon to access the AFS binaries appropriate for your NFS client machine even if its
- system type differs from the translator machine's.</P
-><P
->If you do not issue the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs</B
-></SPAN
-> command (or the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->klog</B
-></SPAN
->
- command on the NFS client machine itself, if it is a supported system type), then you are not authenticated with AFS. For a
- description of unauthenticated access, see <A
-HREF="a33047.html#HDRWQ599"
->Enabling Unauthenticated or Authenticated AFS Access</A
->.
- </P
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="Header_686"
->To authenticate using the knfs command</A
-></H2
-><OL
-TYPE="1"
-><LI
-><P
->Log on to the relevant translator machine, either on the console or remotely by using a program such as <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->telnet</B
-></SPAN
->.</P
-></LI
-><LI
-><P
->Obtain tokens for every cell you wish to access while working on the NFS client. AFS-modified login utilities
- acquire a token for the translator machine's local cell by default; use <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->klog</B
-></SPAN
-> command to
- obtain tokens for other cells if desired.</P
-></LI
-><LI
-><P
->Issue the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs</B
-></SPAN
-> command to create a credential structure in the translator machine's
- kernel memory for storing the tokens obtained in the previous step. Include the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-id</B
-></SPAN
->
- argument to associate the structure with a UID on the NFS client that differs from your local UID on the translator
- machine. This is possible unless the translator machine's administrator has enabled UID checking on the translator
- machine; see <A
-HREF="a33047.html#HDRWQ604"
->Controlling Optional Translator Features</A
->. If the NFS client machine is a
- supported system type and you wish to issue AFS commands on it, include the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-sysname</B
-></SPAN
->
- argument to specify its system type. <PRE
-CLASS="programlisting"
-> % <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs -host</B
-></SPAN
-> <<VAR
-CLASS="replaceable"
->host name</VAR
->> [<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-id</B
-></SPAN
-> <<VAR
-CLASS="replaceable"
->user ID (decimal)</VAR
->>] \
- [<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-sysname</B
-></SPAN
-> <<VAR
-CLASS="replaceable"
->host's '@sys' value</VAR
->>]
-</PRE
-></P
-><P
->where <DIV
-CLASS="variablelist"
-><DL
-><DT
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-host</B
-></SPAN
-></DT
-><DD
-><P
->Specifies the fully-qualified hostname of the NFS client machine on which you are working.</P
-></DD
-><DT
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-id</B
-></SPAN
-></DT
-><DD
-><P
->Specifies a local UID number on the NFS client machine with which to associate the tokens, if different from
- your local UID on the translator machine. If this argument is omitted, the tokens are associated with an NFS UID
- that matches your local UID on the translator machine. In both cases, the NFS client software marks your AFS
- access requests with the NFS UID when it forwards them to the Cache Manager on the translator machine.</P
-></DD
-><DT
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-sysname</B
-></SPAN
-></DT
-><DD
-><P
->Specifies the value that the local machine's remote executor daemon substitutes for the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->@sys</B
-></SPAN
-> variable in pathnames when executing AFS commands issued on the NFS client machine
- (which must be a supported system type).</P
-></DD
-></DL
-></DIV
-></P
-><P
->The following error message indicates that the translator machine's administrator has enabled UID checking and you
- have provided a value that differs from your local UID on the translator machine.</P
-><PRE
-CLASS="programlisting"
-> knfs: Translator in 'passwd sync' mode; remote uid must be the same as local uid
-</PRE
-></LI
-><LI
-><P
->Close the connection to the translator machine (if desired) and work on the NFS client machine.</P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="Header_687"
->To display tokens using the knfs command</A
-></H2
-><OL
-TYPE="1"
-><LI
-><P
->Log on to the relevant translator machine, either on the console or remotely by using a program such as <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->telnet</B
-></SPAN
->.</P
-></LI
-><LI
-><P
->Issue the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs</B
-></SPAN
-> command with the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-tokens</B
-></SPAN
-> flag to
- display the tokens associated with either the NFS UID that matches your local UID on the translator machine or the NFS UID
- specified by the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-id</B
-></SPAN
-> argument. <PRE
-CLASS="programlisting"
-> % <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs -host</B
-></SPAN
-> <<VAR
-CLASS="replaceable"
->host name</VAR
->> [<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-id</B
-></SPAN
-> <<VAR
-CLASS="replaceable"
->user ID (decimal)</VAR
->>] <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-tokens</B
-></SPAN
->
-</PRE
-></P
-><P
->where <DIV
-CLASS="variablelist"
-><DL
-><DT
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-host</B
-></SPAN
-></DT
-><DD
-><P
->Specifies the fully-qualified hostname of the NFS client machine on which you are working.</P
-></DD
-><DT
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-id</B
-></SPAN
-></DT
-><DD
-><P
->Specifies the local UID on the NFS client machine for which to display tokens, if different from your local
- UID on the translator machine. If this argument is omitted, the tokens are for the NFS UID that matches your local
- UID on the translator machine.</P
-></DD
-><DT
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-tokens</B
-></SPAN
-></DT
-><DD
-><P
->Displays the tokens.</P
-></DD
-></DL
-></DIV
-></P
-></LI
-><LI
-><P
->Close the connection to the translator machine if desired.</P
-></LI
-></OL
-></DIV
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="Header_688"
->To discard tokens using the knfs command</A
-></H2
-><OL
-TYPE="1"
-><LI
-><P
->If you closed your connection to the translator machine after issuing the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs</B
-></SPAN
->
- command, reopen it.</P
-></LI
-><LI
-><P
->Issue the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs</B
-></SPAN
-> command with the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-unlog</B
-></SPAN
-> flag.
- <PRE
-CLASS="programlisting"
-> % <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->knfs -host</B
-></SPAN
-> <<VAR
-CLASS="replaceable"
->host name</VAR
->> [<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-id</B
-></SPAN
-> <<VAR
-CLASS="replaceable"
->user ID (decimal)</VAR
->>] <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-unlog</B
-></SPAN
->
-</PRE
-></P
-><P
->where <DIV
-CLASS="variablelist"
-><DL
-><DT
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-host</B
-></SPAN
-></DT
-><DD
-><P
->Specifies the fully-qualified hostname of the NFS client machine you are working on.</P
-></DD
-><DT
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-id</B
-></SPAN
-></DT
-><DD
-><P
->Specifies the local UID number on the NFS client machine for which to discard the associated tokens, if
- different from your local UID on the translator machine. If this argument is omitted, the tokens associated with
- an NFS UID that matches your local UID on the translator machine are discarded.</P
-></DD
-><DT
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-unlog</B
-></SPAN
-></DT
-><DD
-><P
->Discards the tokens.</P
-></DD
-></DL
-></DIV
-></P
-></LI
-><LI
-><P
->If desired, close the connection to the translator machine.</P
-></LI
-></OL
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="c32432.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="book1.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="a33826.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Managing Administrative Privilege</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Using AFS Commands</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<HTML
-><HEAD
-><TITLE
->Using AFS Commands</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="AFS Administration Guide"
-HREF="book1.html"><LINK
-REL="PREVIOUS"
-TITLE="Managing the NFS/AFS Translator"
-HREF="a33047.html"><LINK
-REL="NEXT"
-TITLE="The afsmonitor Program Statistics"
-HREF="a34149.html"></HEAD
-><BODY
-CLASS="appendix"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->AFS Administration Guide: Version 3.6</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="a33047.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="a34149.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="appendix"
-><H1
-><A
-NAME="HDRCOMMANDS"
-></A
->Appendix B. Using AFS Commands</H1
-><P
->This section describes the components of AFS commands and how to make entering commands more efficient by using shortened
- forms. It has the following sections: <TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-><A
-HREF="a33826.html#HDRWQ613"
->AFS Command Syntax</A
-></TD
-></TR
-><TR
-><TD
-><A
-HREF="a33826.html#HDRWQ614"
->Rules for Entering AFS Commands</A
-></TD
-></TR
-><TR
-><TD
-><A
-HREF="a33826.html#HDRWQ615"
->Rules for Using Abbreviations and Aliases</A
-></TD
-></TR
-><TR
-><TD
-><A
-HREF="a33826.html#HDRWQ616"
->Displaying Online Help for AFS Commands</A
-></TD
-></TR
-></TBODY
-></TABLE
-></P
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="HDRWQ613"
->AFS Command Syntax</A
-></H1
-><P
->AFS commands that belong to suites have the following structure:</P
-><PRE
-CLASS="programlisting"
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->command_suite operation_code</B
-></SPAN
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-switch</B
-></SPAN
-> <VAR
-CLASS="replaceable"
-><value></VAR
->[+] [<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-flag</B
-></SPAN
->]
-</PRE
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="Header_691"
->Command Names</A
-></H2
-><P
->Together, the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->command_suite</B
-></SPAN
-> and <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->operation_code</B
-></SPAN
-> make up
- the <SPAN
-CLASS="emphasis"
-><I
-CLASS="emphasis"
->command name</I
-></SPAN
->.</P
-><P
->The <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->command_suite</B
-></SPAN
-> specifies the group of related commands to which the command belongs,
- and indicates which command interpreter and server process perform the command. AFS has several command suites, including
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos</B
-></SPAN
->, <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs</B
-></SPAN
->, <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->kas</B
-></SPAN
->, <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->package</B
-></SPAN
->, <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->pts</B
-></SPAN
->, <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->scout</B
-></SPAN
->, <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->uss</B
-></SPAN
-> and <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->vos</B
-></SPAN
->. Some of these suites have an interactive mode in which
- the issuer omits the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->command_suite</B
-></SPAN
-> portion of the command name.</P
-><P
->The <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->operation_code</B
-></SPAN
-> tells the command interpreter and server process which action to
- perform. Most command suites include several operation codes. The <SPAN
-CLASS="emphasis"
-><I
-CLASS="emphasis"
->IBM AFS Administration Reference</I
-></SPAN
->
- describes each operation code in detail, and the <SPAN
-CLASS="emphasis"
-><I
-CLASS="emphasis"
->IBM AFS Administration Guide</I
-></SPAN
-> describes how to use them
- in the context of performing administrative tasks.</P
-><P
->Several AFS commands do not belong to a suite and so their names do not have a <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->command_suite</B
-></SPAN
-> portion. Their structure is otherwise similar to the commands in the suites.</P
-></DIV
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="Header_692"
->Options</A
-></H2
-><P
->The term <SPAN
-CLASS="emphasis"
-><I
-CLASS="emphasis"
->option</I
-></SPAN
-> refers to both arguments and flags, which are described in the following
- sections.</P
-></DIV
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="Header_693"
->Arguments</A
-></H2
-><P
->One or more arguments can follow the command name. Arguments specify the entities on which to act while performing the
- command (for example, which server machine, server process, or file). To minimize the potential for error, provide a command's
- arguments in the order prescribed in its syntax definition.</P
-><P
->Each argument has two parts, which appear in the indicated order: <UL
-><LI
-><P
->The <SPAN
-CLASS="emphasis"
-><I
-CLASS="emphasis"
->switch</I
-></SPAN
-> specifies the argument's type and is preceded by a hyphen ( <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-</B
-></SPAN
-> ). For instance, the switch <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-server</B
-></SPAN
-> usually indicates that the
- argument names a server machine. Switches can often be omitted, subject to the rules outlined in <A
-HREF="a33826.html#HDRNOSWITCH"
->Conditions for Omitting Switches</A
->.</P
-></LI
-><LI
-><P
->The <SPAN
-CLASS="emphasis"
-><I
-CLASS="emphasis"
->value</I
-></SPAN
-> names a particular entity of the type specified by the preceding switch. For
- example, the proper value for a <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-server</B
-></SPAN
-> switch is a server machine name like <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs3.abc.com</B
-></SPAN
->. Unlike switches (which have a required form), values vary depending on what the
- issuer wants to accomplish. Values appear surrounded by angle brackets (<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->< ></B
-></SPAN
->) in
- command descriptions and the online help to show that they are user-supplied variable information.</P
-></LI
-></UL
-></P
-><P
->Some arguments accept multiple values, as indicated by trailing plus sign ( <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->+</B
-></SPAN
-> ) in the
- command descriptions and online help. How many of a command's arguments take multiple values, and their ordering with respect
- to other arguments, determine when it is acceptable to omit switches. See <A
-HREF="a33826.html#HDRNOSWITCH"
->Conditions for Omitting
- Switches</A
->.</P
-><P
->Some commands have optional as well as required arguments; the command descriptions and online help show optional
- arguments in square brackets ([ ]).</P
-></DIV
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="Header_694"
->Flags</A
-></H2
-><P
->Some commands have one or more flags, which specify the manner in which the command interpreter and server process
- perform the command, or what kind of output it produces. Flags are preceded by hyphens like switches, but they take no values.
- Although the command descriptions and online help generally list a command's flags after its arguments, there is no prescribed
- order for flags. They can appear anywhere on the command line following the operation code, except in between the parts of an
- argument. Flags are always optional.</P
-></DIV
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="HDRCOMMAND-EX"
->An Example Command</A
-></H2
-><P
->The following example illustrates the different parts of a command that belongs to an AFS command suite.</P
-><PRE
-CLASS="programlisting"
-> % <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos getdate -server fs1.abc.com -file ptserver kaserver</B
-></SPAN
->
-</PRE
-><P
->where <UL
-><LI
-><P
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos</B
-></SPAN
-> is the command suite. The BOS Server executes most of the commands in this
- suite.</P
-></LI
-><LI
-><P
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->getdate</B
-></SPAN
-> is the operation code. It tells the BOS Server on the specified server
- machine (in this case <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs1.abc.com</B
-></SPAN
->) to report the modification dates of binary files in
- the local <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/usr/afs/bin</B
-></SPAN
-> directory.</P
-></LI
-><LI
-><P
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-server fs1.abc.com</B
-></SPAN
-> is one argument, with <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-server</B
-></SPAN
-> as the switch and <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs1.abc.com</B
-></SPAN
-> as the value. This
- argument specifies the server machine on which BOS Server is to collect and report binary dates.</P
-></LI
-><LI
-><P
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-file ptserver kaserver</B
-></SPAN
-> is an argument that takes multiple values. The switch is
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-file</B
-></SPAN
-> and the values are <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->ptserver</B
-></SPAN
-> and <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->kaserver</B
-></SPAN
->. This argument tells the BOS Server to report the modification dates on the files
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/usr/afs/bin/kaserver</B
-></SPAN
-> and <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/usr/afs/bin/ptserver</B
-></SPAN
->.</P
-></LI
-></UL
-></P
-></DIV
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="HDRWQ614"
->Rules for Entering AFS Commands</A
-></H2
-><P
->Enter each AFS command on a single line (press <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
-><Return></B
-></SPAN
-> only at the end of the
- command). Some commands in this document appear broken across multiple lines, but that is for legibility only.</P
-><P
->Use a space to separate each element on a command line from its neighbors. Spaces rather than commas also separate
- multiple values of an argument.</P
-><P
->In many cases, the issuer of a command can reduce the amount of typing necessary by using one or both of the following
- methods: <UL
-><LI
-><P
->Omitting switches</P
-></LI
-><LI
-><P
->Using accepted abbreviations for operation codes, switches (if they are included at all), and some types of
- values</P
-></LI
-></UL
-></P
-><P
->The following sections explain the conditions for omitting or shortening parts of the command line. It is always
- acceptable to type a command in full, with all of its switches and no abbreviations.</P
-><DIV
-CLASS="sect3"
-><H3
-CLASS="sect3"
-><A
-NAME="HDRNOSWITCH"
->Conditions for Omitting Switches</A
-></H3
-><P
->It is always acceptable to type the switch part of an argument, but in many cases it is not necessary. Specifically,
- switches can be omitted if the following conditions are met. <UL
-><LI
-><P
->All of the command's required arguments appear in the order prescribed by the syntax statement</P
-></LI
-><LI
-><P
->No switch is provided for any argument</P
-></LI
-><LI
-><P
->There is only one value for each argument (but note the important exception discussed in the following
- paragraph)</P
-></LI
-></UL
-></P
-><P
->Omitting switches is possible only because there is a prescribed order for each command's arguments. When the issuer
- does not include switches, the command interpreter relies instead on the order of arguments; it assumes that the first
- element after the operation code is the command's first argument, the next element is the command's second argument, and so
- on. The important exception is when a command's final required argument accepts multiple values. In this case, the command
- interpreter assumes that the issuer has correctly provided one value for each argument up through the final one, so any
- additional values at the end belong to the final argument.</P
-><P
->The following list describes the rules for omitting switches from the opposite perspective: an argument's switch must
- be provided when any of the following conditions apply. <UL
-><LI
-><P
->The command's arguments do not appear in the prescribed order</P
-></LI
-><LI
-><P
->An optional argument is omitted but a subsequent optional argument is provided</P
-></LI
-><LI
-><P
->A switch is provided for a preceding argument</P
-></LI
-><LI
-><P
->More than one value is supplied for a preceding argument (which must take multiple values, of course); without a
- switch on the current argument, the command interpreter assumes that the current argument is another value for the
- preceding argument</P
-></LI
-></UL
-></P
-></DIV
-><DIV
-CLASS="sect3"
-><H3
-CLASS="sect3"
-><A
-NAME="Header_698"
->An Example of Omitting Switches</A
-></H3
-><P
->Consider again the example command from <A
-HREF="a33826.html#HDRCOMMAND-EX"
->An Example Command</A
->.</P
-><PRE
-CLASS="programlisting"
-> % <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos getdate -server fs1.abc.com -file ptserver kaserver</B
-></SPAN
->
-</PRE
-><P
->This command has two required arguments: the server machine name (identified by the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-server</B
-></SPAN
-> switch) and binary file name (identified by the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-file</B
-></SPAN
->
- switch). The second argument accepts multiple values. By complying with all three conditions, the issuer can omit the
- switches:</P
-><PRE
-CLASS="programlisting"
-> % <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos getdate fs1.abc.com ptserver kaserver</B
-></SPAN
->
-</PRE
-><P
->Because there are no switches, the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos</B
-></SPAN
-> command interpreter relies on the order of
- arguments. It assumes that the first element following the operation code, <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs1.abc.com</B
-></SPAN
->, is
- the server machine name, and that the next argument, <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->ptserver</B
-></SPAN
->, is a binary file name. Then,
- because the command's second (and last) argument accepts multiple values, the command interpreter correctly interprets
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->kaserver</B
-></SPAN
-> as an additional value for it.</P
-><P
->On the other hand, the following is not acceptable because it violates the first two conditions in <A
-HREF="a33826.html#HDRNOSWITCH"
->Conditions for Omitting Switches</A
->: even though there is only one value per argument, the
- arguments do not appear in the prescribed order, and a switch is provided for one argument but not the other.</P
-><PRE
-CLASS="programlisting"
-> % <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos getdate ptserver -server fs1.abc.com</B
-></SPAN
->
-</PRE
-></DIV
-></DIV
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="HDRWQ615"
->Rules for Using Abbreviations and Aliases</A
-></H2
-><P
->This section explains how to abbreviate operation codes, option names, server machine names, partition names, and cell
- names. It is not possible to abbreviate other types of values.</P
-><DIV
-CLASS="sect3"
-><H3
-CLASS="sect3"
-><A
-NAME="Header_700"
->Abbreviating Operation Codes</A
-></H3
-><P
->It is acceptable to abbreviate an operation code to the shortest form that still distinguishes it from the other
- operation codes in its suite.</P
-><P
->For example, it is acceptable to shorten <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos install</B
-></SPAN
-> to <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos
- i</B
-></SPAN
-> because there are no other operation codes in the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos</B
-></SPAN
-> command suite that begin
- with the letter <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->i</B
-></SPAN
->. In contrast, there are several <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos</B
-></SPAN
->
- operation codes that start with the letter <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->s</B
-></SPAN
->, so the abbreviations must be longer to remain
- unambiguous: <TABLE
-BORDER="0"
-><TBODY
-><TR
-><TD
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos sa</B
-></SPAN
-> for <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos salvage</B
-></SPAN
-></TD
-></TR
-><TR
-><TD
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos seta</B
-></SPAN
-> for <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos setauth</B
-></SPAN
-></TD
-></TR
-><TR
-><TD
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos setc</B
-></SPAN
-> for <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos setcellname</B
-></SPAN
-></TD
-></TR
-><TR
-><TD
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos setr</B
-></SPAN
-> for <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos setrestart</B
-></SPAN
-></TD
-></TR
-><TR
-><TD
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos sh</B
-></SPAN
-> for <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos shutdown</B
-></SPAN
-></TD
-></TR
-><TR
-><TD
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos start</B
-></SPAN
-> for <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos start</B
-></SPAN
-></TD
-></TR
-><TR
-><TD
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos startu</B
-></SPAN
-> for <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos startup</B
-></SPAN
-></TD
-></TR
-><TR
-><TD
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos stat</B
-></SPAN
-> for <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos status</B
-></SPAN
-></TD
-></TR
-><TR
-><TD
-><SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos sto</B
-></SPAN
-> for <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos stop</B
-></SPAN
-></TD
-></TR
-></TBODY
-></TABLE
-></P
-><P
->In addition to abbreviations, some operation codes have an <SPAN
-CLASS="emphasis"
-><I
-CLASS="emphasis"
->alias</I
-></SPAN
->, a short form that is not
- derived by abbreviating the operation code to its shortest unambiguous form. For example, the alias for the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs setacl</B
-></SPAN
-> command is <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs sa</B
-></SPAN
->, whereas the shortest unambiguous
- abbreviation is <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs seta</B
-></SPAN
->.</P
-><P
->There are two usual reasons an operation code has an alias: <UL
-><LI
-><P
->Because the command is frequently issued, it is convenient to have a form shorter than the one derived by
- abbreviating. The <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs setacl</B
-></SPAN
-> command is an example.</P
-></LI
-><LI
-><P
->Because the command's name has changed, but users of previous versions of AFS know the former name. For example,
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos listhosts</B
-></SPAN
-> has the alias <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos getcell</B
-></SPAN
->, its former
- name. It is acceptable to abbreviate aliases to their shortest unambiguous form (for example, <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos getcell</B
-></SPAN
-> to <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bos getc</B
-></SPAN
->).</P
-></LI
-></UL
-></P
-><P
->Even if an operation code has an alias, it is still acceptable to use the shortest unambiguous form. Thus, the
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs setacl</B
-></SPAN
-> command has three acceptable forms: <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs setacl</B
-></SPAN
->
- (the full form), <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs seta</B
-></SPAN
-> (the shortest abbreviation), and <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs
- sa</B
-></SPAN
-> (the alias).</P
-></DIV
-><DIV
-CLASS="sect3"
-><H3
-CLASS="sect3"
-><A
-NAME="Header_701"
->Abbreviating Switches and Flags</A
-></H3
-><P
->It is acceptable to shorten a switch or flag to the shortest form that distinguishes it from the other switches and
- flags for its operation code. It is often possible to omit switches entirely, subject to the conditions listed in <A
-HREF="a33826.html#HDRNOSWITCH"
->Conditions for Omitting Switches</A
->.</P
-></DIV
-><DIV
-CLASS="sect3"
-><H3
-CLASS="sect3"
-><A
-NAME="HDRFMSABBREV"
->Abbreviating Server Machine Names</A
-></H3
-><P
->AFS server machines must have fully-qualified Internet-style host names (for example, <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs1.abc.com</B
-></SPAN
->), but it is not always necessary to type the full name on the command line. AFS commands
- accept unambiguous shortened forms, but depend on the cell's name service (such as the Domain Name Service) or a local host
- table to resolve a shortened name to the fully-qualified equivalent when the command is issued.</P
-><P
->Most commands also accept the dotted decimal form of the machine's IP address as an identifier.</P
-></DIV
-><DIV
-CLASS="sect3"
-><H3
-CLASS="sect3"
-><A
-NAME="HDRPARTABBREV"
->Abbreviating Partition Names</A
-></H3
-><P
->Partitions that house AFS volumes must have names of the form <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/vicep</B
-></SPAN
-><VAR
-CLASS="replaceable"
->x</VAR
-> or <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/vicep</B
-></SPAN
-><VAR
-CLASS="replaceable"
->xx</VAR
->, where the variable final portion is one or two lowercase
- letters. By convention, the first server partition created on a file server machine is called <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/vicepa</B
-></SPAN
->, the second <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/vicepb</B
-></SPAN
->, and so on. The <SPAN
-CLASS="emphasis"
-><I
-CLASS="emphasis"
->IBM AFS Quick
- Beginnings</I
-></SPAN
-> explains how to configure and name a file server machine's partitions in preparation for storing AFS
- volumes on them.</P
-><P
->When issuing AFS commands, you can abbreviate a partition name using any of the following forms:</P
-><PRE
-CLASS="programlisting"
-> <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/vicepa</B
-></SPAN
-> = <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->vicepa</B
-></SPAN
-> = <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->a</B
-></SPAN
-> = <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->0</B
-></SPAN
->
-<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/vicepb</B
-></SPAN
-> = <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->vicepb</B
-></SPAN
-> = <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->b</B
-></SPAN
-> = <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->1</B
-></SPAN
->
-</PRE
-><P
->After <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/vicepz</B
-></SPAN
-> (for which the index is 25) comes</P
-><PRE
-CLASS="programlisting"
-> <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/vicepaa</B
-></SPAN
-> = <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->vicepaa</B
-></SPAN
-> = <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->aa</B
-></SPAN
-> = <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->26</B
-></SPAN
->
-<SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/vicepab</B
-></SPAN
-> = <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->vicepab</B
-></SPAN
-> = <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->ab</B
-></SPAN
-> = <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->27</B
-></SPAN
->
-</PRE
-><P
->and so on through</P
-><PRE
-CLASS="programlisting"
-> <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/vicepiv</B
-></SPAN
-> = <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->vicepiv</B
-></SPAN
-> = <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->iv</B
-></SPAN
-> = <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->255</B
-></SPAN
->
-</PRE
-></DIV
-><DIV
-CLASS="sect3"
-><H3
-CLASS="sect3"
-><A
-NAME="HDRCELLABBREV"
->Abbreviating Cell Names</A
-></H3
-><P
->A cell's full name usually matches its Internet domain name (such as <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->stateu.edu</B
-></SPAN
-> for
- the State University or <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->abc.com</B
-></SPAN
-> for ABC Corporation). Some AFS commands accept unambiguous
- shortened forms, usually with respect to the local <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/usr/vice/etc/CellServDB file</B
-></SPAN
-> but
- sometimes depending on the ability of the local name service to resolve the corresponding domain name.</P
-></DIV
-></DIV
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="HDRWQ616"
->Displaying Online Help for AFS Commands</A
-></H2
-><P
->To display online help for AFS commands that belong to suites, use the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->help</B
-></SPAN
-> and
- <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->apropos</B
-></SPAN
-> operation codes. A <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-help</B
-></SPAN
-> flag is also available on
- every almost every AFS command.</P
-><P
->The online help entry for a command consists of two or three lines: <UL
-><LI
-><P
->The first line names the command and briefly describes what it does</P
-></LI
-><LI
-><P
->If the command has aliases, they appear on the next line</P
-></LI
-><LI
-><P
->The final line, which begins with the string <SAMP
-CLASS="computeroutput"
->Usage:</SAMP
->, lists the command's options
- in the prescribed order; online help entries use the same typographical symbols (brackets and so on) as this
- documentation.</P
-></LI
-></UL
-></P
-><P
->If no operation code is specified, the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->help</B
-></SPAN
-> operation code displays the first line
- (short description) for every operation code in the suite:</P
-><PRE
-CLASS="programlisting"
-> % <VAR
-CLASS="replaceable"
->command_suite</VAR
-> <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->help</B
-></SPAN
->
-</PRE
-><P
->If the issuer specifies one or more operation codes, the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->help</B
-></SPAN
-> operation code displays
- each command's complete online entry (short description, alias if any, and syntax):</P
-><PRE
-CLASS="programlisting"
-> % <VAR
-CLASS="replaceable"
->command_suite</VAR
-> <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->help</B
-></SPAN
-> <VAR
-CLASS="replaceable"
->operation_code</VAR
->+
-</PRE
-><P
->The <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-help</B
-></SPAN
-> flag displays a command's syntax but not the short description or
- alias:</P
-><PRE
-CLASS="programlisting"
-> % <VAR
-CLASS="replaceable"
->command_name</VAR
-> <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-help</B
-></SPAN
->
-</PRE
-><P
->The <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->apropos</B
-></SPAN
-> operation code displays the short description of any command in a suite
- whose operation code or short description includes the specified keyword:</P
-><PRE
-CLASS="programlisting"
-> % <VAR
-CLASS="replaceable"
->command_suite</VAR
-> <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->apropos</B
-></SPAN
-> <VAR
-CLASS="replaceable"
->"<help string>"</VAR
->
-</PRE
-><P
->The following example command displays the complete online help entry for the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs setacl</B
-></SPAN
->
- command:</P
-><PRE
-CLASS="programlisting"
-> % <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs help setacl</B
-></SPAN
->
- fs setacl: set access control list
- aliases: sa
- Usage: fs setacl -dir <<VAR
-CLASS="replaceable"
->directory</VAR
->>+ -acl <<VAR
-CLASS="replaceable"
->access list entries</VAR
->>+
- [-clear] [-negative] [-id] [-if] [-help]
-</PRE
-><P
->To see only the syntax statement, use the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->-help</B
-></SPAN
-> flag:</P
-><PRE
-CLASS="programlisting"
-> % <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs setacl -help</B
-></SPAN
->
- Usage: fs setacl -dir <<VAR
-CLASS="replaceable"
->directory</VAR
->>+ -acl <<VAR
-CLASS="replaceable"
->access list entries</VAR
->>+
- [-clear] [-negative] [-id] [-if] [-help]
-</PRE
-><P
->In the following example, a user wants to display the quota for her home volume. She knows that the relevant command
- belongs to the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs</B
-></SPAN
-> suite, but cannot remember the operation code. She uses <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->quota</B
-></SPAN
-> as the keyword:</P
-><PRE
-CLASS="programlisting"
-> % <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs apropos quota</B
-></SPAN
->
- listquota: list volume quota
- quota: show volume quota usage
- setquota: set volume quota
-</PRE
-><P
->The following illustrates the error message that results if no command name or short description contains the
- keyword:</P
-><PRE
-CLASS="programlisting"
-> % <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->fs apropos "list quota"</B
-></SPAN
->
- Sorry, no commands found
-</PRE
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="a33047.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="book1.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="a34149.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Managing the NFS/AFS Translator</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->The afsmonitor Program Statistics</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<HTML
-><HEAD
-><TITLE
->The afsmonitor Program Statistics</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="AFS Administration Guide"
-HREF="book1.html"><LINK
-REL="PREVIOUS"
-TITLE="Using AFS Commands"
-HREF="a33826.html"><LINK
-REL="NEXT"
-TITLE="AIX Audit Events"
-HREF="a35965.html"></HEAD
-><BODY
-CLASS="appendix"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->AFS Administration Guide: Version 3.6</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="a33826.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="a35965.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="appendix"
-><H1
-><A
-NAME="HDRWQ617"
-></A
->Appendix C. The afsmonitor Program Statistics</H1
-><P
->This appendix lists the statistics you can gather with the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->afsmonitor</B
-></SPAN
-> program, grouping
- them by category and section, and briefly describing each field, group, and section. For instructions on using the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->afsmonitor</B
-></SPAN
-> program, see <A
-HREF="c18360.html"
->Monitoring and Auditing AFS Performance</A
-> </P
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="HDRWQ618"
->The Cache Manager Statistics</A
-></H1
-><P
->Cache Manager statistics fields are classified into the following sections and groups: <UL
-><LI
-><P
->PerfStats_section - Performance Statistics Section. <UL
-><LI
-><P
->PerfStats_group - Performance Statistics Group.</P
-></LI
-><LI
-><P
->misc_group - Miscellaneous Group.</P
-></LI
-></UL
-></P
-></LI
-><LI
-><P
->Server_UpDown_section - Server Up/Down Statistics Section. <UL
-><LI
-><P
->FS_upDown_SC_group - File Server Up/Down Statistics in Same Cell Group.</P
-></LI
-><LI
-><P
->FS_upDown_OC_group - File Server Up/Down Statistics in Other Cells Group.</P
-></LI
-><LI
-><P
->VL_upDown_SC_group - VL Server Up/Down Statistics in Same Cell Group.</P
-></LI
-><LI
-><P
->VL_upDown_OC_group - VL Server Up/Down Statistics in Other Cells Group.</P
-></LI
-></UL
-></P
-></LI
-><LI
-><P
->RPCop_section - RPC Operation Measurements Section. <UL
-><LI
-><P
->FS_RPCopTimes_group - File Server RPC Operation Timings Group.</P
-></LI
-><LI
-><P
->FS_RPCopErrors_group - File Server RPC Operation Errors Group.</P
-></LI
-><LI
-><P
->FS_RPCopBytes_group - File Server RPC Transfer Timings Group.</P
-></LI
-><LI
-><P
->CM_RPCopTimes_group - Cache Manager RPC Operation Timings Group.</P
-></LI
-></UL
-></P
-></LI
-><LI
-><P
->Auth_Access_section - Authentication and Replicated File Access Section. <UL
-><LI
-><P
->Auth_Stats_group - Authentication Information for Cache Manager Group.</P
-></LI
-><LI
-><P
->Access_Stats_group - Unreplicated File Access Group.</P
-></LI
-></UL
-></P
-></LI
-></UL
-></P
-><P
->All Cache Manager variables categorized under these sections and groups names are listed below.</P
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="Header_708"
->Performance Statistics Section (PerfStats_section)</A
-></H2
-><P
->Performance Statistics Group (PerfStats_group) <UL
-><LI
-><P
->dlocalAccesses: Number of data accesses to files within local cell.</P
-></LI
-><LI
-><P
->vlocalAccesses: Number of stat accesses to files within local cell.</P
-></LI
-><LI
-><P
->dremoteAccesses: Number of data accesses to files outside of local cell.</P
-></LI
-><LI
-><P
->vremoteAccesses: Number of stat accesses to files outside of local cell.</P
-></LI
-><LI
-><P
->cacheNumEntries: Number of cache entries.</P
-></LI
-><LI
-><P
->cacheBlocksTotal: Number of (1K) blocks configured for cache.</P
-></LI
-><LI
-><P
->cacheBlocksInUse: Number of cache blocks actively in use.</P
-></LI
-><LI
-><P
->cacheBlocksOrig: Number of cache blocks at bootup.</P
-></LI
-><LI
-><P
->cacheMaxDirtyChunks: Maximum number of dirty cache chunks tolerated.</P
-></LI
-><LI
-><P
->cacheCurrDirtyChunks: Current number of dirty cache chunks.</P
-></LI
-><LI
-><P
->dcacheHits: Number of data files found in local cache.</P
-></LI
-><LI
-><P
->vcacheHits: Number of stat entries found in local cache.</P
-></LI
-><LI
-><P
->dcacheMisses: Number of data files <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->not</B
-></SPAN
-> found in local cache.</P
-></LI
-><LI
-><P
->vcacheMisses: Number of stat entries <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->not</B
-></SPAN
-> found in local cache.</P
-></LI
-><LI
-><P
->cacheFlushes: Number of files flushed from cache.</P
-></LI
-><LI
-><P
->cacheFilesReused: Number of cache files reused.</P
-></LI
-><LI
-><P
->dcacheXAllocs: Additionally allocated dcaches.</P
-></LI
-><LI
-><P
->vcacheXAllocs: Additionally allocated vcaches.</P
-></LI
-><LI
-><P
->bufAlloced: Number of buffers allocated by AFS.</P
-></LI
-><LI
-><P
->bufHits: Number of pages found on buffer cache.</P
-></LI
-><LI
-><P
->bufMisses: Number of pages <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->not</B
-></SPAN
-> found on buffer cache.</P
-></LI
-><LI
-><P
->bufFlushDirty: Number of cached dirty buffers flushed because all were busy.</P
-></LI
-><LI
-><P
->LargeBlocksActive: Number of currently used large free pool entries.</P
-></LI
-><LI
-><P
->LargeBlocksAlloced: Number of allocated large free pool entries.</P
-></LI
-><LI
-><P
->SmallBlocksActive: Number of currently used small free pool entries.</P
-></LI
-><LI
-><P
->SmallBlocksAlloced: Number of allocated used small free pool entries.</P
-></LI
-><LI
-><P
->OutStandingMemUsage: Amount of allocated memory.</P
-></LI
-><LI
-><P
->OutStandingAllocs: Outstanding osi_allocs (no osi_frees yet).</P
-></LI
-><LI
-><P
->CallBackAlloced: Number of callback structures allocated.</P
-></LI
-><LI
-><P
->CallBackFlushes: Number of callback flush operations performed.</P
-></LI
-><LI
-><P
->srvRecords: Number of servers currently on record.</P
-></LI
-><LI
-><P
->srvRecordsHWM: Server record high water mark.</P
-></LI
-><LI
-><P
->srvNumBuckets: Number of server hash chain buckets.</P
-></LI
-><LI
-><P
->srvMaxChainLength: Maximum server hash chain length.</P
-></LI
-><LI
-><P
->srvMaxChainLengthHWM: Server hash chain high water mark.</P
-></LI
-><LI
-><P
->sysName_ID: Sysname ID for host hardware.</P
-></LI
-></UL
-></P
-><P
->Miscellaneous Group (misc_group) <UL
-><LI
-><P
->numPerfCalls: Number of performance calls received.</P
-></LI
-><LI
-><P
->epoch: Cache Manager epoch time.</P
-></LI
-><LI
-><P
->numCellsVisible: Number of cells we know about.</P
-></LI
-><LI
-><P
->numCellsContacted: Number of cells contacted.</P
-></LI
-></UL
-></P
-></DIV
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="Header_709"
->Server Up/Down Statistics Section (Server_UpDown_section)</A
-></H2
-><P
->File Server Up/Down Statistics in Same Cell Group (FS_upDown_SC_group) <DIV
-CLASS="note"
-><BLOCKQUOTE
-CLASS="note"
-><P
-><B
->Note: </B
->The <SPAN
-CLASS="emphasis"
-><I
-CLASS="emphasis"
->records</I
-></SPAN
-> referred to in this section are the internal records kept by the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->afsmonitor</B
-></SPAN
-> program to track the processes from which data is being gathered.</P
-></BLOCKQUOTE
-></DIV
-> <UL
-><LI
-><P
->fs_sc_numTtlRecords: Number of fileserver records, active or inactive.</P
-></LI
-><LI
-><P
->fs_sc_numUpRecords: Number of (active) fileserver records currently marked up.</P
-></LI
-><LI
-><P
->fs_sc_numDownRecords: Number of (active) fileserver records currently marked down.</P
-></LI
-><LI
-><P
->fs_sc_sumOfRecordAges: Sum of fileserver record lifetimes.</P
-></LI
-><LI
-><P
->fs_sc_ageOfYoungestRecord: Age of youngest fileserver record.</P
-></LI
-><LI
-><P
->fs_sc_ageOfOldestRecord: Age of oldest fileserver record.</P
-></LI
-><LI
-><P
->fs_sc_numDowntimeIncidents: Number of (completed) downtime incidents.</P
-></LI
-><LI
-><P
->fs_sc_numRecordsNeverDown: Number of fileserver records never marked down.</P
-></LI
-><LI
-><P
->fs_sc_maxDowntimesInARecord: Maximum downtimes seen by any fileserver record.</P
-></LI
-><LI
-><P
->fs_sc_sumOfDowntimes: Sum of all (completed) downtimes, in seconds.</P
-></LI
-><LI
-><P
->fs_sc_shortestDowntime: Shortest downtime, in seconds.</P
-></LI
-><LI
-><P
->fs_sc_longestDowntime: Longest downtime, in seconds.</P
-></LI
-><LI
-><P
->fs_sc_down_0_10_min: Down time incidents: 0-10 minutes.</P
-></LI
-><LI
-><P
->fs_sc_down_10_30_min: Down time incidents: 10-30 minutes.</P
-></LI
-><LI
-><P
->fs_sc_down_half_1_hr: Down time incidents: 30-60 minutes.</P
-></LI
-><LI
-><P
->fs_sc_down_1_2_hr: Down time incidents: 1-2 hours.</P
-></LI
-><LI
-><P
->fs_sc_down_2_4_hr: Down time incidents: 2-4 hours.</P
-></LI
-><LI
-><P
->fs_sc_down_4_8_hr: Down time incidents: 4-8 hours.</P
-></LI
-><LI
-><P
->fs_sc_down_more_8_hr: Down time incidents: more than 8 hours.</P
-></LI
-><LI
-><P
->fs_sc_downDst_0: Down time incidents: 0 times.</P
-></LI
-><LI
-><P
->fs_sc_downDst_1: Down time incidents: 1 time.</P
-></LI
-><LI
-><P
->fs_sc_downDst_2_5: Down time incidents: 2-5 times.</P
-></LI
-><LI
-><P
->fs_sc_downDst_6_10: Down time incidents: 6-10 times.</P
-></LI
-><LI
-><P
->fs_sc_downDst_10_50: Down time incidents: 10-50 times.</P
-></LI
-><LI
-><P
->fs_sc_downDst_more_50: Down time incidents: more than 50 times.</P
-></LI
-></UL
-></P
-><P
->File Server Up/Down Statistics in Other Cells Group (FS_upDown_OC_group) <UL
-><LI
-><P
->fs_oc_numTtlRecords: Number of fileserver records, active or inactive.</P
-></LI
-><LI
-><P
->fs_oc_numUpRecords: Number of (active) fileserver records currently marked up.</P
-></LI
-><LI
-><P
->fs_oc_numDownRecords: Number of (active) fileserver records currently marked down.</P
-></LI
-><LI
-><P
->fs_oc_sumOfRecordAges: Sum of server record lifetimes.</P
-></LI
-><LI
-><P
->fs_oc_ageOfYoungestRecord: Age of youngest fileserver record.</P
-></LI
-><LI
-><P
->fs_oc_ageOfOldestRecord: Age of oldest fileserver record.</P
-></LI
-><LI
-><P
->fs_oc_numDowntimeIncidents: Number of (completed) downtime incidents.</P
-></LI
-><LI
-><P
->fs_oc_numRecordsNeverDown: Number of fileserver records never marked down.</P
-></LI
-><LI
-><P
->fs_oc_maxDowntimesInARecord: Maximum downtimes seen by any fileserver.</P
-></LI
-><LI
-><P
->fs_oc_sumOfDowntimes: Sum of all (completed) downtimes, in seconds.</P
-></LI
-><LI
-><P
->fs_oc_shortestDowntime: Shortest downtime, in seconds.</P
-></LI
-><LI
-><P
->fs_oc_longestDowntime: Longest downtime, in seconds.</P
-></LI
-><LI
-><P
->fs_oc_down_0_10_min: Down time incidents: 0-10 minutes.</P
-></LI
-><LI
-><P
->fs_oc_down_10_30_min: Down time incidents: 10-30 minutes.</P
-></LI
-><LI
-><P
->fs_oc_down_half_1_hr: Down time incidents: 30-60 minutes.</P
-></LI
-><LI
-><P
->fs_oc_down_1_2_hr: Down time incidents: 1-2 hours.</P
-></LI
-><LI
-><P
->fs_oc_down_2_4_hr: Down time incidents: 2-4 hours.</P
-></LI
-><LI
-><P
->fs_oc_down_4_8_hr: Down time incidents: 4-8 hours.</P
-></LI
-><LI
-><P
->fs_oc_down_more_8_hr: Down time incidents: more than 8 hours.</P
-></LI
-><LI
-><P
->fs_oc_downDst_0: Down time incidents: 0 times.</P
-></LI
-><LI
-><P
->fs_oc_downDst_1: Down time incidents: 1 time.</P
-></LI
-><LI
-><P
->fs_oc_downDst_2_5: Down time incidents: 2-5 times.</P
-></LI
-><LI
-><P
->fs_oc_downDst_6_10: Down time incidents: 6-10 times.</P
-></LI
-><LI
-><P
->fs_oc_downDst_10_50: Down time incidents: 10-50 times.</P
-></LI
-><LI
-><P
->fs_oc_downDst_more_50: Down time incidents: more than 50 times.</P
-></LI
-></UL
-></P
-><P
->VL Server Up/Down Statistics in Same Cell Group (VL_upDown_SC_group) <UL
-><LI
-><P
->vl_sc_numTtlRecords: Number of vlserver records, active or inactive.</P
-></LI
-><LI
-><P
->vl_sc_numUpRecords: Number of (active) vlserver records currently marked up.</P
-></LI
-><LI
-><P
->vl_sc_numDownRecords: Number of (active) vlserver records currently marked down.</P
-></LI
-><LI
-><P
->vl_sc_sumOfRecordAges: Sum of vlserver record lifetimes.</P
-></LI
-><LI
-><P
->vl_sc_ageOfYoungestRecord: Age of youngest vlserver record.</P
-></LI
-><LI
-><P
->vl_sc_ageOfOldestRecord: Age of oldest vlserver record.</P
-></LI
-><LI
-><P
->vl_sc_numDowntimeIncidents: Number of (completed) downtime incidents.</P
-></LI
-><LI
-><P
->vl_sc_numRecordsNeverDown: Number of vlserver records never marked down.</P
-></LI
-><LI
-><P
->vl_sc_maxDowntimesInARecord: Maximum downtimes seen by any vlserver record.</P
-></LI
-><LI
-><P
->vl_sc_sumOfDowntimes: Sum of all (completed) downtimes, in seconds.</P
-></LI
-><LI
-><P
->vl_sc_shortestDowntime: Shortest downtime, in seconds.</P
-></LI
-><LI
-><P
->vl_sc_longestDowntime: Longest downtime, in seconds.</P
-></LI
-><LI
-><P
->vl_sc_down_0_10_min: Down time incidents: 0-10 minutes.</P
-></LI
-><LI
-><P
->vl_sc_down_10_30_min: Down time incidents: 10-30 minutes.</P
-></LI
-><LI
-><P
->vl_sc_down_half_1_hr: Down time incidents: 30-60 minutes.</P
-></LI
-><LI
-><P
->vl_sc_down_1_2_hr: Down time incidents: 1-2 hours.</P
-></LI
-><LI
-><P
->vl_sc_down_2_4_hr: Down time incidents: 2-4 hours.</P
-></LI
-><LI
-><P
->vl_sc_down_4_8_hr: Down time incidents: 4-8 hours.</P
-></LI
-><LI
-><P
->vl_sc_down_more_8_hr: Down time incidents: more than 8 hours.</P
-></LI
-><LI
-><P
->vl_sc_downDst_0: Down time incidents: 0 times.</P
-></LI
-><LI
-><P
->vl_sc_downDst_1: Down time incidents: 1 time.</P
-></LI
-><LI
-><P
->vl_sc_downDst_2_5: Down time incidents: 2-5 times.</P
-></LI
-><LI
-><P
->vl_sc_downDst_6_10: Down time incidents: 6-10 times.</P
-></LI
-><LI
-><P
->vl_sc_downDst_10_50: Down time incidents: 10-50 times.</P
-></LI
-><LI
-><P
->vl_sc_downDst_more_50: Down time incidents: more than 50 times.</P
-></LI
-></UL
-></P
-><P
->VL Server Up/Down Statistics in Other Cells Group (VL_upDown_DC_group) <UL
-><LI
-><P
->vl_oc_numTtlRecords: Number of vlserver records, active or inactive.</P
-></LI
-><LI
-><P
->vl_oc_numUpRecords: Number of (active) vlserver records currently marked up.</P
-></LI
-><LI
-><P
->vl_oc_numDownRecords: Number of (active) vlserver records currently marked down.</P
-></LI
-><LI
-><P
->vl_oc_sumOfRecordAges: Sum of vlserver record lifetimes.</P
-></LI
-><LI
-><P
->vl_oc_ageOfYoungestRecord: Age of youngest vlserver record.</P
-></LI
-><LI
-><P
->vl_oc_ageOfOldestRecord: Age of oldest vlserver record.</P
-></LI
-><LI
-><P
->vl_oc_numDowntimeIncidents: Number of (completed) downtime incidents.</P
-></LI
-><LI
-><P
->vl_oc_numRecordsNeverDown: Number of vlserver records never marked down.</P
-></LI
-><LI
-><P
->vl_oc_maxDowntimesInARecord: Maximum downtimes seen by any vlserver record.</P
-></LI
-><LI
-><P
->vl_oc_sumOfDowntimes: Sum of all (completed) downtimes, in seconds.</P
-></LI
-><LI
-><P
->vl_oc_shortestDowntime: Shortest downtime, in seconds.</P
-></LI
-><LI
-><P
->vl_oc_longestDowntime: Longest downtime, in seconds.</P
-></LI
-><LI
-><P
->vl_oc_down_0_10_min: Down time incidents: 0-10 minutes.</P
-></LI
-><LI
-><P
->vl_oc_down_10_30_min: Down time incidents: 10-30 minutes.</P
-></LI
-><LI
-><P
->vl_oc_down_half_1_hr: Down time incidents: 30-60 minutes.</P
-></LI
-><LI
-><P
->vl_oc_down_1_2_hr: Down time incidents: 1-2 hours.</P
-></LI
-><LI
-><P
->vl_oc_down_2_4_hr: Down time incidents: 2-4 hours.</P
-></LI
-><LI
-><P
->vl_oc_down_4_8_hr: Down time incidents: 4-8 hours.</P
-></LI
-><LI
-><P
->vl_oc_down_more_8_hr: Down time incidents: more than 8 hours.</P
-></LI
-><LI
-><P
->vl_oc_downDst_0: Down time incidents: 0 times.</P
-></LI
-><LI
-><P
->vl_oc_downDst_1: Down time incidents: 1 time.</P
-></LI
-><LI
-><P
->vl_oc_downDst_2_5: Down time incidents: 2-5 times.</P
-></LI
-><LI
-><P
->vl_oc_downDst_6_10: Down time incidents: 6-10 times.</P
-></LI
-><LI
-><P
->vl_oc_downDst_10_50: Down time incidents: 10-50 times.</P
-></LI
-><LI
-><P
->vl_oc_downDst_more_50: Down time incidents: more than 50 times.</P
-></LI
-></UL
-></P
-></DIV
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="Header_710"
->RPC Operation Measurements Section (RPCop_section)</A
-></H2
-><P
->File Server RPC Operation Timings Group (FS_RPCopTimes_group) <UL
-><LI
-><P
->FetchData_ops: Number of FetchData operations executed.</P
-></LI
-><LI
-><P
->FetchData_ops_ok: Number of successful FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_sum: Sum of timings for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_sqr: Sum of squares of sample timings for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_min: Minimum execution time observed for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_max: Maximum execution time observed for FetchData operations.</P
-></LI
-><LI
-><P
->FetchACL_ops: Number of FetchACL operations executed.</P
-></LI
-><LI
-><P
->FetchACL_ops_ok: Number of successful FetchACL operations.</P
-></LI
-><LI
-><P
->FetchACL_sum: Sum of timings for FetchACL operations.</P
-></LI
-><LI
-><P
->FetchACL_sqr: Sum of squares of sample timings for FetchACL operations.</P
-></LI
-><LI
-><P
->FetchACL_min: Minimum execution time observed for FetchACL operations.</P
-></LI
-><LI
-><P
->FetchACL_max: Maximum execution time observed for FetchACL operations.</P
-></LI
-><LI
-><P
->FetchStatus_ops: Number of FetchStatus operations executed.</P
-></LI
-><LI
-><P
->FetchStatus_ops_ok: Number of successful FetchStatus operations.</P
-></LI
-><LI
-><P
->FetchStatus_sum: Sum of timings for FetchStatus operations.</P
-></LI
-><LI
-><P
->FetchStatus_sqr: Sum of squares of sample timings for FetchStatus operations.</P
-></LI
-><LI
-><P
->FetchStatus_min: Minimum execution time observed for FetchStatus operations.</P
-></LI
-><LI
-><P
->FetchStatus_max: Maximum execution time observed for FetchStatus operations.</P
-></LI
-><LI
-><P
->StoreData_ops: Number of StoreData operations executed.</P
-></LI
-><LI
-><P
->StoreData_ops_ok: Number of successful StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_sum: Sum of timings for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_sqr: Sum of squares of sample timings for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_min: Minimum execution time observed for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_max: Maximum execution time observed for StoreData operations.</P
-></LI
-><LI
-><P
->StoreACL_ops: Number of StoreACL operations executed.</P
-></LI
-><LI
-><P
->StoreACL_ops_ok: Number of successful StoreACL operation.</P
-></LI
-><LI
-><P
->StoreACL_sum: Sum of timings for StoreACL operations.</P
-></LI
-><LI
-><P
->StoreACL_sqr: Sum of squares of sample timings for StoreACL operations.</P
-></LI
-><LI
-><P
->StoreACL_min: Minimum execution time observed for StoreACL operations.</P
-></LI
-><LI
-><P
->StoreACL_max: Maximum execution time observed for StoreACL operations.</P
-></LI
-><LI
-><P
->StoreStatus_ops: Number of StoreStatus operations executed.</P
-></LI
-><LI
-><P
->StoreStatus_ops_ok: Number of successful StoreStatus operations.</P
-></LI
-><LI
-><P
->StoreStatus_sum: Sum of timings for StoreStatus operations.</P
-></LI
-><LI
-><P
->StoreStatus_sqr: Sum of squares of sample timings for StoreStatus operations.</P
-></LI
-><LI
-><P
->StoreStatus_min: Minimum execution time observed for StoreStatus operations.</P
-></LI
-><LI
-><P
->StoreStatus_max: Maximum execution time observed for StoreStatus operations.</P
-></LI
-><LI
-><P
->RemoveFile_ops: Number of RemoveFile operations executed.</P
-></LI
-><LI
-><P
->RemoveFile_ops_ok: Number of successful RemoveFile operations.</P
-></LI
-><LI
-><P
->RemoveFile_sum: Sum of timings for RemoveFile operations.</P
-></LI
-><LI
-><P
->RemoveFile_sqr: Sum of squares of sample timings for RemoveFile operations.</P
-></LI
-><LI
-><P
->RemoveFile_min: Minimum execution time observed for RemoveFile operations.</P
-></LI
-><LI
-><P
->RemoveFile_max: Maximum execution time observed for RemoveFile operations.</P
-></LI
-><LI
-><P
->CreateFile_ops: Number of CreateFile operations executed.</P
-></LI
-><LI
-><P
->CreateFile_ops_ok: Number of successful CreateFile operations.</P
-></LI
-><LI
-><P
->CreateFile_sum: Sum of timings for CreateFile operations.</P
-></LI
-><LI
-><P
->CreateFile_sqr: Sum of squares of sample timings for CreateFile operations.</P
-></LI
-><LI
-><P
->CreateFile_min: Minimum execution time observed for CreateFile operations.</P
-></LI
-><LI
-><P
->CreateFile_max: Maximum execution time observed for CreateFile operations.</P
-></LI
-><LI
-><P
->Rename_ops: Number of Rename operations executed.</P
-></LI
-><LI
-><P
->Rename_ops_ok: Number of successful Rename operations.</P
-></LI
-><LI
-><P
->Rename_sum: Sum of timings for Rename operations.</P
-></LI
-><LI
-><P
->Rename_sqr: Sum of squares of sample timings for Rename operations.</P
-></LI
-><LI
-><P
->Rename_min: Minimum execution time observed for Rename operations.</P
-></LI
-><LI
-><P
->Rename_max: Maximum execution time observed for Rename operations.</P
-></LI
-><LI
-><P
->Symlink_ops: Number of Symlink operations executed.</P
-></LI
-><LI
-><P
->Symlink_ops_ok: Number of successful Symlink operations.</P
-></LI
-><LI
-><P
->Symlink_sum: Sum of timings for Symlink operations.</P
-></LI
-><LI
-><P
->Symlink_sqr: Sum of squares of sample timings for Symlink operations.</P
-></LI
-><LI
-><P
->Symlink_min: Minimum execution time observed for Symlink operations.</P
-></LI
-><LI
-><P
->Symlink_max: Maximum execution time observed for Symlink operations.</P
-></LI
-><LI
-><P
->Link_ops: Number of Link operations executed.</P
-></LI
-><LI
-><P
->Link_ops_ok: Number of successful Link operations.</P
-></LI
-><LI
-><P
->Link_sum: Sum of timings for Link operations.</P
-></LI
-><LI
-><P
->Link_sqr: Sum of squares of sample timings for Link operations.</P
-></LI
-><LI
-><P
->Link_min: Minimum execution time observed for Link operations.</P
-></LI
-><LI
-><P
->Link_max: Maximum execution time observed for Link operations.</P
-></LI
-><LI
-><P
->MakeDir_ops: Number of MakeDir operations executed.</P
-></LI
-><LI
-><P
->MakeDir_ops_ok: Number of successful MakeDir operations.</P
-></LI
-><LI
-><P
->MakeDir_sum: Sum of timings for MakeDir operations.</P
-></LI
-><LI
-><P
->MakeDir_sqr: Sum of squares of sample timings for MakeDir operations.</P
-></LI
-><LI
-><P
->MakeDir_min: Minimum execution time observed for MakeDir operations.</P
-></LI
-><LI
-><P
->MakeDir_max: Maximum execution time observed for MakeDir operations.</P
-></LI
-><LI
-><P
->RemoveDir_ops: Number of RemoveDir operations executed.</P
-></LI
-><LI
-><P
->RemoveDir_ops_ok: Number of successful RemoveDir operations.</P
-></LI
-><LI
-><P
->RemoveDir_sum: Sum of timings for RemoveDir operations.</P
-></LI
-><LI
-><P
->RemoveDir_sqr: Sum of squares of sample timings for RemoveDir operations.</P
-></LI
-><LI
-><P
->RemoveDir_min: Minimum execution time observed for RemoveDir operations.</P
-></LI
-><LI
-><P
->RemoveDir_max: Maximum execution time observed for RemoveDir operations.</P
-></LI
-><LI
-><P
->SetLock_ops: Number of SetLock operations executed.</P
-></LI
-><LI
-><P
->SetLock_ops_ok: Number of successful SetLock operations.</P
-></LI
-><LI
-><P
->SetLock_sum: Sum of timings for SetLock operations.</P
-></LI
-><LI
-><P
->SetLock_sqr: Sum of squares of sample timings for SetLock operations.</P
-></LI
-><LI
-><P
->SetLock_min: Minimum execution time observed for SetLock operations.</P
-></LI
-><LI
-><P
->SetLock_max: Maximum execution time observed for SetLock operations.</P
-></LI
-><LI
-><P
->ExtendLock_ops: Number of ExtendLock operations executed.</P
-></LI
-><LI
-><P
->ExtendLock_ops_ok: Number of successful ExtendLock operations.</P
-></LI
-><LI
-><P
->ExtendLock_sum: Sum of timings for ExtendLock operations.</P
-></LI
-><LI
-><P
->ExtendLock_sqr: Sum of squares of sample timings for ExtendLock operations.</P
-></LI
-><LI
-><P
->ExtendLock_min: Minimum execution time observed for ExtendLock operations.</P
-></LI
-><LI
-><P
->ExtendLock_max: Maximum execution time observed for ExtendLock operations.</P
-></LI
-><LI
-><P
->ReleaseLock_ops: Number of ReleaseLock operations executed.</P
-></LI
-><LI
-><P
->ReleaseLock_ops_ok: Number of successful ReleaseLock operations.</P
-></LI
-><LI
-><P
->ReleaseLock_sum: Sum of timings for ReleaseLock operations.</P
-></LI
-><LI
-><P
->ReleaseLock_sqr: Sum of squares of sample timings for StoreStatus operations.</P
-></LI
-><LI
-><P
->ReleaseLock_min: Minimum execution time observed for ReleaseLock operations.</P
-></LI
-><LI
-><P
->ReleaseLock_max: Maximum execution time observed for ReleaseLock operations.</P
-></LI
-><LI
-><P
->GetStatistics_ops: Number of GetStatistics operations executed.</P
-></LI
-><LI
-><P
->GetStatistics_ops_ok: Number of successful GetStatistics operations.</P
-></LI
-><LI
-><P
->GetStatistics_sum: Sum of timings for GetStatistics operations.</P
-></LI
-><LI
-><P
->GetStatistics_sqr: Sum of squares of sample timings for GetStatistics operations.</P
-></LI
-><LI
-><P
->GetStatistics_min: Minimum execution time observed for GetStatistics operations.</P
-></LI
-><LI
-><P
->GetStatistics_max: Maximum execution time observed for GetStatistics operations.</P
-></LI
-><LI
-><P
->GiveUpCallbacks_ops: Number of GiveUpCallbacks operations executed.</P
-></LI
-><LI
-><P
->GiveUpCallbacks_ops_ok: Number of successful GiveUpCallbacks operations.</P
-></LI
-><LI
-><P
->GiveUpCallbacks_sum: Sum of timings for GiveUpCallbacks operations.</P
-></LI
-><LI
-><P
->GiveUpCallbacks_sqr: Sum of squares of sample timings for GiveUpCallbacks operations.</P
-></LI
-><LI
-><P
->GiveUpCallbacks_min: Minimum execution time observed for GiveUpCallbacks operations.</P
-></LI
-><LI
-><P
->GiveUpCallbacks_max: Maximum execution time observed for GiveUpCallbacks operations.</P
-></LI
-><LI
-><P
->GetVolumeInfo_ops: Number of GetVolumeInfo operations executed.</P
-></LI
-><LI
-><P
->GetVolumeInfo_ops_ok: Number of successful GetVolumeInfo operations.</P
-></LI
-><LI
-><P
->GetVolumeInfo_sum: Sum of timings for GetVolumeInfo operations.</P
-></LI
-><LI
-><P
->GetVolumeInfo_sqr: Sum of squares of sample timings for GetVolumeInfo operations.</P
-></LI
-><LI
-><P
->GetVolumeInfo_min: Minimum execution time observed for GetVolumeInfo operations.</P
-></LI
-><LI
-><P
->GetVolumeInfo_max: Maximum execution time observed for GetVolumeInfo operations.</P
-></LI
-><LI
-><P
->GetVolumeStatus_ops: Number of GetVolumeStatus operations executed.</P
-></LI
-><LI
-><P
->GetVolumeStatus_ops_ok: Number of successful GetVolumeStatus operations.</P
-></LI
-><LI
-><P
->GetVolumeStatus_sum: Sum of timings for GetVolumeStatus operations.</P
-></LI
-><LI
-><P
->GetVolumeStatus_sqr: Sum of squares of sample timings for GetVolumeStatus operations.</P
-></LI
-><LI
-><P
->GetVolumeStatus_min: Minimum execution time observed for GetVolumeStatus operations.</P
-></LI
-><LI
-><P
->GetVolumeStatus_max: Maximum execution time observed for GetVolumeStatus operations.</P
-></LI
-><LI
-><P
->SetVolumeStatus_ops: Number of SetVolumeStatus operations executed.</P
-></LI
-><LI
-><P
->SetVolumeStatus_ops_ok: Number of successful SetVolumeStatus operations.</P
-></LI
-><LI
-><P
->SetVolumeStatus_sum: Sum of timings for SetVolumeStatus operations.</P
-></LI
-><LI
-><P
->SetVolumeStatus_sqr: Sum of squares of sample timings for SetVolumeStatus operations.</P
-></LI
-><LI
-><P
->SetVolumeStatus_min: Minimum execution time observed for SetVolumeStatus operations.</P
-></LI
-><LI
-><P
->SetVolumeStatus_max: Maximum execution time observed for SetVolumeStatus operations.</P
-></LI
-><LI
-><P
->GetRootVolume_ops: Number of GetRootVolume operations executed.</P
-></LI
-><LI
-><P
->GetRootVolume_ops_ok: Number of successful GetRootVolume operations.</P
-></LI
-><LI
-><P
->GetRootVolume_sum: Sum of timings for GetRootVolume operations.</P
-></LI
-><LI
-><P
->GetRootVolume_sqr: Sum of squares of sample timings for GetRootVolume operations.</P
-></LI
-><LI
-><P
->GetRootVolume_min: Minimum execution time observed for GetRootVolume operations.</P
-></LI
-><LI
-><P
->GetRootVolume_max: Maximum execution time observed for GetRootVolume operations.</P
-></LI
-><LI
-><P
->CheckToken_ops: Number of CheckToken operations executed.</P
-></LI
-><LI
-><P
->CheckToken_ops_ok: Number of successful CheckToken operations.</P
-></LI
-><LI
-><P
->CheckToken_sum: Sum of timings for CheckToken operations.</P
-></LI
-><LI
-><P
->CheckToken_sqr: Sum of squares of sample timings for CheckToken operations.</P
-></LI
-><LI
-><P
->CheckToken_min: Minimum execution time observed for CheckToken operations.</P
-></LI
-><LI
-><P
->CheckToken_max: Maximum execution time observed for CheckToken operations.</P
-></LI
-><LI
-><P
->GetTime_ops: Number of GetTime operations executed.</P
-></LI
-><LI
-><P
->GetTime_ops_ok: Number of successful GetTime operations.</P
-></LI
-><LI
-><P
->GetTime_sum: Sum of timings for GetTime operations.</P
-></LI
-><LI
-><P
->GetTime_sqr: Sum of squares of sample timings for GetTime operations.</P
-></LI
-><LI
-><P
->GetTime_min: Minimum execution time observed for GetTime operations.</P
-></LI
-><LI
-><P
->GetTime_max: Maximum execution time observed for GetTime operations.</P
-></LI
-><LI
-><P
->NGetVolumeInfo_ops: Number of NGetVolumeInfo operations executed.</P
-></LI
-><LI
-><P
->NGetVolumeInfo_ops_ok: Number of successful NGetVolumeInfo operations.</P
-></LI
-><LI
-><P
->NGetVolumeInfo_sum: Sum of timings for NGetVolumeInfo operations.</P
-></LI
-><LI
-><P
->NGetVolumeInfo_sqr: Sum of squares of sample timings for NGetVolumeInfo operations.</P
-></LI
-><LI
-><P
->NGetVolumeInfo_min: Minimum execution time observed for NGetVolumeInfo operations.</P
-></LI
-><LI
-><P
->NGetVolumeInfo_max: Maximum execution time observed for NGetVolumeInfo operations.</P
-></LI
-><LI
-><P
->BulkStatus_ops: Number of BulkStatus operations executed.</P
-></LI
-><LI
-><P
->BulkStatus_ops_ok: Number of successful BulkStatus operations.</P
-></LI
-><LI
-><P
->BulkStatus_sum: Sum of timings for BulkStatus operations.</P
-></LI
-><LI
-><P
->BulkStatus_sqr: Sum of squares of sample timings for BulkStatus operations.</P
-></LI
-><LI
-><P
->BulkStatus_min: Minimum execution time observed for BulkStatus operations.</P
-></LI
-><LI
-><P
->BulkStatus_max: Maximum execution time observed for BulkStatus operations.</P
-></LI
-><LI
-><P
->XStatsVersion_ops: Number of XStatsVersion operations executed.</P
-></LI
-><LI
-><P
->XStatsVersion_ops_ok: Number of successful XStatsVersion operations.</P
-></LI
-><LI
-><P
->XStatsVersion_sum: Sum of timings for XStatsVersion operations.</P
-></LI
-><LI
-><P
->XStatsVersion_sqr: Sum of squares of sample timings for XStatsVersion operations.</P
-></LI
-><LI
-><P
->XStatsVersion_min: Minimum execution time observed for XStatsVersion operations.</P
-></LI
-><LI
-><P
->XStatsVersion_max: Maximum execution time observed for XStatsVersion operations.</P
-></LI
-><LI
-><P
->GetXStats_ops: Number of GetXStats operations executed.</P
-></LI
-><LI
-><P
->GetXStats_ops_ok: Number of successful GetXStats operations.</P
-></LI
-><LI
-><P
->GetXStats_sum: Sum of timings for GetXStats operations.</P
-></LI
-><LI
-><P
->GetXstats_sqr: Sum of squares of sample timings for GetXStats operations.</P
-></LI
-><LI
-><P
->GetXStats_min: Minimum execution time observed for GetXStats operations.</P
-></LI
-><LI
-><P
->GetXStats_max: Maximum execution time observed for GetXStats operations.</P
-></LI
-></UL
-></P
-><P
->File Server RPC Operation Errors Group (FS_RPCopErrors_group) <UL
-><LI
-><P
->FetchData_srv_err: Number of server-down errors during FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_net_err: Number of network errors during FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_prot_err_err: Number of protection violations during FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_vol_err: Number of volume related errors during FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_busy_err: Number of volume busy conditions during FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_other_err: Number of miscellaneous other errors during FetchData operations.</P
-></LI
-><LI
-><P
->FetchACL_srv_err: Number of server-down errors during FetchACL operations.</P
-></LI
-><LI
-><P
->FetchACL_net_err: Number of network errors during FetchACL operations.</P
-></LI
-><LI
-><P
->FetchACL_prot_err: Number of protection violations during FetchACL operations.</P
-></LI
-><LI
-><P
->FetchACL_vol_err: Number of volume related errors during FetchACL operations.</P
-></LI
-><LI
-><P
->FetchACL_busy_err: Number of volume busy conditions encountered during FetchACL operations.</P
-></LI
-><LI
-><P
->FetchACL_other_err: Number of miscellaneous other errors during FetchACL operations.</P
-></LI
-><LI
-><P
->FetchStatus_srv_err: Number of server-down errors during FetchStatus operations.</P
-></LI
-><LI
-><P
->FetchStatus_net_err: Number of network errors during FetchStatus operations.</P
-></LI
-><LI
-><P
->FetchStatus_prot_err: Number of protection violations during FetchStatus operations.</P
-></LI
-><LI
-><P
->FetchStatus_vol_err: Number of volume related errors during FetchStatus operations.</P
-></LI
-><LI
-><P
->FetchStatus_busy_err: Number of volume busy conditions encountered during FetchStatus operations.</P
-></LI
-><LI
-><P
->FetchStatus_other_err: Number of miscellaneous other errors during FetchStatus operations.</P
-></LI
-><LI
-><P
->StoreData_srv_err: Number of server-down errors during StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_net_err: Number of network errors during StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_prot_err: Number of protection violations during StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_vol_err: Number of volume related errors during StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_busy_err: Number of volume busy conditions encountered during StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_other_err: Number of miscellaneous other errors during StoreData operations.</P
-></LI
-><LI
-><P
->StoreACL_srv_err: Number of server-down errors during StoreACL operations.</P
-></LI
-><LI
-><P
->StoreACL_net_err: Number of network errors during StoreACL operations.</P
-></LI
-><LI
-><P
->StoreACL_prot_err: Number of protection violations during StoreACL operations.</P
-></LI
-><LI
-><P
->StoreACL_vol_err: Number of volume related errors during StoreACL operations.</P
-></LI
-><LI
-><P
->StoreACL_busy_err: Number of volume busy conditions encountered during StoreACL operations.</P
-></LI
-><LI
-><P
->StoreACL_other_err: Number of miscellaneous other errors during StoreACL operations.</P
-></LI
-><LI
-><P
->StoreStatus_srv_err: Number of server-down errors during StoreStatus operations.</P
-></LI
-><LI
-><P
->StoreStatus_net_err: Number of network errors during StoreStatus operations.</P
-></LI
-><LI
-><P
->StoreStatus_prot_err: Number of protection violations during StoreStatus operations.</P
-></LI
-><LI
-><P
->StoreStatus_vol_err: Number of volume related errors during StoreStatus operations.</P
-></LI
-><LI
-><P
->StoreStatus_busy_err: Number of volume busy conditions encountered during StoreStatus operations.</P
-></LI
-><LI
-><P
->StoreStatus_other_err: Number of miscellaneous other errors during StoreStatus operations.</P
-></LI
-><LI
-><P
->RemoveFile_srv_err: Number of server-down errors during RemoveFile operations.</P
-></LI
-><LI
-><P
->RemoveFile_net_err: Number of network errors during RemoveFile operations.</P
-></LI
-><LI
-><P
->RemoveFile_prot_err: Number of protection violations during RemoveFile operations.</P
-></LI
-><LI
-><P
->RemoveFile_vol_err: Number of volume related errors during RemoveFile operations.</P
-></LI
-><LI
-><P
->RemoveFile_busy_err: Number of volume busy conditions encountered during RemoveFile operations.</P
-></LI
-><LI
-><P
->RemoveFile_other_err: Number of miscellaneous other errors during RemoveFile operations.</P
-></LI
-><LI
-><P
->CreateFile_srv_err: Number of server-down errors during CreateFile operations.</P
-></LI
-><LI
-><P
->CreateFile_net_err: Number of network errors during CreateFile operations.</P
-></LI
-><LI
-><P
->CreateFile_prot_err: Number of protection violations during CreateFile operations.</P
-></LI
-><LI
-><P
->CreateFile_vol_err: Number of volume related errors during CreateFile operations.</P
-></LI
-><LI
-><P
->CreateFile_busy_err: Number of volume busy conditions encountered during CreateFile operations.</P
-></LI
-><LI
-><P
->CreateFile_other_err: Number of miscellaneous other errors during CreateFile operations.</P
-></LI
-><LI
-><P
->Rename_srv_err: Number of server-down errors during Rename operations.</P
-></LI
-><LI
-><P
->Rename_net_err: Number of network errors during Rename operations.</P
-></LI
-><LI
-><P
->Rename_prot_err: Number of protection violations during Rename operations.</P
-></LI
-><LI
-><P
->Rename_vol_err: Number of volume related errors during Rename operations.</P
-></LI
-><LI
-><P
->Rename_busy_err: Number of volume busy conditions encountered during Rename operations.</P
-></LI
-><LI
-><P
->Rename_other_err: Number of miscellaneous other errors during Rename operations.</P
-></LI
-><LI
-><P
->Symlink_srv_err: Number of server-down errors during Symlink operations.</P
-></LI
-><LI
-><P
->Symlink_net_err: Number of network errors during Symlink operations.</P
-></LI
-><LI
-><P
->Symlink_prot_err: Number of protection violations during Symlink operations.</P
-></LI
-><LI
-><P
->Symlink_vol_err: Number of volume related errors during Symlink operations.</P
-></LI
-><LI
-><P
->Symlink_busy_err: Number of volume busy conditions encountered during Symlink operations.</P
-></LI
-><LI
-><P
->Symlink_other_err: Number of miscellaneous other errors during Symlink operations.</P
-></LI
-><LI
-><P
->Link_srv_err: Number of server-down errors during Link operations.</P
-></LI
-><LI
-><P
->Link_net_err: Number of network errors during Link operations.</P
-></LI
-><LI
-><P
->Link_prot_err: Number of protection violations during Link operations.</P
-></LI
-><LI
-><P
->Link_vol_err: Number of volume related errors during Link operations.</P
-></LI
-><LI
-><P
->Link_busy_err: Number of volume busy conditions encountered during Link operations.</P
-></LI
-><LI
-><P
->Link_other_err: Number of miscellaneous other errors during Link operations.</P
-></LI
-><LI
-><P
->MakeDir_srv_err: Number of server-down errors during MakeDir operations.</P
-></LI
-><LI
-><P
->MakeDir_net_err: Number of network errors during MakeDir operations.</P
-></LI
-><LI
-><P
->MakeDir_prot_err: Number of protection violations during MakeDir operations.</P
-></LI
-><LI
-><P
->MakeDir_vol_err: Number of volume related errors during MakeDir operations.</P
-></LI
-><LI
-><P
->MakeDir_busy_err: Number of volume busy conditions encountered during MakeDir operations.</P
-></LI
-><LI
-><P
->MakeDir_other_err: Number of miscellaneous other errors during MakeDir operations.</P
-></LI
-><LI
-><P
->RemoveDir_srv_err: Number of server-down errors during RemoveDir operations.</P
-></LI
-><LI
-><P
->RemoveDir_net_err: Number of network errors during RemoveDir operations.</P
-></LI
-><LI
-><P
->RemoveDir_prot_err: Number of protection violations during RemoveDir operations.</P
-></LI
-><LI
-><P
->RemoveDir_vol_err: Number of volume related errors during RemoveDir operations.</P
-></LI
-><LI
-><P
->RemoveDir_busy_err: Number of volume busy conditions encountered during RemoveDir operations.</P
-></LI
-><LI
-><P
->RemoveDir_other_err: Number of miscellaneous other errors during RemoveDir operations.</P
-></LI
-><LI
-><P
->SetLock_srv_err: Number of server-down errors during SetLock operations.</P
-></LI
-><LI
-><P
->SetLock_net_err: Number of network errors during SetLock operations.</P
-></LI
-><LI
-><P
->SetLock_prot_err: Number of protection violations during SetLock operations.</P
-></LI
-><LI
-><P
->SetLock_vol_err: Number of volume related errors during SetLock operations.</P
-></LI
-><LI
-><P
->SetLock_busy_err: Number of volume busy conditions encountered during SetLock operations.</P
-></LI
-><LI
-><P
->SetLock_other_err: Number of miscellaneous other errors during SetLock operations.</P
-></LI
-><LI
-><P
->ExtendLock_srv_err: Number of server-down errors during ExtendLock operations.</P
-></LI
-><LI
-><P
->ExtendLock_net_err: Number of network errors during ExtendLock operations.</P
-></LI
-><LI
-><P
->ExtendLock_prot_err: Number of protection violations during ExtendLock operations.</P
-></LI
-><LI
-><P
->ExtendLock_vol_err: Number of volume related errors during ExtendLock operations.</P
-></LI
-><LI
-><P
->ExtendLock_busy_err: Number of volume busy conditions encountered during ExtendLock operations.</P
-></LI
-><LI
-><P
->ExtendLock_other_err: Number of miscellaneous other errors during ExtendLock operations.</P
-></LI
-><LI
-><P
->ReleaseLock_srv_err: Number of server-down errors during ReleaseLock operations.</P
-></LI
-><LI
-><P
->ReleaseLock_net_err: Number of network errors during ReleaseLock operations.</P
-></LI
-><LI
-><P
->ReleaseLock_prot_err: Number of protection violations during ReleaseLock operations.</P
-></LI
-><LI
-><P
->ReleaseLock_vol_err: Number of volume related errors during ReleaseLock operations.</P
-></LI
-><LI
-><P
->ReleaseLock_busy_err: Number of volume busy conditions encountered during ReleaseLock operations.</P
-></LI
-><LI
-><P
->ReleaseLock_other_err: Number of miscellaneous other errors during ReleaseLock operations.</P
-></LI
-><LI
-><P
->GetStatistics_srv_err: Number of server-down errors during GetStatistics operations.</P
-></LI
-><LI
-><P
->GetStatistics_net_err: Number of network errors during GetStatistics operations.</P
-></LI
-><LI
-><P
->GetStatistics_prot_err: Number of protection violations during GetStatistics operations.</P
-></LI
-><LI
-><P
->GetStatistics_vol_err: Number of volume related errors during GetStatistics operations.</P
-></LI
-><LI
-><P
->GetStatistics_busy_err: Number of volume busy conditions encountered during GetStatistics operations.</P
-></LI
-><LI
-><P
->GetStatistics_other_err: Number of miscellaneous other errors during GetStatistics operations.</P
-></LI
-><LI
-><P
->GiveUpCallbacks_srv_err: Number of server-down errors during GiveUpCallbacks operations.</P
-></LI
-><LI
-><P
->GiveUpCallbacks_net_err: Number of network errors during GiveUpCallbacks operations.</P
-></LI
-><LI
-><P
->GiveUpCallbacks_prot_err: Number of protection violations during GiveUpCallbacks operations.</P
-></LI
-><LI
-><P
->GiveUpCallbacks_vol_err: Number of volume related errors during GiveUpCallbacks operations.</P
-></LI
-><LI
-><P
->GiveUpCallbacks_busy_err: Number of volume busy conditions encountered during GiveUpCallbacks operations.</P
-></LI
-><LI
-><P
->GiveUpCallbacks_other_err: Number of miscellaneous other errors during GiveUpCallbacks operations.</P
-></LI
-><LI
-><P
->GetVolumeInfo_srv_err: Number of server-down errors during GetVolumeInfo operations.</P
-></LI
-><LI
-><P
->GetVolumeInfo_net_err: Number of network errors during GetVolumeInfo operations.</P
-></LI
-><LI
-><P
->GetVolumeInfo_prot_err: Number of protection violations during GetVolumeInfo operations.</P
-></LI
-><LI
-><P
->GetVolumeInfo_vol_err: Number of volume related errors during GetVolumeInfo operations.</P
-></LI
-><LI
-><P
->GetVolumeInfo_busy_err: Number of volume busy conditions encountered during GetVolumeInfo operations.</P
-></LI
-><LI
-><P
->GetVolumeInfo_other_err: Number of miscellaneous other errors during GetVolumeInfo operations.</P
-></LI
-><LI
-><P
->GetVolumeStatus_srv_err: Number of server-down errors during GetVolumeStatus operations.</P
-></LI
-><LI
-><P
->GetVolumeStatus_net_err: Number of network errors during GetVolumeStatus operations.</P
-></LI
-><LI
-><P
->GetVolumeStatus_prot_err: Number of protection violations during GetVolumeStatus operations.</P
-></LI
-><LI
-><P
->GetVolumeStatus_vol_err: Number of volume related errors during GetVolumeStatus operations.</P
-></LI
-><LI
-><P
->GetVolumeStatus_busy_err: Number of volume busy conditions encountered during GetVolumeStatus operations.</P
-></LI
-><LI
-><P
->GetVolumeStatus_other_err: Number of miscellaneous other errors during GetVolumeStatus operations.</P
-></LI
-><LI
-><P
->SetVolumeStatus_srv_err : Number of server-down errors during SetVolumeStatus operations.</P
-></LI
-><LI
-><P
->SetVolumeStatus_net_err: Number of network errors during SetVolumeStatus operations.</P
-></LI
-><LI
-><P
->SetVolumeStatus_prot_err: Number of protection violations during SetVolumeStatus operations.</P
-></LI
-><LI
-><P
->SetVolumeStatus_vol_err: Number of volume related errors during SetVolumeStatus operations.</P
-></LI
-><LI
-><P
->SetVolumeStatus_busy_err: Number of volume busy conditions encountered during SetVolumeStatus operations.</P
-></LI
-><LI
-><P
->SetVolumeStatus_other_err: Number of miscellaneous other errors during SetVolumeStatus operations.</P
-></LI
-><LI
-><P
->GetRootVolume_srv_err: Number of server-down errors during GetRootVolume operations.</P
-></LI
-><LI
-><P
->GetRootVolume_net_err: Number of network errors during GetRootVolume operations.</P
-></LI
-><LI
-><P
->GetRootVolume_prot_err: Number of protection violations during GetRootVolume operations.</P
-></LI
-><LI
-><P
->GetRootVolume_vol_err: Number of volume related errors during GetRootVolume operations.</P
-></LI
-><LI
-><P
->GetRootVolume_busy_err: Number of volume busy conditions encountered during GetRootVolume operations.</P
-></LI
-><LI
-><P
->GetRootVolume_other_err: Number of miscellaneous other errors during GetRootVolume operations.</P
-></LI
-><LI
-><P
->CheckToken_srv_err: Number of server-down errors during CheckToken operations.</P
-></LI
-><LI
-><P
->CheckToken_net_err: Number of network errors during CheckToken operations.</P
-></LI
-><LI
-><P
->CheckToken_prot_err: Number of protection violations during CheckToken operations.</P
-></LI
-><LI
-><P
->CheckToken_vol_err: Number of volume related errors during CheckToken operations.</P
-></LI
-><LI
-><P
->CheckToken_busy_err: Number of volume busy conditions encountered during CheckToken operations.</P
-></LI
-><LI
-><P
->CheckToken_other_err: Number of miscellaneous other errors during CheckToken operations.</P
-></LI
-><LI
-><P
->GetTime_srv_err: Number of server-down errors during GetTime operations.</P
-></LI
-><LI
-><P
->GetTime_net_err: Number of network errors during GetTime operations.</P
-></LI
-><LI
-><P
->GetTime_prot_err: Number of protection violations during GetTime operations.</P
-></LI
-><LI
-><P
->GetTime_vol_err: Number of volume related errors during GetTime operations.</P
-></LI
-><LI
-><P
->GetTime_busy_err: Number of volume busy conditions encountered during GetTime operations.</P
-></LI
-><LI
-><P
->GetTime_other_err: Number of miscellaneous other errors during GetTime operations.</P
-></LI
-><LI
-><P
->NGetVolumeInfo_srv_err: Number of server-down errors during NGetVolumeInfo operations.</P
-></LI
-><LI
-><P
->NGetVolumeInfo_net_err: Number of network errors during NGetVolumeInfo operations.</P
-></LI
-><LI
-><P
->NGetVolumeInfo_prot_err: Number of protection violations during NGetVolumeInfo operations.</P
-></LI
-><LI
-><P
->NGetVolumeInfo_vol_err: Number of volume related errors during NGetVolumeInfo operations.</P
-></LI
-><LI
-><P
->NGetVolumeInfo_busy_err: Number of volume busy conditions encountered during NGetVolumeInfo operations.</P
-></LI
-><LI
-><P
->NGetVolumeInfo_other_err: Number of miscellaneous other errors during NGetVolumeInfo operations.</P
-></LI
-><LI
-><P
->BulkStatus_srv_err: Number of server-down errors during BulkStatus operations.</P
-></LI
-><LI
-><P
->BulkStatus_net_err: Number of network errors during BulkStatus operations.</P
-></LI
-><LI
-><P
->BulkStatus_prot_err: Number of protection violations during BulkStatus operations.</P
-></LI
-><LI
-><P
->BulkStatus_vol_err: Number of volume related errors during BulkStatus operations.</P
-></LI
-><LI
-><P
->BulkStatus_busy_err: Number of volume busy conditions encountered during BulkStatus operations.</P
-></LI
-><LI
-><P
->BulkStatus_other_err: Number of miscellaneous other errors during BulkStatus operations.</P
-></LI
-><LI
-><P
->XStatsVersion_srv_err: Number of server-down errors during XStatsVersion operations.</P
-></LI
-><LI
-><P
->XStatsVersion_net_err: Number of network errors during XStatsVersion operations.</P
-></LI
-><LI
-><P
->XStatsVersion_prot_err: Number of protection violations during XStatsVersion operations.</P
-></LI
-><LI
-><P
->XStatsVersion_vol_err: Number of volume related errors during XStatsVersion operations.</P
-></LI
-><LI
-><P
->XStatsVersion_busy_err: Number of volume busy conditions encountered during XStatsVersion operations.</P
-></LI
-><LI
-><P
->XStatsVersion_other_err: Number of miscellaneous other errors during XStatsVersion operations.</P
-></LI
-><LI
-><P
->GetXStats_srv_err: Number of server-down errors during GetXStats operations.</P
-></LI
-><LI
-><P
->GetXStats_net_err: Number of network errors during GetXStats operations.</P
-></LI
-><LI
-><P
->GetXStats_prot_err: Number of protection violations during GetXStats operations.</P
-></LI
-><LI
-><P
->GetXStats_vol_err: Number of volume related errors during GetXStats operations.</P
-></LI
-><LI
-><P
->GetXStats_busy_err: Number of volume busy conditions encountered during GetXStats operations.</P
-></LI
-><LI
-><P
->GetXStats_other_err: Number of miscellaneous other errors during GetXStats operations.</P
-></LI
-></UL
-></P
-><P
->File Server RPC Transfer Timings Group (FS_RPCopBytes_group) <UL
-><LI
-><P
->FetchData_xfers: Number of FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_ok: Number of successful FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_sum: Sum of timing values for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_sqr: Sum of squares of sample timings for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_min: Minimum transfer time observed for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_max: Maximum transfer time observed for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_bytes_sum: Sum of bytes transferred for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_bytes_min: Minimum byte transfer observed for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_bytes_max: Maximum byte transfer observed for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_bucket0: Tally in bucket0 for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_bucket1: Tally in bucket1 for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_bucket2: Tally in bucket2 for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_bucket3: Tally in bucket3 for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_bucket4: Tally in bucket4 for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_bucket5: Tally in bucket5 for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_bucket6: Tally in bucket6 for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_bucket7: Tally in bucket7 for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_bucket8: Tally in bucket8 for FetchData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers: Number of StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_ok: Number of successful StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_sum: Sum of timing values for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_sqr: Sum of squares of sample timings for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_min: Minimum transfer time observed for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_max: Maximum transfer time observed for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_bytes_sum: Sum of bytes transferred for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_bytes_min: Minimum byte transfer observed for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_bytes_max: Maximum byte transfer observed for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_bucket0: Tally in bucket0 for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_bucket1: Tally in bucket1 for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_bucket2: Tally in bucket2 for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_bucket3: Tally in bucket3 for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_bucket4: Tally in bucket4 for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_bucket5: Tally in bucket5 for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_bucket6: Tally in bucket6 for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_bucket7: Tally in bucket7 for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_bucket8: Tally in bucket8 for StoreData operations.</P
-></LI
-></UL
-></P
-><P
->Cache Manager RPC Operation Timings Group (CM_RPCopTimes_group) <UL
-><LI
-><P
->CallBack_ops: Number of CallBack operations executed.</P
-></LI
-><LI
-><P
->CallBack_ops_ok: Number of successful CallBack operations.</P
-></LI
-><LI
-><P
->CallBack_ops_sum: Sum of timings for CallBack operations.</P
-></LI
-><LI
-><P
->CallBack_ops_min: Minimum execution time observed for CallBack operations.</P
-></LI
-><LI
-><P
->CallBack_ops_max: Maximum execution time observed for CallBack operations.</P
-></LI
-><LI
-><P
->CallBack_ops_sqr: Sum of the square of CallBack operations executed.</P
-></LI
-><LI
-><P
->InitCallBackState_ops: Number of InitCallBackState operations executed.</P
-></LI
-><LI
-><P
->InitCallBackState_ops_ok: Number of successful InitCallBackState operations.</P
-></LI
-><LI
-><P
->InitCallBackState_ops_sum: Sum of timings for InitCallBackState operations.</P
-></LI
-><LI
-><P
->InitCallBackState_ops_min: Minimum execution time observed for InitCallBackState operations.</P
-></LI
-><LI
-><P
->InitCallBackState_ops_max: Maximum execution time observed for InitCallBackState operations.</P
-></LI
-><LI
-><P
->InitCallBackState_ops_sqr: Sum of squares of timings for InitCallBackState operations.</P
-></LI
-><LI
-><P
->Probe_ops: Number of Probe operations executed.</P
-></LI
-><LI
-><P
->Probe_ops_ok: Number of successful Probe operations.</P
-></LI
-><LI
-><P
->Probe_ops_sum: Sum of timings for Probe operations.</P
-></LI
-><LI
-><P
->Probe_ops_min: Minimum execution time observed for Probe operations.</P
-></LI
-><LI
-><P
->Probe_ops_max: Maximum execution time observed for Probe operations.</P
-></LI
-><LI
-><P
->Probe_ops_sqr: Sum of squares of timings for Probe operations.</P
-></LI
-><LI
-><P
->GetLock_ops: Number of GetLock operations executed.</P
-></LI
-><LI
-><P
->GetLock_ops_ok: Number of successful GetLock operations.</P
-></LI
-><LI
-><P
->GetLock_ops_sum: Sum of timings for GetLock operations.</P
-></LI
-><LI
-><P
->GetLock_ops_min: Minimum execution time observed for GetLock operations.</P
-></LI
-><LI
-><P
->GetLock_ops_max: Maximum execution time observed for GetLock operations.</P
-></LI
-><LI
-><P
->GetLock_ops_sqr: Sum of squares of timings for GetLock operations.</P
-></LI
-><LI
-><P
->GetCE_ops: Number of GetCE operations executed.</P
-></LI
-><LI
-><P
->GetCE_ops_ok: Number of successful GetCE operations.</P
-></LI
-><LI
-><P
->GetCE_ops_sum: Sum of timings for GetCE operations.</P
-></LI
-><LI
-><P
->GetCE_ops_min: Minimum execution time observed for GetCE operations.</P
-></LI
-><LI
-><P
->GetCE_ops_max: Maximum execution time observed for GetCE operations.</P
-></LI
-><LI
-><P
->GetCE_ops_sqr: Sum of squares of timings for GetCE operations.</P
-></LI
-><LI
-><P
->XStatsVersion_CM_ops: Number of XStatsVersion operations executed.</P
-></LI
-><LI
-><P
->XStatsVersion_CM_ops_ok: Number of successful XStatsVersion operations.</P
-></LI
-><LI
-><P
->XStatsVersion_CM_ops_sum: Sum of timings for XStatsVersion operations.</P
-></LI
-><LI
-><P
->XStatsVersion_CM_ops_min: Minimum execution time observed for XStatsVersion operations.</P
-></LI
-><LI
-><P
->XStatsVersion_CM_ops_max: Maximum execution time observed for XStatsVersion operations.</P
-></LI
-><LI
-><P
->XStatsVersion_CM_ops_sqr: Sum of squares of timings for XStatsVersion operations.</P
-></LI
-><LI
-><P
->GetXStats_CM_ops: Number of GetXStats operations executed.</P
-></LI
-><LI
-><P
->GetXStats_CM_ops_ok: Number of successful GetXStats operations.</P
-></LI
-><LI
-><P
->GetXStats_CM_ops_sum: Sum of timings for GetXStats operations.</P
-></LI
-><LI
-><P
->GetXStats_CM_ops_min: Minimum execution time observed for GetXStats operations.</P
-></LI
-><LI
-><P
->GetXStats_CM_ops_max: Maximum execution time observed for GetXStats operations.</P
-></LI
-><LI
-><P
->GetXStats_CM_ops_sqr: Sum of squares of timings for GetXStats operations.</P
-></LI
-></UL
-></P
-></DIV
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="Header_711"
->Authentication and Replicated File Access Section (Auth_Access_section)</A
-></H2
-><P
->Authentication Information for Cache Manager Group (Auth_Stats_group) <UL
-><LI
-><P
->curr_PAGs: Current number of PAGs.</P
-></LI
-><LI
-><P
->curr_Records: Current number of records in table.</P
-></LI
-><LI
-><P
->curr_AuthRecords: Current number of of authenticated records (with valid ticket).</P
-></LI
-><LI
-><P
->curr_UnauthRecords: Current number of of unauthenticated records (without any ticket at all).</P
-></LI
-><LI
-><P
->curr_MaxRecordsInPAG: Maximum records for a single PAG.</P
-></LI
-><LI
-><P
->curr_LongestChain: Length of longest current hash chain.</P
-></LI
-><LI
-><P
->PAGCreations: Number of PAG creations.</P
-></LI
-><LI
-><P
->TicketUpdates: Number of ticket additions/refreshes.</P
-></LI
-><LI
-><P
->HWM_PAGS: High water mark - number of PAGs.</P
-></LI
-><LI
-><P
->HWM_Records: High water mark - number of records.</P
-></LI
-><LI
-><P
->HWM_MaxRecordsInPAG: High water mark - maximum records for a single PAG.</P
-></LI
-><LI
-><P
->HWM_LongestChain: High water mark - longest hash chain.</P
-></LI
-></UL
-></P
-><P
->Unreplicated File Access Group (Access_Stats_group) <UL
-><LI
-><P
->unreplicatedRefs: Number of references to unreplicated data.</P
-></LI
-><LI
-><P
->replicatedRefs: Number of references to replicated data.</P
-></LI
-><LI
-><P
->numReplicasAccessed: Number of replicas accessed.</P
-></LI
-><LI
-><P
->maxReplicasPerRef: Maximum number of replicas accessed per reference.</P
-></LI
-><LI
-><P
->refFirstReplicaOK: Number of references satisfied by 1st replica.</P
-></LI
-></UL
-></P
-></DIV
-></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="HDRWQ619"
->The File Server Statistics</A
-></H1
-><P
->File Server statistics are classified into the following sections and groups: <UL
-><LI
-><P
->PerfStats_section: Performance Statistics Section. <UL
-><LI
-><P
->VnodeCache_group: Vnode Cache Group.</P
-></LI
-><LI
-><P
->Directory_group: Directory Package Group.</P
-></LI
-><LI
-><P
->Rx_group: Rx Group.</P
-></LI
-><LI
-><P
->HostModule_group: Host Module Fields Group.</P
-></LI
-><LI
-><P
->misc_group: Miscellaneous Variables Group.</P
-></LI
-></UL
-></P
-></LI
-><LI
-><P
->RPCop_section: RPC Operations Section. <UL
-><LI
-><P
->RPCopTimes_group: Individual RPC Operation Timings.</P
-></LI
-><LI
-><P
->RPCopBytes_group: Byte Information for Certain RPC Operations.</P
-></LI
-></UL
-></P
-></LI
-></UL
-></P
-><P
->All File Server variables categorized under the above sections and groups names are listed below.</P
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="Header_713"
->Performance Statistics Section (PerfStats_section)</A
-></H2
-><P
->Vnode Cache Group (VnodeCache_group) <UL
-><LI
-><P
->vcache_L_Entries: Number of entries in LARGE vnode cache.</P
-></LI
-><LI
-><P
->vcache_L_Allocs: Number of allocs (large).</P
-></LI
-><LI
-><P
->vcache_L_Gets: Number of gets (large).</P
-></LI
-><LI
-><P
->vcache_L_Reads: Number of reads (large).</P
-></LI
-><LI
-><P
->vcache_L_Writes: Number of writes (large).</P
-></LI
-><LI
-><P
->vcache_S_Entries: Number of entries in SMALL vnode cache.</P
-></LI
-><LI
-><P
->vcache_S_Allocs: Number of allocs (small).</P
-></LI
-><LI
-><P
->vcache_S_Gets: Number of gets (small).</P
-></LI
-><LI
-><P
->vcache_S_Reads: Number of reads (small).</P
-></LI
-><LI
-><P
->vcache_S_Writes: Number of writes (small).</P
-></LI
-><LI
-><P
->vcache_H_Entries: Number of entries in HEADER vnode cache.</P
-></LI
-><LI
-><P
->vcache_H_Gets: Number of gets (header)</P
-></LI
-><LI
-><P
->vcache_H_Replacements: Number of replacements (header)</P
-></LI
-></UL
-></P
-><P
->Directory Package Group (Directory_group) <UL
-><LI
-><P
->dir_Buffers: Number of buffers in use.</P
-></LI
-><LI
-><P
->dir_Calls: Number of read calls made.</P
-></LI
-><LI
-><P
->dir_IOs: I/O operations performed.</P
-></LI
-></UL
-></P
-><P
->Rx Group (Rx_group) <UL
-><LI
-><P
->rx_packetRequests: Packet allocation requests.</P
-></LI
-><LI
-><P
->rx_noPackets_RcvClass: Failed packet requests (receive class).</P
-></LI
-><LI
-><P
->rx_noPackets_SendClass: Failed packet requests (send class).</P
-></LI
-><LI
-><P
->rx_noPackets_SpecialClass: Failed packet requests (special class).</P
-></LI
-><LI
-><P
->rx_socketGreedy: Did SO_GREEDY succeed?</P
-></LI
-><LI
-><P
->rx_bogusPacketOnRead: Short packets received.</P
-></LI
-><LI
-><P
->rx_bogusHost: Host address from bogus packets.</P
-></LI
-><LI
-><P
->rx_noPacketOnRead: Read packets with no packet there.</P
-></LI
-><LI
-><P
->rx_noPacketBuffersOnRead: Packets dropped due to buffer shortage.</P
-></LI
-><LI
-><P
->rx_selects: Selects waiting on packet or timeout.</P
-></LI
-><LI
-><P
->rx_sendSelects: Selects forced upon sends.</P
-></LI
-><LI
-><P
->rx_packetsRead_RcvClass: Packets read (receive class).</P
-></LI
-><LI
-><P
->rx_packetsRead_SendClass: Packets read (send class).</P
-></LI
-><LI
-><P
->rx_packetsRead_SpecialClass: Packets read (special class).</P
-></LI
-><LI
-><P
->rx_dataPacketsRead: Unique data packets read off wire.</P
-></LI
-><LI
-><P
->rx_ackPacketsRead: ACK packets read.</P
-></LI
-><LI
-><P
->rx_dupPacketsRead: Duplicate data packets read.</P
-></LI
-><LI
-><P
->rx_spuriousPacketsRead: Inappropriate packets read.</P
-></LI
-><LI
-><P
->rx_packetsSent_RcvClass: Packets sent (receive class).</P
-></LI
-><LI
-><P
->rx_packetsSent_SendClass: Packets sent (send class).</P
-></LI
-><LI
-><P
->rx_packetsSent_SpecialClass: Packets sent (special class).</P
-></LI
-><LI
-><P
->rx_ackPacketsSent: ACK packets sent.</P
-></LI
-><LI
-><P
->rx_pingPacketsSent: Ping packets sent.</P
-></LI
-><LI
-><P
->rx_abortPacketsSent: Abort packets sent.</P
-></LI
-><LI
-><P
->rx_busyPacketsSent: Busy packets sent.</P
-></LI
-><LI
-><P
->rx_dataPacketsSent: Unique data packets sent.</P
-></LI
-><LI
-><P
->rx_dataPacketsReSent: Retransmissions sent.</P
-></LI
-><LI
-><P
->rx_dataPacketsPushed: Retransmissions pushed by NACK.</P
-></LI
-><LI
-><P
->rx_ignoreAckedPacket: Packets with ACKed flag on rxi_Start.</P
-></LI
-><LI
-><P
->rx_totalRtt_Sec and rx_totalRtt_Usec: Total round trip time (in seconds and milliseconds).</P
-></LI
-><LI
-><P
->rx_minRtt_Sec and rx_minRtt_Usec: Minimum round trip time (in seconds and milliseconds).</P
-></LI
-><LI
-><P
->rx_maxRtt_Sec and rx_maxRtt_Usec: Maximum round trip time (in seconds and milliseconds).</P
-></LI
-><LI
-><P
->rx_nRttSamples: Round trip samples.</P
-></LI
-><LI
-><P
->rx_nServerConns: Total server connections.</P
-></LI
-><LI
-><P
->rx_nClientConns: Total client connections.</P
-></LI
-><LI
-><P
->rx_nPeerStructs: Total peer structures.</P
-></LI
-><LI
-><P
->rx_nCallStructs: Total call structures.</P
-></LI
-><LI
-><P
->rx_nFreeCallStructs: Total free call structures.</P
-></LI
-></UL
-></P
-><P
->Host Module Fields Group (HostModule_group) <UL
-><LI
-><P
->host_NumHostEntries: Number of host entries.</P
-></LI
-><LI
-><P
->host_HostBlocks: Blocks in use for hosts.</P
-></LI
-><LI
-><P
->host_NonDeletedHosts: Non-deleted hosts.</P
-></LI
-><LI
-><P
->host_HostsInSameNetOrSubnet: Hosts in same subnet as server.</P
-></LI
-><LI
-><P
->host_HostsInDiffSubnet: Hosts in different subnet than server.</P
-></LI
-><LI
-><P
->host_HostsInDiffNetwork: Hosts in different network than server.</P
-></LI
-><LI
-><P
->host_NumClients: Number of client entries.</P
-></LI
-><LI
-><P
->host_ClientBlocks: Blocks in use for clients.</P
-></LI
-></UL
-></P
-><P
->Miscellaneous Variables Group (misc_group) <UL
-><LI
-><P
->numPerfCalls: Number of performance calls received.</P
-></LI
-></UL
-></P
-></DIV
-><DIV
-CLASS="sect2"
-><H2
-CLASS="sect2"
-><A
-NAME="Header_714"
->RPC Operations Section (RPCop_section)</A
-></H2
-><P
->Individual RPC Operation Timings Group (RPCopTimes_group) <UL
-><LI
-><P
->epoch: Time when data collection began.</P
-></LI
-><LI
-><P
->FetchData_ops: Number of FetchData operations executed.</P
-></LI
-><LI
-><P
->FetchData_ops_ok: Number of successful FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_sum: Sum of timings for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_sqr: Sum of squares of sample timings for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_min: Minimum execution time observed for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_max: Maximum execution time observed for FetchData operations.</P
-></LI
-><LI
-><P
->FetchACL_ops: Number of FetchACL operations executed.</P
-></LI
-><LI
-><P
->FetchACL_ops_ok: Number of successful FetchACL operations.</P
-></LI
-><LI
-><P
->FetchACL_sum: Sum of timings for FetchACL operations.</P
-></LI
-><LI
-><P
->FetchACL_sqr: Sum of squares of sample timings for FetchACL operations.</P
-></LI
-><LI
-><P
->FetchACL_min: Minimum execution time observed for FetchACL operations.</P
-></LI
-><LI
-><P
->FetchACL_max: Maximum execution time observed for FetchACL operations.</P
-></LI
-><LI
-><P
->FetchStatus_ops: Number of FetchStatus operations executed.</P
-></LI
-><LI
-><P
->FetchStatus_ops_ok: Number of successful FetchStatus operations.</P
-></LI
-><LI
-><P
->FetchStatus_sum: Sum of timings for FetchStatus operations.</P
-></LI
-><LI
-><P
->FetchStatus_sqr: Sum of squares of sample timings for FetchStatus operations.</P
-></LI
-><LI
-><P
->FetchStatus_min: Minimum execution time observed for FetchStatus operations.</P
-></LI
-><LI
-><P
->FetchStatus_max: Maximum execution time observed for FetchStatus operations.</P
-></LI
-><LI
-><P
->StoreData_ops: Number of StoreData operations executed.</P
-></LI
-><LI
-><P
->StoreData_ops_ok: Number of successful StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_sum: Sum of timings for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_sqr: Sum of squares of sample timings for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_min: Minimum execution time observed for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_max: Maximum execution time observed for StoreData operations.</P
-></LI
-><LI
-><P
->StoreACL_ops: Number of StoreACL operations executed.</P
-></LI
-><LI
-><P
->StoreACL_ops_ok: Number of successful StoreACL operations.</P
-></LI
-><LI
-><P
->StoreACL_sum: Sum of timings for StoreACL operations.</P
-></LI
-><LI
-><P
->StoreACL_sqr: Sum of squares of sample timings for StoreACL operations.</P
-></LI
-><LI
-><P
->StoreACL_min: Minimum execution time observed for StoreACL operations.</P
-></LI
-><LI
-><P
->StoreACL_max: Maximum execution time observed for StoreACL operations.</P
-></LI
-><LI
-><P
->StoreStatus_ops: Number of StoreStatus operations executed.</P
-></LI
-><LI
-><P
->StoreStatus_ops_ok: Number of successful StoreStatus operations.</P
-></LI
-><LI
-><P
->StoreStatus_sum: Sum of timings for StoreStatus operations.</P
-></LI
-><LI
-><P
->StoreStatus_sqr: Sum of squares of sample timings for StoreStatus operations.</P
-></LI
-><LI
-><P
->StoreStatus_min: Minimum execution time observed for StoreStatus operations.</P
-></LI
-><LI
-><P
->StoreStatus_max: Maximum execution time observed for StoreStatus operations.</P
-></LI
-><LI
-><P
->RemoveFile_ops: Number of RemoveFile operations executed.</P
-></LI
-><LI
-><P
->RemoveFile_ops_ok: Number of successful RemoveFile operations.</P
-></LI
-><LI
-><P
->RemoveFile_sum: Sum of timings for RemoveFile operations.</P
-></LI
-><LI
-><P
->RemoveFile_sqr: Sum of squares of sample timings for RemoveFile operations.</P
-></LI
-><LI
-><P
->RemoveFile_min: Minimum execution time observed for RemoveFile operations.</P
-></LI
-><LI
-><P
->RemoveFile_max: Maximum execution time observed for RemoveFile operations.</P
-></LI
-><LI
-><P
->CreateFile_ops: Number of CreateFile operations executed.</P
-></LI
-><LI
-><P
->CreateFile_ops_ok: Number of successful CreateFile operations.</P
-></LI
-><LI
-><P
->CreateFile_sum: Sum of timings for CreateFile operations.</P
-></LI
-><LI
-><P
->CreateFile_sqr: Sum of squares of sample timings for CreateFile operations.</P
-></LI
-><LI
-><P
->CreateFile_min: Minimum execution time observed for CreateFile operations.</P
-></LI
-><LI
-><P
->CreateFile_max: Maximum execution time observed for CreateFile operations.</P
-></LI
-><LI
-><P
->Rename_ops: Number of Rename operations executed.</P
-></LI
-><LI
-><P
->Rename_ops_ok: Number of successful Rename operations.</P
-></LI
-><LI
-><P
->Rename_sum: Sum of timings for Rename operations.</P
-></LI
-><LI
-><P
->Rename_sqr: Sum of squares of sample timings for Rename operations.</P
-></LI
-><LI
-><P
->Rename_min: Minimum execution time observed for Rename operations.</P
-></LI
-><LI
-><P
->Rename_max: Maximum execution time observed for Rename operations.</P
-></LI
-><LI
-><P
->Symlink_ops: Number of Symlink operations executed.</P
-></LI
-><LI
-><P
->Symlink_ops_ok: Number of successful Symlink operations.</P
-></LI
-><LI
-><P
->Symlink_sum: Sum of timings for Symlink operations.</P
-></LI
-><LI
-><P
->Symlink_sqr: Sum of squares of sample timings for Symlink operations.</P
-></LI
-><LI
-><P
->Symlink_min: Minimum execution time observed for Symlink operations.</P
-></LI
-><LI
-><P
->Symlink_max: Maximum execution time observed for Symlink operations.</P
-></LI
-><LI
-><P
->Link_ops: Number of Link operations executed.</P
-></LI
-><LI
-><P
->Link_ops_ok: Number of successful Link operations.</P
-></LI
-><LI
-><P
->Link_sum: Sum of timings for Link operations.</P
-></LI
-><LI
-><P
->Link_sqr: Sum of squares of sample timings for Link operations.</P
-></LI
-><LI
-><P
->Link_min: Minimum execution time observed for Link operations.</P
-></LI
-><LI
-><P
->Link_max: Maximum execution time observed for Link operations.</P
-></LI
-><LI
-><P
->MakeDir_ops: Number of MakeDir operations executed.</P
-></LI
-><LI
-><P
->MakeDir_ops_ok: Number of successful MakeDir operations.</P
-></LI
-><LI
-><P
->MakeDir_sum: Sum of timings for MakeDir operations.</P
-></LI
-><LI
-><P
->MakeDir_sqr: Sum of squares of sample timings for MakeDir operations.</P
-></LI
-><LI
-><P
->MakeDir_min: Minimum execution time observed for MakeDir operations.</P
-></LI
-><LI
-><P
->MakeDir_max: Maximum execution time observed for MakeDir operations.</P
-></LI
-><LI
-><P
->RemoveDir_ops: Number of RemoveDir operations executed.</P
-></LI
-><LI
-><P
->RemoveDir_ops_ok: Number of successful RemoveDir operations.</P
-></LI
-><LI
-><P
->RemoveDir_sum: Sum of timings for RemoveDir operations.</P
-></LI
-><LI
-><P
->RemoveDir_sqr: Sum of squares of sample timings for RemoveDir operations.</P
-></LI
-><LI
-><P
->RemoveDir_min: Minimum execution time observed for RemoveDir operations.</P
-></LI
-><LI
-><P
->RemoveDir_max: Maximum execution time observed for RemoveDir operations.</P
-></LI
-><LI
-><P
->SetLock_ops: Number of SetLock operations executed.</P
-></LI
-><LI
-><P
->SetLock_ops_ok: Number of successful SetLock operations.</P
-></LI
-><LI
-><P
->SetLock_sum: Sum of timings for SetLock operations.</P
-></LI
-><LI
-><P
->SetLock_sqr: Sum of squares of sample timings for SetLock operations.</P
-></LI
-><LI
-><P
->SetLock_min: Minimum execution time observed for SetLock operations.</P
-></LI
-><LI
-><P
->SetLock_max: Maximum execution time observed for SetLock operations.</P
-></LI
-><LI
-><P
->ExtendLock_ops: Number of ExtendLock operations executed.</P
-></LI
-><LI
-><P
->ExtendLock_ops_ok: Number of successful ExtendLock operations.</P
-></LI
-><LI
-><P
->ExtendLock_sum: Sum of timings for ExtendLock operations.</P
-></LI
-><LI
-><P
->ExtendLock_sqr: Sum of squares of sample timings for ExtendLock operations.</P
-></LI
-><LI
-><P
->ExtendLock_min: Minimum execution time observed for ExtendLock operations.</P
-></LI
-><LI
-><P
->ExtendLock_max: Maximum execution time observed for ExtendLock operations.</P
-></LI
-><LI
-><P
->ReleaseLock_ops: Number of ReleaseLock operations executed.</P
-></LI
-><LI
-><P
->ReleaseLock_ops_ok: Number of successful ReleaseLock operations.</P
-></LI
-><LI
-><P
->ReleaseLock_sum: Sum of timings for ReleaseLock operations.</P
-></LI
-><LI
-><P
->ReleaseLock_sqr: Sum of squares of sample timings for ReleaseLock operations.</P
-></LI
-><LI
-><P
->ReleaseLock_min: Minimum execution time observed for ReleaseLock operations.</P
-></LI
-><LI
-><P
->ReleaseLock_max: Maximum execution time observed for ReleaseLock operations.</P
-></LI
-><LI
-><P
->GetStatistics_ops: Number of GetStatistics operations executed.</P
-></LI
-><LI
-><P
->GetStatistics_ops_ok: Number of successful GetStatistics operations.</P
-></LI
-><LI
-><P
->GetStatistics_sum: Sum of timings for GetStatistics operations.</P
-></LI
-><LI
-><P
->GetStatistics_sqr: Sum of squares of sample timings for GetStatistics operations.</P
-></LI
-><LI
-><P
->GetStatistics_min: Minimum execution time observed for GetStatistics operations.</P
-></LI
-><LI
-><P
->GetStatistics_max: Maximum execution time observed for GetStatistics operations.</P
-></LI
-><LI
-><P
->GiveUpCallbacks_ops: Number of GiveUpCallbacks operations executed.</P
-></LI
-><LI
-><P
->GiveUpCallbacks_ops_ok: Number of successful GiveUpCallbacks operations.</P
-></LI
-><LI
-><P
->GiveUpCallbacks_sum: Sum of timings for GiveUpCallbacks operations.</P
-></LI
-><LI
-><P
->GiveUpCallbacks_sqr: Sum of squares of sample timings for GiveUpCallbacks operations.</P
-></LI
-><LI
-><P
->GiveUpCallbacks_min: Minimum execution time observed for GiveUpCallbacks operations.</P
-></LI
-><LI
-><P
->GiveUpCallbacks_max: Maximum execution time observed for GiveUpCallbacks operations.</P
-></LI
-><LI
-><P
->GetVolumeInfo_ops: Number of GetVolumeInfo operations executed.</P
-></LI
-><LI
-><P
->GetVolumeInfo_ops_ok: Number of successful GetVolumeInfo operations.</P
-></LI
-><LI
-><P
->GetVolumeInfo_sum: Sum of timings for GetVolumeInfo operations.</P
-></LI
-><LI
-><P
->GetVolumeInfo_sqr: Sum of squares of sample timings for GetVolumeInfo operations.</P
-></LI
-><LI
-><P
->GetVolumeInfo_min: Minimum execution time observed for GetVolumeInfo operations.</P
-></LI
-><LI
-><P
->GetVolumeInfo_max: Maximum execution time observed for GetVolumeInfo operations.</P
-></LI
-><LI
-><P
->GetVolumeStatus_ops: Number of GetVolumeStatus operations executed.</P
-></LI
-><LI
-><P
->GetVolumeStatus_ops_ok: Number of successful GetVolumeStatus operations.</P
-></LI
-><LI
-><P
->GetVolumeStatus_sum: Sum of timings for GetVolumeStatus operations.</P
-></LI
-><LI
-><P
->GetVolumeStatus_sqr: Sum of squares of sample timings for GetVolumeStatus operations.</P
-></LI
-><LI
-><P
->GetVolumeStatus_min: Minimum execution time observed for GetVolumeStatus operations.</P
-></LI
-><LI
-><P
->GetVolumeStatus_max: Maximum execution time observed for GetVolumeStatus operations.</P
-></LI
-><LI
-><P
->SetVolumeStatus_ops: Number of SetVolumeStatus operations executed.</P
-></LI
-><LI
-><P
->SetVolumeStatus_ops_ok: Number of successful SetVolumeStatus operations.</P
-></LI
-><LI
-><P
->SetVolumeStatus_sum: Sum of timings for SetVolumeStatus operations.</P
-></LI
-><LI
-><P
->SetVolumeStatus_sqr: Sum of squares of sample timings for SetVolumeStatus operations.</P
-></LI
-><LI
-><P
->SetVolumeStatus_min: Minimum execution time observed for SetVolumeStatus operations.</P
-></LI
-><LI
-><P
->SetVolumeStatus_max: Maximum execution time observed for SetVolumeStatus operations.</P
-></LI
-><LI
-><P
->GetRootVolume_ops: Number of GetRootVolume operations executed.</P
-></LI
-><LI
-><P
->GetRootVolume_ops_ok: Number of successful GetRootVolume operations.</P
-></LI
-><LI
-><P
->GetRootVolume_sum: Sum of timings for GetRootVolume operations.</P
-></LI
-><LI
-><P
->GetRootVolume_sqr: Sum of squares of sample timings for GetRootVolume operations.</P
-></LI
-><LI
-><P
->GetRootVolume_min: Minimum execution time observed for GetRootVolume operations.</P
-></LI
-><LI
-><P
->GetRootVolume_max: Maximum execution time observed for GetRootVolume operations.</P
-></LI
-><LI
-><P
->CheckToken_ops: Number of CheckToken operations executed.</P
-></LI
-><LI
-><P
->CheckToken_ops_ok: Number of successful CheckToken operations.</P
-></LI
-><LI
-><P
->CheckToken_sum: Sum of timings for CheckToken operations.</P
-></LI
-><LI
-><P
->CheckToken_sqr: Sum of squares of sample timings for CheckToken operations.</P
-></LI
-><LI
-><P
->CheckToken_min: Minimum execution time observed for CheckToken operations.</P
-></LI
-><LI
-><P
->CheckToken_max: Maximum execution time observed for CheckToken operations.</P
-></LI
-><LI
-><P
->GetTime_ops: Number of GetTime operations executed.</P
-></LI
-><LI
-><P
->GetTime_ops_ok: Number of successful GetTime operations.</P
-></LI
-><LI
-><P
->GetTime_sum: Sum of timings for GetTime operations.</P
-></LI
-><LI
-><P
->GetTime_sqr: Sum of squares of sample timings for GetTime operations.</P
-></LI
-><LI
-><P
->GetTime_min: Minimum execution time observed for GetTime operations.</P
-></LI
-><LI
-><P
->GetTime_max: Maximum execution time observed for GetTime operations.</P
-></LI
-><LI
-><P
->NGetVolumeInfo_ops: Number of NGetVolumeInfo operations executed.</P
-></LI
-><LI
-><P
->NGetVolumeInfo_ops_ok: Number of successful NGetVolumeInfo operations.</P
-></LI
-><LI
-><P
->NGetVolumeInfo_sum: Sum of timings for NGetVolumeInfo operations.</P
-></LI
-><LI
-><P
->NGetVolumeInfo_sqr: Sum of squares of sample timings for NGetVolumeInfo operations.</P
-></LI
-><LI
-><P
->NGetVolumeInfo_min: Minimum execution time observed for NGetVolumeInfo operations.</P
-></LI
-><LI
-><P
->NGetVolumeInfo_max: Maximum execution time observed for NGetVolumeInfo operations.</P
-></LI
-><LI
-><P
->BulkStatus_ops: Number of BulkStatus operations executed.</P
-></LI
-><LI
-><P
->BulkStatus_ops_ok: Number of successful BulkStatus operations.</P
-></LI
-><LI
-><P
->BulkStatus_sum: Sum of timings for BulkStatus operations.</P
-></LI
-><LI
-><P
->BulkStatus_sqr: Sum of squares of sample timings for BulkStatus operations.</P
-></LI
-><LI
-><P
->BulkStatus_min: Minimum execution time observed for BulkStatus operations.</P
-></LI
-><LI
-><P
->BulkStatus_max: Maximum execution time observed for BulkStatus operations.</P
-></LI
-><LI
-><P
->XStatsVersion_ops: Number of XStatsVersion operations executed.</P
-></LI
-><LI
-><P
->XStatsVersion_ops_ok: Number of successful XStatsVersion operations.</P
-></LI
-><LI
-><P
->XStatsVersion_sum: Sum of timings for XStatsVersion operations.</P
-></LI
-><LI
-><P
->XStatsVersion_sqr: Sum of squares of sample timings for XStatsVersion operations.</P
-></LI
-><LI
-><P
->XStatsVersion_min: Minimum execution time observed for XStatsVersion operations.</P
-></LI
-><LI
-><P
->XStatsVersion_max: Maximum execution time observed for XStatsVersion operations.</P
-></LI
-><LI
-><P
->GetXStats_ops: Number of GetXStats operations executed.</P
-></LI
-><LI
-><P
->GetXStats_ops_ok: Number of successful GetXStats operations.</P
-></LI
-><LI
-><P
->GetXStats_sum: Sum of timings for GetXStats operations.</P
-></LI
-><LI
-><P
->GetXStats_sqr: Sum of squares of sample timings for GetXStats operations.</P
-></LI
-><LI
-><P
->GetXStats_min: Minimum execution time observed for GetXStats operations.</P
-></LI
-><LI
-><P
->GetXStats_max: Maximum execution time observed for GetXStats operations.</P
-></LI
-></UL
-></P
-><P
->Byte Information for Certain RPC Operations Group (RPCopBytes_group) <UL
-><LI
-><P
->FetchData_xfers: Number of FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_ok: Number of successful FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_sum: Sum of timing values for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_sqr: Sum of squares of sample timings for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_min: Minimum transfer time observed for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_max: Maximum transfer time observed for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_bytes_sum: Sum of bytes transferred for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_bytes_min: Minimum byte transfer observed for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_bytes_max: Maximum byte transfer observed for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_bucket0: Tally in bucket0 for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_bucket1: Tally in bucket1 for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_bucket2: Tally in bucket2 for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_bucket3: Tally in bucket3 for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_bucket4: Tally in bucket4 for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_bucket5: Tally in bucket5 for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_bucket6: Tally in bucket6 for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_bucket7: Tally in bucket7 for FetchData operations.</P
-></LI
-><LI
-><P
->FetchData_xfers_bucket8: Tally in bucket8 for FetchData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers: Number of StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_ok: Number of successful StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_sum: Sum of timing values for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_sqr: Sum of squares of sample timings for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_min: Minimum transfer time observed for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_max: Maximum transfer time observed for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_bytes_sum: Sum of bytes transferred for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_bytes_min: Minimum byte transfer observed for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_bytes_max: Maximum byte transfer observed for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_bucket0: Tally in bucket0 for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_bucket1: Tally in bucket1 for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_bucket2: Tally in bucket2 for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_bucket3: Tally in bucket3 for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_bucket4: Tally in bucket4 for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_bucket5: Tally in bucket5 for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_bucket6: Tally in bucket6 for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_bucket7: Tally in bucket7 for StoreData operations.</P
-></LI
-><LI
-><P
->StoreData_xfers_bucket8: Tally in bucket8 for StoreData operations.</P
-></LI
-></UL
-></P
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="a33826.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="book1.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="a35965.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Using AFS Commands</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->AIX Audit Events</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+++ /dev/null
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
-<HTML
-><HEAD
-><TITLE
->AIX Audit Events</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
-REL="HOME"
-TITLE="AFS Administration Guide"
-HREF="book1.html"><LINK
-REL="PREVIOUS"
-TITLE="The afsmonitor Program Statistics"
-HREF="a34149.html"><LINK
-REL="NEXT"
-TITLE="Index"
-HREF="i37012.html"></HEAD
-><BODY
-CLASS="appendix"
-BGCOLOR="#FFFFFF"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->AFS Administration Guide: Version 3.6</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="a34149.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="i37012.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="appendix"
-><H1
-><A
-NAME="HDRWQ620"
-></A
->Appendix D. AIX Audit Events</H1
-><P
->This Appendix provides a complete listing of the AFS events that can be audited on AIX file server machines. See Chapter
- <A
-HREF="c18360.html"
->Monitoring and Auditing AFS Performance</A
-> for instructions on auditing AFS events on AIX file server
- machines. <A
-NAME="IDX8189"
-></A
-></P
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="HDRWQ621"
->Introduction</A
-></H1
-><P
->Below is a list of the AFS events contained in the file <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/afs/usr/local/audit/events.sample</B
-></SPAN
->. Each entry contains information on the event class, the name of the
- event, the parameters associated with the event, and a description of the event.</P
-><P
->Most events have an associated error code that shows the outcome of the event (since each event is recorded after it
- occurs), an AFSName (the authentication identify of the requesting process), and a host ID (from which the request originated).
- Many events follow the RPC server entry calls defined in the <SPAN
-CLASS="emphasis"
-><I
-CLASS="emphasis"
->AFS Programmer's Reference Manual</I
-></SPAN
->.</P
-><P
->Events are classed by functionality (this is AIX specific). Some events possibly fall into one of more of the following
- classes which are defined by the file <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->/usr/afs/local/config.sample</B
-></SPAN
->: <UL
-><LI
-><P
->A (afsauthent): Authentication and Identification Events</P
-></LI
-><LI
-><P
->S (afssecurity): Security Events</P
-></LI
-><LI
-><P
->P (afsprivilege): Privilege Required Events</P
-></LI
-><LI
-><P
->O (afsobjects): Object Creation and Deletion Events</P
-></LI
-><LI
-><P
->M (afsattributes): Attribute modification</P
-></LI
-><LI
-><P
->C (afsprocess): Process Control Events</P
-></LI
-></UL
-></P
-></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="HDRWQ622"
->Audit-Specific Events</A
-></H1
-><DIV
-CLASS="informaltable"
-><A
-NAME="AEN35993"
-></A
-><TABLE
-BORDER="1"
-CLASS="CALSTABLE"
-><COL
-WIDTH="28*"><COL
-WIDTH="10*"><COL
-WIDTH="25*"><COL
-WIDTH="38*"><THEAD
-><TR
-><TH
->Event</TH
-><TH
->Class</TH
-><TH
->Parameters</TH
-><TH
->Description</TH
-></TR
-></THEAD
-><TBODY
-><TR
-><TD
->AFS_Audit_WR</TD
-><TD
->None</TD
-><TD
-><string></TD
-><TD
->The file "/usr/afs/Audit" has been written to (AIX specific event).</TD
-></TR
-><TR
-><TD
->AFS_Aud_On</TD
-><TD
->S</TD
-><TD
->ECode</TD
-><TD
->Auditing is on for this server process (recorded on startup of a server).</TD
-></TR
-><TR
-><TD
->AFS_Aud_Off</TD
-><TD
->S</TD
-><TD
->ECode</TD
-><TD
->Auditing is off for this server process (recorded on startup of a server).</TD
-></TR
-><TR
-><TD
->AFS_Aud_Unauth</TD
-><TD
->S</TD
-><TD
->ECode Event</TD
-><TD
->Event triggered by an unauthorized user.</TD
-></TR
-></TBODY
-></TABLE
-></DIV
-><DIV
-CLASS="note"
-><BLOCKQUOTE
-CLASS="note"
-><P
-><B
->Note: </B
->The following audit-specific events indicate an error has occurred while recording the event. Most events have an
- AFSName associated with them and a host ID. If this information cannot be gathered out of the Rx structure, one of these
- events is raised.</P
-></BLOCKQUOTE
-></DIV
-><DIV
-CLASS="informaltable"
-><A
-NAME="AEN36028"
-></A
-><TABLE
-BORDER="1"
-CLASS="CALSTABLE"
-><COL
-WIDTH="28*"><COL
-WIDTH="10*"><COL
-WIDTH="25*"><COL
-WIDTH="38*"><THEAD
-><TR
-><TH
->Event</TH
-><TH
->Class</TH
-><TH
->Parameters</TH
-><TH
->Description</TH
-></TR
-></THEAD
-><TBODY
-><TR
-><TD
->AFS_Aud_NoCall</TD
-><TD
->S</TD
-><TD
->ECode Event</TD
-><TD
->No rx call structure with this event. Cannot get security, AFS ID, or origin of call.</TD
-></TR
-><TR
-><TD
->AFS_Aud_NoConn</TD
-><TD
->S</TD
-><TD
->ECode Event</TD
-><TD
->No connection info associated with rx call. Cannot get security, AFS ID, or origin of call.</TD
-></TR
-><TR
-><TD
->AFS_Aud_UnknSec</TD
-><TD
->S</TD
-><TD
->ECode Event</TD
-><TD
->Security of call is unknown (must be authorized or unauthorized caller).</TD
-></TR
-><TR
-><TD
->AFS_Aud_NoAFSId</TD
-><TD
->S</TD
-><TD
->ECode Event</TD
-><TD
->No AFS ID/name associated with a secure event.</TD
-></TR
-><TR
-><TD
->AFS_Aud_NoHost</TD
-><TD
->S</TD
-><TD
->ECode Event</TD
-><TD
->No information about origin (machine) of caller.</TD
-></TR
-><TR
-><TD
->AFS_Aud_EINVAL</TD
-><TD
->None</TD
-><TD
->Event</TD
-><TD
->Error in audit event parameter (can't record the event parameter).</TD
-></TR
-></TBODY
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="HDRWQ627"
->Volume Server Events</A
-></H1
-><DIV
-CLASS="informaltable"
-><A
-NAME="AEN36073"
-></A
-><TABLE
-BORDER="1"
-CLASS="CALSTABLE"
-><COL
-WIDTH="28*"><COL
-WIDTH="10*"><COL
-WIDTH="25*"><COL
-WIDTH="38*"><THEAD
-><TR
-><TH
->Event</TH
-><TH
->Class</TH
-><TH
->Parameters</TH
-><TH
->Description</TH
-></TR
-></THEAD
-><TBODY
-><TR
-><TD
->AFS_VS_Start</TD
-><TD
->P C</TD
-><TD
->ECode</TD
-><TD
->The volume server has started.</TD
-></TR
-><TR
-><TD
->AFS_VS_Finish</TD
-><TD
->C</TD
-><TD
->ECode</TD
-><TD
->The volume server has finished. Finish events are rare since the server process is normally aborted.</TD
-></TR
-><TR
-><TD
->AFS_VS_Exit</TD
-><TD
->C</TD
-><TD
->ECode</TD
-><TD
->The volume server has exited. Exit events are rare since the server process is normally aborted.</TD
-></TR
-><TR
-><TD
->AFS_VS_TransCr</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID Trans VolID</TD
-><TD
->AFSVolTransCreate - Create transaction for a [volume, partition]</TD
-></TR
-><TR
-><TD
->AFS_VS_EndTrn</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID Trans</TD
-><TD
->AFSVolEndTrans - End a transaction.</TD
-></TR
-><TR
-><TD
->AFS_VS_CrVol</TD
-><TD
->P O</TD
-><TD
->ECode AFSName HostID Trans VolID VolName Type ParentID</TD
-><TD
->AFSVolCreateVolume - Create a volume (volumeId volumeName)</TD
-></TR
-><TR
-><TD
->AFS_VS_DelVol</TD
-><TD
->P O</TD
-><TD
->ECode AFSName HostID Trans</TD
-><TD
->AFSVolDeleteVolume - Delete a volume.</TD
-></TR
-><TR
-><TD
->AFS_VS_NukVol</TD
-><TD
->P O</TD
-><TD
->ECode AFSName HostID VolID</TD
-><TD
->AFSVolNukeVolume - Obliterate a volume completely (volume ID).</TD
-></TR
-><TR
-><TD
->AFS_VS_Dump</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID Trans</TD
-><TD
->AFSVolDump - Dump the contents of a volume.</TD
-></TR
-><TR
-><TD
->AFS_VS_SigRst</TD
-><TD
->P M</TD
-><TD
->ECode AFSName HostID VolName</TD
-><TD
->AFSVolSignalRestore - Show intention to call AFSVolRestore.</TD
-></TR
-><TR
-><TD
->AFS_VS_Restore</TD
-><TD
->P O</TD
-><TD
->ECode AFSName HostID Trans</TD
-><TD
->AFSVolRestore - Recreate a volume from a dump.</TD
-></TR
-><TR
-><TD
->AFS_VS_Forward</TD
-><TD
->P O</TD
-><TD
->ECode AFSName HostID FromTrans Host DestTrans</TD
-><TD
->AFSVolForward - Dump a volume, then restore to a given server and volume.</TD
-></TR
-><TR
-><TD
->AFS_VS_Clone</TD
-><TD
->P O</TD
-><TD
->ECode AFSName HostID Trans Purge NewName NewType NewVolID</TD
-><TD
->AFSVolClone - Clone (and optionally purge) a volume.</TD
-></TR
-><TR
-><TD
->AFS_VS_ReClone</TD
-><TD
->P O</TD
-><TD
->ECode AFSName HostID Trans CloneVolID</TD
-><TD
->AFSVolReClone - Reclone a volume.</TD
-></TR
-><TR
-><TD
->AFS_VS_SetForw</TD
-><TD
->P M</TD
-><TD
->ECode AFSName HostID Trans NewHost</TD
-><TD
->AFSVolSetForwarding - Set forwarding information for a moved volume.</TD
-></TR
-><TR
-><TD
->AFS_VS_GetFlgs</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID Trans</TD
-><TD
->AFSVolGetFlags - Get volume flags for a transaction.</TD
-></TR
-><TR
-><TD
->AFS_VS_SetFlgs</TD
-><TD
->P M</TD
-><TD
->ECode AFSName HostID Trans Flags</TD
-><TD
->AFSVolSetFlags - Set volume flags for a transaction.</TD
-></TR
-><TR
-><TD
->AFS_VS_GetName</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID Trans</TD
-><TD
->AFSVolGetName - Get the volume name associated with a transaction.</TD
-></TR
-><TR
-><TD
->AFS_VS_GetStat</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID Trans</TD
-><TD
->AFSVolGetStatus - Get status of a transaction/volume.</TD
-></TR
-><TR
-><TD
->AFS_VS_SetIdTy</TD
-><TD
->P M</TD
-><TD
->ECode AFSName HostID Trans VolName Type ParentId CloneID BackupID</TD
-><TD
->AFSVolSetIdsTypes - Set header information for a volume.</TD
-></TR
-><TR
-><TD
->AFS_VS_SetDate</TD
-><TD
->P M</TD
-><TD
->ECode AFSName HostID Trans Date</TD
-><TD
->AFSVolSetDate - Set creation date in a volume.</TD
-></TR
-><TR
-><TD
->AFS_VS_ListPar</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->AFSVolListPartitions - Return a list of AFS partitions on a server.</TD
-></TR
-><TR
-><TD
->AFS_VS_ParInf</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID PartName</TD
-><TD
->AFSVolPartitionInfo - Get partition information.</TD
-></TR
-><TR
-><TD
->AFS_VS_ListVol</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->AFSVolListVolumes - Return a list of volumes on a server.</TD
-></TR
-><TR
-><TD
->AFS_VS_XLstVol</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->AFSVolXListVolumes - Return a (detailed) list of volumes on a server.</TD
-></TR
-><TR
-><TD
->AFS_VS_Lst1Vol</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID VolID</TD
-><TD
->AFSVolListOneVolume - Return header information for a single volume.</TD
-></TR
-><TR
-><TD
->AFS_VS_XLst1Vl</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID VolID</TD
-><TD
->AFSVolXListOneVolume - Return (detailed) header information for a single volume.</TD
-></TR
-><TR
-><TD
->AFS_VS_GetNVol</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID VolID</TD
-><TD
->AFSVolGetNthVolume - Get volume header given its index.</TD
-></TR
-><TR
-><TD
->AFS_VS_Monitor</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->AFSVolMonitor - Collect server transaction state.</TD
-></TR
-><TR
-><TD
->AFS_VS_SetInfo</TD
-><TD
->P O M</TD
-><TD
->ECode AFSName HostID Trans</TD
-><TD
->AFSVolSetInfo - Set volume status.</TD
-></TR
-></TBODY
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="HDRWQ630"
->Backup Server Events</A
-></H1
-><DIV
-CLASS="informaltable"
-><A
-NAME="AEN36238"
-></A
-><TABLE
-BORDER="1"
-CLASS="CALSTABLE"
-><COL
-WIDTH="28*"><COL
-WIDTH="10*"><COL
-WIDTH="25*"><COL
-WIDTH="38*"><THEAD
-><TR
-><TH
->Event</TH
-><TH
->Class</TH
-><TH
->Parameters</TH
-><TH
->Description</TH
-></TR
-></THEAD
-><TBODY
-><TR
-><TD
->AFS_BUDB_Start</TD
-><TD
->P</TD
-><TD
->ECode</TD
-><TD
->The backup server has started.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_Finish</TD
-><TD
->None</TD
-><TD
->ECode</TD
-><TD
->The backup server has finished. Finish events are rare since the server process is normally aborted.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_Exit</TD
-><TD
->None</TD
-><TD
->ECode</TD
-><TD
->The backup server has exited. Exit events are rare since the server process is normally aborted.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_CrDmp</TD
-><TD
->P O</TD
-><TD
->ECode AFSName HostID dumpId</TD
-><TD
->BUDB_CreateDump - Create a new dump.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_AppDmp</TD
-><TD
->P</TD
-><TD
->ECode AFSName HostID dumpId</TD
-><TD
->BUDB_makeDumpAppended - Make the dump an appended dump.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_DelDmp</TD
-><TD
->P O</TD
-><TD
->ECode AFSName HostID dumpId</TD
-><TD
->BUDB_DeleteDump - Delete a dump.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_FinDmp</TD
-><TD
->P</TD
-><TD
->ECode AFSName HostID dumpId</TD
-><TD
->BUDB_FinishDump- Notify buserver that dump is finished.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_UseTpe</TD
-><TD
->P M</TD
-><TD
->ECode AFSName HostID dumpId</TD
-><TD
->BUDB_UseTape - Create/add a tape entry to a dump.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_DelTpe</TD
-><TD
->P M</TD
-><TD
->ECode AFSName HostID dumpId</TD
-><TD
->BUDB_DeleteTape - Remove a tape from the database.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_FinTpe</TD
-><TD
->P</TD
-><TD
->ECode AFSName HostID dumpId</TD
-><TD
->BUDB_FinishTape - Writing to a tape is completed.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_AddVol</TD
-><TD
->P M</TD
-><TD
->ECode AFSName HostID volId</TD
-><TD
->BUDB_AddVolume - Add a volume to a particular dump and tape.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_GetTxV</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID Type</TD
-><TD
->BUDB_GetTextVersion - Get the version number for hosts/volume-sets/dump-hierarchy.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_GetTxt</TD
-><TD
->P</TD
-><TD
->ECode AFSName HostID Type</TD
-><TD
->BUDB_GetText - Get the information about hosts/volume-sets/dump-hierarchy.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_SavTxt</TD
-><TD
->M</TD
-><TD
->ECode AFSName HostID Type</TD
-><TD
->BUDB_SaveText - Overwrite the information about hosts/volume-sets/dump-hierarchy.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_GetLck</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BUDB_GetLock - Take a lock for reading/writing text information.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_FrALck</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BUDB_FreeLock - Free a lock.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_FreLck</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BUDB_FreeAllLocks - Free all locks.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_GetIId</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BUDB_GetInstanceId - Get lock instance id.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_DmpDB</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BUDB_DumpDB - Start dumping the database.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_RstDBH</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BUDB_RestoreDbHeader - Restore the database header.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_DBVfy</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BUDB_DbVerify - Verify the database.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_FndDmp</TD
-><TD
->P</TD
-><TD
->ECode AFSName HostID volName</TD
-><TD
->BUDB_FindDump - Find the dump a volume belongs to.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_GetDmp</TD
-><TD
->P</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BUDB_GetDumps - Get a list of dumps in the database.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_FnLTpe</TD
-><TD
->P</TD
-><TD
->ECode AFSName HostID dumpId</TD
-><TD
->BUDB_FindLastTape - Find last tape, and last volume on tape of a dump.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_GetTpe</TD
-><TD
->P</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BUDB_GetTapes - Find a list of tapes based on name or dump ID.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_GetVol</TD
-><TD
->P</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BUDB_GetVolumes - Find a list of volumes based on dump or tape name.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_DelVDP</TD
-><TD
->P M</TD
-><TD
->ECode AFSName HostID dumpSetName</TD
-><TD
->BUDB_DeleteVDP - Delete dumps with given name and dump path.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_FndCln</TD
-><TD
->P M</TD
-><TD
->ECode AFSName HostID volName</TD
-><TD
->BUDB_FindClone - Find clone time of volume.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_FndLaD</TD
-><TD
->P</TD
-><TD
->ECode AFSName HostID volName</TD
-><TD
->BUDB_FindLatestDump - Find the latest dump a volume belongs to.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_TGetVr</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BUDB_T_GetVersion - Test Get version.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_TDmpHa</TD
-><TD
->P</TD
-><TD
->ECode AFSName HostID file</TD
-><TD
->BUDB_T_DumpHashTable - Test dump of hash table.</TD
-></TR
-><TR
-><TD
->AFS_BUDB_TDmpDB</TD
-><TD
->P</TD
-><TD
->ECode AFSName HostID file</TD
-><TD
->BUDB_T_DumpDatabase - Test dump of database.</TD
-></TR
-></TBODY
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="HDRWQ633"
->Protection Server Events</A
-></H1
-><DIV
-CLASS="informaltable"
-><A
-NAME="AEN36413"
-></A
-><TABLE
-BORDER="1"
-CLASS="CALSTABLE"
-><COL
-WIDTH="28*"><COL
-WIDTH="10*"><COL
-WIDTH="25*"><COL
-WIDTH="38*"><THEAD
-><TR
-><TH
->Event</TH
-><TH
->Class</TH
-><TH
->Parameters</TH
-><TH
->Description</TH
-></TR
-></THEAD
-><TBODY
-><TR
-><TD
->AFS_PTS_Start</TD
-><TD
->P</TD
-><TD
->ECode</TD
-><TD
->The protection server has started.</TD
-></TR
-><TR
-><TD
->AFS_PTS_Finish</TD
-><TD
->C</TD
-><TD
->ECode</TD
-><TD
->The protection server has finished. Finish events are rare since the server process is normally aborted.</TD
-></TR
-><TR
-><TD
->AFS_PTS_Exit</TD
-><TD
->C</TD
-><TD
->ECode</TD
-><TD
->The protection server has exited. Exit events are rare since the server process is normally aborted.</TD
-></TR
-><TR
-><TD
->AFS_PTS_NmToId</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->PR_NameToID - Perform one or more name-to-ID translations.</TD
-></TR
-><TR
-><TD
->AFS_PTS_IdToNm</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID GroupId</TD
-><TD
->PR_IDToName - Perform one or more ID-to-name translations.</TD
-></TR
-><TR
-><TD
->AFS_PTS_NewEnt</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID GroupId Name OwnerId</TD
-><TD
->PR_NewEntry - Create a PDB (Protection DataBase) entry for the given name.</TD
-></TR
-><TR
-><TD
->AFS_PTS_INewEnt</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID GroupId Name OwnerId</TD
-><TD
->PR_INewEntry - Create a PDB entry for the given name and ID.</TD
-></TR
-><TR
-><TD
->AFS_PTS_LstEnt</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID GroupId</TD
-><TD
->PR_ListEntry - Get the contents of a PDB entry based on its ID.</TD
-></TR
-><TR
-><TD
->AFS_PTS_DmpEnt</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID Position</TD
-><TD
->PR_DumpEntry - Get the contents of a PDB entry based on its offset.</TD
-></TR
-><TR
-><TD
->AFS_PTS_ChgEnt</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID GroupId NewName NewOwnerId NewId</TD
-><TD
->PR_ChangeEntry - Change an existing PDB entry's ID, name, owner, or a combination.</TD
-></TR
-><TR
-><TD
->AFS_PTS_SetFEnt</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID GroupId</TD
-><TD
->PR_SetFieldsEntry - Change miscellaneous fields in an existing PDB entry.</TD
-></TR
-><TR
-><TD
->AFS_PTS_Del</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID GroupId</TD
-><TD
->PR_Delete - Delete an existing PDB entry.</TD
-></TR
-><TR
-><TD
->FS_PTS_WheIsIt</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID GroupId Position</TD
-><TD
->PR_WhereIsIt - Get the PDB byte offset of the entry for a given ID.</TD
-></TR
-><TR
-><TD
->AFS_PTS_AdToGrp</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID GroupId UserId</TD
-><TD
->PR_AddToGroup - Add a user to a group.</TD
-></TR
-><TR
-><TD
->AFS_PTS_RmFmGrp</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID GroupId UserId</TD
-><TD
->PR_RemoveFromGroup - Remove a user from a chosen group.</TD
-></TR
-><TR
-><TD
->AFS_PTS_LstMax</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->PR_ListMax - Get the largest allocated user and group ID.</TD
-></TR
-><TR
-><TD
->AFS_PTS_SetMax</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID GroupId flag</TD
-><TD
->PR_SetMax - Set the largest allocated user and group ID.</TD
-></TR
-><TR
-><TD
->AFS_PTS_LstEle</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID GroupId</TD
-><TD
->PR_ListElements - List all IDs associated with a user or group.</TD
-></TR
-><TR
-><TD
->AFS_PTS_GetCPS</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID GroupId</TD
-><TD
->PR_GetCPS - Get the CPS (Current Protection Subdomain) for the given ID.</TD
-></TR
-><TR
-><TD
->AFS_PTS_GetCPS2</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID GroupId Host</TD
-><TD
->PR_GetCPS2 - Get the CPS for the given id and host.</TD
-></TR
-><TR
-><TD
->AFS_PTS_GetHCPS</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID Host</TD
-><TD
->PR_GetHostCPS - Get the CPS for the given host.</TD
-></TR
-><TR
-><TD
->AFS_PTS_LstOwn</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID GroupId</TD
-><TD
->PR_ListOwned - Get all IDs owned by the given ID.</TD
-></TR
-><TR
-><TD
->AFS_PTS_IsMemOf</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID UserId GroupId</TD
-><TD
->PR_IsAMemberOf - Is a given user ID a member of a specified group?</TD
-></TR
-></TBODY
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="HDRWQ636"
->Authentication Events</A
-></H1
-><DIV
-CLASS="informaltable"
-><A
-NAME="AEN36543"
-></A
-><TABLE
-BORDER="1"
-CLASS="CALSTABLE"
-><COL
-WIDTH="28*"><COL
-WIDTH="10*"><COL
-WIDTH="25*"><COL
-WIDTH="38*"><THEAD
-><TR
-><TH
->Event</TH
-><TH
->Class</TH
-><TH
->Parameters</TH
-><TH
->Description</TH
-></TR
-></THEAD
-><TBODY
-><TR
-><TD
->AFS_KAA_ChPswd</TD
-><TD
->S</TD
-><TD
->ECode AFSName HostID name instance</TD
-><TD
->KAA_ChangePassword - Change password.</TD
-></TR
-><TR
-><TD
->AFS_KAA_Auth</TD
-><TD
->A S</TD
-><TD
->ECode AFSName HostID name instance</TD
-><TD
->KAA_Authenticate - Authenticate to the cell.</TD
-></TR
-><TR
-><TD
->AFS_KAA_AuthO</TD
-><TD
->S</TD
-><TD
->ECode AFSName HostID name instance</TD
-><TD
->KAA_Authenticate_old - Old style authentication.</TD
-></TR
-><TR
-><TD
->AFS_KAT_GetTkt</TD
-><TD
->A S</TD
-><TD
->ECode AFSName HostID name instance</TD
-><TD
->KAT_GetTicket - An attempt was made to get an AFS ticket for some principal listed in the Authentication
- Database.</TD
-></TR
-><TR
-><TD
->AFS_KAT_GetTktO</TD
-><TD
->S</TD
-><TD
->ECode AFSName HostID name instance</TD
-><TD
->KAT_GetTicket_old - An attempt was made to get an AFS ticket for some principal listed in the Authentication
- Database.</TD
-></TR
-><TR
-><TD
->AFS_KAM_CrUser</TD
-><TD
->S P</TD
-><TD
->ECode AFSName HostID name instance</TD
-><TD
->KAM_CreateUser - Create a user.</TD
-></TR
-><TR
-><TD
->AFS_KAM_DelUser</TD
-><TD
->S P</TD
-><TD
->ECode AFSName HostID name instance</TD
-><TD
->KAM_DeleteUser - Delete a user.</TD
-></TR
-><TR
-><TD
->AFS_KAM_SetPswd</TD
-><TD
->S</TD
-><TD
->ECode AFSName HostID name instance</TD
-><TD
->KAM_SetPassword - Set the password for a user.</TD
-></TR
-><TR
-><TD
->AFS_KAM_GetPswd</TD
-><TD
->S</TD
-><TD
->ECode AFSName HostID name</TD
-><TD
->KAM_GetPassword - Get the password of a user.</TD
-></TR
-><TR
-><TD
->AFS_KAM_GetEnt</TD
-><TD
->S</TD
-><TD
->ECode AFSName HostID name instance</TD
-><TD
->KAM_GetEntry - The RPC made by the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->kas examine</B
-></SPAN
-> command to get one entry from the
- Authentication Database (by index entry).</TD
-></TR
-><TR
-><TD
->AFS_KAM_LstEnt</TD
-><TD
->S</TD
-><TD
->ECode AFSName HostID index</TD
-><TD
->KAM_ListEntry - The RPC made to list one or more entries in the Authentication Database.</TD
-></TR
-><TR
-><TD
->AFS_KAM_Dbg</TD
-><TD
->S</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->KAM_Debug - The RPC that produces a debugging trace for the Authentication Server.</TD
-></TR
-><TR
-><TD
->AFS_KAM_SetFld</TD
-><TD
->S P</TD
-><TD
->ECode AFSName HostID name instance flags date lifetime maxAssoc</TD
-><TD
->KAM_SetFields - The RPC used by the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->kas setfields</B
-></SPAN
-> command to manipulate the
- Authentication Database.</TD
-></TR
-><TR
-><TD
->AFS_KAM_GetStat</TD
-><TD
->S</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->KAM_GetStatus - An RPC used to get statistics on the Authentication Server.</TD
-></TR
-><TR
-><TD
->AFS_KAM_GRnKey</TD
-><TD
->S</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->KAM_GetRandomKey - An RPC used to generate a random encryption key.</TD
-></TR
-><TR
-><TD
->AFS_UnlockUser</TD
-><TD
->S</TD
-><TD
->ECode AFSName HostID name instance</TD
-><TD
->KAM_Unlock - The RPC used to initiate the <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->kas unlock</B
-></SPAN
-> command.</TD
-></TR
-><TR
-><TD
->AFS_LockStatus</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID name instance</TD
-><TD
->KAM_LockStatus - The RPC used to determine whether a user's Authentication Database entry is locked.</TD
-></TR
-><TR
-><TD
->AFS_UseOfPriv</TD
-><TD
->P</TD
-><TD
->ECode AFSName HostID name instance cell</TD
-><TD
->An authorized command was issued and allowed because the user had privilege.</TD
-></TR
-><TR
-><TD
->AFS_UnAth</TD
-><TD
->S</TD
-><TD
->ECode AFSName HostID name instance cell</TD
-><TD
->An authorized command was issued and allowed because the system was running in noauth mode.</TD
-></TR
-><TR
-><TD
->AFS_UDPAuth</TD
-><TD
->A S</TD
-><TD
->ECode name instance</TD
-><TD
->An authentication attempt was made with a Kerberos client.</TD
-></TR
-><TR
-><TD
->AFS_UDPGetTckt</TD
-><TD
->A S</TD
-><TD
->ECode name instance cell name instance</TD
-><TD
->An attempt was made to get a Kerberos ticket.</TD
-></TR
-><TR
-><TD
->AFS_RunNoAuth</TD
-><TD
->S</TD
-><TD
->ECode</TD
-><TD
->Check was made and some random server is running noauth.</TD
-></TR
-><TR
-><TD
->AFS_NoAuthDsbl</TD
-><TD
->S P</TD
-><TD
->ECode</TD
-><TD
->Server is set to run in authenticated mode.</TD
-></TR
-><TR
-><TD
->AFS_NoAuthEnbl</TD
-><TD
->S P</TD
-><TD
->ECode</TD
-><TD
->Server is set to run in unauthenticated mode.</TD
-></TR
-></TBODY
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="HDRWQ639"
->File Server and Cache Manager Interface Events</A
-></H1
-><DIV
-CLASS="informaltable"
-><A
-NAME="AEN36681"
-></A
-><TABLE
-BORDER="1"
-CLASS="CALSTABLE"
-><COL
-WIDTH="28*"><COL
-WIDTH="10*"><COL
-WIDTH="25*"><COL
-WIDTH="38*"><THEAD
-><TR
-><TH
->Event</TH
-><TH
->Class</TH
-><TH
->Parameters</TH
-><TH
->Description</TH
-></TR
-></THEAD
-><TBODY
-><TR
-><TD
->AFS_SRX_FchACL</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID (FID)</TD
-><TD
->RXAFS_FetchACL - Fetch the ACL associated with the given AFS file identifier.</TD
-></TR
-><TR
-><TD
->AFS_SRX_FchStat</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID (FID)</TD
-><TD
->RXAFS_FetchStatus - Fetch the status information for a file system object.</TD
-></TR
-><TR
-><TD
->AFS_SRX_StACL</TD
-><TD
->M</TD
-><TD
->ECode AFSName HostID (FID)</TD
-><TD
->RXAFS_StoreACL - Associate an ACL with the names directory.</TD
-></TR
-><TR
-><TD
->AFS_SRX_StStat</TD
-><TD
->M</TD
-><TD
->ECode AFSName HostID (FID)</TD
-><TD
->RXAFS_StoreStatus - Store status information for the specified file.</TD
-></TR
-><TR
-><TD
->AFS_SRX_RmFile</TD
-><TD
->O</TD
-><TD
->ECode AFSName HostID (FID) name</TD
-><TD
->RXAFS_RemoveFile - Delete the given file.</TD
-></TR
-><TR
-><TD
->AFS_SRX_CrFile</TD
-><TD
->O</TD
-><TD
->ECode AFSName HostID (FID) name</TD
-><TD
->RXAFS_CreateFile - Create the given file.</TD
-></TR
-><TR
-><TD
->AFS_SRX_RNmFile</TD
-><TD
->O M</TD
-><TD
->ECode AFSName HostID (oldFID) oldName (newFID) newName</TD
-><TD
->RXAFS_Rename - Rename the specified file in the given directory.</TD
-></TR
-><TR
-><TD
->AFS_SRX_SymLink</TD
-><TD
->O</TD
-><TD
->ECode AFSName HostID (FID) name</TD
-><TD
->RXAFS_Symlink - Create a symbolic link.</TD
-></TR
-><TR
-><TD
->AFS_SRX_Link</TD
-><TD
->O</TD
-><TD
->ECode AFSName HostID (FID) name (FID)</TD
-><TD
->RXAFS_Link - Create a hard link.</TD
-></TR
-><TR
-><TD
->AFS_SRX_MakeDir</TD
-><TD
->O</TD
-><TD
->ECode AFSName HostID (FID) name</TD
-><TD
->RXAFS_MakeDir - Create a directory.</TD
-></TR
-><TR
-><TD
->AFS_SRX_RmDir</TD
-><TD
->O</TD
-><TD
->ECode AFSName HostID (FID) name</TD
-><TD
->RXAFS_RemoveDir - Remove a directory.</TD
-></TR
-><TR
-><TD
->AFS_SRX_SetLock</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID (FID) type</TD
-><TD
->RXAFS_SetLock - Set an advisory lock on the given file identifier.</TD
-></TR
-><TR
-><TD
->AFS_SRX_ExtLock</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID (FID)</TD
-><TD
->RXAFS_ExtendLock - Extend an advisory lock on a file.</TD
-></TR
-><TR
-><TD
->AFS_SRX_RelLock</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID (FID)</TD
-><TD
->RXAFS_ReleaseLock - Release the advisory lock on a file.</TD
-></TR
-><TR
-><TD
->AFS_SRX_FchData</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID (FID)</TD
-><TD
->StartRXAFS_FetchData - Begin a request to fetch file data.</TD
-></TR
-><TR
-><TD
->AFS_SRX_StData</TD
-><TD
->O</TD
-><TD
->ECode AFSName HostID (FID)</TD
-><TD
->StartRXAFS_StoreData - Begin a request to store file data.</TD
-></TR
-><TR
-><TD
->AFS_SRX_BFchSta</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID (FID)</TD
-><TD
->RXAFS_BulkStatus - Fetch status information regarding a set of file system objects.</TD
-></TR
-><TR
-><TD
->AFS_SRX_SetVolS</TD
-><TD
->M</TD
-><TD
->ECode AFSName HostID volId volName</TD
-><TD
->RXAFS_SetVolumeStatus - Set the basic status information for the named volume.</TD
-></TR
-><TR
-><TD
->AFS_Priv</TD
-><TD
->P</TD
-><TD
->ECode viceId callRoutine</TD
-><TD
->Checking Permission Rights of user - user has permissions.</TD
-></TR
-><TR
-><TD
->AFS_PrivSet</TD
-><TD
->P</TD
-><TD
->ECode viceId callRoutine</TD
-><TD
->Set the privileges of a user.</TD
-></TR
-></TBODY
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="HDRWQ642"
->BOS Server Events</A
-></H1
-><DIV
-CLASS="informaltable"
-><A
-NAME="AEN36796"
-></A
-><TABLE
-BORDER="1"
-CLASS="CALSTABLE"
-><COL
-WIDTH="28*"><COL
-WIDTH="10*"><COL
-WIDTH="25*"><COL
-WIDTH="38*"><THEAD
-><TR
-><TH
->Event</TH
-><TH
->Class</TH
-><TH
->Parameters</TH
-><TH
->Description</TH
-></TR
-></THEAD
-><TBODY
-><TR
-><TD
->AFS_BOS_CreBnod</TD
-><TD
->P C</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BOZO_CreateBnode - Create a process instance.</TD
-></TR
-><TR
-><TD
->AFS_BOS_DelBnod</TD
-><TD
->P C</TD
-><TD
->ECode AFSName HostID instance</TD
-><TD
->BOZO_DeleteBnode - Delete a process instance.</TD
-></TR
-><TR
-><TD
->AFS_BOS_SetReSt</TD
-><TD
->P M C</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BOZO_Restart - Restart a given process instance.</TD
-></TR
-><TR
-><TD
->AFS_BOS_GetLog</TD
-><TD
->P</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->StartBOZO_GetLog - Pass the IN params when fetching a BOS Server log file.</TD
-></TR
-><TR
-><TD
->AFS_BOS_SetStat</TD
-><TD
->P M C</TD
-><TD
->ECode AFSName HostID instance</TD
-><TD
->BOZO_SetStatus - Set process instance status and goal.</TD
-></TR
-><TR
-><TD
->AFS_BOS_SetTSta</TD
-><TD
->P M C</TD
-><TD
->ECode AFSName HostID instance</TD
-><TD
->BOZO_SetTStatus - Temporarily set process instance status and goal.</TD
-></TR
-><TR
-><TD
->AFS_BOS_StartAl</TD
-><TD
->P C</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BOZO_StartupAll - Start all existing process instances.</TD
-></TR
-><TR
-><TD
->AFS_BOS_ShtdAll</TD
-><TD
->P C</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BOZO_ShutdownAll - Shut down all process instances.</TD
-></TR
-><TR
-><TD
->AFS_BOS_ReStAll</TD
-><TD
->P C</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BOZO_RestartAll - Shut down, then restart all process instances.</TD
-></TR
-><TR
-><TD
->AFS_BOS_ReBos</TD
-><TD
->P C</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BOZO_ReBozo - Shut down, then restart all process instances and the BOS Server itself.</TD
-></TR
-><TR
-><TD
->AFS_BOS_ReBosIn</TD
-><TD
->P C</TD
-><TD
->ECode</TD
-><TD
->BOZO_ReBozo - Same as AFS_BOS_ReBos but done internally (server restarts).</TD
-></TR
-><TR
-><TD
->AFS_BOS_ReStart</TD
-><TD
->P C</TD
-><TD
->ECode AFSName HostID instance</TD
-><TD
->BOZO_Restart - Restart a given process instance.</TD
-></TR
-><TR
-><TD
->AFS_BOS_WaitAll</TD
-><TD
->P C</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BOZO_WaitAll - Wait until all process instances have reached their goals.</TD
-></TR
-><TR
-><TD
->AFS_BOS_AddSUsr</TD
-><TD
->S P</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BOZO_AddSUser - Add a user to the UserList.</TD
-></TR
-><TR
-><TD
->AFS_BOS_DelSUsr</TD
-><TD
->S P</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BOZO_DeleteSUser - Delete a user from the UserList.</TD
-></TR
-><TR
-><TD
->AFS_BOS_LstSUsr</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BOZO_ListSUsers - Get the name of the user in the given position in the UserList file.</TD
-></TR
-><TR
-><TD
->AFS_BOS_LstKey</TD
-><TD
->P</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BOZO_ListKeys - List information about the key at a given index in the key file.</TD
-></TR
-><TR
-><TD
->AFS_BOS_LstKeyU</TD
-><TD
->P</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BOZO_ListKeys - Same as AFS_BOS_LstKey, but unauthorized.</TD
-></TR
-><TR
-><TD
->AFS_BOS_AddKey</TD
-><TD
->S P</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BOZO_AddKey - Add a key to the key file.</TD
-></TR
-><TR
-><TD
->AFS_BOS_DelKey</TD
-><TD
->S P</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BOZO_DeleteKey - Delete the entry for an AFS key.</TD
-></TR
-><TR
-><TD
->AFS_BOS_SetNoAu</TD
-><TD
->S P</TD
-><TD
->ECode AFSName HostID flag</TD
-><TD
->BOZO_SetNoAuthFlag - Enable or disable authenticated call requirements.</TD
-></TR
-><TR
-><TD
->AFS_BOS_SetCell</TD
-><TD
->S P</TD
-><TD
->ECode AFSName HostID name</TD
-><TD
->BOZO_SetCellName - Set the name of the cell to which the BOS Server belongs.</TD
-></TR
-><TR
-><TD
->AFS_BOS_AddHst</TD
-><TD
->S P</TD
-><TD
->ECode AFSName HostID name</TD
-><TD
->BOZO_AddCellHost - Add an entry to the list of database server hosts.</TD
-></TR
-><TR
-><TD
->AFS_BOS_DelHst</TD
-><TD
->S P</TD
-><TD
->ECode AFSName HostID name</TD
-><TD
->BOZO_DeleteCellHost - Delete an entry from the list of database server hosts.</TD
-></TR
-><TR
-><TD
->AFS_BOS_Inst</TD
-><TD
->P O M</TD
-><TD
->ECode AFSName HostID name</TD
-><TD
-><P
->StartBOZO_Install - Pass the IN parameters when installing a server binary.</P
-> <P
->EndBOZO_Install -
- Get the OUT parameters when installing a server binary.</P
-></TD
-></TR
-><TR
-><TD
->AFS_BOS_UnInst</TD
-><TD
->P O M</TD
-><TD
->ECode AFSName HostID name</TD
-><TD
->BOZO_UnInstall - Roll back from a server binary installation.</TD
-></TR
-><TR
-><TD
->AFS_BOS_PrnLog</TD
-><TD
->P O</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->BOZO_Prune - Throw away old versions of server binaries and core file.</TD
-></TR
-><TR
-><TD
->AFS_BOS_Exec</TD
-><TD
->P C</TD
-><TD
->ECode AFSName HostID cmd</TD
-><TD
->BOZO_Exec - Execute a shell command at the server.</TD
-></TR
-><TR
-><TD
->AFS_BOS_DoExec</TD
-><TD
->P C</TD
-><TD
->ECode exec</TD
-><TD
->The <SPAN
-CLASS="bold"
-><B
-CLASS="emphasis"
->bosserver</B
-></SPAN
-> process was restarted.</TD
-></TR
-><TR
-><TD
->AFS_BOS_StpProc</TD
-><TD
->P C</TD
-><TD
->ECode cmd</TD
-><TD
->An RPC to stop any process controlled by the BOS Server.</TD
-></TR
-></TBODY
-></TABLE
-></DIV
-></DIV
-><DIV
-CLASS="sect1"
-><H1
-CLASS="sect1"
-><A
-NAME="HDRWQ645"
->Volume Location Server Events</A
-></H1
-><DIV
-CLASS="informaltable"
-><A
-NAME="AEN36964"
-></A
-><TABLE
-BORDER="1"
-CLASS="CALSTABLE"
-><COL
-WIDTH="28*"><COL
-WIDTH="10*"><COL
-WIDTH="25*"><COL
-WIDTH="38*"><THEAD
-><TR
-><TH
->Event</TH
-><TH
->Class</TH
-><TH
->Parameters</TH
-><TH
->Description</TH
-></TR
-></THEAD
-><TBODY
-><TR
-><TD
->AFS_VL_CreEnt</TD
-><TD
->P M</TD
-><TD
->ECode AFSName HostID name</TD
-><TD
->VL_CreateEntry - Create a VLDB entry.</TD
-></TR
-><TR
-><TD
->AFS_VL_DelEnt</TD
-><TD
->P M</TD
-><TD
->ECode AFSName HostID volID</TD
-><TD
->VL_DeleteEntry - Delete a VLDB entry.</TD
-></TR
-><TR
-><TD
->AFS_VL_GetNVlID</TD
-><TD
->None</TD
-><TD
->ECode AFSName HostID</TD
-><TD
->VL_GetNewVolumeId - Generate a new volume ID.</TD
-></TR
-><TR
-><TD
->AFS_VL_RepEnt</TD
-><TD
->P M</TD
-><TD
->ECode AFSName HostID volID</TD
-><TD
->VL_ReplaceEntry - Replace entire contents of VLDB entry.</TD
-></TR
-><TR
-><TD
->AFS_VL_UpdEnt</TD
-><TD
->P M</TD
-><TD
->ECode AFSName HostID volID</TD
-><TD
->VL_UpdateEntry - Update contents of VLDB entry.</TD
-></TR
-><TR
-><TD
->AFS_VL_SetLck</TD
-><TD
->P</TD
-><TD
->ECode AFSName HostID volID</TD
-><TD
->VL_SetLock - Lock VLDB entry.</TD
-></TR
-><TR
-><TD
->AFS_VL_RelLck</TD
-><TD
->P</TD
-><TD
->ECode AFSName HostID volID</TD
-><TD
->VL_ReleaseLock - Unlock VLDB entry.</TD
-></TR
-></TBODY
-></TABLE
-></DIV
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="a34149.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="book1.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="i37012.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->The afsmonitor Program Statistics</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Index</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
<!ENTITY appendixB SYSTEM "auagd023.xml">
<!ENTITY appendixC SYSTEM "auagd024.xml">
<!ENTITY appendixD SYSTEM "auagd025.xml">
-<!ENTITY index SYSTEM "auagd026.xml">
]>
-<book label="Version 3.6" fpi="Document Number GC09-4563-00">
+<book label="Version M.m">
<bookinfo>
- <title>AFS Administration Guide</title>
+ <title>OpenAFS Administration Guide</title>
- <subtitle>Version 3.6</subtitle>
-
- <pubsnumber>Document Number GC09-4563-00</pubsnumber>
+ <subtitle>Version M.m</subtitle>
<copyright>
<year>2000</year>
<revhistory>
<revision>
+ <revnumber>M.m</revnumber>
+
+ <date>May 2008</date>
+
+ <revremark>First OpenAFS Edition</revremark>
+
+ </revision>
+
+ <revision>
<revnumber>3.6</revnumber>
<date>April 2000</date>
- <revremark>First Edition</revremark>
+ <revremark>First IBM Edition, Document Number GC09-4563-00</revremark>
+
+ <pubsnumber>Document Number GC09-4563-00</pubsnumber>
</revision>
</revhistory>
<abstract>
<para>This edition applies to: <simplelist>
- <member>IBM AFS for AIX, Version 3.6</member>
- <member>IBM AFS for Digital Unix, Version 3.6</member>
- <member>IBM AFS for HP-UX, Version 3.6</member>
- <member>IBM AFS for Linux, Version 3.6</member>
- <member>IBM AFS for SGI IRIX, Version 3.6</member>
- <member>IBM AFS for Solaris, Version 3.6</member>
+ <member>OpenAFS for AIX, Version M.m</member>
+ <member>OpenAFS for Digital Unix, Version M.m</member>
+ <member>OpenAFS for HP-UX, Version M.m</member>
+ <member>OpenAFS for Linux, Version M.m</member>
+ <member>OpenAFS for SGI IRIX, Version M.m</member>
+ <member>OpenAFS for Solaris, Version M.m</member>
</simplelist></para>
<para>and to all subsequent releases and modifications until otherwise
&appendixB;
&appendixC;
&appendixD;
- &index;
+ <index>Name Index</index>
</book>
with UNIX(R) administration, but no previous knowledge of AFS.</para>
<para>This document describes AFS commands in the context of specific tasks. Thus, it does not describe all commands in detail.
- Refer to the IBM AFS Administration Reference for detailed command descriptions.</para>
+ Refer to the OpenAFS Administration Reference for detailed command descriptions.</para>
</sect1>
<sect1 id="HDRWQ2">
</listitem>
<listitem>
- <para>If necessary, refer to the IBM AFS Administration Reference for more detailed information about the commands.</para>
+ <para>If necessary, refer to the OpenAFS Administration Reference for more detailed information about the commands.</para>
</listitem>
</orderedlist>
</para>
<variablelist>
<varlistentry>
- <term>IBM AFS Administration Reference</term>
+ <term>OpenAFS Administration Reference</term>
<listitem>
<para>This reference manual details the syntax and effect of each AFS command. It is intended for the experienced AFS
- administrator, programmer, or user. The IBM AFS Administration Reference lists AFS files and commands in alphabetical
+ administrator, programmer, or user. The OpenAFS Administration Reference lists AFS files and commands in alphabetical
order. The reference page for each command specifies its syntax, including the acceptable aliases and abbreviations. It
then describes the command's function, arguments, and output if any. Examples and a list of related commands are provided,
as are warnings where appropriate.</para>
- <para>This manual complements the IBM AFS Administration Guide: it does not include procedural information, but describes
- commands in more detail than the IBM AFS Administration Guide.</para>
+ <para>This manual complements the OpenAFS Administration Guide: it does not include procedural information, but describes
+ commands in more detail than the OpenAFS Administration Guide.</para>
</listitem>
</varlistentry>
<varlistentry>
- <term>IBM AFS Quick Beginnings</term>
+ <term>OpenAFS Quick Beginnings</term>
<listitem>
<para>This guide provides instructions for installing AFS server and client machines. It is assumed that the installer is
</varlistentry>
<varlistentry>
- <term>IBM AFS Release Notes</term>
+ <term>OpenAFS Release Notes</term>
<listitem>
<para>This document provides information specific to each release of AFS, such as a list of new features and commands, a
</varlistentry>
<varlistentry>
- <term>IBM AFS User Guide</term>
+ <term>OpenAFS User Guide</term>
<listitem>
<para>This guide presents the basic concepts and procedures necessary for using AFS effectively. It assumes that the
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="HDRWQ5">
- <title>An Overview of AFS Administration</title>
+ <title>An Overview of OpenAFS Administration</title>
<para>This chapter provides a broad overview of the concepts and organization of AFS. It is strongly recommended that anyone
involved in administering an AFS cell read this chapter before beginning to issue commands.</para>
<para>Keeping clocks synchronized is particularly important to the correct operation of AFS's distributed database technology,
which coordinates the copies of the Authentication, Backup, Protection, and Volume Location Databases; see <link
- linkend="HDRWQ52">Replicating the AFS Administrative Databases</link>. Client machines also refer to these clocks for the
+ linkend="HDRWQ52">Replicating the OpenAFS Administrative Databases</link>. Client machines also refer to these clocks for the
correct time; therefore, it is less confusing if all file server machines have the same time. For more technical detail about
the NTPD, see <link linkend="HDRWQ151">The runntp Process</link>.</para>
</sect2>
<para>This chapter discusses many of the issues to consider when configuring and administering a cell, and directs you to detailed
related information available elsewhere in this guide. It is assumed you are already familiar with the material in <link
- linkend="HDRWQ5">An Overview of AFS Administration</link>.</para>
+ linkend="HDRWQ5">An Overview of OpenAFS Administration</link>.</para>
<para>It is best to read this chapter before installing your cell's first file server machine or performing any other
administrative task.</para>
<para>AFS provides a modified login utility for each system type that accomplishes both local login and AFS
authentication in one step, based on a single password. If you choose not to use the AFS-modified login utility, your
- users must login and authenticate in separate steps, as detailed in the <emphasis>IBM AFS User Guide</emphasis>.</para>
+ users must login and authenticate in separate steps, as detailed in the <emphasis>OpenAFS User Guide</emphasis>.</para>
</listitem>
<listitem>
UNIX Remote Services in the AFS Environment</link>.</para>
<para>The AFS distribution for some system types possibly does not include a modified <emphasis
- role="bold">rlogind</emphasis> program. See the <emphasis>IBM AFS Release Notes</emphasis>.</para>
+ role="bold">rlogind</emphasis> program. See the <emphasis>OpenAFS Release Notes</emphasis>.</para>
<indexterm>
<primary>rsh command</primary>
role="bold">lost+found</emphasis> directory on the partition.</para>
<para>Instead, use the version of the <emphasis role="bold">fsck</emphasis> program that is included in the AFS distribution.
- The <emphasis>IBM AFS Quick Beginnings</emphasis> explains how to replace the vendor-supplied <emphasis
+ The <emphasis>OpenAFS Quick Beginnings</emphasis> explains how to replace the vendor-supplied <emphasis
role="bold">fsck</emphasis> program with the AFS version as you install each server machine.</para>
<para>The AFS version functions like the standard <emphasis role="bold">fsck</emphasis> program on data stored on both UFS and
<para>For file server machines, the two files that record the cell name are the <emphasis
role="bold">/usr/afs/etc/ThisCell</emphasis> and <emphasis role="bold">/usr/afs/etc/CellServDB</emphasis> files. As described
- more explicitly in the <emphasis>IBM AFS Quick Beginnings</emphasis>, you set the cell name in both by issuing the <emphasis
+ more explicitly in the <emphasis>OpenAFS Quick Beginnings</emphasis>, you set the cell name in both by issuing the <emphasis
role="bold">bos setcellname</emphasis> command on the first file server machine you install in your cell. It is not usually
necessary to issue the command again. If you run the United States edition of AFS and use the Update Server, it distributes
its copy of the <emphasis role="bold">ThisCell</emphasis> and <emphasis role="bold">CellServDB</emphasis> files to additional
- server machines that you install. If you use the international edition of AFS, the <emphasis>IBM AFS Quick
+ server machines that you install. If you use the international edition of AFS, the <emphasis>OpenAFS Quick
Beginnings</emphasis> explains how to copy the files manually.</para>
<para>For client machines, the two files that record the cell name are the <emphasis
See <link linkend="HDRWQ406">Maintaining Knowledge of Database Server Machines</link> for details.</para>
<para>Change the cell name in these files only when you want to transfer the machine to a different cell (it can only belong
- to one cell at a time). If the machine is a file server, follow the complete set of instructions in the <emphasis>IBM AFS
+ to one cell at a time). If the machine is a file server, follow the complete set of instructions in the <emphasis>OpenAFS
Quick Beginnings</emphasis> for configuring a new cell. If the machine is a client, all you need to do is change the files
appropriately and reboot the machine. The next section explains further the negative consequences of changing the name of an
existing cell.</para>
<para>A separate directory for storing the server and client binaries for each system type you use in the cell.
Configuration is simplest if you use the system type names assigned in the AFS distribution, particularly if you wish
to use the <emphasis role="bold">@sys</emphasis> variable in pathnames (see <link linkend="HDRWQ56">Using the @sys
- Variable in Pathnames</link>). The <emphasis>IBM AFS Release Notes</emphasis> lists the conventional name for each
+ Variable in Pathnames</link>). The <emphasis>OpenAFS Release Notes</emphasis> lists the conventional name for each
supported system type.</para>
<para>Within each such directory, create directories named <emphasis role="bold">bin</emphasis>, <emphasis
</listitem>
</itemizedlist></para>
- <para>The <emphasis>IBM AFS Quick Beginnings</emphasis> explains how to configure your cell's first file server machine to
- assume all four roles. The <emphasis>IBM AFS Quick Beginnings</emphasis> chapter on installing additional server machines also
+ <para>The <emphasis>OpenAFS Quick Beginnings</emphasis> explains how to configure your cell's first file server machine to
+ assume all four roles. The <emphasis>OpenAFS Quick Beginnings</emphasis> chapter on installing additional server machines also
explains how to configure them to perform one or more roles.</para>
<indexterm>
</indexterm>
<sect2 id="HDRWQ52">
- <title>Replicating the AFS Administrative Databases</title>
+ <title>Replicating the OpenAFS Administrative Databases</title>
<para>The AFS administrative databases are housed on database server machines and store information that is crucial for
correct cell functioning. Both server processes and Cache Managers access the information frequently: <itemizedlist>
<para>Unlike replicated volumes, however, replicated databases do change frequently. Consistent system performance demands
that all copies of the database always be identical, so it is not acceptable to record changes in only some of them. To
synchronize the copies of a database, the database server processes use AFS's distributed database technology, Ubik. See <link
- linkend="HDRWQ102">Replicating the AFS Administrative Databases</link>.</para>
+ linkend="HDRWQ102">Replicating the OpenAFS Administrative Databases</link>.</para>
<para>If your cell has only one file server machine, it must also serve as a database server machine. If you cell has two file
server machines, it is not always advantageous to run both as database server machines. If a server, process, or network
first <emphasis role="bold">r</emphasis> (<emphasis role="bold">read</emphasis>) mode bit turned on (for example, the
<emphasis role="bold">/usr/afs/etc/KeyFile</emphasis> file, which lists the AFS server encryption keys). Each time the BOS
Server starts, it checks that the mode bits on certain files and directories match the expected values. For a list, see the
- <emphasis>IBM AFS Quick Beginnings</emphasis> section about protecting sensitive AFS directories, or the discussion of the
+ <emphasis>OpenAFS Quick Beginnings</emphasis> section about protecting sensitive AFS directories, or the discussion of the
output from the <emphasis role="bold">bos status</emphasis> command in <link linkend="HDRWQ159">To display the status of
server processes and their BosConfig entries</link>.</para>
directory, and so on through the <emphasis role="bold">/vicepz</emphasis> directory. The names then continue with <emphasis
role="bold">/vicepaa</emphasis> through <emphasis role="bold">/vicepaz</emphasis>, <emphasis role="bold">/vicepba</emphasis>
through <emphasis role="bold">/vicepbz</emphasis>, and so on, up to the maximum supported number of server partitions, which
- is specified in the IBM AFS Release Notes.</para>
+ is specified in the OpenAFS Release Notes.</para>
<para>Each <emphasis role="bold">/vicep</emphasis>x directory must correspond to an entire partition or logical volume, and
must be a subdirectory of the root directory (/). It is not acceptable to configure part of (for example) the <emphasis
Solaris 7 converts it to <emphasis role="bold">/afs/abc.com/sun4x_57</emphasis>.</para>
<para>If you want to use the @sys variable, it is simplest to use the conventional AFS system type names as specified in the
- IBM AFS Release Notes. The Cache Manager records the local machine's system type name in kernel memory during initialization.
+ OpenAFS Release Notes. The Cache Manager records the local machine's system type name in kernel memory during initialization.
If you do not use the conventional names, you must use the <emphasis role="bold">fs sysname</emphasis> command to change the
value in kernel memory from its default just after Cache Manager initialization, on every client machine of the relevant
system type. The <emphasis role="bold">fs sysname</emphasis> command also displays the current value; see <link
<note>
<para>The AFS-modified libraries do not necessarily support all features available in an operating system's proprietary login
utility. In some cases, it is not possible to support a utility at all. For more information about the supported utilities in
- each AFS version, see the IBM AFS Release Notes.</para>
+ each AFS version, see the OpenAFS Release Notes.</para>
</note>
<indexterm>
<para>Systems that use a Pluggable Authentication Module (PAM) for login and AFS authentication do not necessarily consult the
local password file at all, in which case they do not use the password field to control authentication and login attempts.
Instead, instructions in the PAM configuration file (on many system types, <emphasis role="bold">/etc/pam.conf</emphasis>)
- fill the same function. See the instructions in the IBM AFS Quick Beginnings for installing AFS-modified login
+ fill the same function. See the instructions in the OpenAFS Quick Beginnings for installing AFS-modified login
utilities.</para>
<indexterm>
<title>Using Two-Step Login and Authentication</title>
<para>In cells that do not use an AFS-modified login utility, users must issue separate commands to login and authenticate, as
- detailed in the IBM AFS User Guide: <orderedlist>
+ detailed in the OpenAFS User Guide: <orderedlist>
<listitem>
<para>They use the standard <emphasis role="bold">login</emphasis> program to login to the local file system, providing
the password listed in the local password file (the <emphasis role="bold">/etc/passwd</emphasis> file or
logged in to the local file system. To authenticate as a different identity, use the <emphasis
role="bold">-principal</emphasis> argument. To obtain a token for a foreign cell, use the <emphasis
role="bold">-cell</emphasis> argument (it can be combined with the <emphasis role="bold">-principal</emphasis> argument). See
- the IBM AFS User Guide and the entry for the <emphasis role="bold">klog</emphasis> command in the IBM AFS Administration
+ the OpenAFS User Guide and the entry for the <emphasis role="bold">klog</emphasis> command in the OpenAFS Administration
Reference.</para>
<para>To discard either all tokens or the token for a particular cell, issue the <emphasis role="bold">unlog</emphasis>
- command. The command affects only the tokens associated with the current command shell. See the IBM AFS User Guideand the
- entry for the <emphasis role="bold">unlog</emphasis> command in the IBM AFS Administration Reference.</para>
+ command. The command affects only the tokens associated with the current command shell. See the OpenAFS User Guideand the
+ entry for the <emphasis role="bold">unlog</emphasis> command in the OpenAFS Administration Reference.</para>
<para>To display the tokens associated with the current command shell, issue the <emphasis role="bold">tokens</emphasis>
command. The following examples illustrate its output in various situations.</para>
<note>
<para>An AFS-modified login utility always grants a token with a lifetime calculated from the previously described three
values. When issuing the <emphasis role="bold">klog</emphasis> command, a user can request a lifetime shorter than the
- default by using the <emphasis role="bold">-lifetime</emphasis> argument. For further information, see the IBM AFS User
- Guide and the <emphasis role="bold">klog</emphasis> reference page in the IBM AFS Administration Reference.</para>
+ default by using the <emphasis role="bold">-lifetime</emphasis> argument. For further information, see the OpenAFS User
+ Guide and the <emphasis role="bold">klog</emphasis> reference page in the OpenAFS Administration Reference.</para>
</note>
</sect2>
setpassword</emphasis> commands pass the proposed password to a program or script called <emphasis
role="bold">kpwvalid</emphasis>, if it exists. The <emphasis role="bold">kpwvalid</emphasis> performs quality checks and
returns a code to indicate whether the password is acceptable. You can create your own program or modified the sample program
- included in the AFS distribution. See the <emphasis role="bold">kpwvalid</emphasis> reference page in the IBM AFS
+ included in the AFS distribution. See the <emphasis role="bold">kpwvalid</emphasis> reference page in the OpenAFS
Administration Reference.</para>
<para>There are several types of quality checks that can improve password quality. <itemizedlist>
<para>Use either the Kerberos version or the standard command throughout the cell; do not mix the two versions. AFS Product
Support can provide instructions on installing the Kerberos version of these four commands. For information on the differences
- between the two versions of these commands, see the IBM AFS Administration Reference.</para>
+ between the two versions of these commands, see the OpenAFS Administration Reference.</para>
</sect2>
</sect1>
a user accidentally removes or changes data, the user can restore it from the backup volume, rather than having to ask you to
restore it.</para>
- <para>The IBM AFS User Guide does not mention backup volumes, so regular users do not know about them if you decide not to use
+ <para>The OpenAFS User Guide does not mention backup volumes, so regular users do not know about them if you decide not to use
them. This implies that if you <emphasis role="bold">do</emphasis> make backup versions of user volumes, you need to tell your
users about how the backup works and where you have mounted it.</para>
<para>The conventional installation location for the modified remote commands are the <emphasis
role="bold">/usr/afsws/bin</emphasis> and <emphasis role="bold">/usr/afsws/etc</emphasis> directories. To learn more about
- commands' functionality, see their reference pages in the IBM AFS Administration Reference.</para>
+ commands' functionality, see their reference pages in the OpenAFS Administration Reference.</para>
</sect1>
<sect1 id="HDRWQ79">
</listitem>
</itemizedlist></para>
- <para>To learn how to install and configure a new server machine, see the <emphasis>IBM AFS Quick Beginnings</emphasis>.</para>
+ <para>To learn how to install and configure a new server machine, see the <emphasis>OpenAFS Quick Beginnings</emphasis>.</para>
<para>To learn how to administer the server processes themselves, see <link linkend="HDRWQ142">Monitoring and Controlling Server
Processes</link>.</para>
<para>An ASCII file that consists of a single line defining the complete Internet domain-style name of the cell (such
as <computeroutput>abc.com</computeroutput>). You create this file with the <emphasis role="bold">bos
setcellname</emphasis> command during the installation of your cell's first file server machine, as instructed in the
- <emphasis>IBM AFS Quick Beginnings</emphasis>.</para>
+ <emphasis>OpenAFS Quick Beginnings</emphasis>.</para>
<para>Note that changing this file is only one step in changing your cell's name. For discussion, see <link
linkend="HDRWQ34">Choosing a Cell Name</link>.</para>
restarts processes for maintenance purposes.</para>
<para>As you create server processes during a file server machine's installation, their entries are defined in this
- file automatically. The <emphasis>IBM AFS Quick Beginnings</emphasis> outlines the <emphasis
+ file automatically. The <emphasis>OpenAFS Quick Beginnings</emphasis> outlines the <emphasis
role="bold">bos</emphasis> commands to use. For a more complete description of the file, and instructions for
controlling process status by editing the file with commands from the <emphasis role="bold">bos</emphasis> suite, see
<link linkend="HDRWQ142">Monitoring and Controlling Server Processes</link>.</para>
<para>If a cell runs more than one database server machine, each database server process keeps its own copy of its database on
its machine's hard disk. However, it is important that all the copies of a given database are the same. To synchronize them,
the database server processes call on AFS's distributed database technology, Ubik, as described in <link
- linkend="HDRWQ102">Replicating the AFS Administrative Databases</link>.</para>
+ linkend="HDRWQ102">Replicating the OpenAFS Administrative Databases</link>.</para>
<para>The files listed here appear in this directory only on database server machines. On non-database server machines, this
directory is empty. <variablelist>
name. The directory name is of the form <emphasis role="bold">/vicep</emphasis>index, where each index is one or two lowercase
letters. By convention, the first AFS partition on a machine is mounted at <emphasis role="bold">/vicepa</emphasis>, the
second at <emphasis role="bold">/vicepb</emphasis>, and so on. If there are more than 26 partitions, continue with <emphasis
- role="bold">/vicepaa</emphasis>, <emphasis role="bold">/vicepab</emphasis> and so on. The <emphasis>IBM AFS Release
+ role="bold">/vicepaa</emphasis>, <emphasis role="bold">/vicepab</emphasis> and so on. The <emphasis>OpenAFS Release
Notes</emphasis> specifies the number of supported partitions per server machine.</para>
<para>Do not store non-AFS files on AFS partitions. The File Server and Volume Server expect to have available all of the
</itemizedlist></para>
<para>If a cell has a single server machine, it assumes the simple file server and database server roles. The instructions in
- the <emphasis>IBM AFS Quick Beginnings</emphasis> also have you configure it as the system control machine and binary
+ the <emphasis>OpenAFS Quick Beginnings</emphasis> also have you configure it as the system control machine and binary
distribution machine for its system type, but it does not actually perform those functions until you install another server
machine.</para>
<para>Unlike replicated volumes, however, replicated databases do change frequently. Consistent system performance demands
that all copies of the database always be identical, so it is not possible to record changes in only some of them. To
synchronize the copies of a database, the database server processes use AFS's distributed database technology, Ubik. See <link
- linkend="HDRWQ102">Replicating the AFS Administrative Databases</link>.</para>
+ linkend="HDRWQ102">Replicating the OpenAFS Administrative Databases</link>.</para>
<para>It is critical that the AFS server processes on every server machine in a cell know which machines are the database
server machines. The database server processes in particular must maintain constant contact with their peers in order to
<para>For a list of the configuration files stored in the <emphasis role="bold">/usr/afs/etc</emphasis> directory, see <link
linkend="HDRWQ85">Common Configuration Files in the /usr/afs/etc Directory</link>.</para>
- <para>The <emphasis>IBM AFS Quick Beginnings</emphasis> configures a cell's first server machine as the system control
+ <para>The <emphasis>OpenAFS Quick Beginnings</emphasis> configures a cell's first server machine as the system control
machine. If you wish, you can reassign the role to a different machine that you install later, but you must then change the
client portion of the Update Server (<emphasis role="bold">upclientetc</emphasis>) process running on all other server
machines to refer to the new system control machine.</para>
Command 1 is '/usr/afs/bin/upserver'
</programlisting>
- <para>If you are using the default configuration recommended in the <emphasis>IBM AFS Quick Beginnings</emphasis>, the
+ <para>If you are using the default configuration recommended in the <emphasis>OpenAFS Quick Beginnings</emphasis>, the
system control machine is also the binary distribution machine for its system type, and a single <emphasis
role="bold">upserver</emphasis> process distributes both kinds of updates. In that case, the output includes the following
messages:</para>
<sect1 id="HDRWQ101">
<title>Administering Database Server Machines</title>
- <para>This section explains how to administer database server machines. For installation instructions, see the <emphasis>IBM AFS
+ <para>This section explains how to administer database server machines. For installation instructions, see the <emphasis>OpenAFS
Quick Beginnings</emphasis>.</para>
<indexterm>
</indexterm>
<sect2 id="HDRWQ102">
- <title>Replicating the AFS Administrative Databases</title>
+ <title>Replicating the OpenAFS Administrative Databases</title>
<para>There are several benefits to replicating the AFS administrative databases (the Authentication, Backup, Protection, and
- Volume Location Databases), as discussed in <link linkend="HDRWQ52">Replicating the AFS Administrative Databases</link>. For
+ Volume Location Databases), as discussed in <link linkend="HDRWQ52">Replicating the OpenAFS Administrative Databases</link>. For
correct cell functioning, the copies of each database must be identical at all times. To keep the databases synchronized, AFS
uses library of utilities called <emphasis>Ubik</emphasis>. Each database server process runs an associated lightweight Ubik
process, and client-side programs call Ubik's client-side subroutines when they submit requests to read and change the
<para>If you run the United States version of AFS and use the Update Server, it is simplest to maintain the <emphasis
role="bold">/usr/afs/etc/CellServDB</emphasis> file on the system control machine, which distributes its copy to all
- other server machines. The <emphasis>IBM AFS Quick Beginnings</emphasis> explains how to configure the Update Server.
+ other server machines. The <emphasis>OpenAFS Quick Beginnings</emphasis> explains how to configure the Update Server.
If you run the international version of AFS, you must update the file on each machine individually.</para>
<para>The only reason to alter the file is when configuring or decommissioning a database server machine. Use the
<link linkend="HDRWQ118">Maintaining the Server CellServDB File</link>. The instructions in <link
linkend="HDRWQ142">Monitoring and Controlling Server Processes</link> for stopping and starting processes remind you
to alter the <emphasis role="bold">CellServDB</emphasis> file when appropriate, as do the instructions in the
- <emphasis>IBM AFS Quick Beginnings</emphasis> for installing or decommissioning a database server machine.</para>
+ <emphasis>OpenAFS Quick Beginnings</emphasis> for installing or decommissioning a database server machine.</para>
<para>(Client processes and the server processes that do not maintain databases also rely on correct information in
the <emphasis role="bold">CellServDB</emphasis> file for proper operation, but their use of the information does not
<listitem>
<para>Keep the clocks synchronized on all machines in the cell, especially the database server machines.</para>
- <para>In the conventional configuration specified in the <emphasis>IBM AFS Quick Beginnings</emphasis>, you run the
+ <para>In the conventional configuration specified in the <emphasis>OpenAFS Quick Beginnings</emphasis>, you run the
<emphasis role="bold">runntp</emphasis> process to supervise the local Network Time Protocol Daemon (NTPD) on every
AFS server machine. The NTPD on the system control machine synchronizes its clock with a reliable source outside the
cell and broadcasts the time to the NTPDs on the other server machines. You can choose to run a different time
restrictions. The most basic is that it halts if it finds that an existing dump record in the database has the same dump
ID number as a dump on the tape it is scanning. If you want to continue with the scanning operation, you must locate and
remove the existing record from the database. For further discussion, see the <emphasis role="bold">backup
- scantape</emphasis> command's reference page in the <emphasis>IBM AFS Administration Reference</emphasis>.</para>
+ scantape</emphasis> command's reference page in the <emphasis>OpenAFS Administration Reference</emphasis>.</para>
</listitem>
</itemizedlist></para>
server machine of each system type as the <emphasis>binary distribution machine</emphasis> by running the server portion of the
Update Server (<emphasis role="bold">upserver</emphasis> process) on it. All other server machines of that system type run the
client portion of the Update Server (<emphasis role="bold">upclientbin</emphasis> process) to retrieve updated software from the
- binary distribution machine. The <emphasis>IBM AFS Quick Beginnings</emphasis> explains how to install the appropriate
+ binary distribution machine. The <emphasis>OpenAFS Quick Beginnings</emphasis> explains how to install the appropriate
processes. For more on binary distribution machines, see <link linkend="HDRWQ93">Binary Distribution Machines</link>.</para>
<para>When you use the Update Server, you install new binaries on binary distribution machines only. If you install binaries
<para>It is best to store AFS binaries in the <emphasis role="bold">/usr/afs/bin</emphasis> directory, because that is the
only directory the BOS Server automatically checks for new binaries. You can, however, use the <emphasis role="bold">bos
install</emphasis> command's <emphasis role="bold">-dir</emphasis> argument to install non-AFS binaries into other directories
- on a server machine's local disk. See the command's reference page in the <emphasis>IBM AFS Administration
+ on a server machine's local disk. See the command's reference page in the <emphasis>OpenAFS Administration
Reference</emphasis> for further information.</para>
<indexterm>
from its binary distribution machine before restarting a server process to use the new binaries.</para>
<para>To check dates on binaries in a directory other than <emphasis role="bold">/usr/afs/bin</emphasis>, add the <emphasis
- role="bold">-dir</emphasis> argument. See the <emphasis>IBM AFS Administration Reference</emphasis>.</para>
+ role="bold">-dir</emphasis> argument. See the <emphasis>OpenAFS Administration Reference</emphasis>.</para>
<indexterm>
<primary>bos commands</primary>
@(#)Base configuration afsversion build_level
</programlisting>
- <para>For example, the following string indicates the binary is from AFS 3.6 build 3.0:</para>
+ <para>For example, the following string indicates the binary is from AFS M.m build 3.0:</para>
<programlisting>
- @(#)Base configuration afs3.6 3.0
+ @(#)Base configuration afsM.m 3.0
</programlisting>
</listitem>
</orderedlist>
constant contact with their peers in order to keep their copies of the replicated administrative databases
synchronized.</para>
- <para>As detailed in <link linkend="HDRWQ102">Replicating the AFS Administrative Databases</link>, the database server
+ <para>As detailed in <link linkend="HDRWQ102">Replicating the OpenAFS Administrative Databases</link>, the database server
processes use the Ubik utility to synchronize the information in the databases they maintain. The Ubik coordinator at the
synchronization site for each database maintains the single read/write copy of the database and distributes changes to the
secondary sites as necessary. It must maintain contact with a majority of the secondary sites to remain the coordinator,
<para>To avoid the negative consequences of incorrect information in the <emphasis
role="bold">/usr/afs/etc/CellServDB</emphasis> file, you must update it on all of your cell's server machines every time you
- add or remove a database server machine. The <emphasis>IBM AFS Quick Beginnings</emphasis> provides complete instructions for
+ add or remove a database server machine. The <emphasis>OpenAFS Quick Beginnings</emphasis> provides complete instructions for
installing or removing a database server machine and for updating the <emphasis role="bold">CellServDB</emphasis> file in that
context. This section explains how to distribute the file to your server machines and how to make other cells aware of the
changes if you participate in the AFS global name space.</para>
edition of AFS, instead change the file on each server machine individually. For further discussion of the system control
machine and why international cells must not use it for files in the <emphasis role="bold">/usr/afs/etc</emphasis> directory,
see <link linkend="HDRWQ94">The System Control Machine</link>. For instructions on configuring the Update Server when using
- the United States version of AFS, see the <emphasis>IBM AFS Quick Beginnings</emphasis>.</para>
+ the United States version of AFS, see the <emphasis>OpenAFS Quick Beginnings</emphasis>.</para>
<para>To avoid formatting errors that can cause errors, always use the <emphasis role="bold">bos addhost</emphasis> and
<emphasis role="bold">bos removehost</emphasis> commands, rather than editing the file directly. You must also restart the
<para>Provide the <emphasis role="bold">-noauth</emphasis> flag which is available on many of the commands in the suites. To
verify that a command accepts the flag, issue the <emphasis role="bold">help</emphasis> command in its suite, or consult the
- command's reference page in the <emphasis>IBM AFS Administration Reference</emphasis> (the reference page also specifies the
+ command's reference page in the <emphasis>OpenAFS Administration Reference</emphasis> (the reference page also specifies the
shortest acceptable abbreviation for the flag on each command). The suites' <emphasis role="bold">apropos</emphasis> and
<emphasis role="bold">help</emphasis> commands do not themselves accept the flag.</para>
<para>AFS makes it very easy to add storage space to your cell, just by adding disks to existing file server machines. This
section explains how to install or remove a disk used to store AFS volumes. (Another way to add storage space is to install
- additional server machines, as instructed in the <emphasis>IBM AFS Quick Beginnings</emphasis>.)</para>
+ additional server machines, as instructed in the <emphasis>OpenAFS Quick Beginnings</emphasis>.)</para>
<para>Both adding and removing a disk cause at least a brief file system outage, because you must restart the <emphasis
role="bold">fs</emphasis> process to have it recognize the new set of server partitions. Some operating systems require that you
<para>These instructions assume that the machine's AFS initialization file includes the following command to restart the BOS
Server after each reboot. The BOS Server starts the other AFS server processes listed in the local <emphasis
role="bold">/usr/afs/local/BosConfig</emphasis> file. For information on the <emphasis role="bold">bosserver</emphasis>
- command's optional arguments, see its reference page in the <emphasis>IBM AFS Administration Reference</emphasis>.</para>
+ command's optional arguments, see its reference page in the <emphasis>OpenAFS Administration Reference</emphasis>.</para>
<programlisting>
/usr/afs/bin/bosserver &
files also determine which interfaces the Ubik database synchronization library uses when communicating with the database server
processes running on other database server machines.</para>
- <para>There is a maximum number of IP addresses in each server entry, as documented in the <emphasis>IBM AFS Release
+ <para>There is a maximum number of IP addresses in each server entry, as documented in the <emphasis>OpenAFS Release
Notes</emphasis>. If a multihomed file server machine has more interfaces than the maximum, AFS simply ignores the excess ones.
It is probably appropriate for such machines to use the <emphasis role="bold">NetInfo</emphasis> and <emphasis
role="bold">NetRestrict</emphasis> files to control which interfaces are registered.</para>
<para>Except in this type of rare error case, the only appropriate use of the <emphasis role="bold">vos changeaddr</emphasis>
command is to remove a VLDB server entry completely when you remove a file server machine from service. The VLDB can accommodate
- a maximum number of server entries, as specified in the <emphasis>IBM AFS Release Notes</emphasis>. Removing obsolete entries
+ a maximum number of server entries, as specified in the <emphasis>OpenAFS Release Notes</emphasis>. Removing obsolete entries
makes it possible to allocate server entries for new file server machines as required. See the instructions that follow.</para>
<para>Do not use the <emphasis role="bold">vos changeaddr</emphasis> command to change the list of interfaces registered in a
<para>The output from the <emphasis role="bold">bos status</emphasis> command refers to a process by the name assigned
when the <emphasis role="bold">bos create</emphasis> command creates its entry in the <emphasis
role="bold">/usr/afs/local/BosConfig</emphasis> file. The name can differ from machine to machine, but it is easiest to
- maintain the cell if you assign the same name on all machines. The <emphasis>IBM AFS Quick Beginnings</emphasis> and the
+ maintain the cell if you assign the same name on all machines. The <emphasis>OpenAFS Quick Beginnings</emphasis> and the
reference page for the <emphasis role="bold">bos create</emphasis> command list the conventional names. Examples are
<emphasis role="bold">bosserver</emphasis>, <emphasis role="bold">kaserver</emphasis>, and <emphasis
role="bold">vlserver</emphasis>.</para>
</indexterm>
<para>As a system administrator, you do not contact the NTPD directly once you have installed it according to the instructions
- in the <emphasis>IBM AFS Quick Beginnings</emphasis>.</para>
+ in the <emphasis>OpenAFS Quick Beginnings</emphasis>.</para>
</sect2>
<sect2 id="HDRWQ152">
<para>A process's entry in the <emphasis role="bold">BosConfig</emphasis> file includes the following information:
<itemizedlist>
<listitem>
- <para>The process's name. The recommended conventional names are defined in both the <emphasis>IBM AFS Quick
+ <para>The process's name. The recommended conventional names are defined in both the <emphasis>OpenAFS Quick
Beginnings</emphasis> and <link linkend="HDRWQ161">Creating and Removing Processes</link>. The name of a simple process
usually matches the name of its binary file (for example, <emphasis role="bold">ptserver</emphasis> for the Protection
Server).</para>
</indexterm>
<para>When you start or stop a database server process (Authentication Server, Backup Server, Protection Server, or Volume
- Location Server) for more than a short time, you must follow the instructions in the <emphasis>IBM AFS Quick
+ Location Server) for more than a short time, you must follow the instructions in the <emphasis>OpenAFS Quick
Beginnings</emphasis> for installing or removing a database server machine. Here is a summary of the tasks you must perform to
preserve correct AFS functioning. <itemizedlist>
<listitem>
</programlisting>
<para>The expected protections for the directories and files in the <emphasis role="bold">/usr/afs</emphasis> directory are as
- follows. A question mark indicates that the BOS Server does not check the mode bit. See the <emphasis>IBM AFS Quick
+ follows. A question mark indicates that the BOS Server does not check the mode bit. See the <emphasis>OpenAFS Quick
Beginnings</emphasis> for more information about setting the protections on these files and directories.</para>
<informaltable frame="none">
<note>
<para>If you are starting or stopping a database server process in the manner described in this section, follow the complete
- instructions in the <emphasis>IBM AFS Quick Beginnings</emphasis> for creating or removing a database server machine. If you
+ instructions in the <emphasis>OpenAFS Quick Beginnings</emphasis> for creating or removing a database server machine. If you
run one database server process on a given machine, you must run them all; for more information, see <link
linkend="HDRWQ156">About Starting and Stopping the Database Server Processes</link>. Similarly, if you are stopping the
<emphasis role="bold">upserver</emphasis> process on the system control machine or a binary distribution machine, you must
<listitem>
<para>Specifies the pathname of a program that the BOS Server runs when the process terminates. For more
information on notifier programs, see the <emphasis role="bold">bos create</emphasis> command reference page in
- the <emphasis>IBM AFS Administration Reference</emphasis>.</para>
+ the <emphasis>OpenAFS Administration Reference</emphasis>.</para>
</listitem>
</varlistentry>
</variablelist></para>
<note>
<para>If you are starting or stopping a database server process in the manner described in this section, follow the complete
- instructions in the <emphasis>IBM AFS Quick Beginnings</emphasis> for creating or removing a database server machine. If you
+ instructions in the <emphasis>OpenAFS Quick Beginnings</emphasis> for creating or removing a database server machine. If you
run one database server process on a given machine, you must run them all; for more information, see <link
linkend="HDRWQ156">About Starting and Stopping the Database Server Processes</link>. Similarly, if you are stopping the
<emphasis role="bold">upserver</emphasis> process on the system control machine or a binary distribution machine, you must
demand for the volume's contents and how much disk space you are willing to use for multiple copies of the volume. Of course,
each prospective read-only site must have enough available space to accommodate the volume. The limit on the number of
read-only copies of a volume is determined by the maximum number of site definitions in a volume's VLDB entry, which is
- defined in the <emphasis> IBM AFS Release Notes</emphasis>. The site housing the read/write and backup versions of the volume
+ defined in the <emphasis> OpenAFS Release Notes</emphasis>. The site housing the read/write and backup versions of the volume
counts as one site, and each read-only site counts as an additional site (even the read-only site defined on the same file
server machine and partition as the read/write site counts as a separate site). Note also that the Volume Server permits only
one read-only copy of a volume per file server machine.</para>
home directory as it was at the time the backup was created, with all files and subdirectories in the same relative
positions.</para>
- <para>If you do create and mount backup volumes for your users, inform users of their existence. The <emphasis> IBM AFS User
+ <para>If you do create and mount backup volumes for your users, inform users of their existence. The <emphasis> OpenAFS User
Guide</emphasis> does not mention backup volumes because making them available to users is optional. Explain to users how
often you make a new backup, so they know what they can recover. Remind them also that the data in their backup volume cannot
change; however, they can use the standard UNIX <emphasis role="bold">cp</emphasis> command to copy it into their home volume
<note>
<para>It is best not to halt a <emphasis role="bold">vos move</emphasis> operation before it completes, because parts of
the volume can be left on both the source and destination machines. For more information, see the command's reference
- page in the <emphasis> IBM AFS Administration Reference</emphasis>.</para>
+ page in the <emphasis>OpenAFS Administration Reference</emphasis>.</para>
</note>
</listitem>
files or directories in it. If an application is writing data into an existing file in a full volume, the File Server allows a
defined overage (by default, 1 MB). (You can use the <emphasis role="bold">fileserver</emphasis> command's <emphasis
role="bold">-spare</emphasis> or <emphasis role="bold">-pctspare</emphasis> argument to change the default overage; see the
- command's reference page in the <emphasis> IBM AFS Administration Reference</emphasis>.)</para>
+ command's reference page in the <emphasis>OpenAFS Administration Reference</emphasis>.)</para>
<para>To set a quota other than 5000 KB as you create a volume, include the <emphasis role="bold">-maxquota</emphasis> argument
to the <emphasis role="bold">vos create</emphasis> command, as described in <link linkend="HDRWQ185">Creating Read/write
<para>In general, smaller volumes are easier to administer than larger ones. If you need to move volumes, say for load-balancing
purposes, it is easier to find enough free space on other partitions for small volumes. Move operations complete more quickly
for small volumes, reducing the potential for outages or other errors to interrupt the move. AFS supports a maximum volume size,
- which can vary for different AFS releases; see the <emphasis> IBM AFS Release Notes</emphasis> for the version you are using.
+ which can vary for different AFS releases; see the <emphasis> OpenAFS Release Notes</emphasis> for the version you are using.
Also, the size of a partition or logical places an absolute limit on volume size, because a volume cannot span multiple
partitions or logical volumes.</para>
it automatically removes a volume's VLDB entry and both the volume header and all data from the partition. If either the VLDB
entry or volume header does not exist, it is sometimes necessary to use other commands that remove only the remaining element.
Do not use these commands in the normal case when both the VLDB entry and the volume header exist, because by definition they
- create discrepancies between them. For details on the commands' syntax, see their reference pages in the <emphasis> IBM AFS
+ create discrepancies between them. For details on the commands' syntax, see their reference pages in the <emphasis> OpenAFS
Administration Reference</emphasis>.</para>
<indexterm>
<para>The <emphasis>Backup Database</emphasis> is a replicated administrative database maintained by the Backup Server process
on the cell's database server machines. Like the other AFS database server processes, the <emphasis>Backup Server</emphasis>
uses the Ubik utility to keep the various copies of the database synchronized (for a discussion of Ubik, see <link
- linkend="HDRWQ52">Replicating the AFS Administrative Databases</link>).</para>
+ linkend="HDRWQ52">Replicating the OpenAFS Administrative Databases</link>).</para>
<para>The Backup Database records the following information: <itemizedlist>
<listitem>
id</computeroutput> respectively). The <computeroutput>cell</computeroutput> field reports the cell in which the dump
operation was performed, and the <computeroutput>useCount</computeroutput> field reports the number of times the tape has been
relabeled, either with the <emphasis role="bold">backup labeltape</emphasis> command or during a dump operation. For further
- details, see the command's reference page in the <emphasis>IBM AFS Administration Reference</emphasis>.</para>
+ details, see the command's reference page in the <emphasis>OpenAFS Administration Reference</emphasis>.</para>
<para>If the tape has no label, or if the drive is empty, the following message appears at the command shell:</para>
<listitem>
<para>The Backup System cannot determine if the dump set includes any more tapes while running the <emphasis
- role="bold">backup scantape</emphasis> command (the command's reference page in the <emphasis>IBM AFS Administration
+ role="bold">backup scantape</emphasis> command (the command's reference page in the <emphasis>OpenAFS Administration
Reference</emphasis> discusses possible reasons for this problem). When you assign the value <emphasis
role="bold">NO</emphasis>, the Tape Coordinator proceeds as though there are more tapes and invokes the <emphasis
role="bold">MOUNT</emphasis> script named in the device configuration file, or prompts the operator to insert the next
<listitem>
<para>The Backup Server (<emphasis role="bold">buserver</emphasis>) process must be running on database server machines,
- because most backup operations require accessing or changing information in the Backup Database. The <emphasis>IBM AFS
+ because most backup operations require accessing or changing information in the Backup Database. The <emphasis>OpenAFS
Quick Beginnings</emphasis> explains how to configure the Backup Server.</para>
</listitem>
</itemizedlist></para>
<para>For each dump on the tape, the output in the Tape Coordinator window displays the dump label followed by an entry for
each volume. There is no output in the command window. The dump label has the same fields as the tape label displayed by the
<emphasis role="bold">backup readlabel</emphasis> command, as described in <link linkend="HDRWQ272">Writing and Reading Tape
- Labels</link>. Or see the <emphasis>IBM AFS Administration Reference</emphasis> for a detailed description of the fields in
+ Labels</link>. Or see the <emphasis>OpenAFS Administration Reference</emphasis> for a detailed description of the fields in
the output.</para>
<para>The following example shows the dump label and first volume entry on the tape in the device that has port offset
<listitem>
<para>Reports the existence of orphan blocks and other information about the database, as described on the
- <emphasis role="bold">backup dbverify</emphasis> reference page in the <emphasis>IBM AFS Administration
+ <emphasis role="bold">backup dbverify</emphasis> reference page in the <emphasis>OpenAFS Administration
Reference</emphasis>.</para>
</listitem>
</varlistentry>
role="bold">-to</emphasis> argument is equivalent in effect and is simpler because it does not require starting a Tape
Coordinator process as the <emphasis role="bold">backup savedb</emphasis> command does. For further information on the
<emphasis role="bold">-archive</emphasis> argument to the <emphasis role="bold">backup savedb</emphasis> command, see the
- command's reference page in the <emphasis>IBM AFS Administration Reference</emphasis>.</para>
+ command's reference page in the <emphasis>OpenAFS Administration Reference</emphasis>.</para>
<para>If you later need to access deleted dump records, and the corresponding tapes still exist, you can use the <emphasis
role="bold">-dbadd</emphasis> argument to the <emphasis role="bold">backup scantape</emphasis> command to scan their contents
<para>Specifies which individual statistic, group of statistics, or section of statistics to display on the
<computeroutput>File Servers</computeroutput> screen (<emphasis role="bold">fs</emphasis>) or <computeroutput>Cache
Managers</computeroutput> screen (<emphasis role="bold">cm</emphasis>) and the order in which to display them. The
- appendix of <emphasis role="bold">afsmonitor</emphasis> statistics in the <emphasis>IBM AFS Administration
+ appendix of <emphasis role="bold">afsmonitor</emphasis> statistics in the <emphasis>OpenAFS Administration
Guide</emphasis> specifies the group and section to which each statistic belongs. Include as many <emphasis
role="bold">show</emphasis> lines as necessary to customize the screen display as desired, and place them anywhere in
the file. The top-to-bottom order of the <emphasis role="bold">show</emphasis> lines in the configuration file
</orderedlist></para>
<para>For instructions on creating the initial <emphasis role="bold">afs</emphasis> entry and <emphasis
- role="bold">KeyFile</emphasis> files as you install your cell's first server machine, see the IBM AFS Quick
+ role="bold">KeyFile</emphasis> files as you install your cell's first server machine, see the OpenAFS Quick
Beginnings.</para>
</listitem>
<listitem>
<para>You must run the <emphasis role="bold">upserver</emphasis> process on the system control machine and an
<emphasis role="bold">upclientetc</emphasis> process on all other server machines that references the system
- control machine. The IBM AFS Quick Beginnings explains how to install both processes. For instructions on
+ control machine. The OpenAFS Quick Beginnings explains how to install both processes. For instructions on
verifying that the Update Server processes are running, see <link linkend="HDRWQ158">Displaying Process Status and
Information from the BosConfig File</link>.</para>
between this date and the date reported by the <emphasis role="bold">bos listkeys</emphasis> command, because the latter date
changes for any type of change to the <emphasis role="bold">KeyFile</emphasis> file, not just a key addition. For a
description of the other lines in the output from the <emphasis role="bold">kas examine</emphasis> command, see its reference
- page in the IBM AFS Administration Reference.</para>
+ page in the OpenAFS Administration Reference.</para>
<programlisting>
% <emphasis role="bold">kas examine afs -admin admin</emphasis>
</listitem>
</itemizedlist></para>
- <para>To learn how to install the client functionality on a machine, see the <emphasis>IBM AFS Quick Beginnings</emphasis>.</para>
+ <para>To learn how to install the client functionality on a machine, see the <emphasis>OpenAFS Quick Beginnings</emphasis>.</para>
<sect1 id="HDRWQ388">
<title>Summary of Instructions</title>
Cache Manager mounts the AFS filespace, the local disk directory to use as the cache, and how many kilobytes to
allocate to the cache.</para>
- <para>The <emphasis>IBM AFS Quick Beginnings</emphasis> explains how to create this file as you install a client
+ <para>The <emphasis>OpenAFS Quick Beginnings</emphasis> explains how to create this file as you install a client
machine. To change the cache size on a machine that uses a memory cache, edit the file and reboot the machine. On a
machine that uses a disk cache, you can change the cache size without rebooting by issuing the <emphasis
role="bold">fs setcachesize</emphasis> command. For instructions, see <link linkend="HDRWQ394">Determining the Cache
authenticated, and in which the command interpreters (for example, the <emphasis role="bold">bos</emphasis> command)
contact server processes.</para>
- <para>The <emphasis>IBM AFS Quick Beginnings</emphasis> explains how to create this file as you install the AFS client
+ <para>The <emphasis>OpenAFS Quick Beginnings</emphasis> explains how to create this file as you install the AFS client
functionality. To learn about changing a client machine's cell membership, see <link linkend="HDRWQ411">Setting a
Client Machine's Cell Membership</link>.</para>
</listitem>
<listitem>
<para>The AFS initialization script, called <emphasis role="bold">afs.rc</emphasis> on many system types. In the
- conventional configuration specified by the <emphasis>IBM AFS Quick Beginnings</emphasis>, it is a symbolic link to the
+ conventional configuration specified by the <emphasis>OpenAFS Quick Beginnings</emphasis>, it is a symbolic link to the
actual script kept in the same directory as other initialization files used by the operating system. <indexterm>
<primary>dynamic kernel loader programs</primary>
memory from other sources on the machine (number of users and processes). Machines running only a few processes possibly can
use a smaller memory cache.</para>
- <para>AFS imposes an absolute limit on cache size in some versions. See the <emphasis>IBM AFS Release Notes</emphasis> for the
+ <para>AFS imposes an absolute limit on cache size in some versions. See the <emphasis>OpenAFS Release Notes</emphasis> for the
version you are using.</para>
</sect2>
</indexterm>
<para>The Cache Manager determines how big to make the cache by reading the <emphasis
- role="bold">/usr/vice/etc/cacheinfo</emphasis> file as it initializes. As directed in the <emphasis>IBM AFS Quick
+ role="bold">/usr/vice/etc/cacheinfo</emphasis> file as it initializes. As directed in the <emphasis>OpenAFS Quick
Beginnings</emphasis>, you must create the file before running the <emphasis role="bold">afsd</emphasis> program. The file
also defines the directory on which to mount AFS (by convention, <emphasis role="bold">/afs</emphasis>), and the local disk
directory to use for a cache directory.</para>
<para>To change the cache size at reboot without editing the <emphasis role="bold">cacheinfo</emphasis> file, include the
<emphasis role="bold">-blocks</emphasis> argument to the <emphasis role="bold">afsd</emphasis> command; see the command's
- reference page in the IBM AFS Administration Reference.</para>
+ reference page in the OpenAFS Administration Reference.</para>
<para>For a disk cache, you can also use the <emphasis role="bold">fs setcachesize</emphasis> command to reset the cache size
without rebooting. The value you set persists until the next reboot, at which time the cache size returns to the value
and Location</link>. However, if you want to experiment with fine-tuning cache performance, you can use the arguments on the
<emphasis role="bold">afsd</emphasis> command to control several other parameters. This section discusses a few of these
parameters that have the most direct effect on cache performance. To learn more about the <emphasis role="bold">afsd</emphasis>
- command's arguments, see its reference page in the <emphasis>IBM AFS Administration Reference</emphasis>.</para>
+ command's arguments, see its reference page in the <emphasis>OpenAFS Administration Reference</emphasis>.</para>
<para>In addition, the AFS initialization script included in the AFS distribution for each system type includes several
variables that set several <emphasis role="bold">afsd</emphasis> arguments in a way that is suitable for client machines of
different sizes and usage patterns. For instructions on using the script most effectively, see the section on configuring the
- Cache Manager in the <emphasis>IBM AFS Quick Beginnings</emphasis>.</para>
+ Cache Manager in the <emphasis>OpenAFS Quick Beginnings</emphasis>.</para>
<sect2 id="HDRWQ403">
<title>Setting Cache Configuration Parameters</title>
the <emphasis role="bold">/usr/vice/etc/CellServDB</emphasis> file on the machine's local disk. In addition to the machine's
home cell, you can list any foreign cells that you want to enable users to access. (To enable access to a cell's filespace, you
must also mount its <emphasis role="bold">root.cell</emphasis> volume in the local AFS filespace; the conventional location is
- just under the AFS root directory, <emphasis role="bold">/afs</emphasis>. For instructions, see the <emphasis>IBM AFS Quick
+ just under the AFS root directory, <emphasis role="bold">/afs</emphasis>. For instructions, see the <emphasis>OpenAFS Quick
Beginnings</emphasis>.)</para>
<sect2 id="Header_451">
<para>Because a correct entry in the <emphasis role="bold">CellServDB</emphasis> file is vital for consistent client
performance, you must also update the file on each client machine whenever a cell's list of database server machines changes
- (for instance, when you follow the instructions in the <emphasis>IBM AFS Quick Beginnings</emphasis> to add or remove a
+ (for instance, when you follow the instructions in the <emphasis>OpenAFS Quick Beginnings</emphasis> to add or remove a
database server machine). To facilitate the client updates, you can use the <emphasis role="bold">package</emphasis> program,
which copies files from a central source in AFS to the local disk of client machines. It is conventional to invoke the
<emphasis role="bold">package</emphasis> program in a client machine's AFS initialization file so that it runs as the machine
<listitem>
<para>Specifies the complete Internet domain name of the AFS cell to link to a DCE cell for the purposes of DFS
fileset location. You can use this argument if the machine's AFS users access DFS via the AFS/DFS Migration
- Toolkit Protocol Translator. For instructions, see the <emphasis>IBM AFS/DFS Migration Toolkit Administration
+ Toolkit Protocol Translator. For instructions, see the <emphasis>OpenAFS/DFS Migration Toolkit Administration
Guide and Reference</emphasis>.</para>
</listitem>
</varlistentry>
<para>The Cache Manager assigns preference ranks to a file server machine when it obtains the server's VLDB record from the VL
Server, the first time that it accesses a volume that resides on the machine. If the machine is multihomed, the Cache Manager
assigns a distinct rank to each of its interfaces (up to the number of interfaces that the VLDB can store for each machine,
- which is specified in the <emphasis>IBM AFS Release Notes</emphasis>). The Cache Manager compares the interface's IP address
+ which is specified in the <emphasis>OpenAFS Release Notes</emphasis>). The Cache Manager compares the interface's IP address
to the local machine's address and applies the following algorithm: <itemizedlist>
<listitem>
<para>If the local machine is a file server machine, the base rank for each of its interfaces is 5,000.</para>
described in <link linkend="HDRWQ419">Configuring Client Machines with the package Program</link>.) The link also remains valid
when you upgrade the machine to a new system type.</para>
- <para>Configuration is simplest if you use the system type names that AFS assigns. For a list, see the <emphasis>IBM AFS Release
+ <para>Configuration is simplest if you use the system type names that AFS assigns. For a list, see the <emphasis>OpenAFS Release
Notes</emphasis>.</para>
<para>To display the system name stored in kernel memory, use the <emphasis role="bold">sys</emphasis> or <emphasis
<para>This section assumes that the <emphasis role="bold">package</emphasis>-related files have been installed in three
subdirectories of the <emphasis role="bold">/afs/</emphasis>cellname/<emphasis role="bold">wsadmin</emphasis> directory:
<emphasis role="bold">src</emphasis>, <emphasis role="bold">lib</emphasis> and <emphasis role="bold">etc</emphasis>, as
- recommended in the <emphasis>IBM AFS Quick Beginnings</emphasis>.</para>
+ recommended in the <emphasis>OpenAFS Quick Beginnings</emphasis>.</para>
<para>These directories contain several sample prototype, library, and configuration files, which can help to clarify how the
<emphasis role="bold">package</emphasis> program works. However, they are not necessarily suitable for use in your cell; you
directories, sockets, etc. Each line, called a <emphasis>configuration file instruction</emphasis>, defines a specific
component of disk configuration. The proper syntax for these instructions is briefly described in <link
linkend="HDRWQ429">Package Configuration File Instruction Syntax</link>; see the reference page for the <emphasis
- role="bold">package</emphasis> configuration file in the <emphasis>IBM AFS Administration Reference</emphasis> for detailed
+ role="bold">package</emphasis> configuration file in the <emphasis>OpenAFS Administration Reference</emphasis> for detailed
descriptions.</para>
<para>In this example, the library file contains instructions specific to the configuration of an <emphasis
<para>Within a library file, configuration file instructions are used to define the specific disk configuration. Each
instruction can be used to define a file, directory, socket, or device on the client machine. The syntax for each valid
- instruction type is described briefly here; detailed descriptions of the fields appear in the <emphasis>IBM AFS Command
+ instruction type is described briefly here; detailed descriptions of the fields appear in the <emphasis>OpenAFS Command
Reference Manual</emphasis>. <itemizedlist>
<listitem>
<para><emphasis role="bold">D</emphasis> defines a directory</para>
<para>Determine where the three <emphasis role="bold">package</emphasis>-related subdirectories (<emphasis
role="bold">src</emphasis>, <emphasis role="bold">lib</emphasis> and <emphasis role="bold">etc</emphasis>) reside in your
cell's file tree; the following instructions assume they were loaded into the <emphasis
- role="bold">/afs/</emphasis>cellname<emphasis role="bold">/wsadmin</emphasis> directory, as described in the IBM AFS Quick
+ role="bold">/afs/</emphasis>cellname<emphasis role="bold">/wsadmin</emphasis> directory, as described in the OpenAFS Quick
Beginnings.</para>
</listitem>
<para>To prepare a client to run the <emphasis role="bold">package</emphasis> program automatically, perform the following
steps. The instructions are generic because they do not refer to system-specific configuration files. If desired, you can invoke
- the <emphasis role="bold">package</emphasis> program with specific arguments, as described in the <emphasis>IBM AFS
+ the <emphasis role="bold">package</emphasis> program with specific arguments, as described in the <emphasis>OpenAFS
Administration Reference</emphasis>. <orderedlist>
<listitem>
<para>Specify the configuration file to use.</para>
<para>Using the <emphasis role="bold">-v</emphasis> and <emphasis role="bold">-c</emphasis> options is recommended. The
<emphasis role="bold">-v</emphasis> flag produces a detailed trace, and the <emphasis role="bold">-c</emphasis> option
- appends the system type to the base name of the configuration file. See the <emphasis>IBM AFS Administration
+ appends the system type to the base name of the configuration file. See the <emphasis>OpenAFS Administration
Reference</emphasis> for a description of other options.</para>
<note>
you do not provide this argument. There is no corresponding variable in the template file.</para>
<para>Instruct users to change their passwords to a truly secret string as soon as they authenticate with AFS for
- the first time. The <emphasis>IBM AFS User Guide</emphasis> explains how to use the <emphasis
+ the first time. The <emphasis>OpenAFS User Guide</emphasis> explains how to use the <emphasis
role="bold">kpasswd</emphasis> command to change an AFS password.</para>
</listitem>
</varlistentry>
</programlisting>
<para>For a complete description of the acceptable values in each field, see the <emphasis role="bold">uss Bulk Input
- File</emphasis> reference page in the <emphasis>IBM AFS Administration Reference</emphasis>, or the description of the
+ File</emphasis> reference page in the <emphasis>OpenAFS Administration Reference</emphasis>, or the description of the
corresponding arguments to the <emphasis role="bold">uss add</emphasis> command, in <link linkend="HDRWQ483">To create an AFS
account with the uss add command</link>. Following are some basic notes: <itemizedlist>
<listitem>
</programlisting>
<para>For a complete description of the acceptable values in each field, see the <emphasis role="bold">uss Bulk Input
- File</emphasis> reference page in the <emphasis>IBM AFS Administration Reference</emphasis> or the description of the
+ File</emphasis> reference page in the <emphasis>OpenAFS Administration Reference</emphasis> or the description of the
corresponding arguments to the <emphasis role="bold">uss delete</emphasis> command, in <link linkend="HDRWQ487">To delete an
AFS account</link>. Following are some basic notes: <itemizedlist>
<listitem>
<listitem>
<para>The initial password. Advise the user to change this at the first login, using the password changing
- instructions in the <emphasis>IBM AFS User Guide</emphasis>.</para>
+ instructions in the <emphasis>OpenAFS User Guide</emphasis>.</para>
</listitem>
<listitem>
<para>A persistent user can try to bypass this restriction by changing the password 20 times in quick succession (or
running a script to do so). If you believe this is likely to be a problem, you can include the <emphasis
role="bold">-minhours</emphasis> argument to the <emphasis role="bold">kaserver</emphasis> initialization command (for
- details, see the command's reference page in the <emphasis>IBM AFS Administration Reference</emphasis>. If the user
+ details, see the command's reference page in the <emphasis>OpenAFS Administration Reference</emphasis>. If the user
attempts to change passwords too frequently, the following message appears.</para>
<programlisting>
</itemizedlist></para>
<para>The AFS distribution includes an example <emphasis role="bold">kpwvalid</emphasis> program. See the <emphasis
- role="bold">kpwvalid</emphasis> reference page in the <emphasis>IBM AFS Administration Reference</emphasis>.</para>
+ role="bold">kpwvalid</emphasis> reference page in the <emphasis>OpenAFS Administration Reference</emphasis>.</para>
</listitem>
</itemizedlist></para>
<title>Changing AFS Passwords</title>
<para>After setting an initial password during account creation, you normally do not need to change user passwords, since they
- can use the <emphasis role="bold">kpasswd</emphasis> command themselves by following the instructions in the <emphasis>IBM AFS
+ can use the <emphasis role="bold">kpasswd</emphasis> command themselves by following the instructions in the <emphasis>OpenAFS
User Guide</emphasis>. In the rare event that a user forgets the password or otherwise cannot log in, you can use the <emphasis
role="bold">kas setpassword</emphasis> command to set a new password.</para>
restriction that some applications impose. Possible choices for an initial password include the username, a string
of digits from a personal identification number such as the Social Security number, or a standard string such as
<emphasis role="bold">changeme</emphasis>. Instruct the user to change the string to a truly secret password as soon
- as possible by using the <emphasis role="bold">kpasswd</emphasis> command as instructed in the <emphasis>IBM AFS
+ as possible by using the <emphasis role="bold">kpasswd</emphasis> command as instructed in the <emphasis>OpenAFS
User Guide</emphasis>.</para>
</listitem>
</varlistentry>
role="bold">fs listacl</emphasis> command is configured to access a DCE cell's DFS filespace via the AFS/DFS Migration Toolkit,
you can use the command to display the ACL on DFS files and directories. To display a DFS directory's Initial Container and
Initial Object ACL instead of the regular one, include the <emphasis role="bold">fs listacl</emphasis> command's <emphasis
- role="bold">-id</emphasis> or <emphasis role="bold">-if</emphasis> flag. For instructions, see the <emphasis>IBM AFS/DFS
+ role="bold">-id</emphasis> or <emphasis role="bold">-if</emphasis> flag. For instructions, see the <emphasis>OpenAFS/DFS
Migration Toolkit Administration Guide and Reference</emphasis>. The <emphasis role="bold">fs</emphasis> command interpreter
ignores the <emphasis role="bold">-id</emphasis> and <emphasis role="bold">-if</emphasis> flags if you include them when
displaying an AFS ACL. <indexterm>
role="bold">fs setacl</emphasis> command is configured to access a DCE cell's DFS filespace via the AFS/DFS Migration Toolkit,
you can use the command to set the ACL on DFS files and directories. To set a DFS directory's Initial Container and Initial
Object ACL instead of the regular one, include the <emphasis role="bold">fs setacl</emphasis> command's <emphasis
- role="bold">-id</emphasis> or <emphasis role="bold">-if</emphasis> flag. For instructions, see the <emphasis>IBM AFS/DFS
+ role="bold">-id</emphasis> or <emphasis role="bold">-if</emphasis> flag. For instructions, see the <emphasis>OpenAFS/DFS
Migration Toolkit Administration Guide and Reference</emphasis>. The <emphasis role="bold">fs</emphasis> command interpreter
ignores the <emphasis role="bold">-id</emphasis> and <emphasis role="bold">-if</emphasis> flags if you include them when setting
an AFS ACL. <indexterm>
users to access a DCE cell's DFS filespace via the AFS/DFS Migration Toolkit, then you can use the <emphasis role="bold">fs
copyacl</emphasis> command to copy ACLs between DFS files and directories also. The command includes <emphasis
role="bold">-id</emphasis> and <emphasis role="bold">-if</emphasis> flags for altering a DFS directory's Initial Container and
- Initial Object ACLs as well as its regular ACL; see the <emphasis>IBM AFS/DFS Migration Toolkit Administration Guide and
+ Initial Object ACLs as well as its regular ACL; see the <emphasis>OpenAFS/DFS Migration Toolkit Administration Guide and
Reference</emphasis>. You cannot copy ACLs between AFS and DFS directories, because they use different ACL formats. The
<emphasis role="bold">fs</emphasis> command interpreter ignores the <emphasis role="bold">-id</emphasis> and <emphasis
role="bold">-if</emphasis> flags if you include them when copying AFS ACLs. <indexterm>
you issue the <emphasis role="bold">bos create</emphasis> command to create and start the <emphasis
role="bold">fs</emphasis> process on the machine, include the <emphasis role="bold">-implicit</emphasis> argument to the
<emphasis role="bold">fileserver</emphasis> initialization command. For syntax details,
git://git.openafs.org / openafs.git / commitdiff
