jimzah/openafs
1
0
Fork 0
mirror of https://git.openafs.org/openafs.git synced 2025-01-18 15:00:12 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

doc-xml-20090513

Browse Source 
LICENSE IPL10
FIXES 124760

Remove generated HTML from the respository

Update XML to support autogeneration of Index files via XSLT

Add graphics referenced by generated HTML output

Add top level index.html used by the docs.openafs.org web site.

Add NTMakefile for AdminGuide, QuickStartUnix, and UserGuide
that utilizes XSLT to generate Windows HTMLHelp (.CHM) and
website appropriate HTML output.

In AdminGuide and UserGuide, relabel the documentation as OpenAFS
instead of IBM AFS.  Create a new revision entry for the OpenAFS
docs.

Incorporate updates to QuickStartUnix Appendix A
This commit is contained in:
Jeffrey Altman 2009-05-14 03:25:35 +00:00
parent 070f02923c
commit 9e8e080a5c
85 changed files with 567 additions and 160380 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

83
doc/xml/AdminGuide/NTMakefile Normal file
View File

@ -0,0 +1,83 @@
# 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

3305
doc/xml/AdminGuide/a33047.html
View File

File diff suppressed because it is too large Load Diff

1598
doc/xml/AdminGuide/a33826.html
View File

File diff suppressed because it is too large Load Diff

3822
doc/xml/AdminGuide/a34149.html
View File

File diff suppressed because it is too large Load Diff

2338
doc/xml/AdminGuide/a35965.html
View File

File diff suppressed because it is too large Load Diff

36
doc/xml/AdminGuide/auagd000.xml
View File

@ -22,15 +22,12 @@
<!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>
@ -39,23 +36,34 @@
</copyright>
<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
@ -107,5 +115,5 @@
&appendixB;
&appendixC;
&appendixD;
&index;
<index>Name Index</index>
</book>

18
doc/xml/AdminGuide/auagd005.xml
View File

@ -11,7 +11,7 @@
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">
@ -81,7 +81,7 @@
</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>
@ -94,22 +94,22 @@
<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
@ -121,7 +121,7 @@
</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
@ -130,7 +130,7 @@
</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

4
doc/xml/AdminGuide/auagd006.xml
View File

@ -1,6 +1,6 @@
<?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>
@ -1123,7 +1123,7 @@
<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>

54
doc/xml/AdminGuide/auagd007.xml
View File

@ -4,7 +4,7 @@
<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>
@ -118,7 +118,7 @@
<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>
@ -342,7 +342,7 @@
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>
@ -411,7 +411,7 @@
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
@ -675,11 +675,11 @@
<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
@ -688,7 +688,7 @@
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>
@ -1231,7 +1231,7 @@
<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
@ -1819,8 +1819,8 @@
</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>
@ -1844,7 +1844,7 @@
</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>
@ -1882,7 +1882,7 @@
<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
@ -1915,7 +1915,7 @@
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>
@ -1935,7 +1935,7 @@
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
@ -2168,7 +2168,7 @@
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
@ -2819,7 +2819,7 @@
<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>
@ -3027,7 +3027,7 @@
<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>
@ -3041,7 +3041,7 @@
<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
@ -3165,12 +3165,12 @@
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>
@ -3253,8 +3253,8 @@
<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>
@ -3413,7 +3413,7 @@
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>
@ -3478,7 +3478,7 @@
<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>
@ -3949,7 +3949,7 @@
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>
@ -4087,7 +4087,7 @@
<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">

58
doc/xml/AdminGuide/auagd008.xml
View File

