From 9cde8b8854f255a2cc264e0391dbb855fcfab23b Mon Sep 17 00:00:00 2001 From: "Chas Williams (CONTRACTOR)" Date: Tue, 7 Jun 2011 14:26:11 -0400 Subject: [PATCH] doc: fixes for the xsltproc -> fop -> pdf toolchain "Empty" entities seem to trigger a bug in fop. These are easily converted to reference on the containing block. Additionally, 's seem to need to be inside a non-structural entity (like a ) in order to determine their page number/location correctly. Change-Id: I2ab577f6ba8989685257fb9429e00a71dd51075c Reviewed-on: http://gerrit.openafs.org/4812 Tested-by: BuildBot Reviewed-by: Jeffrey Altman --- doc/xml/AdminGuide/auagd007.xml | 15 +- doc/xml/AdminGuide/auagd008.xml | 39 ++--- doc/xml/AdminGuide/auagd009.xml | 15 +- doc/xml/AdminGuide/auagd010.xml | 100 ++++++------ doc/xml/AdminGuide/auagd011.xml | 14 +- doc/xml/AdminGuide/auagd012.xml | 50 +++--- doc/xml/AdminGuide/auagd013.xml | 3 +- doc/xml/AdminGuide/auagd014.xml | 66 ++++---- doc/xml/AdminGuide/auagd015.xml | 4 +- doc/xml/AdminGuide/auagd017.xml | 8 +- doc/xml/AdminGuide/auagd018.xml | 82 +++++----- doc/xml/AdminGuide/auagd019.xml | 4 +- doc/xml/AdminGuide/auagd020.xml | 4 +- doc/xml/AdminGuide/auagd021.xml | 4 +- doc/xml/AdminGuide/auagd022.xml | 29 ++-- doc/xml/AdminGuide/auagd025.xml | 4 +- doc/xml/QuickStartUnix/appendix.xml | 30 ++-- doc/xml/QuickStartUnix/auqbg005.xml | 47 +++--- doc/xml/QuickStartUnix/auqbg006.xml | 86 +++++----- doc/xml/QuickStartUnix/auqbg007.xml | 15 +- doc/xml/QuickStartUnix/auqbg008.xml | 4 +- doc/xml/ReleaseNotesWindows/relnotes.xml | 194 ++++++++++------------- doc/xml/UserGuide/auusg009.xml | 16 +- doc/xml/UserGuide/auusg010.xml | 8 +- doc/xml/UserGuide/auusg011.xml | 3 +- 25 files changed, 409 insertions(+), 435 deletions(-) diff --git a/doc/xml/AdminGuide/auagd007.xml b/doc/xml/AdminGuide/auagd007.xml index b7d84c584..4455bad3e 100644 --- a/doc/xml/AdminGuide/auagd007.xml +++ b/doc/xml/AdminGuide/auagd007.xml @@ -11,7 +11,7 @@ It is best to read this chapter before installing your cell's first file server machine or performing any other administrative - task. + task. AFS @@ -30,6 +30,7 @@ between AFS and UNIX, summarized + Differences between AFS and UNIX: A Summary @@ -3691,12 +3692,12 @@ the attempt proceeds to the next step. - - The utility obtains a PAG. + + The utility obtains a PAG. - - The utility converts the password + + The utility converts the password provided by the user into an encryption key and encrypts a packet of data with the key. It sends the packet to the AFS authentication service (the AFS Authentication Server in the @@ -3735,8 +3736,8 @@ - - If no AFS token was granted in + + If no AFS token was granted in Step 4, the login utility attempts to log the user into the local file system, by comparing the password provided to the local password file. diff --git a/doc/xml/AdminGuide/auagd008.xml b/doc/xml/AdminGuide/auagd008.xml index 4ce35dfb3..4b8bbe69e 100644 --- a/doc/xml/AdminGuide/auagd008.xml +++ b/doc/xml/AdminGuide/auagd008.xml @@ -2,6 +2,7 @@ Administering Server Machines + server machine @@ -14,7 +15,7 @@ server machine - This chapter describes how to administer an AFS server machine. It describes the following configuration information and + This chapter describes how to administer an AFS server machine. It describes the following configuration information and administrative tasks: The binary and configuration files that must reside in the subdirectories of the - - Issue the bos shutdown command to shut down the + + Issue the bos shutdown command to shut down the relevant server process on the local machine. For a complete description of the command, see To stop processes temporarily. @@ -2976,8 +2977,8 @@ cell. - - Working on one of the machines, issue the bos + + Working on one of the machines, issue the bos shutdown command once for each database server machine, to shut down the relevant server process on all of them. For a complete description of the command, see To stop processes temporarily. @@ -3308,8 +3309,8 @@ using a transfer utility such as the ftp command. - - Issue the bos install command for the binary distribution + + Issue the bos install command for the binary distribution machine. (If you have forgotten which machine is performing that role, see To locate the binary distribution machine for a system type.) % bos install <machine name> <files to install>+ @@ -3489,8 +3490,8 @@ role="bold">.BAK - - Issue the bos uninstall command for a binary distribution + + Issue the bos uninstall command for a binary distribution machine. (If you have forgotten which machine is performing that role, see To locate the binary distribution machine for a system type.) % bos uninstall <machine name> <files to uninstall>+ @@ -4966,15 +4967,15 @@ - - Using a text editor, create an entry in the machine's file systems registry file ( + Using a text editor, create an entry in the machine's file systems registry file (/etc/fstab or equivalent) for each new disk partition, mapping its device name to the directory you created in the previous step. Refer to existing entries in the file to learn the proper format, which varies for different operating systems. - - If the operating system requires that you shut off the machine to install a new disk, issue + + If the operating system requires that you shut off the machine to install a new disk, issue the bos shutdown command to shut down all AFS server processes other than the BOS Server (it terminates safely when you shut off the machine). Include the -localauth flag because you are logged in as the local superuser root but do not necessarily have administrative @@ -4985,8 +4986,8 @@ - - If necessary, shut off the machine. Install and format the new disk according to the + + If necessary, shut off the machine. Install and format the new disk according to the instructions provided by the disk and operating system vendors. If necessary, edit the disk's partition table to reflect the changes you made to the files system registry file in step 4; consult the operating system documentation for instructions. @@ -5117,8 +5118,8 @@ - - Using a text editor, remove or comment out each partition's entry from the machine's file + + Using a text editor, remove or comment out each partition's entry from the machine's file systems registry file (/etc/fstab or equivalent). @@ -5139,8 +5140,8 @@ - - If necessary, shut off the machine. Remove the disk according to the instructions provided by + + If necessary, shut off the machine. Remove the disk according to the instructions provided by the disk and operating system vendors. If necessary, edit the disk's partition table to reflect the changes you made to the files system registry file in step 7; consult the operating system documentation for instructions. diff --git a/doc/xml/AdminGuide/auagd009.xml b/doc/xml/AdminGuide/auagd009.xml index 187176bdb..e75ff0bfc 100644 --- a/doc/xml/AdminGuide/auagd009.xml +++ b/doc/xml/AdminGuide/auagd009.xml @@ -2,6 +2,7 @@ Monitoring and Controlling Server Processes + monitoring @@ -14,7 +15,7 @@ monitoring server processes - One of your most important responsibilities as a system administrator is ensuring that the processes on file server machines + One of your most important responsibilities as a system administrator is ensuring that the processes on file server machines are running correctly. The BOS Server, which runs on every file server machine, relieves you of much of the responsibility by constantly monitoring the other AFS server processes on its machine. It can automatically restart processes that have failed, ordering the restarts to take interdependencies into account. @@ -1527,7 +1528,7 @@ - Issue the bos create command to create an entry in the + Issue the bos create command to create an entry in the BosConfig file and start the process. % bos create <machine name> <server process name> \ <server type> <command lines>+ [ - - Issue the bos stop command to change each process's + + Issue the bos stop command to change each process's status flag in the BosConfig file to NotRun and to stop it. You must issue this command even for cron processes that you wish to remove from the BosConfig file, even though they do not run continuously. For a detailed description of this @@ -1802,7 +1803,7 @@ - Issue the bos delete command to remove each process from + Issue the bos delete command to remove each process from the BosConfig file. % bos delete <machine name> <server process name>+ @@ -2030,7 +2031,7 @@ - Issue the bos start command to change each process's + Issue the bos start command to change each process's status flag to Run in both the BosConfig file and the BOS Server's memory and to start it. % bos start <machine name> <server process name>+ @@ -2118,7 +2119,7 @@ - Issue the bos shutdown command to stop each process by + Issue the bos shutdown command to stop each process by changing its status flag in the BOS Server's memory to NotRun. % bos shutdown <machine name> [<instances>+] [-wait] diff --git a/doc/xml/AdminGuide/auagd010.xml b/doc/xml/AdminGuide/auagd010.xml index 9200b2bb0..7e68e1895 100644 --- a/doc/xml/AdminGuide/auagd010.xml +++ b/doc/xml/AdminGuide/auagd010.xml @@ -730,8 +730,8 @@ - - Select a site (disk partition on a file server machine) for the new volume. To verify that + + Select a site (disk partition on a file server machine) for the new volume. To verify that the site has enough free space to house the volume (now, or if it grows to use its entire quota), issue the vos partinfo command. @@ -774,8 +774,8 @@ - - Select a volume name, taking note of the information in About Volume + + Select a volume name, taking note of the information in About Volume Names. @@ -795,8 +795,8 @@ - - Issue the vos create command to create the volume. + + Issue the vos create command to create the volume. % vos create <machine name> <partition name> <volume name> \ [-maxquota <initial quota (KB)>] @@ -874,9 +874,7 @@ - - - + (Optional) Issue the fs mkmount command to mount the volume in the filespace. For complete syntax, see To create a regular or read/write mount point. @@ -1386,16 +1384,16 @@ - - Verify that you are listed in the /usr/afs/etc/UserList + + Verify that you are listed in the /usr/afs/etc/UserList file. If necessary, issue the bos listusers command, which is fully described in To display the users in the UserList file. % bos listusers <machine name> - - Select one or more sites at which to replicate the volume. There are several factors to + + Select one or more sites at which to replicate the volume. There are several factors to consider: How many sites are already defined. As previously noted, it is usually appropriate to define a read-only site @@ -1467,8 +1465,8 @@ - - Issue the vos addsite command to define each new read-only + + Issue the vos addsite command to define each new read-only site in the VLDB. % vos addsite <machine name> <partition name> <volume name or ID> @@ -1509,8 +1507,8 @@ - - (Optional) Verify that the + (Optional) Verify that the fs process (which incorporates the Volume Server) is functioning normally on each file server machine where you have defined a read-only site, and that the vlserver process (the Volume Location Server) is functioning correctly on each database server machine. Knowing that they are functioning @@ -1550,8 +1548,8 @@ - - Issue the vos release command to clone the read/write source + + Issue the vos release command to clone the read/write source volume and distribute the clone to each read-only site. % vos release <volume name or ID> [-f] @@ -1585,9 +1583,7 @@ - - - + (Optional) Issue the vos examine command to verify that no site definition in the VLDB entry is marked with an Old release or New release flag. The command is described fully in Displaying @@ -1898,8 +1894,8 @@ - - Issue the vos backup command to create a backup version of a + + Issue the vos backup command to create a backup version of a read/write source volume. The message shown confirms the success of the backup operation. % vos backup <volume name or ID> Created backup volume for volume name or ID @@ -1941,8 +1937,8 @@ - - (Optional) Issue the fs + + (Optional) Issue the fs mkmount to mount the backup volume. While this step is optional, Cache Managers cannot access the volume's contents if it is not mounted. % fs mkmount <directory> <volume name> - - If you are mounting one or more foreign cells' root.cell + + If you are mounting one or more foreign cells' root.cell volume at the second level in your filespace and your cell's root.afs volume is replicated, you must create a temporary mount point for the root.afs volume's read/write version in a directory on which the ACL grants you the i and vos operation, by performing the following series of steps. - - The VL Server locks the VLDB entry. The lock advises other operations not to manipulate any + + The VL Server locks the VLDB entry. The lock advises other operations not to manipulate any of the volume versions (read/write, read-only, or backup), which prevents the inconsistency that can result from multiple simultaneous operations. - + intention flag in VLDB entry VLDB intention flag set by VL Server - The VL Server sets an intention flag in the VLDB entry that + + The VL Server sets an intention flag in the VLDB entry that indicates the kind of operation to be performed. This flag never appears in VLDB listings because it is for internal use only. In case the operation terminates prematurely, this flag tells the Salvager which operation was interrupted. (The Salvager then determines the steps necessary either to complete the operation or return the volume to a previous consistent state. For more information on salvaging, see Salvaging Volumes.) - - The Volume Server manipulates the volume. It usually sets the + + The Volume Server manipulates the volume. It usually sets the Off-line flag in the volume header, which makes the volume inaccessible to the File Server and other Volume Server operations during the manipulation. When the operation completes, the volume is again marked On-line. - - The VL Server records any changes resulting from the operation in the VLDB entry. Once the + + The VL Server records any changes resulting from the operation in the VLDB entry. Once the operation is complete, it removes the intention flag set in Step 2and releases the lock set in Step 1. @@ -4532,8 +4529,8 @@ - - Issue the vos syncvldb command to make the VLDB reflect + + Issue the vos syncvldb command to make the VLDB reflect the true state of all volumes on a machine or partition, or the state of one volume. @@ -4600,8 +4597,8 @@ - - Issue the vos syncserv command to inspect each volume + + Issue the vos syncserv command to inspect each volume for which the VLDB lists a version at the specified site. @@ -5701,8 +5698,7 @@ role="bold">fs setacl command to grant other rights as necessary. - - + (Optional) Dump the volume to a file or to tape, in case you want to restore it later. To copy the volume's contents to a file, use the vos dump command as instructed in @@ -5731,8 +5727,8 @@ - - Issue the vos remove command to remove the volume. If + + Issue the vos remove command to remove the volume. If removing a read-only volume from multiple sites, repeat the command for each one. % vos remove [-server machine name>] [-partition <partition name>] \ -id <volume name or ID> @@ -5792,8 +5788,8 @@ - - If you are removing the last existing version of the volume, issue the + If you are removing the last existing version of the volume, issue the fs rmmount command remove the corresponding mount point. Complete instructions appear in To remove a volume and unmount it. @@ -6013,8 +6009,8 @@ role="bold">fs setacl command to grant other rights as necessary. - - Issue the vos dump command to dump the volume. + + Issue the vos dump command to dump the volume. % vos dump -id <volume name or ID> [-time <dump from time>] [-file <arg>] [-server <server>] [ - - Issue the vos restore command to create a new volume and + + Issue the vos restore command to create a new volume and restore the dump file into it. Type it on a single line; it appears on multiple lines here only for legibility. % vos restore <machine name> <partition name> \ @@ -6554,8 +6550,8 @@ role="bold">fs setacl command to grant other rights as necessary. - - Issue the vos rename command to rename the volume. + + Issue the vos rename command to rename the volume. % vos rename <old volume name> <new volume name> diff --git a/doc/xml/AdminGuide/auagd011.xml b/doc/xml/AdminGuide/auagd011.xml index b91ccea9d..3a7db915d 100644 --- a/doc/xml/AdminGuide/auagd011.xml +++ b/doc/xml/AdminGuide/auagd011.xml @@ -1141,8 +1141,8 @@ - - Install one or more tape devices on the Tape Coordinator machine according to the + + Install one or more tape devices on the Tape Coordinator machine according to the manufacturer's instructions. The Backup System can track a maximum of 58,511 tape devices or backup data files per cell. @@ -1262,8 +1262,8 @@ - - Issue the backup addhost command to create a Tape + + Issue the backup addhost command to create a Tape Coordinator entry in the Backup Database. Repeat the command for each Tape Coordinator. # backup addhost <tape machine name> [<TC port offset>] @@ -4124,8 +4124,8 @@ volume_set_name.dump_level_nameUsing a text editor, create an entry for the backup data file in the local + + Using a text editor, create an entry for the backup data file in the local /usr/afs/backup/tapeconfig file, using the standard syntax: [capacity filemark_size] device_name port_offset @@ -4299,4 +4299,4 @@ volume_set_name.dump_level_name/usr/afs/backup directory. - - Open a connection (using a command such as telnet or + + Open a connection (using a command such as telnet or rlogin) to the Tape Coordinator machine that drives the tape device, or whose local disk houses the backup data file. The Tape Coordinator uses a devoted connection or window that must remain open for the Tape Coordinator to accept requests and while it is executing them. @@ -845,8 +845,8 @@ role="bold">root. - - Issue the butc command to start the Tape Coordinator. You + + Issue the butc command to start the Tape Coordinator. You can include either, but not both, of the -localauth and -cell options, as discussed in Performing Backup Operations as the Local Superuser Root or in a Foreign Cell. @@ -1542,8 +1542,8 @@ - - You issue the butc command to start a Tape Coordinator + + You issue the butc command to start a Tape Coordinator to handle the dump operation. The Tape Coordinator does not have to be running when you issue the backup dump command, but must be active in time to accept the list of volumes to be included in the dump, when Step 3 is completed. To avoid coordination problems, it is best to @@ -1570,8 +1570,8 @@ mode. - - The Backup System works with the VL Server to generate a list of the volumes in the + + The Backup System works with the VL Server to generate a list of the volumes in the VLDB that match the name and location criteria defined in the volume set's volume entries. If a volume matches more than one volume entry, the Backup System ignores the duplicates so that the dump includes only one copy of data from the volume. @@ -1591,8 +1591,8 @@ role="bold">user.terry.backup, and user.smith.backup. - - The Backup System next scans the dump hierarchy for the dump level you have + + The Backup System next scans the dump hierarchy for the dump level you have specified on the backup dump command line. If it is a full level, then in the current operation the Backup System backs up all of the data in all of the volumes in the list obtained in Step 3. @@ -1662,8 +1662,8 @@ - - The Tape Coordinator prepares to back up the data. If there is a + The Tape Coordinator prepares to back up the data. If there is a CFG_device_name file, the Tape Coordinator already read it in Step 1. The following list describes how the instructions in the file guide the Tape Coordinator's behavior at this point: @@ -1734,8 +1734,8 @@ the -noautoquery flag to the butc command). - - The Tape Coordinator opens either a tape drive or backup data file at this point, as + + The Tape Coordinator opens either a tape drive or backup data file at this point, as directed by the instructions in the CFG_device_name file (described in Step 6). The instructions also determine whether it invokes a mount script or prompts the operator. In Step 1 the Tape Coordinator read in the device's capacity and filemark @@ -1751,8 +1751,8 @@ linkend="HDRWQ280">Eliminating the AFS Tape Name Check. - - For an initial dump, the Tape Coordinator starts writing at the beginning of the tape + + For an initial dump, the Tape Coordinator starts writing at the beginning of the tape or backup dump file, overwriting any existing data. To prevent inappropriate overwriting, the Backup System first checks the Backup Database for any dump records associated with the name (permanent or AFS tape name) on the tape or backup dump file's label. It refuses to write to a backup data file that has unexpired dumps in it, or to a tape that belongs to a @@ -1779,8 +1779,8 @@ - - The Tape Coordinator now writes data to the tape or backup data file. It uses the + + The Tape Coordinator now writes data to the tape or backup data file. It uses the capacity and filemark size it obtained in Step 7 as it tracks how much more space is available, automatically using its tape acquisition procedure if the dump is not finished when it reaches the end of the tape. For a more detailed description, and a discussion of what happens if the Tape Coordinator reaches the physical @@ -2087,8 +2087,8 @@ - - Issue the backup dump command to dump the volume + + Issue the backup dump command to dump the volume set. To create one initial dump, provide only the volume set name, dump level name, and port offset (if not @@ -4270,8 +4270,8 @@ cell. - - If the Tape Coordinator for the tape device that is to perform the operation is not + + If the Tape Coordinator for the tape device that is to perform the operation is not already running, open a connection to the appropriate Tape Coordinator machine and issue the butc command, for which complete instructions appear in To start a Tape Coordinator process. @@ -4302,8 +4302,8 @@ - - Issue the (backup) savedb command to repair corruption + + Issue the (backup) savedb command to repair corruption in the database as it is written to tape or a file. backup> savedb [-portoffset <TC port offset>] @@ -4617,4 +4617,4 @@ - \ No newline at end of file + diff --git a/doc/xml/AdminGuide/auagd013.xml b/doc/xml/AdminGuide/auagd013.xml index 7e5791cb0..191171ea5 100644 --- a/doc/xml/AdminGuide/auagd013.xml +++ b/doc/xml/AdminGuide/auagd013.xml @@ -2,6 +2,7 @@ Monitoring and Auditing AFS Performance + scout program @@ -48,7 +49,7 @@ monitoring activity - AFS comes with three main monitoring tools: + AFS comes with three main monitoring tools: The scout program, which monitors and gathers statistics on File Server performance. diff --git a/doc/xml/AdminGuide/auagd014.xml b/doc/xml/AdminGuide/auagd014.xml index 49ca7a97a..3f746deca 100644 --- a/doc/xml/AdminGuide/auagd014.xml +++ b/doc/xml/AdminGuide/auagd014.xml @@ -651,8 +651,8 @@ - - Issue the bos listkeys command to display the key version + + Issue the bos listkeys command to display the key version numbers that are already in use, as a first step in choosing the key version number for the new key. % bos listkeys <machine name> @@ -676,8 +676,8 @@ - - Choose a key version number for the new key, based on the output from Step + Choose a key version number for the new key, based on the output from Step 2 and the following requirements: A key version number must be an integer between 0 (zero) and 255 to comply with Kerberos standards. It is @@ -709,8 +709,8 @@ - - Issue the bos addkey command to create a new AFS server + + Issue the bos addkey command to create a new AFS server encryption key in the KeyFile file. If you run the United States edition of AFS and use the Update Server to distribute the contents of the system @@ -807,8 +807,8 @@ - - Issue the kas setpassword command to enter the same key in + + Issue the kas setpassword command to enter the same key in the afs entry in the Authentication Database. The Authentication Server performs its own authentication rather than accepting your existing AFS token. By default, @@ -1201,8 +1201,8 @@ - - Create the file /usr/afs/local/NoAuth to disable + + Create the file /usr/afs/local/NoAuth to disable authorization checking. # touch /usr/afs/local/NoAuth @@ -1268,13 +1268,13 @@ To create a new server encryption key in emergencies - - On the system control machine, disable authorization + + On the system control machine, disable authorization checking as instructed in Disabling Authorization Checking in an Emergency. - - Issue the bos listkeys command to display the key version + + Issue the bos listkeys command to display the key version numbers already in use in the KeyFile file, as a first step in choosing the new key's key version number. # bos listkeys <machine name> -noauth @@ -1308,8 +1308,8 @@ - - Choose a key version number for the new key, based on what you learned in Step + Choose a key version number for the new key, based on what you learned in Step 2 plus the following requirements: It is best to keep your key version numbers in sequence by choosing a key version number one greater than the @@ -1335,8 +1335,8 @@ - - On the system control machine, issue the + On the system control machine, issue the bos addkey command to create a new AFS server encryption key in the KeyFile file. # bos addkey <machine name> -kvno <key version number> - - On every database server machine in your cell (other than + + On every database server machine in your cell (other than the system control machine), disable authorization checking as instructed in Disabling Authorization Checking in an Emergency. Do not repeat the procedure on the system control machine, if it is a database server machine, because you already disabled authorization checking in Step 1. (If @@ -1409,8 +1409,8 @@ command as described in To locate database server machines.) - - Wait at least 90 seconds after finishing Step 5, to allow each + + Wait at least 90 seconds after finishing Step 5, to allow each of the database server processes (the Authentication, Backup, Protection and Volume Location Servers) to finish electing a new sync site. Then issue the udebug command to verify that the election worked properly. Issue the following commands, substituting each database server machine's name for server machine in turn. Include the @@ -1442,8 +1442,8 @@ assistance. - - On every database server machine in your cell (other than + + On every database server machine in your cell (other than the system control machine), issue the bos addkey command described in Step 4. Be sure to use the same values for afs_password and kvno as you used in that step. @@ -1454,8 +1454,8 @@ - - Issue the kas setpassword command to define the new key in + + Issue the kas setpassword command to define the new key in the Authentication Database's afs entry. It must match the key you created in Step 4 and Step 7. # kas setpassword -name afs -kvno <key version number> - - On every database server machine in your cell (including the + + On every database server machine in your cell (including the system control machine if it is a database server machine), reenable authorization checking as instructed in Reenabling Authorization Checking in an Emergency. If the system control machine is not a database server machine, do not perform this procedure until Step 11. @@ -1505,8 +1505,8 @@ site after being restarted in Step 9. - - On the system control machine (if it is not a database + + On the system control machine (if it is not a database server machine), reenable authorization checking as instructed in Reenabling Authorization Checking in an Emergency. If it is a database server machine, you already performed the procedure in Step 9. @@ -1517,8 +1517,8 @@ instructed in Disabling Authorization Checking in an Emergency. - - On all remaining (simple) file server machines, issue the + + On all remaining (simple) file server machines, issue the bos addkey command described in Step 4. Be sure to use the same values for afs_password and kvno as you used in that step. @@ -1530,4 +1530,4 @@ - \ No newline at end of file + diff --git a/doc/xml/AdminGuide/auagd015.xml b/doc/xml/AdminGuide/auagd015.xml index 73086cd7e..7aa2eefa0 100644 --- a/doc/xml/AdminGuide/auagd015.xml +++ b/doc/xml/AdminGuide/auagd015.xml @@ -1133,7 +1133,7 @@ - Issue the fs setcachesize command to set a new disk cache + Issue the fs setcachesize command to set a new disk cache size. @@ -2095,7 +2095,7 @@ - Issue the fs newcell command to add or change a cell's + Issue the fs newcell command to add or change a cell's entry in kernel memory. Repeat the command for each cell. diff --git a/doc/xml/AdminGuide/auagd017.xml b/doc/xml/AdminGuide/auagd017.xml index 8977047c1..9b1537b34 100644 --- a/doc/xml/AdminGuide/auagd017.xml +++ b/doc/xml/AdminGuide/auagd017.xml @@ -2912,7 +2912,7 @@ - (Optional) Change to the directory where the template + (Optional) Change to the directory where the template resides. This affects the type of pathname you must type in Step 6. % cd template_directory @@ -2935,8 +2935,8 @@ - - Issue the uss add command to create the account. Enter the + + Issue the uss add command to create the account. Enter the command on a single line; it appears here on multiple lines only for legibility. The uss add operation creates an Authentication Database entry. The Authentication @@ -3912,7 +3912,7 @@ - Issue the uss bulk command to create or delete accounts, or + Issue the uss bulk command to create or delete accounts, or both. Enter the command on a single line; it appears here on multiple lines only for legibility. The bulk operation always manipulates user entries in the Authentication Database. The Authentication Server diff --git a/doc/xml/AdminGuide/auagd018.xml b/doc/xml/AdminGuide/auagd018.xml index 52290f5f9..a3e6675ca 100644 --- a/doc/xml/AdminGuide/auagd018.xml +++ b/doc/xml/AdminGuide/auagd018.xml @@ -533,8 +533,8 @@ To create one user account with individual commands - - Decide on the value to assign to each of the following account components. If you are + + Decide on the value to assign to each of the following account components. If you are creating an authentication-only account, you need to pick only a username, AFS UID, and initial password. The username. By convention, the names of many components of the user account incorporate this name. For a @@ -590,8 +590,8 @@ - - Authenticate as an AFS identity with all of the following privileges. In the conventional + + Authenticate as an AFS identity with all of the following privileges. In the conventional configuration, the admin user account has them, or you possibly have a personal administrative account. (To increase cell security, it is best to create special privileged accounts for use only while performing administrative procedures; for further discussion, see An Overview of Administrative @@ -661,8 +661,8 @@ - - Issue the pts createuser command to create an entry in the + + Issue the pts createuser command to create an entry in the Protection Database. For a discussion of setting AFS UIDs, see Assigning AFS and UNIX UIDs that Match. If you are converting an existing UNIX account into an AFS account, also see Converting Existing UNIX Accounts. @@ -719,8 +719,8 @@ - - Issue the kas create command to create an entry in the + + Issue the kas create command to create an entry in the Authentication Database. To avoid having the user's temporary initial password echo visibly on the screen, omit the -initial_password argument; instead enter the password at the prompts that appear when you omit the argument, as shown in the following syntax specification. @@ -798,8 +798,8 @@ - - Issue the vos create command to create the user's volume. + + Issue the vos create command to create the user's volume. % vos create <machine name> <partition name> <volume name> \ [-maxquota <initial quota (KB)>] @@ -869,8 +869,8 @@ - - Issue the fs mkmount command to mount the volume in the + + Issue the fs mkmount command to mount the volume in the filespace and create the user's home directory. % fs mkmount <directory> <volume name> @@ -959,8 +959,8 @@ - - Issue the fs setacl command to set the ACL on the new home + + Issue the fs setacl command to set the ACL on the new home directory. At the least, create an entry that grants all permissions to the user, as shown. You can also use the command to edit or remove the entry that the vos create @@ -980,8 +980,8 @@ - - (Optional) Create configuration files and subdirectories in + + (Optional) Create configuration files and subdirectories in the new home directory. Possibilities include .login and .logout files, a shell-initialization file such as .cshrc, files to help with printing and mail delivery, and so on. @@ -998,8 +998,8 @@ directories). - - In Step 12 and Step 14, you + + In Step 12 and Step 14, you must know the user's AFS UID. If you had the Protection Server assign it in Step 3, you probably do not know it. If necessary, issue the pts examine command to display it. @@ -1030,8 +1030,8 @@ see Displaying Information from the Protection Database. - - Designate the user as the owner of the home directory and any files and subdirectories + + Designate the user as the owner of the home directory and any files and subdirectories created or moved in Step 9. Specify the owner by the AFS UID you learned in Step 11 rather than by username. This is necessary for new accounts because the user does not yet have an entry in your local machine's password file (/etc/passwd or equivalent). If you are @@ -1083,8 +1083,8 @@ - - Create or modify an entry for the new user in the local password file ( + Create or modify an entry for the new user in the local password file (/etc/passwd or equivalent) of each machine the user can log onto. Remember to make the UNIX UID the same as the AFS UID you learned in Step 11, and to fill the password field appropriately (for instructions, see Specifying Passwords in the Local Password File). @@ -1832,8 +1832,8 @@ - - Issue the pts listowned command to display the names of the + + Issue the pts listowned command to display the names of the groups the user owns. After you change the username in the Protection Database in Step 3, you must issue the pts rename command to change each group's owner prefix to match the new name, because the Protection Server does not automatically make this change. For a complete description of the @@ -1843,8 +1843,8 @@ - - Issue the pts rename command to change the user's name in + + Issue the pts rename command to change the user's name in the Protection Database. % pts rename <old name> <new name> @@ -2018,7 +2018,7 @@ - Issue the vos rename command to change the name of the + Issue the vos rename command to change the name of the user's volume. For complete syntax, see To rename a volume. % vos rename <old volume name> <new volume name> @@ -2048,8 +2048,8 @@ - - Issue the fs rmmount command to remove the existing mount + + Issue the fs rmmount command to remove the existing mount point. For the directory argument, specify the read/write path to the mount point, to avoid the failure that results when you attempt to delete a mount point from a read-only volume. % fs rmmount <directory> @@ -2072,8 +2072,8 @@ - - Issue the fs mkmount command to create a mount point for the + + Issue the fs mkmount command to create a mount point for the volume's new name. Specify the read/write path to the mount point for the directory argument, as in the previous step. For complete syntax, see Step 6 in To create one user account with individual commands. @@ -2189,8 +2189,8 @@ Volumes or the AFS Backup System as described in Backing Up Data. - - (Optional) If you intend to remove groups that the user owns + + (Optional) If you intend to remove groups that the user owns from the Protection Database after removing the user's entry, issue the pts listowned command to display them. For complete instructions, see Displaying Information from the Protection Database. @@ -2198,8 +2198,8 @@ - - (Optional) Issue the pts + + (Optional) Issue the pts delete command to remove the groups the user owns. However, if it is likely that other users have placed the groups on the ACLs of directories they own, it is best not to remove them. % pts delete <user or group name or id>+ @@ -2295,8 +2295,8 @@ - - Issue the vos listvldb command to display the site of the + + Issue the vos listvldb command to display the site of the user's home volume in preparation for removing it. By convention, user volumes are named user.username. % vos listvldb <volume name or ID> @@ -2352,7 +2352,7 @@ - Issue the vos remove command to remove the user's volume. It + Issue the vos remove command to remove the user's volume. It automatically removes the backup version of the volume, if it exists. It is not conventional to replicate user volumes, so the command usually also completely removes the volume's entry from the Volume Location Database (VLDB). If there are ReadOnly replicas of the volume, you must repeat the vos remove command to remove each @@ -2426,7 +2426,7 @@ - Issue the fs rmmount command to remove the volume's mount + Issue the fs rmmount command to remove the volume's mount point. If you mounted the user's backup volume as a subdirectory of the home directory, then this command is sufficient to @@ -2492,7 +2492,7 @@ - Issue the pts delete command to remove the user's Protection + Issue the pts delete command to remove the user's Protection Database entry. A complete description of this command appears in Step 5. % pts delete <user or group name or id> @@ -2517,4 +2517,4 @@ - \ No newline at end of file + diff --git a/doc/xml/AdminGuide/auagd019.xml b/doc/xml/AdminGuide/auagd019.xml index 2c8e737f5..c151f2e86 100644 --- a/doc/xml/AdminGuide/auagd019.xml +++ b/doc/xml/AdminGuide/auagd019.xml @@ -896,7 +896,7 @@ - Issue the pts membership command to display the list of + Issue the pts membership command to display the list of groups to which a user or machine belongs, or the list of users and machines that belong to a group. % pts membership <user or group name or id>+ @@ -3133,4 +3133,4 @@ - \ No newline at end of file + diff --git a/doc/xml/AdminGuide/auagd020.xml b/doc/xml/AdminGuide/auagd020.xml index 7b279ebb0..2363cb5a2 100644 --- a/doc/xml/AdminGuide/auagd020.xml +++ b/doc/xml/AdminGuide/auagd020.xml @@ -1385,7 +1385,7 @@ - Issue the fs copyacl command to copy a source ACL to the ACL + Issue the fs copyacl command to copy a source ACL to the ACL on one or more destination directories. (The command appears here on two lines only for legibility.) % fs copyacl -fromdir <source directory> -todir <destination directory>+ \ [-clear] @@ -1701,4 +1701,4 @@ - \ No newline at end of file + diff --git a/doc/xml/AdminGuide/auagd021.xml b/doc/xml/AdminGuide/auagd021.xml index 3ad9eed78..c98484350 100644 --- a/doc/xml/AdminGuide/auagd021.xml +++ b/doc/xml/AdminGuide/auagd021.xml @@ -455,7 +455,7 @@ - Issue the kas examine command to display an entry from the + Issue the kas examine command to display an entry from the Authentication Database. The Authentication Server performs its own authentication rather than accepting your existing AFS token. By default, @@ -931,4 +931,4 @@ - \ No newline at end of file + diff --git a/doc/xml/AdminGuide/auagd022.xml b/doc/xml/AdminGuide/auagd022.xml index 73b9c0e88..107fece0f 100644 --- a/doc/xml/AdminGuide/auagd022.xml +++ b/doc/xml/AdminGuide/auagd022.xml @@ -2,6 +2,7 @@ Managing the NFS/AFS Translator + NFS/AFS Translator @@ -12,7 +13,7 @@ NFS/AFS - The NFS(R)/AFS(R) Translator enables users working on NFS client machines to access, create and remove files stored in AFS. + 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. @@ -470,8 +471,8 @@ cell. - - Modify the file that controls mounting of directories on the machine by remote + + Modify the file that controls mounting of directories on the machine by remote NFS clients. etc/exports file @@ -535,8 +536,8 @@ for the entire AFS filespace; before, it is a local directory like any other. - - Modify the afsd command in the AFS initialization file to + + Modify the afsd command in the AFS initialization file to include the -rmtsys flag. For system types other than IRIX, the instructions in the OpenAFS Quick Beginnings for @@ -750,8 +751,8 @@ - - Modify the machine's file systems registry file (/etc/fstab + + Modify the machine's file systems registry file (/etc/fstab or equivalent) to include a command that mounts a translator machine's /afs directory. To verify the correct syntax of the mount command, see the operating system's mount(5) manual page. The following example includes options that are appropriate on many system @@ -815,8 +816,8 @@ - - (Optional) If appropriate, create the + (Optional) If appropriate, create the /.AFSSERVER file to set the AFSSERVER environment variable for all of the machine's users. For a discussion, see Setting the AFSSERVER and AFSCONF Environment Variables. Place a single line in the file, specifying the fully-qualified hostname of the translator machine that is to serve as the remote @@ -824,8 +825,8 @@ 4. - - (Optional) If appropriate, create the + (Optional) If appropriate, create the /.AFSCONF file to set the AFSCONF environment variable for all of the machine's users. For a discussion, see Setting the AFSSERVER and AFSCONF Environment Variables. Place a single line in the file, specifying the name of the directory where the CellServDB and or Administering User Accounts. - - Modify the user's PATH environment variable to include the pathname of AFS binaries, such as + + Modify the user's PATH environment variable to include the pathname of AFS binaries, such as /afs/cellname/sysname/usr/afsws/bin. If the user works on NFS client machines of different system types, considering replacing the specific sysname value with the @sys variable. The PATH variable is @@ -1169,4 +1170,4 @@ - \ No newline at end of file + diff --git a/doc/xml/AdminGuide/auagd025.xml b/doc/xml/AdminGuide/auagd025.xml index cbd865d0e..442987bc5 100644 --- a/doc/xml/AdminGuide/auagd025.xml +++ b/doc/xml/AdminGuide/auagd025.xml @@ -4,7 +4,7 @@ This Appendix provides a complete listing of the AFS events that can be audited on AIX file server machines. See Chapter Monitoring and Auditing AFS Performance for instructions on auditing AFS events on AIX file server - machines. + machines. Introduction @@ -2081,4 +2081,4 @@ - \ No newline at end of file + diff --git a/doc/xml/QuickStartUnix/appendix.xml b/doc/xml/QuickStartUnix/appendix.xml index c450cb98f..57cc4c63c 100644 --- a/doc/xml/QuickStartUnix/appendix.xml +++ b/doc/xml/QuickStartUnix/appendix.xml @@ -300,8 +300,8 @@ - - Issue the + + Issue the kas create command to create Authentication Database entries called admin and @@ -350,8 +350,8 @@ - - Issue the + + Issue the kas examine command to display the afs entry. The output includes a checksum generated by encrypting a constant with the @@ -381,8 +381,8 @@ - - Issue the + + Issue the kas setfields command to turn on the ADMIN flag in the admin entry. This enables the @@ -451,8 +451,8 @@ - - Issue the + + Issue the bos adduser command to add the admin user to the /usr/afs/etc/UserList file. @@ -483,8 +483,8 @@ - - Issue the + + Issue the bos addkey command to define the AFS server encryption key in the /usr/afs/etc/KeyFile file. @@ -520,8 +520,8 @@ - - Issue the + + Issue the bos listkeys command to verify that the checksum for the new key in the KeyFile file is the same as the @@ -595,8 +595,8 @@ ll name> - - Start the Authentication Server + + Start the Authentication Server (the kaserver process). % bos create <machine name> kaserver simple /usr/afs/bin/kaserver @@ -1673,4 +1673,4 @@ localusertwo:<thelocalusertwo'skey>:11500:0:99999:7::: - \ No newline at end of file + diff --git a/doc/xml/QuickStartUnix/auqbg005.xml b/doc/xml/QuickStartUnix/auqbg005.xml index fb52bada1..b976ad246 100644 --- a/doc/xml/QuickStartUnix/auqbg005.xml +++ b/doc/xml/QuickStartUnix/auqbg005.xml @@ -2,6 +2,7 @@ Installing the First AFS Machine + file server machine @@ -22,7 +23,7 @@ first AFS machine - This chapter describes how to install the first AFS machine in your cell, configuring it as both a file server machine and a + This chapter describes how to install the first AFS machine in your cell, configuring it as both a file server machine and a client machine. After completing all procedures in this chapter, you can remove the client functionality if you wish, as described in Removing Client Functionality. @@ -3340,8 +3341,8 @@ Password for you/admin@REALM: your_passw - - Issue the + + Issue the add_principal command to create Kerberos Database entries called admin and @@ -3386,8 +3387,8 @@ Password for you/admin@REALM: your_passw - - Issue the kadmin + + Issue the kadmin get_principal command to display the afs/<cell name> entry. @@ -3456,8 +3457,8 @@ Entry for principal afs/<cell name> with kvno 3 - - Issue the bos adduser command to add the + Issue the bos adduser command to add the admin user to the /usr/afs/etc/UserList file. This enables the admin user to issue privileged bos and vos commands. @@ -3478,8 +3479,8 @@ Entry for principal afs/<cell name> with kvno 3 - - Issue the + + Issue the asetkey command to set the AFS server encryption key in the /usr/afs/etc/KeyFile file. This key @@ -3518,8 +3519,8 @@ Entry for principal afs/<cell name> with kvno 3 - - Issue the + + Issue the bos listkeys command to verify that the key version number for the new key in the KeyFile file is the same as the key @@ -5530,8 +5531,8 @@ and so may already be available at your site. - - Issue the vos create command to create the + Issue the vos create command to create the root.cell volume. Then issue the fs mkmount command to mount it as a subdirectory of the /afs directory, where it serves as the root of your cell's local AFS filespace. Finally, issue the fs setacl command to create an ACL entry for the @@ -5630,8 +5631,8 @@ and so may already be available at your site. - - Issue the vos addsite command to define a replication site + + Issue the vos addsite command to define a replication site for both the root.afs and root.cell volumes. In each case, substitute for the partition name argument the partition where the volume's read/write version resides. When you install additional file server machines, it is a good idea to create replication sites on them @@ -5788,8 +5789,8 @@ and so may already be available at your site. volume for AFS binaries - - Issue the vos create command to create volumes for storing + + Issue the vos create command to create volumes for storing the AFS client binaries for this system type. The following example instruction creates volumes called sysname, sysname.usr, and sysname.usr.afsws. Refer to the OpenAFS Release @@ -5848,8 +5849,8 @@ and so may already be available at your site. - - Issue the fs setquota command to set an unlimited quota on + + Issue the fs setquota command to set an unlimited quota on the volume mounted at the /afs/cellname/sysname/usr/afsws directory. This enables you to copy all of the appropriate files from the CD-ROM into the volume without exceeding the volume's @@ -5910,8 +5911,8 @@ and so may already be available at your site. - - Create /usr/afsws on the local disk as a symbolic link to the + + Create /usr/afsws on the local disk as a symbolic link to the directory /afs/cellname/@sys/usr/afsws. You can specify the actual system name instead of @sys if you wish, but the advantage of using @sys is that it @@ -6474,8 +6475,8 @@ and so may already be available at your site. - - If this machine is going to remain an AFS client after you complete the installation, verify + + If this machine is going to remain an AFS client after you complete the installation, verify that the local /usr/vice/etc/CellServDB file includes an entry for each foreign cell. diff --git a/doc/xml/QuickStartUnix/auqbg006.xml b/doc/xml/QuickStartUnix/auqbg006.xml index c90a9c627..b47135094 100644 --- a/doc/xml/QuickStartUnix/auqbg006.xml +++ b/doc/xml/QuickStartUnix/auqbg006.xml @@ -2,6 +2,7 @@ Installing Additional Server Machines + instructions @@ -20,7 +21,7 @@ file server machine, additional - Instructions for the following procedures appear in the indicated section of this chapter. + Instructions for the following procedures appear in the indicated section of this chapter. Installing an Additional File Server Machine @@ -58,13 +59,14 @@ your operating system, either on the local filesystem or via an NFS mount of the distribution's contents. - + requirements file server machine (additional) + Installing an Additional File Server Machine @@ -1063,8 +1065,8 @@ - - Create a directory called + Create a directory called /vicepxx for each AFS server partition you are configuring (there must be at least one). Repeat the command for each partition. # mkdir /vicepxx @@ -1883,8 +1885,8 @@ - - If you run a system control machine, create the + If you run a system control machine, create the upclientetc process as an instance of the client portion of the Update Server. It accepts updates of the common configuration files stored in the system control machine's /usr/afs/etc directory from the upserver process (server portion of the Update Server) running on @@ -1928,8 +1930,8 @@ - - Create an instance of the Update + + Create an instance of the Update Server to handle distribution of the file server binaries stored in the /usr/afs/bin directory. If your architecture using a package management system @@ -2945,8 +2947,8 @@ - - Verify that /usr/afs and its subdirectories on the new + + Verify that /usr/afs and its subdirectories on the new file server machine meet the ownership and mode bit requirements outlined in Protecting Sensitive AFS Directories. If necessary, use the chmod command to correct the mode bits. @@ -3164,8 +3166,8 @@ - - Issue the bos addhost command to add the new database server + + Issue the bos addhost command to add the new database server machine to the /usr/afs/etc/CellServDB file on existing server machines (as well as the new database server machine itself). @@ -3202,8 +3204,8 @@ - - Add the new database server machine to your cell's central + Add the new database server machine to your cell's central CellServDB source file, if you use one. The standard location is /afs/cellname/common/etc/CellServDB. @@ -3232,8 +3234,8 @@ - - If this machine's IP address is lower than any existing database server machine's, update + + If this machine's IP address is lower than any existing database server machine's, update every client machine's /usr/vice/etc/CellServDB file and kernel memory list to include this machine. (If this machine's IP address is not the lowest, it is acceptable to wait until Step 12.) @@ -3270,7 +3272,7 @@ for an additional installation step. - + Backup Server starting @@ -3281,7 +3283,7 @@ new db-server machine - Start the Backup Server (the buserver process). You must + Start the Backup Server (the buserver process). You must perform other configuration procedures before actually using the AFS Backup System, as detailed in the OpenAFS Administration Guide. % bos create <machine name> buserver simple /usr/afs/bin/buserver @@ -3300,8 +3302,8 @@ - - Start the Protection Server (the ptserver process). + + Start the Protection Server (the ptserver process). % bos create <machine name> ptserver simple /usr/afs/bin/ptserver @@ -3319,8 +3321,8 @@ - - Start the Volume Location (VL) Server (the vlserver + + Start the Volume Location (VL) Server (the vlserver process). % bos create <machine name> vlserver simple /usr/afs/bin/vlserver @@ -3348,8 +3350,8 @@ - - Issue the bos restart command on every database server + + Issue the bos restart command on every database server machine in the cell, including the new machine. The command restarts the Authentication, Backup, Protection, and VL Servers, which forces an election of a new Ubik coordinator for each process. The new machine votes in the election and is considered as a potential new coordinator. @@ -3379,13 +3381,13 @@ - - If you did not update the CellServDB file on client machines + + If you did not update the CellServDB file on client machines in Step 6, do so now. - - If you wish to participate in the AFS + + If you wish to participate in the AFS global name space, send the new database server machine's name and IP address to grand.central.org. Do so, by emailing an updated CellServDB fragment for your cell @@ -3498,8 +3500,8 @@ - - If your cell is included in the global + + If your cell is included in the global CellServDB, send the revised list of your cell's database server machines to grand.central.org @@ -3510,8 +3512,8 @@ machine. - - Remove the decommissioned machine from your cell's central + Remove the decommissioned machine from your cell's central CellServDB source file, if you use one. The conventional location is /afs/cellname/common/etc/CellServDB. @@ -3542,8 +3544,8 @@ - - Update every client machine's /usr/vice/etc/CellServDB file + + Update every client machine's /usr/vice/etc/CellServDB file and kernel memory list to exclude this machine. Altering the CellServDB file and kernel memory list before stopping the actual database server processes avoids possible time-out delays that result when users send requests to a decommissioned database server machine that is still listed in the file. @@ -3574,8 +3576,8 @@ - - Issue the bos removehost command to remove the + + Issue the bos removehost command to remove the decommissioned database server machine from the /usr/afs/etc/CellServDB file on server machines. @@ -3631,8 +3633,8 @@ - - Issue the bos stop command to stop the database server + + Issue the bos stop command to stop the database server processes on the machine, by substituting its fully-qualified hostname for the machine name argument. The command changes each process's status in the /usr/afs/local/BosConfig file to NotRun, but does not remove its @@ -3661,8 +3663,8 @@ - - (Optional) Issue the bos + + (Optional) Issue the bos delete command to remove the entries for database server processes from the BosConfig file. This step is unnecessary if you plan to restart the database server functionality on this machine in future. @@ -3692,8 +3694,8 @@ - - Issue the bos restart command on every database server + + Issue the bos restart command on every database server machine in the cell, to restart the Backup, Protection, and VL Servers. This forces the election of a Ubik coordinator for each process, ensuring that the remaining database server processes recognize that the machine is no longer a database server. diff --git a/doc/xml/QuickStartUnix/auqbg007.xml b/doc/xml/QuickStartUnix/auqbg007.xml index 5b27d9fdf..a1fb9c331 100644 --- a/doc/xml/QuickStartUnix/auqbg007.xml +++ b/doc/xml/QuickStartUnix/auqbg007.xml @@ -2,6 +2,7 @@ Installing Additional Client Machines + instructions @@ -16,7 +17,7 @@ client machine - This chapter describes how to install AFS client machines after you have installed the first AFS machine. Some parts of the + This chapter describes how to install AFS client machines after you have installed the first AFS machine. Some parts of the installation differ depending on whether or not the new client is of the same AFS system type (uses the same AFS binaries) as a previously installed client machine. overview @@ -2763,8 +2764,8 @@ - - Issue the vos create command to create volumes for storing + + Issue the vos create command to create volumes for storing the AFS client binaries for this system type. The following example instruction creates volumes called sysname, sysname.usr, and sysname.usr.afsws. Refer to the OpenAFS Release @@ -2823,8 +2824,8 @@ - - Copy the contents of the indicated + + Copy the contents of the indicated directories from the OpenAFS binary distribution into the /afs/cellname/sysname/usr/afsws directory. @@ -2863,8 +2864,8 @@ - - Perform this step on the new client machine even if you have performed the previous steps + + Perform this step on the new client machine even if you have performed the previous steps on another machine. Create /usr/afsws on the local disk as a symbolic link to the directory /afs/cellname/@sys/usr/afsws. You can specify the actual system name instead of - - Working in the + Working in the /afs/.cellname/afs directory on a machine of the system type for which you are building AFS, issue the make install command. diff --git a/doc/xml/ReleaseNotesWindows/relnotes.xml b/doc/xml/ReleaseNotesWindows/relnotes.xml index 58bf2a2ea..4ace06f22 100644 --- a/doc/xml/ReleaseNotesWindows/relnotes.xml +++ b/doc/xml/ReleaseNotesWindows/relnotes.xml @@ -47,7 +47,7 @@ a Windows Installer package (.msi) that is built using the open source WiX Toolkit. The MSI can be customized for organizations via the use of MSI Transforms (see - MSI Deployment Guide) + MSI Deployment Guide) @@ -173,8 +173,8 @@ It is important to note that AFS file servers are character-set agnostic. All file system object names are stored as octet strings without any character set tagging. If a file system object is created using OEM Code Page 858 and then interpreted as UTF-8 it is likely that the object name will appear to be gibberish. OpenAFS for Windows goes to great lengths to ensure that the object name is converted to a form that will permit the user to rename the object using Unicode. Accessing UTF-8 names on UNIX systems that have the locale set to one of the ISO Latin character sets will result in the UTF-8 strings appearing to be gibberish. Neither UNIX AFS nor Microsoft Windows 2000 systems can perform Unicode Normalization for string comparisons. Although it is possible to store and read Unicode object names, it is possible that a user may not be able to open an object by typing the name of the object at the keyboard. GUI point and click operations should permit any object to be accessed. -
- 3.2. Requirements for Kerberos v5 Authentication +
+ 3.2. Requirements for Kerberos v5 Authentication kerberos for windows @@ -229,8 +229,8 @@ Note that the OpenAFS 1.4.x servers permit the use of a secondary realm name that can be treated as equivalent to the cell name for authentication. This functionality can be used to avoid the need for the krb524 service if and only if both realms are managed by the same administrative entity.
-
- 3.2.3. Network Identity Manager Provider +
+ 3.2.3. Network Identity Manager Provider network identity manager @@ -1304,8 +1304,8 @@ Prior to the 1.5.31 release, out of quota errors were reported to the calling application as an out of space error. As of 1.5.31, an out of space error will indicate that the partition on which the volume is located is in fact out of space. Whereas an out of quota error indicates that the user does not have permission to allocate additional space.
-
- 3.48. Linked Cells +
+ 3.48. Linked Cells linked cells @@ -1348,8 +1348,8 @@ aklog and Network Identity Manager will automatically obtain tokens for the linked cell when tokens for the other cell is specified.
-
- 3.49 Registry Configuration for AFS Volume Database Servers +
+ 3.49 Registry Configuration for AFS Volume Database Servers vldb server locations @@ -1420,13 +1420,14 @@ How to Troubleshoot Problems with OpenAFS for Windows + debugging troubleshooting - OpenAFS for Windows provides a wide range of tools to assist you in debugging problems. The techniques available to you are varied because of the wide range of issues that have been discovered over the years. + OpenAFS for Windows provides a wide range of tools to assist you in debugging problems. The techniques available to you are varied because of the wide range of issues that have been discovered over the years.
4.1. pioctl debugging ( <link linkend="Value_IoctlDebug">IoctlDebug</link> registry key) @@ -1657,12 +1658,13 @@ </para> </section> </chapter> - <chapter id="chap_5"> - <title id="Reporting_Bugs">Reporting Bugs + + Reporting Bugs + bug reports - Bug reports should be sent to + Bug reports should be sent to openafs-bugs@openafs.org. Please include as much information as possible about the issue. If you are reporting a crash, please install the debugging symbols by re-running the installer. If a dump file is available for the problem, %WINDIR%\TEMP\afsd.dmp, include it along with the AFS Client Trace file %WINDIR%\TEMP\afsd.log. The AFS Client startup log is %WINDIR%\TEMP\afsd_init.log. Send the last continuous block of log information from this file. Configuring DrWatson to generate dump files for crashes: @@ -1710,16 +1712,17 @@ How to Contribute to the Development of OpenAFS for Windows + contributing to OpenAFS - Contributions to the development of OpenAFS for Windows are continuously needed. Contributions may take many forms including cash donations, support contracts, donated developer time, and even donated tech writer time. + Contributions to the development of OpenAFS for Windows are continuously needed. Contributions may take many forms including cash donations, support contracts, donated developer time, and even donated tech writer time.
6.1. The USENIX OpenAFS Fund + USENIX OpenAFS Fund - USENIX, a 501c3 non-profit corporation, has formed the USENIX OpenAFS Fund in order to accept tax deductible donations on behalf of the OpenAFS Elders. The donated funds will be allocated by the OpenAFS Elders to fund OpenAFS development, documentation, project management, and maintaining openafs.org. @@ -1747,10 +1750,10 @@
6.2. Secure Endpoints Inc. + Secure Endpoints Inc. - Secure Endpoints Inc. provides development and support services for OpenAFS for Windows and MIT Kerberos for Windows. Donations provided to Secure Endpoints Inc. for the development of OpenAFS are used to cover the OpenAFS gatekeeper responsibilities; providing support to the OpenAFS community via the OpenAFS mailing lists; and furthering development of desired features that are either too small to be financed by development contracts. @@ -1791,15 +1794,15 @@ MSI Deployment Guide - - msi deployment - - - msi transforms -
- 7.1. Introduction - A MSI installer option is available for those who wish to use Windows Installer for installing OpenAFS and for organizations that wish to deploy OpenAFS through Group Policy. The first version of OpenAFS for Windows available as an MSI was 1.3.65. + 7.1. Introduction + + msi deployment + + + msi transforms + + A MSI installer option is available for those who wish to use Windows Installer for installing OpenAFS and for organizations that wish to deploy OpenAFS through Group Policy. The first version of OpenAFS for Windows available as an MSI was 1.3.65. This document provides a guide for authoring transforms used to customize the MSI package for a particular organization. Although many settings can be deployed via transforms, in an Active Directory environment it is advisable to deploy registry settings and configuration files through group policy and/or startup scripts so that machines where OpenAFS for Windows is already installed will pick up these customizations.
7.1.1 Requirements @@ -2501,8 +2504,8 @@ -
- 7.2.3.1 Components for Configuration Files +
+ 7.2.3.1 Components for Configuration Files CellServDB: 'cpf_CellServDB' (ID {D5BA4C15-DBEC-4292-91FC-B54C30F24F2A})
@@ -2811,8 +2814,8 @@ Registry Values -
- A.1. Service parameters +
+ A.1. Service parameters The service parameters primarily affect the behavior of the AFS client service (afsd_service.exe).
Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] @@ -2828,12 +2831,11 @@ LAN adapter number to use. This is the lana number of the LAN adapter that the SMB server should bind to. If unspecified or set to -1, a LAN adapter with named 'AFS' or a loopback adapter will be selected. If neither are present, then all available adapters will be bound to. When binding to a non-loopback adapter, the NetBIOS name hostname%-AFS' will be used (where %hostname% is the NetBIOS name of the host truncated to 11 characters). Otherwise, the NetBIOS name will be 'AFS'.
- - <anchor id="Value_CacheSize" />Value: CacheSize + Value: CacheSize CacheSize - Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] + Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] Type: DWORD Default: 98304 (CM_CONFIGDEFAULT_CACHESIZE) Variable: cm_initParams.cacheSize @@ -2876,8 +2878,7 @@ Stats - - Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] + Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] Type: DWORD Default: 10000 (CM_CONFIGDEFAULT_STATS) Variable: cm_initParams.nStatCaches @@ -2920,8 +2921,7 @@ Variable: cm_initParams.nCells LogoffPreserveTokens - - Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] + Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] Type: DWORD {1,0} @@ -2954,8 +2954,7 @@ Variable: cm_rootVolumeName /afs - - Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] + Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] Type: REG_SZ @@ -2973,8 +2972,7 @@ Variable: cm_mountRoot AFSCache - - Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] + Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] Type: REG_SZ or REG_EXPAND_SZ @@ -2989,8 +2987,7 @@ Variable: cm_CachePath NonPersistentCaching - - Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] + Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] Type: DWORD [0..1] @@ -3048,8 +3045,7 @@ Variable: traceOnPanic \\AFS - - Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] + Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] Type: REG_EXPAND_SZ @@ -3095,8 +3091,7 @@ Variable: reportSessionStartups TraceBufferSize - - Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] + Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] Type: DWORD @@ -3111,8 +3106,7 @@ Variable: traceBufSize SysName - - Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] + Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] Type: REG_SZ @@ -3133,8 +3127,7 @@ Variable: cm_sysName fs setcrypt - - Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] + Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] Type: DWORD {1,0} @@ -3155,8 +3148,7 @@ Variable: cryptall SRV DNS records - - Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] + Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] Type: DWORD {1,0} @@ -3174,8 +3166,7 @@ Variable: cm_dnsEnabled dynroot - - Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] + Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] Type: DWORD {1,0} @@ -3190,8 +3181,7 @@ Variable: cm_freelanceEnabled HideDotFiles - - Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] + Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] Type: DWORD {1,0} @@ -3239,8 +3229,7 @@ Variable: smb_maxVCPerServer workstation cell name - - Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] + Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] Type: REG_SZ @@ -3302,8 +3291,7 @@ Variable: rx_extraPackets RxMaxMTU - - Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] + Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] Type: DWORD @@ -3334,8 +3322,7 @@ Variable: rx_nojumbo ConnDeadTimeout - - Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] + Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] Type: DWORD @@ -3421,8 +3408,7 @@ Variable: rx_nojumbo TraceOption - - Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] + Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] Type: DWORD {0-15} @@ -3451,8 +3437,7 @@ Default: 1 NoFindLanaByName - - Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] + Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] Type: DWORD {0, 1} @@ -3476,8 +3461,7 @@ Default: <no default> SMBAuthType - - Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] + Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] Type: DWORD {0..2} @@ -3503,8 +3487,7 @@ The default is Extended authentication MaxLogSize - - Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] + Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] Type: DWORD {0 .. MAXDWORD} @@ -3627,8 +3610,7 @@ Default: 7001 EnableServerLocks - - Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] + Regkey: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters] Type: DWORD {0, 1, 2} @@ -3769,8 +3751,8 @@ Default: 262144
-
- Regkey: [HKLM\SOFTWARE\OpenAFS\Client] +
+ Regkey: [HKLM\SOFTWARE\OpenAFS\Client]
Value: CellServDBDir @@ -3779,8 +3761,7 @@ Default: 262144 CellServDBDir - - Regkey: [HKLM\SOFTWARE\OpenAFS\Client] + Regkey: [HKLM\SOFTWARE\OpenAFS\Client] Type: REG_SZ @@ -3792,8 +3773,7 @@ Default: <not defined> VerifyServiceSignature - - Regkey: [HKLM\SOFTWARE\OpenAFS\Client] + Regkey: [HKLM\SOFTWARE\OpenAFS\Client] Type: REG_DWORD @@ -3808,8 +3788,7 @@ Default: 0x1 path ioctl debugging - - Regkey: [HKLM\SOFTWARE\OpenAFS\Client] + Regkey: [HKLM\SOFTWARE\OpenAFS\Client] Type: REG_DWORD @@ -3824,8 +3803,7 @@ Default: 0x0 MiniDumpType - - Regkey: [HKLM\SOFTWARE\OpenAFS\Client] + Regkey: [HKLM\SOFTWARE\OpenAFS\Client] Type: REG_DWORD @@ -3887,8 +3865,7 @@ MiniDumpWithCodeSegs = 0x00002000 EnableSMBAsyncStore - - Regkey: [HKLM\SOFTWARE\OpenAFS\Client] + Regkey: [HKLM\SOFTWARE\OpenAFS\Client] Type: REG_DWORD @@ -3900,8 +3877,7 @@ Default: 0x1 SMBAsyncStoreSize - - Regkey: [HKLM\SOFTWARE\OpenAFS\Client] + Regkey: [HKLM\SOFTWARE\OpenAFS\Client] Type: REG_DWORD @@ -3919,8 +3895,7 @@ Default: 32 character sets - - Regkey: [HKLM\SOFTWARE\OpenAFS\Client] + Regkey: [HKLM\SOFTWARE\OpenAFS\Client] Type: REG_DWORD @@ -3946,8 +3921,8 @@ Default: <none> These values used to be stored in afsdsbmt.ini
-
- Regkey: [HKLM\SOFTWARE\OpenAFS\Client\CellServDB] +
+ Regkey: [HKLM\SOFTWARE\OpenAFS\Client\CellServDB] CellServDB @@ -4032,8 +4007,8 @@ Default: <none> A text string that can be displayed to end users to describe the server.
-
- Regkey: [HKLM\SOFTWARE\OpenAFS\Client\Freelance] +
+ Regkey: [HKLM\SOFTWARE\OpenAFS\Client\Freelance] Freelance @@ -4053,8 +4028,8 @@ Default: <none> These values used to be stored in afs_freelance.ini
-
- Regkey: [HKLM\SOFTWARE\OpenAFS\Client\Freelance\Symlinks] +
-
- Regkey: -[HKLM\SOFTWARE\OpenAFS\Client\Server Preferences\VLDB] +
+ Regkey: [HKLM\SOFTWARE\OpenAFS\Client\Server Preferences\VLDB] Server Preferences @@ -4282,8 +4256,8 @@ NSIS: %WINDIR%\SYSTEM32\afslogon.dll
-
- A.2.1 Domain specific configuration keys for the Network Provider +
+ A.2.1 Domain specific configuration keys for the Network Provider domain logon configuration @@ -4317,8 +4291,8 @@ NSIS: %WINDIR%\SYSTEM32\afslogon.dll
A.2.1.1 Domain Specific Configuration Values -
- Regkeys: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider] + <section id="Domain_Specific_Regkeys"> + <title>Regkeys: [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider] [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain] [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\"domain name"] [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LOCALHOST] @@ -4327,8 +4301,7 @@ NSIS: %WINDIR%\SYSTEM32\afslogon.dll LogonOptions - - [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain] + [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain] [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\<domain name>] [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LOCALHOST] Type: DWORD @@ -4427,8 +4400,7 @@ NSIS/WiX: (not set) Realm - - [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain] + [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain] [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\<domain name>] [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LOCALHOST] Type: REG_SZ @@ -4442,8 +4414,7 @@ NSIS: <not set> TheseCells - - [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain] + [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain] [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\<domain name>] [HKLM\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\NetworkProvider\Domain\LOCALHOST] Type: REG_MULTI_SZ @@ -4552,8 +4523,7 @@ Function: InitApp(), Main_OnCheckTerminate() EnableKFW - - Regkey: [HKLM\SOFTWARE\OpenAFS\Client] + Regkey: [HKLM\SOFTWARE\OpenAFS\Client] Regkey: [HKCU\SOFTWARE\OpenAFS\Client] Type: DWORD {0, 1} @@ -4585,8 +4555,7 @@ Function: KFW_accept_dotted_usernames() Use524 - - Regkey: [HKLM\SOFTWARE\OpenAFS\Client] + Regkey: [HKLM\SOFTWARE\OpenAFS\Client] Regkey: [HKCU\SOFTWARE\OpenAFS\Client] Type: DWORD {0, 1} @@ -4602,8 +4571,7 @@ Function: KFW_use_krb524() AfscredsShortcutParams - - Regkey: [HKLM\SOFTWARE\OpenAFS\Client] + Regkey: [HKLM\SOFTWARE\OpenAFS\Client] Regkey: [HKCU\SOFTWARE\OpenAFS\Client] Type: REG_SZ @@ -4761,4 +4729,4 @@ sgml-exposed-tags:nil sgml-local-catalogs:nil sgml-local-ecat-files:nil End: - --> \ No newline at end of file + --> diff --git a/doc/xml/UserGuide/auusg009.xml b/doc/xml/UserGuide/auusg009.xml index ac0c15a0b..916244380 100644 --- a/doc/xml/UserGuide/auusg009.xml +++ b/doc/xml/UserGuide/auusg009.xml @@ -35,8 +35,8 @@ - - Issue the tokens command to verify that you have valid + + Issue the tokens command to verify that you have valid tokens. For complete instructions, see To Display Your Tokens. % tokens @@ -57,8 +57,8 @@ - - Issue the fs checkservers command to check the + + Issue the fs checkservers command to check the status of file server machines. For complete instructions, see Checking the Status of Server Machines. % fs checkservers & @@ -93,8 +93,8 @@ - - Issue the fs listacl command to verify that you have + + Issue the fs listacl command to verify that you have the permissions you need for accessing, copying, or saving the file. For complete instructions, see To display an ACL. % fs listacl <dir/file path> @@ -141,8 +141,8 @@ have the necessary permissions, proceed to Step 4. - - If copying a file, issue the fs listquota command to + + If copying a file, issue the fs listquota command to check whether the volume into which you are copying it, or the partition that houses that volume, is almost full. For saving, check the volume and partition that contain the directory into which you are saving the file. For complete instructions, see Displaying Volume Quota. diff --git a/doc/xml/UserGuide/auusg010.xml b/doc/xml/UserGuide/auusg010.xml index 7480a5e33..008f28837 100644 --- a/doc/xml/UserGuide/auusg010.xml +++ b/doc/xml/UserGuide/auusg010.xml @@ -66,7 +66,7 @@ To Authenticate on an Unsupported Operating System Log onto the NFS client machine using your NFS username. - Establish a connection to the NFS/AFS translator machine you are + Establish a connection to the NFS/AFS translator machine you are using (for example, using the telnet utility) and log onto it using your AFS username (which is normally the same as your NFS username). @@ -82,8 +82,8 @@ % klog -setpag - - Issue the knfs command to associate your AFS tokens + + Issue the knfs command to associate your AFS tokens with your UNIX UID on the NFS client machine where you are working. This enables the Cache Manager on the translator machine to use the tokens properly when you access AFS from the NFS client machine. If your NFS client machine is a system type for which AFS defines a system name, it can make sense @@ -114,7 +114,7 @@ Specifies your NFS client machine's system type name. - (Optional) Log out from the + (Optional) Log out from the translator machine, but do not unauthenticate. Work on the NFS client machine, accessing AFS as necessary. diff --git a/doc/xml/UserGuide/auusg011.xml b/doc/xml/UserGuide/auusg011.xml index d29b2cf4e..4f855bbbf 100644 --- a/doc/xml/UserGuide/auusg011.xml +++ b/doc/xml/UserGuide/auusg011.xml @@ -1,9 +1,10 @@ OpenAFS Command Syntax and Online Help + syntax of AFS commands described - The AFS commands available to you are used to authenticate, list AFS information, protect directories, create + The AFS commands available to you are used to authenticate, list AFS information, protect directories, create and manage groups, and create and manage ACLs. There are three general types of commands available to all AFS users: file server commands, protection server commands, and miscellaneous commands. This chapter discusses the syntax of these AFS commands, the rules that must be followed when issuing them, and ways of accessing help -- 2.39.5