@ -57,7 +57,7 @@
</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>
@ -1090,7 +1090,7 @@
<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>
@ -1174,7 +1174,7 @@
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>
@ -1396,7 +1396,7 @@
<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>
@ -1785,7 +1785,7 @@
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
@ -1883,7 +1883,7 @@
</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>
@ -1994,7 +1994,7 @@
<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
@ -2114,7 +2114,7 @@
<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>
@ -2370,7 +2370,7 @@
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>
@ -2422,7 +2422,7 @@
<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>
@ -2494,10 +2494,10 @@
</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
@ -2572,7 +2572,7 @@
<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
@ -2580,7 +2580,7 @@
<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
@ -2597,7 +2597,7 @@
<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
@ -2857,7 +2857,7 @@
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>
@ -3174,7 +3174,7 @@
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
@ -3273,7 +3273,7 @@
<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>
@ -3602,7 +3602,7 @@
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>
@ -3878,10 +3878,10 @@
@(#)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>
@ -3929,7 +3929,7 @@
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,
@ -4012,7 +4012,7 @@
<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>
@ -4022,7 +4022,7 @@
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
@ -4772,7 +4772,7 @@
<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>
@ -4801,7 +4801,7 @@
<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
@ -4830,7 +4830,7 @@
<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 &amp;
@ -5258,7 +5258,7 @@
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>
@ -5285,7 +5285,7 @@
<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

16
doc/xml/AdminGuide/auagd009.xml
View File

@ -134,7 +134,7 @@
<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>
@ -606,7 +606,7 @@
</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">
@ -767,7 +767,7 @@
<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>
@ -1007,7 +1007,7 @@
</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>
@ -1298,7 +1298,7 @@
</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">
@ -1444,7 +1444,7 @@
<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
@ -1703,7 +1703,7 @@
<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>
@ -1884,7 +1884,7 @@
<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

12
doc/xml/AdminGuide/auagd010.xml
View File

@ -1314,7 +1314,7 @@
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>
@ -1852,7 +1852,7 @@
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
@ -4284,7 +4284,7 @@
<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>
@ -5057,7 +5057,7 @@
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
@ -5068,7 +5068,7 @@
<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>
@ -5609,7 +5609,7 @@
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>

6
doc/xml/AdminGuide/auagd011.xml
View File

@ -617,7 +617,7 @@
<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>
@ -3317,7 +3317,7 @@ volume_set_name<emphasis role="bold">.</emphasis>dump_level_name<emphasis role="
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>
@ -3913,7 +3913,7 @@ volume_set_name<emphasis role="bold">.</emphasis>dump_level_name<emphasis role="
<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

8
doc/xml/AdminGuide/auagd012.xml
View File

@ -162,7 +162,7 @@
<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>
@ -2983,7 +2983,7 @@
<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
@ -4228,7 +4228,7 @@
<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>
@ -4477,7 +4477,7 @@
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

2
doc/xml/AdminGuide/auagd013.xml
View File

@ -2477,7 +2477,7 @@
<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

6
doc/xml/AdminGuide/auagd014.xml
View File

@ -209,7 +209,7 @@
</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>
@ -260,7 +260,7 @@
<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>
@ -534,7 +534,7 @@
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>

28
doc/xml/AdminGuide/auagd015.xml
View File

@ -23,7 +23,7 @@
</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>
@ -417,7 +417,7 @@
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
@ -507,7 +507,7 @@
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>
@ -538,7 +538,7 @@
<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>
@ -737,7 +737,7 @@
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>
@ -899,7 +899,7 @@
</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>
@ -910,7 +910,7 @@
<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
@ -1307,12 +1307,12 @@
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>
@ -1601,7 +1601,7 @@
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">
@ -1720,7 +1720,7 @@
<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
@ -2020,7 +2020,7 @@
<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>
@ -2760,7 +2760,7 @@
<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>
@ -3492,7 +3492,7 @@
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

12
doc/xml/AdminGuide/auagd016.xml
View File

@ -270,7 +270,7 @@
<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
@ -526,7 +526,7 @@
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
@ -575,7 +575,7 @@
<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>
@ -1001,7 +1001,7 @@
<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>
@ -1516,7 +1516,7 @@
<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>
@ -1610,7 +1610,7 @@
<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>

6
doc/xml/AdminGuide/auagd017.xml
View File

@ -3027,7 +3027,7 @@
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>
@ -3599,7 +3599,7 @@
</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>
@ -3651,7 +3651,7 @@
</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>

10
doc/xml/AdminGuide/auagd018.xml
View File

@ -551,7 +551,7 @@
<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>
@ -1231,7 +1231,7 @@
<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>
@ -1271,7 +1271,7 @@
</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>
@ -1618,7 +1618,7 @@
<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>
@ -1978,7 +1978,7 @@
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>

6
doc/xml/AdminGuide/auagd020.xml
View File

@ -678,7 +678,7 @@
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>
@ -891,7 +891,7 @@
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>
@ -1356,7 +1356,7 @@
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>

2
doc/xml/AdminGuide/auagd021.xml
View File

@ -206,7 +206,7 @@
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, see the <emphasis
role="bold">fileserver</emphasis> reference page in the <emphasis>IBM AFS Administration Reference</emphasis>. You can
role="bold">fileserver</emphasis> reference page in the <emphasis>OpenAFS Administration Reference</emphasis>. You can
grant additional permissions, or remove the <emphasis role="bold">l</emphasis> permission. However, the File Server always
implicitly grants the <emphasis role="bold">a</emphasis> permission to members of the group, even if you set the value of
the <emphasis role="bold">-implicit</emphasis> argument to <emphasis role="bold">none</emphasis>.</para>

16
doc/xml/AdminGuide/auagd022.xml
View File

@ -314,7 +314,7 @@
<para>To act as an NFS/AFS translator machine, a machine must configured as follows: <itemizedlist>
<listitem>
<para>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 <emphasis>IBM AFS Release Notes</emphasis>.</para>
possible restrictions in a specific release of AFS, see the <emphasis>OpenAFS Release Notes</emphasis>.</para>
</listitem>
<listitem>
@ -339,12 +339,12 @@
using NFS (the latter AFS kernel extensions file generally has the string <emphasis role="bold">nonfs</emphasis> 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 <emphasis>IBM AFS Quick Beginnings</emphasis> for
automatic selection of the correct file. See the instructions in the <emphasis>OpenAFS Quick Beginnings</emphasis> for
incorporating AFS into the kernel on each system type.</para>
<para>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 <emphasis>IBM AFS Quick Beginnings</emphasis> describes how to incorporate the AFS initialization
kernel extensions. The <emphasis>OpenAFS Quick Beginnings</emphasis> 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.</para>
<para>In addition, the AFS extensions must be loaded into the kernel before the <emphasis role="bold">afsd</emphasis> command
@ -361,7 +361,7 @@
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 <link linkend="HDRWQ600">Setting the AFSSERVER and AFSCONF Environment Variables</link>.</para>
<para>The instructions in the IBM AFS Quick Beginnings for configuring the Cache Manager explain how to add options such as
<para>The instructions in the OpenAFS Quick Beginnings for configuring the Cache Manager explain how to add options such as
the <emphasis role="bold">-rmtsys</emphasis> flag to the <emphasis role="bold">afsd</emphasis> 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 <emphasis>remote executor daemon</emphasis> does not consume many resources, so it is simplest to add it
@ -539,13 +539,13 @@
<para><anchor id="LIWQ605" />Modify the <emphasis role="bold">afsd</emphasis> command in the AFS initialization file to
include the <emphasis role="bold">-rmtsys</emphasis> flag.</para>
<para>For system types other than IRIX, the instructions in the <emphasis>IBM AFS Quick Beginnings</emphasis> for
<para>For system types other than IRIX, the instructions in the <emphasis>OpenAFS Quick Beginnings</emphasis> for
configuring the Cache Manager explain how to add the <emphasis role="bold">-rmtsys</emphasis> flag, for example by
adding it to the line in the script that defines the value for the OPTIONS variable.</para>
<para>On IRIX systems, the AFS initialization script automatically adds the <emphasis role="bold">-rmtsys</emphasis>
flag if you have activated the <emphasis role="bold">afsxnfs</emphasis> configuration variable as instructed in the
<emphasis>IBM AFS Quick Beginnings</emphasis> instructions for incorporating AFS extensions into the kernel. If the
<emphasis>OpenAFS Quick Beginnings</emphasis> instructions for incorporating AFS extensions into the kernel. If the
variable is not already activated, issue the following command.</para>
<programlisting>
@ -558,7 +558,7 @@
serve, it can be beneficial to add other arguments to the <emphasis role="bold">afsd</emphasis> command in the machine's
initialization file, such as the <emphasis role="bold">-daemons</emphasis> argument to set the number of background
daemons. See <link linkend="HDRWQ387">Administering Client Machines and the Cache Manager</link> and the <emphasis
role="bold">afsd</emphasis> reference page in the <emphasis>IBM AFS Administration Reference</emphasis>.</para>
role="bold">afsd</emphasis> reference page in the <emphasis>OpenAFS Administration Reference</emphasis>.</para>
</listitem>
<listitem>
@ -707,7 +707,7 @@
</itemizedlist></para>
<para>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 <emphasis>IBM AFS Release Notes</emphasis> list the
binaries are available) and able to access the AFS command binaries. The <emphasis>OpenAFS Release Notes</emphasis> list the
supported system types in each release.</para>
<para>In addition, the AFSSERVER and AFSCONF environment variables must be set appropriately, as discussed in <link

6
doc/xml/AdminGuide/auagd023.xml
View File

@ -36,8 +36,8 @@
the issuer omits the <emphasis role="bold">command_suite</emphasis> portion of the command name.</para>
<para>The <emphasis role="bold">operation_code</emphasis> tells the command interpreter and server process which action to
perform. Most command suites include several operation codes. The <emphasis>IBM AFS Administration Reference</emphasis>
describes each operation code in detail, and the <emphasis>IBM AFS Administration Guide</emphasis> describes how to use them
perform. Most command suites include several operation codes. The <emphasis>OpenAFS Administration Reference</emphasis>
describes each operation code in detail, and the <emphasis>OpenAFS Administration Guide</emphasis> describes how to use them
in the context of performing administrative tasks.</para>
<para>Several AFS commands do not belong to a suite and so their names do not have a <emphasis
@ -324,7 +324,7 @@
role="bold">/vicep</emphasis><replaceable>x</replaceable> or <emphasis
role="bold">/vicep</emphasis><replaceable>xx</replaceable>, 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 <emphasis
role="bold">/vicepa</emphasis>, the second <emphasis role="bold">/vicepb</emphasis>, and so on. The <emphasis>IBM AFS Quick
role="bold">/vicepa</emphasis>, the second <emphasis role="bold">/vicepb</emphasis>, and so on. The <emphasis>OpenAFS Quick
Beginnings</emphasis> explains how to configure and name a file server machine's partitions in preparation for storing AFS
volumes on them.</para>

10
doc/xml/AdminGuide/auagd026.xml
View File

@ -1703,7 +1703,7 @@
<ulink url="c3025.html#HDRWQ118" role="AEN5325">Maintaining the Server CellServDB File</ulink>
</secondaryie>
<secondaryie>importance to Ubik operation,
<ulink url="c3025.html#HDRWQ102" role="AEN4453">Replicating the AFS Administrative Databases</ulink>
<ulink url="c3025.html#HDRWQ102" role="AEN4453">Replicating the OpenAFS Administrative Databases</ulink>
</secondaryie>
<secondaryie>maintaining,
<ulink url="c3025.html#Header_138" role="AEN5295">To display an AFS binary's build level</ulink>
@ -3344,7 +3344,7 @@
<ulink url="c6449.html#HDRWQ156" role="AEN7037">About Starting and Stopping the Database Server Processes</ulink>
</secondaryie>
<secondaryie>need to run all on every database server machine,
<ulink url="c3025.html#HDRWQ102" role="AEN4450">Replicating the AFS Administrative Databases</ulink>
<ulink url="c3025.html#HDRWQ102" role="AEN4450">Replicating the OpenAFS Administrative Databases</ulink>
</secondaryie>
<secondaryie>restarting after adding entry to server CellServDB file,
<ulink url="c3025.html#HDRWQ120" role="AEN5452">To display a cell's database server machines</ulink>
@ -5745,7 +5745,7 @@
<ulink url="c667.html#HDRWQ54" role="AEN1884">Configuring Client Machines</ulink>
</secondaryie>
<secondaryie>protecting on file server machine,
<ulink url="c667.html#HDRWQ52" role="AEN1801">Replicating the AFS Administrative Databases</ulink>
<ulink url="c667.html#HDRWQ52" role="AEN1801">Replicating the OpenAFS Administrative Databases</ulink>
</secondaryie>
</indexentry>
@ -8143,7 +8143,7 @@
<ulink url="c3025.html#HDRWQ109" role="AEN4796">To restore an administrative database</ulink>
</secondaryie>
<secondaryie>protecting directories on local disk,
<ulink url="c667.html#HDRWQ52" role="AEN1798">Replicating the AFS Administrative Databases</ulink>
<ulink url="c667.html#HDRWQ52" role="AEN1798">Replicating the OpenAFS Administrative Databases</ulink>
</secondaryie>
<secondaryie>rebooting,
<ulink url="c3025.html#Header_160" role="AEN6362">To change a server machine's IP addresses</ulink>
@ -9180,7 +9180,7 @@
<ulink url="c3025.html#HDRWQ101" role="AEN4413">Administering Database Server Machines</ulink>
</secondaryie>
<secondaryie>requirements summarized,
<ulink url="c3025.html#HDRWQ102" role="AEN4447">Replicating the AFS Administrative Databases</ulink>
<ulink url="c3025.html#HDRWQ102" role="AEN4447">Replicating the OpenAFS Administrative Databases</ulink>
</secondaryie>
<secondaryie>server and client portions,
<ulink url="c3025.html#HDRWQ103" role="AEN4499">Configuring the Cell for Proper Ubik Operation</ulink>

1517
doc/xml/AdminGuide/book1.html
View File

File diff suppressed because it is too large Load Diff

8913
doc/xml/AdminGuide/c12776.html
View File

File diff suppressed because it is too large Load Diff

1550
doc/xml/AdminGuide/c130.html
View File

File diff suppressed because it is too large Load Diff

10575
doc/xml/AdminGuide/c15383.html
View File

File diff suppressed because it is too large Load Diff

7104
doc/xml/AdminGuide/c18360.html
View File

File diff suppressed because it is too large Load Diff

3231
doc/xml/AdminGuide/c20494.html
View File

File diff suppressed because it is too large Load Diff

7090
doc/xml/AdminGuide/c21473.html
View File

File diff suppressed because it is too large Load Diff

4202
doc/xml/AdminGuide/c23832.html
View File

File diff suppressed because it is too large Load Diff

9663
doc/xml/AdminGuide/c24913.html
View File

File diff suppressed because it is too large Load Diff

5718
doc/xml/AdminGuide/c27596.html
View File

File diff suppressed because it is too large Load Diff

5238
doc/xml/AdminGuide/c29323.html
View File

File diff suppressed because it is too large Load Diff

3951
doc/xml/AdminGuide/c31274.html
View File

File diff suppressed because it is too large Load Diff

1755
doc/xml/AdminGuide/c32432.html
View File

File diff suppressed because it is too large Load Diff

5627
doc/xml/AdminGuide/c6449.html
View File

File diff suppressed because it is too large Load Diff

7163
doc/xml/AdminGuide/c667.html
View File

File diff suppressed because it is too large Load Diff

12981
doc/xml/AdminGuide/c8420.html
View File

File diff suppressed because it is too large Load Diff

437
doc/xml/AdminGuide/f24.html
View File

@ -1,437 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>About This Guide</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="AFS Administration Guide"
HREF="book1.html"><LINK
REL="NEXT"
TITLE="Concepts and Configuration Issues"
HREF="p128.html"></HEAD
><BODY
CLASS="preface"
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="book1.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="p128.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="preface"
><H1
><A
NAME="Header_3"
></A
>About This Guide</H1
><P
>This section describes the purpose, organization, and conventions of this document.</P
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="HDRWQ1"
>Audience and Purpose</A
></H1
><P
>This guide describes the concepts and procedures that an AFS(R) system administrator needs to know. It assumes familiarity
with UNIX(R) administration, but no previous knowledge of AFS.</P
><P
>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.</P
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="HDRWQ2"
>Document Organization</A
></H1
><P
>This document groups AFS administrative tasks into the following conceptual sections: <UL
><LI
><P
>Concepts and Configuration Issues</P
></LI
><LI
><P
>Managing File Server Machines</P
></LI
><LI
><P
>Managing Client Machines</P
></LI
><LI
><P
>Managing Users and Groups</P
></LI
></UL
></P
><P
>The individual chapters in each section contain the following: <UL
><LI
><P
>A chapter overview</P
></LI
><LI
><P
>A quick reference list of the tasks and commands described in the chapter</P
></LI
><LI
><P
>An introduction to concepts that pertain to all of the tasks described in the chapter</P
></LI
><LI
><P
>A set of sections devoted to specific tasks. Each section begins with a discussion of concepts specific to that
task, followed by step-by-step instructions for performing the task. The instructions are as specific as has been judged
practical. If two related procedures differ from one another in important details, separate sets of instructions are
usually provided.</P
></LI
></UL
></P
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="HDRWQ3"
>How to Use This Document</A
></H1
><P
>When you need to perform a specific administrative task, follow these steps:
<OL
TYPE="1"
><LI
><P
>Determine if the task concerns file server machines, client machines, or users and groups. Turn to the appropriate
section in this document and then to the appropriate chapter.</P
></LI
><LI
><P
>Read or review the general introductory material at the beginning of the chapter.</P
></LI
><LI
><P
>Read or review the introductory material concerning the specific task you wish to perform.</P
></LI
><LI
><P
>Follow the step-by-step instructions for the task.</P
></LI
><LI
><P
>If necessary, refer to the IBM AFS Administration Reference for more detailed information about the commands.</P
></LI
></OL
>
</P
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="HDRWQ4"
>Related Documents</A
></H1
><P
>The following documents are also included in the AFS documentation set.
<DIV
CLASS="variablelist"
><DL
><DT
>IBM AFS Administration Reference</DT
><DD
><P
>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
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.</P
><P
>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.</P
></DD
><DT
>IBM AFS Quick Beginnings</DT
><DD
><P
>This guide provides instructions for installing AFS server and client machines. It is assumed that the installer is
an experienced UNIX(R) system administrator.</P
><P
>For predictable performance, machines must be installed and configured in accordance with the instructions in this
guide.</P
></DD
><DT
>IBM AFS Release Notes</DT
><DD
><P
>This document provides information specific to each release of AFS, such as a list of new features and commands, a
list of requirements and limitations, and instructions for upgrading server and client machines.</P
></DD
><DT
>IBM AFS User Guide</DT
><DD
><P
>This guide presents the basic concepts and procedures necessary for using AFS effectively. It assumes that the
reader has some experience with UNIX, but does not require familiarity with networking or AFS.</P
><P
>The guide explains how to perform basic functions, including authenticating, changing a password, protecting AFS
data, creating groups, and troubleshooting. It provides illustrative examples for each function and describes some of the
differences between the UNIX file system and AFS.</P
></DD
></DL
></DIV
>
</P
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="HDRTYPO_CONV"
>Typographical Conventions</A
></H1
><P
>This document uses the following typographical conventions:
<UL
><LI
><P
>Command and option names appear in <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>bold type</B
></SPAN
> in syntax definitions, examples, and
running text. Names of directories, files, machines, partitions, volumes, and users also appear in <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>bold type</B
></SPAN
>.</P
></LI
><LI
><P
>Variable information appears in <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>italic type</I
></SPAN
>. This includes user-supplied information on command
lines and the parts of prompts that differ depending on who issues the command. New terms also appear in <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>italic
type</I
></SPAN
>.</P
></LI
><LI
><P
>Examples of screen output and file contents appear in <SAMP
CLASS="computeroutput"
>monospace type</SAMP
>.</P
></LI
></UL
>
</P
><P
>In addition, the following symbols appear in command syntax definitions, both in the documentation and in AFS online help
statements. When issuing a command, do not type these symbols. <UL
><LI
><P
>Square brackets <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>[ ]</B
></SPAN
> surround optional items.</P
></LI
><LI
><P
>Angle brackets <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>&#60; &#62;</B
></SPAN
> surround user-supplied values in AFS commands.</P
></LI
><LI
><P
>A superscripted plus sign <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>+</B
></SPAN
> follows an argument that accepts more than one
value.</P
></LI
><LI
><P
>The percent sign <SAMP
CLASS="computeroutput"
>%</SAMP
> represents the regular command shell prompt. Some operating systems possibly use a different
character for this prompt.</P
></LI
><LI
><P
>The number sign <SAMP
CLASS="computeroutput"
>#</SAMP
> represents the command shell prompt for the local superuser <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>root</B
></SPAN
>.
Some operating systems possibly use a different character for this prompt.</P
></LI
><LI
><P
>The pipe symbol <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>|</B
></SPAN
> in a command syntax statement separates mutually exclusive values
for an argument.</P
></LI
></UL
></P
><P
>For additional information on AFS commands, including a description of command string components, acceptable abbreviations
and aliases, and how to get online help for commands, see <A
HREF="a33826.html"
>Appendix B, Using AFS
Commands</A
>.</P
></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="book1.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="p128.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>AFS Administration Guide</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Concepts and Configuration Issues</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

29950
doc/xml/AdminGuide/i37012.html
View File

File diff suppressed because it is too large Load Diff

159
doc/xml/AdminGuide/p128.html
View File

@ -1,159 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Concepts and Configuration Issues</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="About This Guide"
HREF="f24.html"><LINK
REL="NEXT"
TITLE="An Overview of AFS Administration"
HREF="c130.html"></HEAD
><BODY
CLASS="part"
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="f24.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="c130.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="PART"
><A
NAME="AEN128"
></A
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="title"
>I. Concepts and Configuration Issues</H1
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>1. <A
HREF="c130.html"
>An Overview of AFS Administration</A
></DT
><DT
>2. <A
HREF="c667.html"
>Issues in Cell Configuration and Administration</A
></DT
></DL
><BR></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="f24.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="c130.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>About This Guide</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>An Overview of AFS Administration</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

159
doc/xml/AdminGuide/p21471.html
View File

@ -1,159 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Managing Client Machines</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 Server Encryption Keys"
HREF="c20494.html"><LINK
REL="NEXT"
TITLE="Administering Client Machines and the Cache Manager"
HREF="c21473.html"></HEAD
><BODY
CLASS="part"
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="c20494.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="c21473.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="PART"
><A
NAME="AEN21471"
></A
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="title"
>III. Managing Client Machines</H1
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>10. <A
HREF="c21473.html"
>Administering Client Machines and the Cache Manager</A
></DT
><DT
>11. <A
HREF="c23832.html"
>Configuring Client Machines with the package Program</A
></DT
></DL
><BR></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="c20494.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="c21473.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Managing Server Encryption Keys</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Administering Client Machines and the Cache Manager</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

174
doc/xml/AdminGuide/p24911.html
View File

@ -1,174 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Managing Users and Groups</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="Configuring Client Machines with the package Program"
HREF="c23832.html"><LINK
REL="NEXT"
TITLE="Creating and Deleting User Accounts with the uss Command Suite"
HREF="c24913.html"></HEAD
><BODY
CLASS="part"
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="c23832.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="c24913.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="PART"
><A
NAME="AEN24911"
></A
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="title"
>IV. Managing Users and Groups</H1
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>12. <A
HREF="c24913.html"
>Creating and Deleting User Accounts with the uss Command Suite</A
></DT
><DT
>13. <A
HREF="c27596.html"
>Administering User Accounts</A
></DT
><DT
>14. <A
HREF="c29323.html"
>Administering the Protection Database</A
></DT
><DT
>15. <A
HREF="c31274.html"
>Managing Access Control Lists</A
></DT
><DT
>16. <A
HREF="c32432.html"
>Managing Administrative Privilege</A
></DT
></DL
><BR></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="c23832.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="c24913.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Configuring Client Machines with the package Program</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Creating and Deleting User Accounts with the uss Command Suite</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

184
doc/xml/AdminGuide/p3023.html
View File

@ -1,184 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Managing File Server Machines</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="Issues in Cell Configuration and Administration"
HREF="c667.html"><LINK
REL="NEXT"
TITLE="Administering Server Machines"
HREF="c3025.html"></HEAD
><BODY
CLASS="part"
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="c667.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="c3025.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="PART"
><A
NAME="AEN3023"
></A
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="title"
>II. Managing File Server Machines</H1
><DIV
CLASS="TOC"
><DL
><DT
><B
>Table of Contents</B
></DT
><DT
>3. <A
HREF="c3025.html"
>Administering Server Machines</A
></DT
><DT
>4. <A
HREF="c6449.html"
>Monitoring and Controlling Server Processes</A
></DT
><DT
>5. <A
HREF="c8420.html"
>Managing Volumes</A
></DT
><DT
>6. <A
HREF="c12776.html"
>Configuring the AFS Backup System</A
></DT
><DT
>7. <A
HREF="c15383.html"
>Backing Up and Restoring AFS Data</A
></DT
><DT
>8. <A
HREF="c18360.html"
>Monitoring and Auditing AFS Performance</A
></DT
><DT
>9. <A
HREF="c20494.html"
>Managing Server Encryption Keys</A
></DT
></DL
><BR></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="c667.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="c3025.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Issues in Cell Configuration and Administration</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Administering Server Machines</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

68
doc/xml/QuickStartUnix/NTMakefile Normal file
View File

@ -0,0 +1,68 @@
# 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 = \
auqbg000.xml \
auqbg003.xml \
auqbg004.xml \
auqbg005.xml \
auqbg006.xml \
auqbg007.xml \
auqbg008.xml \
appendix.xml
index.html: $(XMLSRCS)
@echo Building Unix Quick Start Guide in HTML format
$(XSLTPROC) $(HTML_PARMS) $(HTML_XSL) auqbg000.xml
htmlhelp.chm: $(XMLSRCS)
@echo Building Unix Quick Start Guide in HTML Help format
$(XSLTPROC) $(CHM_XSL) auqbg000.xml
-hhc.exe htmlhelp.hhp
$(DEL) *.html
$(DEL) *.hh?
$(DEL) *.chw
install: htmlhelp.chm index.html
clean::
$(DEL) *.html
$(DEL) htmlhelp.chm

2
doc/xml/QuickStartUnix/appendix.xml
View File

@ -1456,7 +1456,7 @@ localusertwo:&lt;thelocalusertwo'skey&gt;:11500:0:99999:7:::
are installing your first file server;
<link linkend="HDRWQ108">Starting Server Programs</link> if you
are installing an additional file server machine; or
<link linkend="HDRWQ145"></link> if you are installing a client.
<link linkend="HDRWQ145">Loading and Creating Client Files</link> if you are installing a client.
</para>
</listitem>
</orderedlist>

17
doc/xml/QuickStartUnix/auqbg000.xml
View File

@ -8,17 +8,16 @@
<!ENTITY chapter4 SYSTEM "auqbg007.xml">
<!ENTITY appendixA SYSTEM "auqbg008.xml">
<!ENTITY appendixB SYSTEM "appendix.xml">
<!ENTITY index SYSTEM "auqbg009.xml">
]>
<book>
<bookinfo>
<title>OpenAFS Quick Beginnings</title>
<title>OpenAFS Quick Start Guide for UNIX</title>
<subtitle>Version 1.4.2</subtitle>
<subtitle>Version 1.4.10</subtitle>
<copyright>
<year>2000-2007</year>
<year>2000-2009</year>
<holder>IBM Corporation and other contributors. All Rights Reserved</holder>
</copyright>
@ -29,16 +28,16 @@
<revhistory>
<revision>
<revnumber>1.4.4</revnumber>
<date>March 2007</date>
<revnumber>1.4.10</revnumber>
<date>May 2009</date>
</revision>
</revhistory>
<abstract>
<para>This document describes the initial setup of an OpenAFS cell
and an OpenAFS client. It is currently being updated for OpenAFS
1.4.4 and is still dated and incorrect in some details. This
edition applies to OpenAFS for UNIX, Version 1.4.4, and to all
1.4.10 and is still dated and incorrect in some details. This
edition applies to OpenAFS for UNIX, Version 1.4.10, and to all
subsequent releases and modifications until otherwise indicated in
new editions.</para>
</abstract>
@ -51,7 +50,7 @@
&chapter4;
&appendixA;
&appendixB;
&index;
<index>Name Index</index>
</book>
<!-- Keep this comment at the end of the file
Local variables:

2
doc/xml/QuickStartUnix/auqbg004.xml
View File

@ -77,7 +77,7 @@
functions:
<itemizedlist>
<listitem>
<para>It acts as the <emphasis>system control
<para>It may act as the <emphasis>system control
machine</emphasis>, distributing certain
configuration files to the other server machines in the
cell</para>

8
doc/xml/QuickStartUnix/auqbg005.xml
View File

@ -1977,7 +1977,7 @@
often only need to add configuration to the session group:</para>
<example>
<title>PAM session example</title>
<title>Linux PAM session example</title>
<literallayout>session required pam_afs_session.so</literallayout>
</example>
@ -1991,7 +1991,7 @@
<literal>sufficient</literal>.</para>
<example>
<title>PAM auth example</title>
<title>Linux PAM auth example</title>
<literallayout>auth [success=ok default=1] pam_krb5.so
auth [default=done] pam_afs_session.so
auth required pam_unix.so try_first_pass</literallayout>
@ -2461,8 +2461,8 @@ auth required pam_unix.so try_first_pass</literallayout>
<filename>pam.conf</filename>:</para>
<example>
<title>PAM session example</title>
<literallayout>login session required pam_afs_session.so</literallayout>
<title>Solaris PAM session example</title>
<literallayout>login session required pam_afs_session.so</literallayout>
</example>
<para>This example enables PAM authentication only for console login.

134
doc/xml/QuickStartUnix/auqbg008.xml
View File

@ -1,21 +1,21 @@
<?xml version="1.0" encoding="UTF-8"?>
<appendix id="HDRWQ163">
<title>Appendix A. Building AFS from Source Code</title>
<title>Appendix A. Building OpenAFS from Source Code</title>
<para>This chapter describes how to build AFS from source code. <indexterm>
<para>This chapter describes how to build OpenAFS from source code. <indexterm>
<primary>storing</primary>
<secondary>AFS source in volume</secondary>
<secondary>OpenAFS source in volume</secondary>
</indexterm> <indexterm>
<primary>creating</primary>
<secondary>volume</secondary>
<tertiary>for AFS source</tertiary>
<tertiary>for OpenAFS source</tertiary>
</indexterm> <indexterm>
<primary>volume</primary>
<secondary>for AFS source</secondary>
<secondary>for OpenAFS source</secondary>
</indexterm> <indexterm>
<primary>source (AFS)</primary>
@ -23,13 +23,15 @@
</indexterm> <indexterm>
<primary>files</primary>
<secondary>AFS source</secondary>
<secondary>OpenAFS source</secondary>
</indexterm></para>
<sect1 id="HDRWQ164">
<title>Loading the Source Files</title>
<para>Working on an AFS client machine, perform these steps to load the AFS source tree from the AFS Source Distribution.
<para>Working on an AFS client machine, login to AFS as a
administrative user, then perform these steps to load the OpenAFS
source tree from the OpenAFS Source Distribution.
<orderedlist>
<indexterm>
<primary>commands</primary>
@ -66,7 +68,7 @@
</indexterm>
<listitem>
<para>Create and mount a volume for housing the AFS source tree. These instructions name the volume <emphasis
<para>Create and mount a volume for housing the OpenAFS source tree. These instructions name the volume <emphasis
role="bold">src.afs</emphasis> and mount it at the <emphasis
role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/afs/src</emphasis> directory.</para>
@ -88,22 +90,34 @@
</listitem>
<listitem>
<para>On the local <emphasis role="bold">/cdrom</emphasis> directory, mount the CD-ROM that contains the AFS source files.
For instructions on mounting CD-ROMs (either locally or remotely via NFS), consult the operating system documentation.
<para>Download the latest stable OpenAFS source distribution
(openafs-src.<replaceable>X.Y.Z</replaceable>.tar.gz)
from <ulink url="http://www.openafs.org/release/latest.html">openafs.org</ulink>
to the local <emphasis role="bold">/tmp</emphasis> directory.
<indexterm>
<primary>copying</primary>
<primary>downloading</primary>
<secondary>source files from CD-ROM</secondary>
</indexterm> <indexterm>
<primary>CD-ROM</primary>
<secondary>copying source files from</secondary>
</indexterm></para>
<secondary>source files from openafs.org</secondary>
</indexterm>
</para>
</listitem>
<listitem>
<para>Copy the source files from the CD-ROM into the newly created volume. <programlisting>
# <emphasis role="bold">cd /cdrom/src</emphasis>
<para>In the local <emphasis role="bold">/tmp</emphasis> directory, unpack the source archive. <programlisting>
# <emphasis role="bold">cd /tmp</emphasis>
# <emphasis role="bold">gzip -dc openafs-src-<replaceable>X.Y.Z</replaceable>.tar.gz | tar xvf -</emphasis>
</programlisting>
<indexterm>
<primary>unpacking</primary>
<secondary>source files from the archive</secondary>
</indexterm>
</para>
</listitem>
<listitem>
<para>Copy the source files from the unpacked archive into the newly created volume. <programlisting>
# <emphasis role="bold">cd /tmp/openafs-<replaceable>X.Y.Z</replaceable></emphasis>
# <emphasis role="bold">cp -rp * /afs/.</emphasis><replaceable>cellname</replaceable>/<emphasis role="bold">afs/src</emphasis>
</programlisting></para>
</listitem>
@ -127,10 +141,9 @@
</sect1>
<sect1 id="HDRWQ165">
<title>Compiling AFS Binaries Using the washtool Program</title>
<title>Compiling OpenAFS Binaries Using Configure and Make</title>
<para>The AFS distribution includes the <emphasis role="bold">washtool</emphasis> program for managing a hierarchy of software
development projects. The program builds project trees for program editing, compilation, and installation. <orderedlist>
<para>The OpenAFS distribution uses the <emphasis role="bold">autoconf</emphasis> program and Makefiles for compiling the OpenAFS software.<orderedlist>
<listitem>
<para>Create a subdirectory under the <emphasis role="bold">/afs/.</emphasis><replaceable>cellname</replaceable><emphasis
role="bold">/afs</emphasis> directory for each system type for which you will build AFS binaries. Creating and mounting a
@ -205,40 +218,23 @@
</programlisting> <indexterm>
<primary>commands</primary>
<secondary>washtool</secondary>
</indexterm> <indexterm>
<primary>washtool command</primary>
<secondary></secondary>
</indexterm></para>
</listitem>
<!--
% cd /afs/.rampaginggeek.com/src/afs/@sys
% ../src/configure
make
make dest
-->
<listitem>
<para>For each system type you plan to build, copy the binary for the <emphasis role="bold">washtool</emphasis> program to
the directory specified in the AFS <emphasis role="bold">Makefile</emphasis>, which is <emphasis
role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
role="bold">/afs/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/dest/bin</emphasis>. If you prefer to
store the program in a different directory, you can use the WASHTOOL variable on the <emphasis role="bold">make</emphasis>
command line as described in Step <link linkend="LIWQ166">6</link>.</para>
<para>If there is a volume that houses the AFS binaries for each system type (as recommended), the conventional location
for the <emphasis role="bold">washtool</emphasis> binary is the <emphasis
role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
role="bold">/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/usr/afsws/bin</emphasis> directory. Use
the following instruction to copy it.</para>
<para>For each system type you plan to build, run the following commands on a machine of that system type:</para>
<programlisting>
# <emphasis role="bold">cd /afs/</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/</emphasis><replaceable>sysname</replaceable><emphasis
role="bold">/usr/afsws/bin</emphasis>
# <emphasis role="bold">cp washtool</emphasis> <emphasis role="bold">/afs/.</emphasis><replaceable>cellname</replaceable><emphasis
role="bold">/afs/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/dest/bin</emphasis>
</programlisting>
<para>Otherwise, mount the (binary) AFS CD-ROM for this system type on the local <emphasis role="bold">/cdrom</emphasis>
directory, and copy the <emphasis role="bold">washtool</emphasis> binary directly from it.</para>
<programlisting>
# <emphasis role="bold">cd /cdrom/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/bin</emphasis>
# <emphasis role="bold">cp washtool</emphasis> <emphasis role="bold">/afs/.</emphasis><replaceable>cellname</replaceable><emphasis
role="bold">/afs/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/dest/bin</emphasis>
# <emphasis role="bold">cd /afs/</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/</emphasis><replaceable>sysname</replaceable>
# <emphasis role="bold">../src/configure</emphasis>
# <emphasis role="bold">make</emphasis>
# <emphasis role="bold">make dest</emphasis>
</programlisting>
<indexterm>
@ -247,47 +243,27 @@
<secondary>make</secondary>
</indexterm>
<indexterm>
<primary>configure command</primary>
</indexterm>
<indexterm>
<primary>make command</primary>
</indexterm>
<indexterm>
<primary>variables</primary>
<primary>commands</primary>
<secondary>WASHTOOL</secondary>
<secondary>configure</secondary>
</indexterm>
<indexterm>
<primary>variables</primary>
<secondary>SYS_NAME for washtool command</secondary>
</indexterm>
<indexterm>
<primary>SYS_NAME variable for washtool command</primary>
</indexterm>
<indexterm>
<primary>WASHTOOL variable</primary>
</indexterm>
</listitem>
<listitem>
<para><anchor id="LIWQ166" />Working in the <emphasis
role="bold">/afs/.</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/afs</emphasis> directory on a
machine of the system type for which you are building AFS, issue the <emphasis role="bold">make install</emphasis>
command. Set the SYS_NAME variable to the appropriate system type name.</para>
<para>If the <emphasis role="bold">washtool</emphasis> binary is not in the conventional directory (<emphasis
role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
role="bold">/afs/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/dest/bin</emphasis>), set the
WASHTOOL variable to the alternate full pathname of the binary.</para>
<programlisting>
# <emphasis role="bold">cd /afs/.</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/afs</emphasis>
# <emphasis role="bold">make SYS_NAME=</emphasis><replaceable>sysname</replaceable> [<emphasis role="bold">WASHTOOL=</emphasis><replaceable>alternate_washtool_directory</replaceable>] <emphasis
role="bold">install</emphasis>
</programlisting>
command.</para>
</listitem>
</orderedlist></para>
</sect1>

72
doc/xml/UserGuide/NTMakefile Normal file
View File

@ -0,0 +1,72 @@
# 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 = \
auusg000.xml \
auusg003.xml \
auusg004.xml \
auusg005.xml \
auusg006.xml \
auusg007.xml \
auusg008.xml \
auusg009.xml \
auusg010.xml \
auusg011.xml \
auusg012.xml \
auusg013.xml \
index.html: $(XMLSRCS)
@echo Building OpenAFS User Guide in HTML format
$(XSLTPROC) $(HTML_PARMS) $(HTML_XSL) auusg000.xml
htmlhelp.chm: $(XMLSRCS)
@echo Building OpenAFS User Guide in HTML Help format
$(XSLTPROC) $(CHM_XSL) auusg000.xml
-hhc.exe htmlhelp.hhp
$(DEL) *.html
$(DEL) *.hh?
$(DEL) *.chw
install: htmlhelp.chm index.html
clean::
$(DEL) *.html
$(DEL) htmlhelp.chm

785
doc/xml/UserGuide/a3632.html
View File

@ -1,785 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Using the NFS/AFS Translator</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="AFS User Guide"
HREF="book1.html"><LINK
REL="PREVIOUS"
TITLE="Troubleshooting"
HREF="c3402.html"><LINK
REL="NEXT"
TITLE="AFS Command Syntax and Online Help"
HREF="a3812.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 User Guide: Version 3.6</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="c3402.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="a3812.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="appendix"
><H1
><A
NAME="HDRWQ80"
></A
>Appendix A. Using the NFS/AFS Translator</H1
><P
>&#13;
Some
cells use the Network File System (NFS) in addition to AFS. If you work on an NFS client machine, your system
administrator can configure it to access the AFS filespace through a program called the <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>NFS/AFS
Translator</I
></SPAN
><SUP
>TM</SUP
>. If you have an AFS account, you can access AFS as an
authenticated user while working on your NFS client machine. Otherwise, you access AFS as the
<SPAN
CLASS="bold"
><B
CLASS="emphasis"
>anonymous</B
></SPAN
> user.</P
><DIV
CLASS="note"
><BLOCKQUOTE
CLASS="note"
><P
><B
>Note: </B
>Acceptable NFS/AFS Translator performance requires that NFS is functioning correctly.</P
></BLOCKQUOTE
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="HDRWQ81"
>Requirements for Using the NFS/AFS Translator</A
></H1
><P
>&#13;
For you to use the NFS/AFS Translator, your system
administrator must configure the following types of machines as indicated:</P
><UL
><LI
><P
>An <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>NFS/AFS translator machine</I
></SPAN
> is an AFS client machine that also acts as an
NFS server machine. Its Cache Manager acts as the surrogate Cache Manager for your NFS client machine. Ask your
system administrator which translator machines you can use.</P
></LI
><LI
><P
>Your NFS client machine must have an NFS mount to a translator machine. Most often, your system
administrator mounts the translator machine's <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>/afs</B
></SPAN
> directory and names the mount
<SPAN
CLASS="bold"
><B
CLASS="emphasis"
>/afs</B
></SPAN
> as well. This enables you to access the entire AFS filespace using standard
AFS pathnames. It is also possible to create mounts directly to subdirectories of
<SPAN
CLASS="bold"
><B
CLASS="emphasis"
>/afs</B
></SPAN
>, and to give NFS mounts different names on the NFS client
machine.</P
></LI
></UL
><P
>Your access to AFS is much more extensive if you have an AFS user account. If you do not, the AFS servers
recognize you as the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>anonymous</B
></SPAN
> user and only grant you the access available to
members of the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>system:anyuser</B
></SPAN
> group.</P
><P
>If your NFS client machine uses an operating system that AFS supports, your system administrator can
configure it to enable you to issue many AFS commands on the machine. Ask him or her about the configuration and
which commands you can issue.</P
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="Header_160"
>Accessing AFS via the Translator</A
></H1
><P
>If you do not have an AFS account or choose not to access AFS as an authenticated user, then all you do to
access AFS is provide the pathname of the relevant file. Its ACL must grant the necessary permissions to the
<SPAN
CLASS="bold"
><B
CLASS="emphasis"
>system:anyuser</B
></SPAN
> group.</P
><P
>If you have an AFS account and want to access AFS as an authenticated user, the best method depends on
whether your NFS machine is a supported type. If it is, use the instructions in <A
HREF="a3632.html#HDRWQ82"
>To
Authenticate on a Supported Operating System</A
>. If it is not a supported type, use the instructions in
<A
HREF="a3632.html#HDRWQ83"
>To Authenticate on an Unsupported Operating System</A
>.</P
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="HDRWQ82"
>To Authenticate on a Supported Operating System</A
></H2
><OL
TYPE="1"
><LI
><P
>Log into the NFS client machine using your NFS username.</P
></LI
><LI
><P
>&#13; Issue the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>klog</B
></SPAN
> command. For complete instructions, see
<A
HREF="c569.html#HDRWQ29"
>To Authenticate with AFS</A
>.
<PRE
CLASS="programlisting"
>&#13; % <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>klog -setpag</B
></SPAN
>
</PRE
>
</P
></LI
></OL
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="HDRWQ83"
>To Authenticate on an Unsupported Operating System</A
></H2
><OL
TYPE="1"
><LI
><P
>Log onto the NFS client machine using your NFS username.</P
></LI
><LI
><P
><A
NAME="LINFS-TELNET"
></A
>Establish a connection to the NFS/AFS translator machine you are
using (for example, using the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>telnet</B
></SPAN
> utility) and log onto it using your AFS
username (which is normally the same as your NFS username).</P
></LI
><LI
><P
>&#13; If the NFS/AFS translator machine uses an AFS-modified login utility, then you obtained AFS tokens in Step
<A
HREF="a3632.html#LINFS-TELNET"
>2</A
>. To check, issue the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>tokens</B
></SPAN
> command,
which is described fully in <A
HREF="c569.html#HDRWQ30"
>To Display Your Tokens</A
>.
<PRE
CLASS="programlisting"
>&#13; % <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>tokens</B
></SPAN
>
</PRE
>
If you do not have tokens, issue the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>klog</B
></SPAN
> command, which is described fully in
<A
HREF="c569.html#HDRWQ29"
>To Authenticate with AFS</A
>.
<PRE
CLASS="programlisting"
>&#13; % <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>klog -setpag</B
></SPAN
>
</PRE
>
</P
></LI
><LI
><P
>&#13; <A
NAME="LINFS-KNFS"
></A
>Issue the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>knfs</B
></SPAN
> 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.
</P
><P
>If your NFS client machine is a system type for which AFS defines a system name, it can make sense
to add the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>-sysname</B
></SPAN
> argument. This argument helps the Cache Manager access
binaries specific to your NFS client machine, if your system administrator has used the
<SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>@sys</I
></SPAN
> variable in pathnames. Ask your system administrator if this argument is useful for
you.
</P
><PRE
CLASS="programlisting"
>&#13; % <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>knfs</B
></SPAN
> &#60;<VAR
CLASS="replaceable"
>host name</VAR
>&#62; [&#60;<VAR
CLASS="replaceable"
>user ID (decimal)</VAR
>&#62;] \
[<SPAN
CLASS="bold"
><B
CLASS="emphasis"
>-sysname</B
></SPAN
> &#60;<VAR
CLASS="replaceable"
>host's '@sys' value</VAR
>&#62;]
</PRE
><P
>where</P
><DIV
CLASS="variablelist"
><DL
><DT
><SPAN
CLASS="bold"
><B
CLASS="emphasis"
><VAR
CLASS="replaceable"
>host name</VAR
></B
></SPAN
></DT
><DD
><P
>Specifies the fully-qualified hostname of your NFS client machine (such as
<SPAN
CLASS="bold"
><B
CLASS="emphasis"
>nfs52.abc.com</B
></SPAN
>).</P
></DD
><DT
><SPAN
CLASS="bold"
><B
CLASS="emphasis"
><VAR
CLASS="replaceable"
>user ID</VAR
></B
></SPAN
></DT
><DD
><P
>Specifies your UNIX UID or equivalent (not your username) on the NFS client machine. If your
system administrator has followed the conventional practice, then your UNIX and AFS UIDs are the same. If you
do not know your local UID on the NFS machine, ask your system administrator for assistance. Your system
administrator can also explain the issues you need to be aware of if your two UIDs do not match, or if you
omit this argument.</P
></DD
><DT
><SPAN
CLASS="bold"
><B
CLASS="emphasis"
>-sysname</B
></SPAN
></DT
><DD
><P
>Specifies your NFS client machine's system type name.</P
></DD
></DL
></DIV
></LI
><LI
><P
><A
NAME="LINFS-LOGOUT"
></A
>(<SPAN
CLASS="bold"
><B
CLASS="emphasis"
>Optional</B
></SPAN
>) Log out from the
translator machine, but do not unauthenticate.</P
></LI
><LI
><P
>Work on the NFS client machine, accessing AFS as necessary.</P
></LI
><LI
><P
>&#13; When you are finished accessing AFS, issue the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>knfs</B
></SPAN
> command on the translator
machine again. Provide the same <VAR
CLASS="replaceable"
>host name</VAR
> and <VAR
CLASS="replaceable"
>user ID</VAR
>
arguments as in Step <A
HREF="a3632.html#LINFS-KNFS"
>4</A
>, and add the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>-unlog</B
></SPAN
>
flag to destroy your tokens. If you logged out from the translator machine in Step
<A
HREF="a3632.html#LINFS-LOGOUT"
>5</A
>, then you must first reestablish a connection to the translator machine
as in Step <A
HREF="a3632.html#LINFS-TELNET"
>2</A
>.
<PRE
CLASS="programlisting"
>&#13; % <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>knfs</B
></SPAN
> &#60;<VAR
CLASS="replaceable"
>host name</VAR
>&#62; [&#60;<VAR
CLASS="replaceable"
>user ID (decimal)</VAR
>&#62;] <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>-unlog</B
></SPAN
>
</PRE
>
</P
></LI
></OL
></DIV
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="HDRWQ84"
>Troubleshooting the NFS/AFS Translator</A
></H1
><P
>Acceptable performance by the NFS/AFS translator depends for the most part on NFS. Sometimes, problems that
appear to be AFS file server outages, broken connections, or inaccessible files are actually caused by NFS
outages.</P
><P
>This section describes some common problems and their possible causes. If other problems arise, contact your
system administrator, who can ask the AFS Product Support group for assistance if necessary.</P
><DIV
CLASS="note"
><BLOCKQUOTE
CLASS="note"
><P
><B
>Note: </B
>To avoid degrading AFS performance, the Cache Manager on the translator machine does not immediately
send changes made on NFS client machines to the File Server. Instead, it checks every 60 seconds for such
changes and sends them then. It can take longer for changes made on an NFS client machine to be saved than for
changes made on an AFS client machine. The save operation must complete before the changes are visible on NFS
client machines that are using a different translator machine or on AFS client machines.</P
></BLOCKQUOTE
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="HDRWQ85"
>Your NFS Client Machine is Frozen</A
></H2
><P
>If your system administrator has used the recommended options when creating an NFS mount to an NFS/AFS
translator machine, then the mount is both <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>hard</I
></SPAN
> and <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>interruptible</I
></SPAN
>:</P
><UL
><LI
><P
>A hard mount means that the NFS client retries its requests if it does not receive a response
within the expected time frame. This is useful because requests have to pass through both the NFS and AFS client
software, which can sometimes take longer than the NFS client expects. However, it means that if the NFS/AFS
translator machine actually becomes inaccessible, your NFS client machine can become inoperative
(<SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>freeze</I
></SPAN
> or <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>hang</I
></SPAN
>).</P
></LI
><LI
><P
>If the NFS mount is interruptible, then in the case of an NFS/AFS translator machine outage you
can press &#60;<SPAN
CLASS="bold"
><B
CLASS="emphasis"
>Ctrl-c</B
></SPAN
>&#62; or another interrupt signal to halt the NFS client's
repeated attempts to access AFS. You can then continue to work locally, or can NFS-mount another translator
machine. If the NFS mount is not interruptible, you must actually remove the mount to the inaccessible translator
machine.</P
></LI
></UL
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="Header_165"
>NFS/AFS Translator Reboots</A
></H2
><P
>If you have authenticated to AFS and your translator machine reboots, you must issue the
<SPAN
CLASS="bold"
><B
CLASS="emphasis"
>klog</B
></SPAN
> command (and <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>knfs</B
></SPAN
> command, if appropriate)
to reauthenticate. If you used the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>knfs</B
></SPAN
> command's
<SPAN
CLASS="bold"
><B
CLASS="emphasis"
>-sysname</B
></SPAN
> argument to define your NFS client machine's system name, use it
again.</P
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="Header_166"
>System Error Messages</A
></H2
><P
>This section explains possible meanings for NFS error messages you receive while accessing AFS
filespace.</P
><P
><SAMP
CLASS="computeroutput"
>stale NFS client</SAMP
></P
><P
><SAMP
CLASS="computeroutput"
>Getpwd: can't read</SAMP
></P
><P
>Both messages possibly means that your translator machine was rebooted and cannot determine the pathname to
the current working directory. To reestablish the path, change directory and specify the complete pathname starting
with <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>/afs</B
></SPAN
>.</P
><P
><SAMP
CLASS="computeroutput"
>NFS server <VAR
CLASS="replaceable"
>translator_machine</VAR
> is not responding still
trying</SAMP
>.</P
><P
>The NFS client is not getting a response from the NFS/AFS translator machine. If the NFS mount to the
translator machine is a hard mount, your NFS client continues retrying the request until it gets a response (see
<A
HREF="a3632.html#HDRWQ85"
>Your NFS Client Machine is Frozen</A
>). If the NFS mount to the translator machine is a
soft mount, the NFS client stops retrying after a certain number of attempts (three by default).</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="c3402.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="a3812.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Troubleshooting</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>AFS Command Syntax and Online Help</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

1317
doc/xml/UserGuide/a3812.html
View File

File diff suppressed because it is too large Load Diff

35
doc/xml/UserGuide/auusg000.xml
View File

@ -11,16 +11,13 @@
<!ENTITY appendixA SYSTEM "auusg010.xml">
<!ENTITY appendixB SYSTEM "auusg011.xml">
<!ENTITY glossary SYSTEM "auusg012.xml">
<!ENTITY index SYSTEM "auusg013.xml">
]>
<book>
<bookinfo>
<title>AFS User Guide</title>
<title>OpenAFS User Guide</title>
<subtitle>Version 3.6</subtitle>
<pubsnumber>Document Number GC09-4561-00</pubsnumber>
<subtitle>Version M.n</subtitle>
<copyright>
<year>2000</year>
@ -29,23 +26,33 @@
</copyright>
<revhistory>
<revision>
<revnumber>M.n</revnumber>
<date>May 2008</date>
<revremark>First OpenAFS Edition</revremark>
</revision>
<revision>
<revnumber>3.6</revnumber>
<date>April 2000</date>
<revremark>First Edition</revremark>
</revision>
<pubsnumber>Document Number GC09-4561-00</pubsnumber>
<revremark>First IBM Edition, Document Number GC09-4561-00</revremark>
</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.n</member>
<member>OpenAFS for Digital Unix, Version M.n</member>
<member>OpenAFS for HP-UX, Version M.n</member>
<member>OpenAFS for Linux, Version M.n</member>
<member>OpenAFS for SGI IRIX, Version M.n</member>
<member>OpenAFS for Solaris, Version M.n</member>
</simplelist></para>
<para>and to all subsequent releases and modifications until otherwise
@ -65,5 +72,5 @@
&appendixA;
&appendixB;
&glossary;
&index;
<index>Name Index</index>
</book>

28
doc/xml/UserGuide/auusg003.xml
View File

@ -16,7 +16,7 @@
or group of related tasks are presented in context, just prior to the procedures. Many examples are provided.</para>
<para>Instructions generally include only the commands and command options necessary for a specific task. For a complete list of
AFS commands and description of all options available on every command, see the <emphasis>IBM AFS Administration
AFS commands and description of all options available on every command, see the <emphasis>OpenAFS Administration
Reference</emphasis>.</para>
</sect1>
@ -25,13 +25,13 @@
<para>This document is divided into the following chapters.</para>
<para><link linkend="HDRWQ2">An Introduction to AFS</link> introduces the basic concepts and functions of AFS. To use AFS
<para><link linkend="HDRWQ2">An Introduction to OpenAFS</link> introduces the basic concepts and functions of AFS. To use AFS
successfully, it is important to be familiar with the terms and concepts described in this chapter.</para>
<para><link linkend="HDRWQ20">Using AFS</link> describes how to use AFS's basic features: how to log in and authenticate, unlog,
<para><link linkend="HDRWQ20">Using OpenAFS</link> describes how to use AFS's basic features: how to log in and authenticate, unlog,
log out, access AFS files and directories in AFS, and change your password.</para>
<para><link linkend="HDRWQ38">Displaying Information about AFS</link> describes how to display information about AFS volume
<para><link linkend="HDRWQ38">Displaying Information about OpenAFS</link> describes how to display information about AFS volume
quota and location, file server machine status, and the foreign cells you can access.</para>
<para><link linkend="HDRWQ44">Protecting Your Directories and Files</link> describes how to protect your data using AFS access
@ -45,18 +45,18 @@
<para><link linkend="HDRWQ80">Appendix A, Using the NFS/AFS Translator</link> describes how to use the NFS/AFS Translator to
access the AFS filespace from an NFS client machine.</para>
<para><link linkend="HDRWQ86">Appendix B, AFS Command Syntax and Online Help</link> describes AFS command syntax and how to
<para><link linkend="HDRWQ86">Appendix B, OpenAFS Command Syntax and Online Help</link> describes AFS command syntax and how to
obtain online information about commands.</para>
<para><link linkend="HDRWQ90">Appendix C, Glossary</link> defines terms used in the <emphasis>IBM AFS User
<para><link linkend="HDRWQ90">Appendix C, Glossary</link> defines terms used in the <emphasis>OpenAFS User
Guide</emphasis>.</para>
</sect1>
<sect1 id="HDRUSERFRONTHOWTO">
<title>How To Use This Document</title>
<para>Before you begin using AFS, read <link linkend="HDRWQ2">An Introduction to AFS</link>. Next, follow the procedures
outlined in <link linkend="HDRWQ20">Using AFS</link> to get started using AFS as an authenticated user. It describes how to
<para>Before you begin using OpenAFS, read <link linkend="HDRWQ2">An Introduction to OpenAFS</link>. Next, follow the procedures
outlined in <link linkend="HDRWQ20">Using OpenAFS</link> to get started using OpenAFS as an authenticated user. It describes how to
access files in the AFS filespace and how to end an AFS session. Consult the other chapters as you need to perform the tasks
they describe.</para>
</sect1>
@ -68,19 +68,19 @@
<itemizedlist>
<listitem>
<para>The <emphasis>IBM AFS Administration Reference</emphasis> details the syntax of each AFS command and is intended for
the experienced AFS administrator, programmer, or user. For each AFS command, the <emphasis>IBM AFS Administration
<para>The <emphasis>OpenAFS Administration Reference</emphasis> details the syntax of each AFS command and is intended for
the experienced AFS administrator, programmer, or user. For each AFS command, the <emphasis>OpenAFS Administration
Reference</emphasis> lists the command syntax, aliases and abbreviations, description, arguments, warnings, output,
examples, and related topics. Commands are organized alphabetically.</para>
</listitem>
<listitem>
<para>The <emphasis>IBM AFS Administration Guide</emphasis> describes concepts and procedures necessary for administering an
AFS cell, as well as more extensive coverage of the topics in the <emphasis>IBM AFS User Guide</emphasis>.</para>
<para>The <emphasis>OpenAFS Administration Guide</emphasis> describes concepts and procedures necessary for administering an
AFS cell, as well as more extensive coverage of the topics in the <emphasis>OpenAFS User Guide</emphasis>.</para>
</listitem>
<listitem>
<para>The <emphasis>IBM AFS Quick Beginnings</emphasis> provides instructions for installing AFS server and client
<para>The <emphasis>OpenAFS Quick Beginnings</emphasis> provides instructions for installing AFS server and client
machines.</para>
</listitem>
</itemizedlist>
@ -146,7 +146,7 @@
</para>
<para>For additional information on AFS commands, including a description of command string components, acceptable abbreviations
and aliases, and how to get online help for commands, see <link linkend="HDRWQ86">Appendix B, AFS Command Syntax and Online
and aliases, and how to get online help for commands, see <link linkend="HDRWQ86">Appendix B, OpenAFS Command Syntax and Online
Help</link>.</para>
</sect1>
</preface>

4
doc/xml/UserGuide/auusg004.xml
View File

@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="HDRWQ2">
<title>An Introduction to AFS</title>
<title>An Introduction to OpenAFS</title>
<para>This chapter introduces basic AFS concepts and terms. It assumes that you are already familiar with standard UNIX commands,
file protection, and pathname conventions.</para>
@ -519,7 +519,7 @@
</sect1>
<sect1 id="HDRWQ19">
<title>Using AFS with NFS</title>
<title>Using OpenAFS with NFS</title>
<para>Some cells use the Networking File System (NFS) in addition to AFS. If you work on an NFS client machine, your system
administrator can configure it to access the AFS filespace through a program called the <emphasis>NFS/AFS

4
doc/xml/UserGuide/auusg005.xml
View File

@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="HDRWQ20">
<title>Using AFS</title>
<title>Using OpenAFS</title>
<para>This chapter explains how to perform four basic AFS tasks: logging in and authenticating with AFS, ending an AFS session,
accessing the AFS filespace, and changing your password.</para>
@ -170,7 +170,7 @@
<para>Your cell's administrators set the default lifetime of your token. The AFS authentication service never grants a token
lifetime longer than the default, but you can request a token with a shorter lifetime. See the <emphasis
role="bold">klog</emphasis> reference page in the <emphasis>IBM AFS Administration Reference</emphasis> to learn how to use
role="bold">klog</emphasis> reference page in the <emphasis>OpenAFS Administration Reference</emphasis> to learn how to use
its <emphasis role="bold">-lifetime</emphasis> argument for this purpose.</para>
</sect3>

2
doc/xml/UserGuide/auusg006.xml
View File

@ -1,6 +1,6 @@
<?xml version="1.0" encoding="UTF-8"?>
<chapter id="HDRWQ38">
<title>Displaying Information about AFS</title>
<title>Displaying Information about OpenAFS</title>
<para>This chapter explains how to display information that can help you use AFS more effectively. It includes the following
sections.

4
doc/xml/UserGuide/auusg007.xml
View File

@ -912,7 +912,7 @@
<para>If you specify only one directory (or file) name, you can omit the <emphasis role="bold">-dir</emphasis> and
<emphasis role="bold">-acl</emphasis> switches. For more on omitting switches, see <link linkend="HDRWQ86">Appendix B,
AFS Command Syntax and Online Help</link>.</para>
OpenAFS Command Syntax and Online Help</link>.</para>
</listitem>
</varlistentry>
@ -1487,7 +1487,7 @@
<para>Although AFS protects data primarily with ACLs rather than mode bits, it does not ignore the mode bits entirely. An
explanation of how mode bits work in the UNIX file system is outside the scope of this document, and the following discussion
assumes you understand them; if necessary, see your UNIX documentation. Also, the following discussion does not cover the
setuid, setgid or sticky bits. If you need to understand how those bits work on AFS files, see the <emphasis>IBM AFS
setuid, setgid or sticky bits. If you need to understand how those bits work on AFS files, see the <emphasis>OpenAFS
Administration Guide</emphasis> or ask your system administrator.</para>
<para>AFS uses the UNIX mode bits in the following way:</para>

12
doc/xml/UserGuide/auusg011.xml
View File

@ -1,5 +1,5 @@
<?xml version="1.0" encoding="utf-8"?>
<appendix id="HDRWQ86"><title>AFS Command Syntax and Online Help</title>
<appendix id="HDRWQ86"><title>OpenAFS Command Syntax and Online Help</title>
<indexterm><primary>syntax of AFS commands described</primary></indexterm>
@ -8,7 +8,7 @@
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
relevant to them.</para>
<sect1 id="HDRWQ87"><title>AFS Command Syntax</title>
<sect1 id="HDRWQ87"><title>OpenAFS Command Syntax</title>
<para>
<indexterm><primary>commands</primary><secondary>syntax for AFS</secondary></indexterm>
Most AFS commands use the following syntax:</para>
@ -80,7 +80,7 @@
<listitem><para><emphasis role="bold">-negative</emphasis> is a flag; it directs the command to put the access
list entries on the negative rather than the normal permissions list.</para></listitem>
</itemizedlist>
</sect2></sect1><sect1 id="HDRWQ88"><title>Rules for Using AFS Commands</title>
</sect2></sect1><sect1 id="HDRWQ88"><title>Rules for Using OpenAFS Commands</title>
<para>This section describes the rules to follow when using AFS commands.</para>
<sect2 id="Header_171"><title>Spaces and Lines</title>
<para>Separate each command element (command suite, operation code, switches, instances, and flags) with a space.
@ -104,7 +104,7 @@
<listitem><para><emphasis role="bold">fs lista</emphasis> (abbreviation)</para></listitem>
<listitem><para><emphasis role="bold">fs la</emphasis> (alias)</para></listitem>
</itemizedlist>
<para>The <emphasis>IBM AFS Administration Reference</emphasis> provides information on the full and abbreviated
<para>The <emphasis>OpenAFS Administration Reference</emphasis> provides information on the full and abbreviated
command syntax as well as any aliases for all of the commands discussed in this guide.</para>
</sect2><sect2 id="Header_173"><title>Omitting Argument Switches</title>
@ -173,7 +173,7 @@
</programlisting>
</sect2></sect1><sect1 id="Header_176"><title>Commonly Used fs and pts Commands</title>
<para>This section provides additional information on the commonly used AFS <emphasis role="bold">fs</emphasis> and
<emphasis role="bold">pts</emphasis> commands. For more detailed information, see the <emphasis>IBM AFS
<emphasis role="bold">pts</emphasis> commands. For more detailed information, see the <emphasis>OpenAFS
Administration Reference</emphasis>.</para>
<sect2 id="Header_177"><title>About the fs Commands</title>
@ -221,7 +221,7 @@
group entries they own, as well as their own user entries. Depending on the setting of an entry's privacy flags,
regular users can sometimes access and manipulate group entries in certain ways.</para>
<para>All <emphasis role="bold">pts</emphasis> commands accept optional arguments and flags. They are listed in the
command descriptions in the <emphasis>IBM AFS Administration Reference</emphasis> and are described here in
command descriptions in the <emphasis>OpenAFS Administration Reference</emphasis> and are described here in
detail:</para>
<variablelist>

2
doc/xml/UserGuide/auusg012.xml
View File

@ -168,7 +168,7 @@
<glossdef>
<para>A string of characters indicating an action for an AFS server to perform. For a description of AFS command syntax, see
<link linkend="HDRWQ86">Appendix B, AFS Command Syntax and Online Help</link>.</para>
<link linkend="HDRWQ86">Appendix B, OpenAFS Command Syntax and Online Help</link>.</para>
</glossdef>
</glossentry>

18
doc/xml/UserGuide/auusg013.xml
View File

@ -213,7 +213,7 @@
<indexentry>
<primaryie>arguments to AFS commands,
<ulink url="a3812.html#HDRWQ87" role="AEN3856">AFS Command Syntax</ulink>
<ulink url="a3812.html#HDRWQ87" role="AEN3856">OpenAFS Command Syntax</ulink>
</primaryie>
</indexentry>
@ -482,10 +482,10 @@
<ulink url="c113.html#HDRWQ18" role="AEN471">Remote Commands</ulink>
</secondaryie>
<secondaryie>suite organization for AFS,
<ulink url="a3812.html#HDRWQ87" role="AEN3830">AFS Command Syntax</ulink>
<ulink url="a3812.html#HDRWQ87" role="AEN3830">OpenAFS Command Syntax</ulink>
</secondaryie>
<secondaryie>syntax for AFS,
<ulink url="a3812.html#HDRWQ87" role="AEN3820">AFS Command Syntax</ulink>
<ulink url="a3812.html#HDRWQ87" role="AEN3820">OpenAFS Command Syntax</ulink>
</secondaryie>
<secondaryie>tokens,
<ulink url="c569.html#HDRWQ30" role="AEN759">To Display Your Tokens</ulink>
@ -854,7 +854,7 @@
<indexentry>
<primaryie>flags on AFS commands,
<ulink url="a3812.html#HDRWQ87" role="AEN3867">AFS Command Syntax</ulink>
<ulink url="a3812.html#HDRWQ87" role="AEN3867">OpenAFS Command Syntax</ulink>
</primaryie>
</indexentry>
@ -1087,7 +1087,7 @@
<indexentry>
<primaryie>instances to AFS commands,
<ulink url="a3812.html#HDRWQ87" role="AEN3863">AFS Command Syntax</ulink>
<ulink url="a3812.html#HDRWQ87" role="AEN3863">OpenAFS Command Syntax</ulink>
</primaryie>
</indexentry>
@ -1328,7 +1328,7 @@
<ulink url="a3812.html#Header_172" role="AEN3915">Abbreviations and Aliases for Operation Codes</ulink>
</secondaryie>
<secondaryie>defined,
<ulink url="a3812.html#HDRWQ87" role="AEN3846">AFS Command Syntax</ulink>
<ulink url="a3812.html#HDRWQ87" role="AEN3846">OpenAFS Command Syntax</ulink>
</secondaryie>
</indexentry>
@ -1652,7 +1652,7 @@
<indexentry>
<primaryie>suite, defined for AFS command,
<ulink url="a3812.html#HDRWQ87" role="AEN3833">AFS Command Syntax</ulink>
<ulink url="a3812.html#HDRWQ87" role="AEN3833">OpenAFS Command Syntax</ulink>
</primaryie>
</indexentry>
@ -1663,7 +1663,7 @@
<ulink url="a3812.html#Header_174" role="AEN3963">Shortening Switches and Flags</ulink>
</secondaryie>
<secondaryie>defined,
<ulink url="a3812.html#HDRWQ87" role="AEN3860">AFS Command Syntax</ulink>
<ulink url="a3812.html#HDRWQ87" role="AEN3860">OpenAFS Command Syntax</ulink>
</secondaryie>
<secondaryie>omitting,
<ulink url="a3812.html#Header_173" role="AEN3942">Omitting Argument Switches</ulink>
@ -1672,7 +1672,7 @@
<indexentry>
<primaryie>syntax of AFS commands described,
<ulink url="a3812.html" role="AEN3814">AFS Command Syntax and Online Help</ulink>
<ulink url="a3812.html" role="AEN3814">OpenAFS Command Syntax and Online Help</ulink>
</primaryie>
</indexentry>

1210
doc/xml/UserGuide/book1.html
View File

File diff suppressed because it is too large Load Diff

1118
doc/xml/UserGuide/c1095.html
View File

File diff suppressed because it is too large Load Diff

1351
doc/xml/UserGuide/c113.html
View File

File diff suppressed because it is too large Load Diff

3358
doc/xml/UserGuide/c1444.html
View File

File diff suppressed because it is too large Load Diff

2927
doc/xml/UserGuide/c2454.html
View File

File diff suppressed because it is too large Load Diff

870
doc/xml/UserGuide/c3402.html
View File

@ -1,870 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Troubleshooting</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="AFS User Guide"
HREF="book1.html"><LINK
REL="PREVIOUS"
TITLE="Using Groups"
HREF="c2454.html"><LINK
REL="NEXT"
TITLE="Using the NFS/AFS Translator"
HREF="a3632.html"></HEAD
><BODY
CLASS="chapter"
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 User Guide: Version 3.6</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="c2454.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="a3632.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="chapter"
><H1
><A
NAME="HDRWQ76"
></A
>Chapter 6. Troubleshooting</H1
><P
>This chapter explains how to investigate and solve some problems you can sometimes encounter when working with AFS files. To
use the instructions, find the heading that describes your problem or matches the error message you received.</P
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="HDRWQ77"
>Problem: Cannot Access, Copy, or Save File</A
></H1
><P
> </P
><OL
TYPE="1"
><LI
><P
><A
NAME="LINOSAVE-TOKENS"
></A
>Issue the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>tokens</B
></SPAN
> command to verify that you have valid
tokens. For complete instructions, see <A
HREF="c569.html#HDRWQ30"
>To Display Your Tokens</A
>. <PRE
CLASS="programlisting"
>&#13; % <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>tokens</B
></SPAN
>
</PRE
></P
><UL
><LI
><P
>If your tokens are valid, proceed to Step <A
HREF="c3402.html#LINOSAVE-FSCHECKS"
>2</A
>.</P
></LI
><LI
><P
>If your do not have tokens for the relevant cell, or they are expired, issue the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>klog</B
></SPAN
> command to authenticate. For complete instructions, see <A
HREF="c569.html#HDRWQ29"
>To
Authenticate with AFS</A
>. Then try accessing or saving the file again. If you are not successful, proceed to Step
<A
HREF="c3402.html#LINOSAVE-FSCHECKS"
>2</A
>. <PRE
CLASS="programlisting"
>&#13; % <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>klog</B
></SPAN
>
</PRE
></P
></LI
></UL
></LI
><LI
><P
><A
NAME="LINOSAVE-FSCHECKS"
></A
>Issue the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>fs checkservers</B
></SPAN
> command to check the
status of file server machines. For complete instructions, see <A
HREF="c1095.html#HDRWQ41"
>Checking the Status of Server
Machines</A
>. <PRE
CLASS="programlisting"
>&#13; % <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>fs checkservers &#38;</B
></SPAN
>
</PRE
></P
><UL
><LI
><P
>If the following message appears, proceed to Step <A
HREF="c3402.html#LINOSAVE-PERMS"
>3</A
>. <PRE
CLASS="programlisting"
>&#13; All servers are running.
</PRE
></P
></LI
><LI
><P
>Output like the following indicates that your Cache Manager cannot reach the indicated file server machines.
<PRE
CLASS="programlisting"
>&#13; These servers unavailable due to network or server problem:
<VAR
CLASS="replaceable"
>list of machines</VAR
>.
</PRE
></P
><P
>Issue the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>fs whereis</B
></SPAN
> command to check if the file you are attempting to access or
save is stored on one of the inaccessible file server machines. For complete instructions, see <A
HREF="c1095.html#HDRWQ40"
>Locating Files and Directories</A
>.</P
><PRE
CLASS="programlisting"
>&#13; % <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>fs whereis</B
></SPAN
> &#60;<VAR
CLASS="replaceable"
>dir/file path</VAR
>&#62;
</PRE
><P
>If your file is stored on an inaccessible machine, then you cannot access the file or save it back to the File
Server until the machine is again accessible. If your file is on a machine that is not listed as inaccessible, proceed
to Step <A
HREF="c3402.html#LINOSAVE-PERMS"
>3</A
>.</P
></LI
></UL
></LI
><LI
><P
><A
NAME="LINOSAVE-PERMS"
></A
>Issue the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>fs listacl</B
></SPAN
> command to verify that you have
the permissions you need for accessing, copying, or saving the file. For complete instructions, see <A
HREF="c1444.html#HDRWQ53"
>To display an ACL</A
>. <PRE
CLASS="programlisting"
>&#13; % <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>fs listacl</B
></SPAN
> &#60;<VAR
CLASS="replaceable"
>dir/file path</VAR
>&#62;
</PRE
></P
><P
>You need the indicated permissions:</P
><UL
><LI
><P
>To access, copy, or save a file, you must have the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>l</B
></SPAN
> (<SPAN
CLASS="bold"
><B
CLASS="emphasis"
>lookup</B
></SPAN
>) permission on the directory and on all directories above it in the pathname.</P
></LI
><LI
><P
>To save changes to an existing file, you must in addition have the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>w</B
></SPAN
> (<SPAN
CLASS="bold"
><B
CLASS="emphasis"
>write</B
></SPAN
>) permission. To create a new file, you must in addition have the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>i</B
></SPAN
> (<SPAN
CLASS="bold"
><B
CLASS="emphasis"
>insert</B
></SPAN
>) and <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>w</B
></SPAN
>
permissions.</P
></LI
><LI
><P
>To copy a file between two directories, you must in addition have the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>r</B
></SPAN
>
(<SPAN
CLASS="bold"
><B
CLASS="emphasis"
>read</B
></SPAN
>) permission on the source directory and the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>i</B
></SPAN
>
permission on the destination directory.</P
></LI
></UL
><P
>If you do not have the necessary permissions but own the directory, you always have the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>a</B
></SPAN
> (<SPAN
CLASS="bold"
><B
CLASS="emphasis"
>administer</B
></SPAN
>) permission even if you do not appear on the ACL.
Issue the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>fs setacl</B
></SPAN
> command to grant yourself the necessary permissions. For complete
instructions, see <A
HREF="c1444.html#HDRWQ54"
>Changing an ACL</A
>.</P
><PRE
CLASS="programlisting"
>&#13; % <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>fs setacl -dir</B
></SPAN
> &#60;<VAR
CLASS="replaceable"
>directory</VAR
>&#62;<SUP
>+</SUP
> <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>-acl</B
></SPAN
> &#60;<VAR
CLASS="replaceable"
>access list entries</VAR
>&#62;<SUP
>+</SUP
>
</PRE
><P
>If you do not have the necessary permissions and do not own the directory, ask the owner or a system administrator to
grant them to you. If they add you to a group that has the required permissions, you must issue the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>klog</B
></SPAN
> command to reauthenticate before you can exercise them.</P
><P
>If you still cannot access the file even though you have the necessary permissions, contact your system administrator
for help in investigating further possible causes of your problem. If you still cannot copy or save the file even though you
have the necessary permissions, proceed to Step <A
HREF="c3402.html#LINOSAVE-QUOTA"
>4</A
>.</P
></LI
><LI
><P
><A
NAME="LINOSAVE-QUOTA"
></A
>If copying a file, issue the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>fs listquota</B
></SPAN
> 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 <A
HREF="c1095.html#HDRWQ39"
>Displaying Volume Quota</A
>. <PRE
CLASS="programlisting"
>&#13; % <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>fs listquota</B
></SPAN
> &#60;<VAR
CLASS="replaceable"
>dir/file path</VAR
>&#62;
</PRE
></P
><P
>The command produces output as in the following example:</P
><PRE
CLASS="programlisting"
>&#13; % <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>fs listquota /afs/abc.com/usr/terry</B
></SPAN
>
Volume Name Quota Used % Used Partition
user.terry 10000 3400 34% 86%
</PRE
><UL
><LI
><P
>If the value in the <SAMP
CLASS="computeroutput"
>Partition</SAMP
> field is not close to 100%, the partition is not
almost full. Check the value in the <SAMP
CLASS="computeroutput"
>% Used</SAMP
> field. If it is close to 100%, then the
volume is almost full. If possible, delete files from the volume that are no longer needed, or ask your system
administrator to increase the volume's quota.</P
><P
>If the value in the <SAMP
CLASS="computeroutput"
>% Used</SAMP
> field is not close to 100% (is, say, 90% or less),
then it is unlikely that you are exceeding the volume's quota, unless the file is very large or the volume's quota is
small. Contact your system administrator for help in investigating further possible causes of your problem.</P
></LI
><LI
><P
>If the value in the <SAMP
CLASS="computeroutput"
>Partition</SAMP
> field is very close to 100%, the partition is
possibly nearly full. However, server machine partitions are usually very large and can still have enough space for an
average file when nearly full. You can either ask your system administrator about the partition's status, or issue the
<SPAN
CLASS="bold"
><B
CLASS="emphasis"
>fs examine</B
></SPAN
> command. The final line in its output reports how many kilobyte blocks are
still available on the partition. For complete instructions, see <A
HREF="c1095.html#HDRWQ39"
>Displaying Volume Quota</A
>.
<PRE
CLASS="programlisting"
>&#13; % <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>fs examine</B
></SPAN
> &#60;<VAR
CLASS="replaceable"
>dir/file path</VAR
>&#62;
</PRE
></P
><P
>If there is enough free space on the partition but you still cannot save the file, ask your system administrator
for help in investigating further possible causes of your problem.</P
></LI
></UL
></LI
></OL
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="HDRWQ78"
>Problem: Accidentally Removed Your Entry from an ACL</A
></H1
><P
> </P
><OL
TYPE="1"
><LI
><P
>If you own the directory from which you have accidentally removed your ACL entry, then you actually still have the
<SPAN
CLASS="bold"
><B
CLASS="emphasis"
>a</B
></SPAN
> (<SPAN
CLASS="bold"
><B
CLASS="emphasis"
>administer</B
></SPAN
>) permission even if it does not appear on
the ACL. You normally own your home directory and all of its subdirectories, for instance. Issue the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>fs setacl</B
></SPAN
> command to grant yourself all other permissions. For complete instructions, see <A
HREF="c1444.html#HDRWQ55"
>To Add, Remove, or Edit Normal ACL Permissions</A
>. <PRE
CLASS="programlisting"
>&#13; % <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>fs setacl -dir</B
></SPAN
> &#60;<VAR
CLASS="replaceable"
>directory</VAR
>&#62; <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>-acl &#60;</B
></SPAN
><VAR
CLASS="replaceable"
>your_username</VAR
>&#62; <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>all</B
></SPAN
>
</PRE
></P
><P
>For <VAR
CLASS="replaceable"
>directory</VAR
>, provide the complete pathname to the directory (for example, <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>/afs/abc.com/usr/</B
></SPAN
><VAR
CLASS="replaceable"
>your_username</VAR
>). This is necessary because AFS cannot
interpret pathname abbreviations if you do not have the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>l</B
></SPAN
> (<SPAN
CLASS="bold"
><B
CLASS="emphasis"
>lookup</B
></SPAN
>) permission.</P
></LI
><LI
><P
>If you do not own the directory, issue the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>fs listacl</B
></SPAN
> to check if any remaining
entries grant you the permissions you need (perhaps you belong to one or more groups that appear on the ACL). For complete
instructions, see <A
HREF="c1444.html#HDRWQ53"
>To display an ACL</A
>. <PRE
CLASS="programlisting"
>&#13; % <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>fs listacl</B
></SPAN
> &#60;<VAR
CLASS="replaceable"
>dir/file path</VAR
>&#62;
</PRE
></P
><UL
><LI
><P
>The following message displays the directory's ACL. If you need permissions that no entry currently grants you,
ask the directory's owner or your system administrator for help. <PRE
CLASS="programlisting"
>&#13; Access list for &#60;<VAR
CLASS="replaceable"
>dir/file path</VAR
>&#62; is
Normal rights
<VAR
CLASS="replaceable"
>list of entries</VAR
>
</PRE
></P
></LI
><LI
><P
>If the command returns the following error message instead of an ACL, then you do not have the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>l</B
></SPAN
> permission. <PRE
CLASS="programlisting"
>&#13; fs: You don't have the required access rights on '<VAR
CLASS="replaceable"
>dir/file path</VAR
>'
</PRE
></P
><P
>Ask the directory's owner or your system administrator to grant you the permissions you need. If they add you to a
group that has the required permissions, you must issue the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>klog</B
></SPAN
> command to
reauthenticate before you can exercise them.</P
></LI
></UL
></LI
></OL
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="HDRWQ79"
>Error Message: "afs: Lost contact with fileserver"</A
></H1
><P
>Issue the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>fs checkservers</B
></SPAN
> command to check the status of file server machines. For
complete instructions, see <A
HREF="c1095.html#HDRWQ41"
>Checking the Status of Server Machines</A
>.</P
><PRE
CLASS="programlisting"
>&#13; % <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>fs checkservers &#38;</B
></SPAN
>
</PRE
><UL
><LI
><P
>If the following message appears, ask your system administrator for assistance in diagnosing the cause of the
<SAMP
CLASS="computeroutput"
>Lost contact</SAMP
> error message. <PRE
CLASS="programlisting"
>&#13; All servers are running.
</PRE
></P
></LI
><LI
><P
>Output like the following indicates that your Cache Manager cannot reach the indicated file server machines. You must
wait until they are again accessible before continuing to work with the files that are stored on them. <PRE
CLASS="programlisting"
>&#13; These servers unavailable due to network or server problem:
<VAR
CLASS="replaceable"
>list_of_machines</VAR
>.
</PRE
></P
></LI
></UL
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="Header_155"
>Error Message: "<VAR
CLASS="replaceable"
>command</VAR
>: Connection timed out"</A
></H1
><P
>Issue the <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>fs checkservers</B
></SPAN
> command as described in <A
HREF="c3402.html#HDRWQ79"
>Error Message:
afs: Lost contact with fileserver</A
>. </P
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="Header_156"
>Error Message: "fs: You don't have the required access rights on '<VAR
CLASS="replaceable"
>file</VAR
>'"</A
></H1
><P
>You do not have the ACL permissions you need to perform the operation you are attempting. If you own the directory and
have accidentally removed yourself from the ACL, see <A
HREF="c3402.html#HDRWQ78"
>Problem: Accidentally Removed Your Entry from an
ACL</A
>. Otherwise, ask the directory's owner or your system administrator to grant you the appropriate permissions.
</P
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="Header_157"
>Error Message: "afs: failed to store file"</A
></H1
><P
>Follow the instructions in <A
HREF="c3402.html#HDRWQ77"
>Problem: Cannot Access, Copy, or Save File</A
>.</P
></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="c2454.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="a3632.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Using Groups</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Using the NFS/AFS Translator</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

1774
doc/xml/UserGuide/c569.html
View File

File diff suppressed because it is too large Load Diff

455
doc/xml/UserGuide/f24.html
View File

@ -1,455 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>About This Guide</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="AFS User Guide"
HREF="book1.html"><LINK
REL="PREVIOUS"
TITLE="AFS User Guide"
HREF="book1.html"><LINK
REL="NEXT"
TITLE="An Introduction to AFS"
HREF="c113.html"></HEAD
><BODY
CLASS="preface"
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 User Guide: Version 3.6</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="book1.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="c113.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="preface"
><H1
><A
NAME="HDRWQ1"
></A
>About This Guide</H1
><P
>This section describes the purpose, organization, and conventions of this document.</P
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="HDRPREFAUDPUR"
>Audience and Purpose</A
></H1
><P
>This guide describes concepts and procedures for accessing information stored in the AFS filespace. It is intended for AFS
users who are familiar with UNIX but not necessarily AFS.</P
><P
>The first chapter describes basic AFS concepts and guidelines for using it, and summarizes some of the differences between
the UNIX file system and AFS. The remaining chapters explain how to perform basic AFS functions, including logging in, changing
a password, listing information, protecting files, creating groups, and troubleshooting. Concepts important to a specific task
or group of related tasks are presented in context, just prior to the procedures. Many examples are provided.</P
><P
>Instructions generally include only the commands and command options necessary for a specific task. For a complete list of
AFS commands and description of all options available on every command, see the <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>IBM AFS Administration
Reference</I
></SPAN
>.</P
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="HDRPREFORGAN"
>Document Organization</A
></H1
><P
>This document is divided into the following chapters.</P
><P
><A
HREF="c113.html"
>An Introduction to AFS</A
> introduces the basic concepts and functions of AFS. To use AFS
successfully, it is important to be familiar with the terms and concepts described in this chapter.</P
><P
><A
HREF="c569.html"
>Using AFS</A
> describes how to use AFS's basic features: how to log in and authenticate, unlog,
log out, access AFS files and directories in AFS, and change your password.</P
><P
><A
HREF="c1095.html"
>Displaying Information about AFS</A
> describes how to display information about AFS volume
quota and location, file server machine status, and the foreign cells you can access.</P
><P
><A
HREF="c1444.html"
>Protecting Your Directories and Files</A
> describes how to protect your data using AFS access
control lists (ACLs).</P
><P
><A
HREF="c2454.html"
>Using Groups</A
> describes how to create and manage groups.</P
><P
><A
HREF="c3402.html"
>Troubleshooting</A
> outlines step-by-step diagnostic and corrective steps for specific
problems.</P
><P
><A
HREF="a3632.html"
>Appendix A, Using the NFS/AFS Translator</A
> describes how to use the NFS/AFS Translator to
access the AFS filespace from an NFS client machine.</P
><P
><A
HREF="a3812.html"
>Appendix B, AFS Command Syntax and Online Help</A
> describes AFS command syntax and how to
obtain online information about commands.</P
><P
><A
HREF="g4153.html"
>Appendix C, Glossary</A
> defines terms used in the <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>IBM AFS User
Guide</I
></SPAN
>.</P
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="HDRUSERFRONTHOWTO"
>How To Use This Document</A
></H1
><P
>Before you begin using AFS, read <A
HREF="c113.html"
>An Introduction to AFS</A
>. Next, follow the procedures
outlined in <A
HREF="c569.html"
>Using AFS</A
> to get started using AFS as an authenticated user. It describes how to
access files in the AFS filespace and how to end an AFS session. Consult the other chapters as you need to perform the tasks
they describe.</P
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="HDRPREFRELATE"
>Related Documents</A
></H1
><P
>The AFS Documentation Kit also includes the following documents:
<UL
><LI
><P
>The <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>IBM AFS Administration Reference</I
></SPAN
> details the syntax of each AFS command and is intended for
the experienced AFS administrator, programmer, or user. For each AFS command, the <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>IBM AFS Administration
Reference</I
></SPAN
> lists the command syntax, aliases and abbreviations, description, arguments, warnings, output,
examples, and related topics. Commands are organized alphabetically.</P
></LI
><LI
><P
>The <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>IBM AFS Administration Guide</I
></SPAN
> describes concepts and procedures necessary for administering an
AFS cell, as well as more extensive coverage of the topics in the <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>IBM AFS User Guide</I
></SPAN
>.</P
></LI
><LI
><P
>The <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>IBM AFS Quick Beginnings</I
></SPAN
> provides instructions for installing AFS server and client
machines.</P
></LI
></UL
>
</P
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="HDRTYPO_CONV"
>Typographical Conventions</A
></H1
><P
>This document uses the following typographical conventions:
<UL
><LI
><P
>Command and option names appear in <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>bold type</B
></SPAN
> in syntax definitions, examples, and
running text. Names of directories, files, machines, partitions, volumes, and users also appear in <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>bold type</B
></SPAN
>.</P
></LI
><LI
><P
>Variable information appears in <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>italic type</I
></SPAN
>. This includes user-supplied information on command
lines and the parts of prompts that differ depending on who issues the command. New terms also appear in <SPAN
CLASS="emphasis"
><I
CLASS="emphasis"
>italic
type</I
></SPAN
>.</P
></LI
><LI
><P
>Examples of screen output and file contents appear in <SAMP
CLASS="computeroutput"
>monospace type</SAMP
>.</P
></LI
></UL
>
</P
><P
>In addition, the following symbols appear in command syntax definitions, both in the documentation and in AFS online help
statements. When issuing a command, do not type these symbols.
<UL
><LI
><P
>Square brackets <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>[ ]</B
></SPAN
> surround optional items.</P
></LI
><LI
><P
>Angle brackets <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>&#60; &#62;</B
></SPAN
> surround user-supplied values in AFS commands.</P
></LI
><LI
><P
>A superscripted plus sign <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>+</B
></SPAN
> follows an argument that accepts more than one
value.</P
></LI
><LI
><P
>The percent sign <SAMP
CLASS="computeroutput"
>%</SAMP
> represents the regular command shell prompt. Some operating
systems possibly use a different character for this prompt.</P
></LI
><LI
><P
>The number sign <SAMP
CLASS="computeroutput"
>#</SAMP
> represents the command shell prompt for the local superuser
<SPAN
CLASS="bold"
><B
CLASS="emphasis"
>root</B
></SPAN
>. Some operating systems possibly use a different character for this prompt.</P
></LI
><LI
><P
>The pipe symbol <SPAN
CLASS="bold"
><B
CLASS="emphasis"
>|</B
></SPAN
> in a command syntax statement separates mutually exclusive values
for an argument.</P
></LI
></UL
>
</P
><P
>For additional information on AFS commands, including a description of command string components, acceptable abbreviations
and aliases, and how to get online help for commands, see <A
HREF="a3812.html"
>Appendix B, AFS Command Syntax and Online
Help</A
>.</P
></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="book1.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="c113.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>AFS User Guide</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>An Introduction to AFS</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

1669
doc/xml/UserGuide/g4153.html
View File

File diff suppressed because it is too large Load Diff

4843
doc/xml/UserGuide/i4608.html
View File

File diff suppressed because it is too large Load Diff

BIN
doc/xml/banner.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 8.1 KiB

BIN
doc/xml/books.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 332 B

BIN
doc/xml/down.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 269 B

BIN
doc/xml/home.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 241 B

BIN
doc/xml/index.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 241 B

55
doc/xml/index.html Normal file
View File

@ -0,0 +1,55 @@
<html>
<head>
<meta http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<title>OpenAFS Documentation</title>
</head>
<body bgcolor=white lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p>
<a href="http://www.openafs.org/">
<img border=0 width=201 height=139 src="logo.jpg" align=left title="www.openafs.org"></a>
<a name="Top_Of_Page"></a></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<h1>Documentation</h1>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>Welcome to the OpenAFS Documentation set!</p>
<h3>Documentation:</h3>
<ul>
<li>Release Notes:
<ul>
<!-- <li><a href="ReleaseNotesUnix/index.html">Unix</a></li> -->
<li><a href="ReleaseNotesWindows/index.html">Microsoft Windows</a></li>
</ul>
</li>
<li>Quick Start Guides:
<ul>
<li><a href="QuickStartUnix/index.html">Unix</a></li>
<li><a href="http://www.dementia.org/twiki/bin/view/AFSLore/WindowsEndUserQuickStartGuide">Microsoft Windows</a></li>
</ul>
</li>
<li><a href="UserGuide/index.html">User Guide</a></li>
<li><a href="AdminGuide/index.html">Administrator Guide</a></li>
<li><a href="Reference/index">Reference Manual</a></li>
</ul>
<a name="Bot_Of_Page"></a>
</div>
</body>
</html>

BIN
doc/xml/logo.jpg Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 35 KiB

BIN
doc/xml/next.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 271 B

BIN
doc/xml/prev.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 273 B

BIN
doc/xml/up.gif Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 268 B