<chapter id="HDRWQ17">
<title>Installing the First AFS Machine</title>
+ <para>
<indexterm>
<primary>file server machine</primary>
<secondary>first AFS machine</secondary>
</indexterm>
- <para>This chapter describes how to install the first AFS machine in your cell, configuring it as both a file server machine and a
+ This chapter describes how to install the first AFS machine in your cell, configuring it as both a file server machine and a
client machine. After completing all procedures in this chapter, you can remove the client functionality if you wish, as described
in <link linkend="HDRWQ98">Removing Client Functionality</link>.</para>
<sect1 id="Header_29">
<title>Requirements and Configuration Decisions</title>
- <para>The instructions in this chapter assume that you meet the following requirements. <itemizedlist>
+ <para>The instructions in this chapter assume that you meet the following requirements.
+ <itemizedlist>
<listitem>
<para>You are logged onto the machine's console as the local superuser <emphasis role="bold">root</emphasis></para>
</listitem>
</listitem>
<listitem>
- <para>You can access the data on the AFS CD-ROMs, either through a local CD drive or via an NFS mount of a CD drive
- attached to a machine that is accessible by network</para>
+ <para>You have either installed the provided OpenAFS packages for
+ your system, have access to a binary distribution tarball, or have
+ successfully built OpenAFS from source</para>
+ </listitem>
+
+ <listitem>
+ <para>You have a Kerberos v5 realm running for your site. If you are
+ working with an existing cell which uses legacy
+ <emphasis role="bold">kaserver</emphasis> or Kerberos v4 for
+ authentication, please see
+ <link linkend="KAS001">kaserver and Legacy Kerberos v4 Authentication</link>
+ for the modifications required to this installation procedure.</para>
+ </listitem>
+
+ <listitem>
+ <para>You have NTP or a similar time service deployed to ensure
+ rough clock syncronistation between your clients and servers.</para>
</listitem>
</itemizedlist></para>
<para>You must make the following configuration decisions while installing the first AFS machine. To speed the installation
- itself, it is best to make the decisions before beginning. See the chapter in the <emphasis>IBM AFS Administration
+ itself, it is best to make the decisions before beginning. See the chapter in the <emphasis>OpenAFS Administration
Guide</emphasis> about issues in cell administration and configuration for detailed guidelines. <indexterm>
<primary>cell name</primary>
</listitem>
<listitem>
- <para>Decide whether to use the standard AFS authentication and authorization software or Kerberos as obtained from
- another source. On several system types, the decision determines how you incorporate AFS into the machine's authentication
- system. If you wish to use Kerberos, contact the AFS Product Support group now to learn about how you must modify the
- installation procedure.</para>
- </listitem>
-
- <listitem>
<para>Decide how big to make the client cache</para>
</listitem>
<title>Overview: Installing Server Functionality</title>
<para>In the first phase of installing your cell's first AFS machine, you install file server and database server functionality
- by performing the following procedures: <orderedlist>
+ by performing the following procedures:
+ <orderedlist>
<listitem>
<para>Choose which machine to install as the first AFS machine</para>
</listitem>
</listitem>
<listitem>
- <para>On some system types, install and configure an AFS-modified version of the <emphasis role="bold">fsck</emphasis>
+ <para>On some system types (very rare), install and configure
+ an AFS-modified version of the <emphasis role="bold">fsck</emphasis>
program</para>
</listitem>
</listitem>
<listitem>
- <para>Start the database server processes: Authentication Server, Backup Server, Protection Server, and Volume Location
+ <para>Start the database server processes: Backup Server, Protection Server, and Volume Location
(VL) Server</para>
</listitem>
</listitem>
<listitem>
- <para>Start the server portion of the Update Server</para>
+ <para>Optionally, start the server portion of the Update Server</para>
</listitem>
- <listitem>
- <para>Start the controller process (called <emphasis role="bold">runntp</emphasis>) for the Network Time Protocol Daemon,
- which synchronizes machine clocks</para>
- </listitem>
</orderedlist></para>
</sect1>
<sect1 id="HDRWQ19">
<title>Choosing the First AFS Machine</title>
- <para>The first AFS machine you install must have sufficient disk space to store AFS volumes. To take best advantage of AFS's
- capabilities, store client-side binaries as well as user files in volumes. When you later install additional file server
+ <para>The first AFS machine you install must have sufficient disk space to store AFS volumes.
+ When you later install additional file server
machines in your cell, you can distribute these volumes among the different machines as you see fit.</para>
- <para>These instructions configure the first AFS machine as a <emphasis>database server machine</emphasis>, the <emphasis>binary
- distribution machine</emphasis> for its system type, and the cell's <emphasis>system control machine</emphasis>. For a
- description of these roles, see the <emphasis>IBM AFS Administration Guide</emphasis>.</para>
+ <para>These instructions configure the first AFS machine as a <emphasis>database server machine</emphasis>, and optionally as the <emphasis>binary
+ distribution machine</emphasis> for its system type and the cell's <emphasis>system control machine</emphasis>. For a
+ description of these roles, see the <emphasis>OpenAFS Administration Guide</emphasis>.</para>
<para>Installation of additional machines is simplest if the first machine has the lowest IP address of any database server
machine you currently plan to install. If you later install database server functionality on a machine with a lower IP address,
<title>Creating AFS Directories</title>
<indexterm>
- <primary>CD-ROM</primary>
-
- <secondary>creating /cdrom directory</secondary>
-
- <tertiary>first AFS machine</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>cdrom directory</primary>
-
- <secondary>first AFS machine</secondary>
- </indexterm>
-
- <indexterm>
- <primary>first AFS machine</primary>
-
- <secondary>/cdrom directory</secondary>
- </indexterm>
-
- <indexterm>
- <primary>creating</primary>
-
- <secondary>/cdrom directory</secondary>
-
- <tertiary>first AFS machine</tertiary>
- </indexterm>
-
- <indexterm>
<primary>usr/afs directory</primary>
<secondary>first AFS machine</secondary>
<secondary>see alphabetized entries without initial slash</secondary>
</indexterm>
- <para>Create the <emphasis role="bold">/usr/afs</emphasis> and <emphasis role="bold">/usr/vice/etc</emphasis> directories on the
- local disk, to house server and client files respectively. Subsequent instructions copy files from the AFS CD-ROM into them.
- Create the <emphasis role="bold">/cdrom</emphasis> directory as a mount point for CD-ROMs, if it does not already exist.</para>
-
- <programlisting>
+ <para>If you are installing from packages (such as Debian .deb or
+ Fedora/SuSe .rpm files), you should now install all of the available
+ OpenAFS packages for your system type. Typically, these will include
+ packages for client and server functionality, and a seperate package
+ containing a suitable kernel module for your running kernel. Consult
+ the package lists on the OpenAFS website to determine the packages
+ appropriate for your system. The preparer of such packages may
+ have included some helper scripts to partially automate the
+ creation of a new cell; such scripts can supersede much of the
+ procedures described in the rest of this document.</para>
+
+ <para>If you are installing from a tarfile, or from a locally compiled
+ source tree you should create the <emphasis role="bold">/usr/afs</emphasis>
+ and <emphasis role="bold">/usr/vice/etc</emphasis> directories on the
+ local disk, to house server and client files respectively. Subsequent
+ instructions copy files from the distribution tarfile into them. </para>
+<programlisting>
# <emphasis role="bold">mkdir /usr/afs</emphasis>
# <emphasis role="bold">mkdir /usr/vice</emphasis>
# <emphasis role="bold">mkdir /usr/vice/etc</emphasis>
- # <emphasis role="bold">mkdir /cdrom</emphasis>
</programlisting>
</sect1>
<listitem>
<para>Incorporate AFS modifications into the kernel.</para>
- <para>The kernel on every AFS file server and client machine must incorporate AFS extensions. On machines that use a
- dynamic kernel module loader, it is conventional to alter the machine's initialization script to load the AFS extensions
- at each reboot. <indexterm>
+ <para>The kernel on every AFS client machine and, on some systems,
+ the AFS fileservers, must incorporate AFS extensions. On machines
+ that use a dynamic kernel module loader, it is conventional to
+ alter the machine's initialization script to load the AFS extensions
+ at each reboot. The preparer of OS-format binary packages
+ may have included an init script which automates the loading
+ of the needed kernel module, eliminating a need to manually
+ configure this step. <indexterm>
<primary>AFS server partition</primary>
<secondary>mounted on /vicep directory</secondary>
<listitem>
<para>Configure server partitions or logical volumes to house AFS volumes.</para>
- <para>Every AFS file server machine must have at least one partition or logical volume dedicated to storing AFS volumes
+ <para>Every AFS file server machine should have at least one partition or logical volume dedicated to storing AFS volumes
(for convenience, the documentation hereafter refers to partitions only). Each server partition is mounted at a directory
named <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>, where <replaceable>xx</replaceable> is one or
two lowercase letters. By convention, the first 26 partitions are mounted on the directories called <emphasis
role="bold">/vicepa</emphasis> through <emphasis role="bold">/vicepz</emphasis>, the 27th one is mounted on the <emphasis
role="bold">/vicepaa</emphasis> directory, and so on through <emphasis role="bold">/vicepaz</emphasis> and <emphasis
role="bold">/vicepba</emphasis>, continuing up to the index corresponding to the maximum number of server partitions
- supported in the current version of AFS (which is specified in the <emphasis>IBM AFS Release Notes</emphasis>).</para>
+ supported in the current version of AFS (which is specified in the <emphasis>OpenAFS Release Notes</emphasis>).</para>
<para>The <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable> directories must reside in the file server
machine's root directory, not in one of its subdirectories (for example, <emphasis role="bold">/usr/vicepa</emphasis> is
- not an acceptable directory location).</para>
+ not an acceptable directory location).
+
+ The <emphasis role="bold">fileserver</emphasis> will refuse to
+ mount
+ any <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>
+ folders that are not separate partitions without additional
+ configuration. </para>
+
+ <warning>
+ <para>The separate partition requirement may be overridden by
+ creating a file named
+ <emphasis role="bold">/vicep<replaceable>xx</replaceable>/AlwaysAttach</emphasis>;
+ however, mixed-use partitions, whether cache or fileserver,
+ have the risk that a non-AFS use will fill the partition and
+ not leave enough free space for AFS. Even though it is
+ allowed, be wary of configuring a mixed-use partition
+ without understanding the ramifications of doing so with the
+ workload on your filesystem.
+ <indexterm>
+ <primary>AFS server partition</primary>
+ <secondary>AlwaysAttach</secondary>
+ </indexterm>
+ </para>
+ </warning>
<para>You can also add or remove server partitions on an existing file server machine. For instructions, see the chapter
- in the <emphasis>IBM AFS Administration Guide</emphasis> about maintaining server machines.</para>
+ in the <emphasis>OpenAFS Administration Guide</emphasis> about maintaining server machines.</para>
<note>
<para>Not all file system types supported by an operating system are necessarily supported as AFS server partitions. For
- possible restrictions, see the <emphasis>IBM AFS Release Notes</emphasis>.</para>
+ possible restrictions, see the <emphasis>OpenAFS Release Notes</emphasis>.</para>
</note>
</listitem>
<listitem>
- <para>On some system types, install and configure a modified <emphasis role="bold">fsck</emphasis> program which
+ <para>On (rare) system types using the <emphasis role="bold">inode</emphasis> storage format, install and configure a modified <emphasis role="bold">fsck</emphasis> program which
recognizes the structures that the File Server uses to organize volume data on AFS server partitions. The <emphasis
role="bold">fsck</emphasis> program provided with the operating system does not understand the AFS data structures, and so
removes them to the <emphasis role="bold">lost+found</emphasis> directory.</para>
<listitem>
<para>If the machine is to remain an AFS client machine, modify the machine's authentication system so that users obtain
an AFS token as they log into the local file system. Using AFS is simpler and more convenient for your users if you make
- the modifications on all client machines. Otherwise, users must perform a two-step login procedure (login to the local
- file system and then issue the <emphasis role="bold">klog</emphasis> command). For further discussion of AFS
- authentication, see the chapter in the <emphasis>IBM AFS Administration Guide</emphasis> about cell configuration and
+ the modifications on all client machines. Otherwise, users must perform a two or three step login procedure (login to the local
+ system, then obtain Kerberos credentials, and then issue the <emphasis role="bold">aklog</emphasis> command). For further discussion of AFS
+ authentication, see the chapter in the <emphasis>OpenAFS Administration Guide</emphasis> about cell configuration and
administration issues.</para>
</listitem>
</itemizedlist></para>
<para>To continue, proceed to the appropriate section: <itemizedlist>
<listitem>
- <para><link linkend="HDRWQ21">Getting Started on AIX Systems</link></para>
- </listitem>
-
- <listitem>
- <para><link linkend="HDRWQ26">Getting Started on Digital UNIX Systems</link></para>
- </listitem>
-
- <listitem>
- <para><link linkend="HDRWQ31">Getting Started on HP-UX Systems</link></para>
- </listitem>
-
- <listitem>
- <para><link linkend="HDRWQ36">Getting Started on IRIX Systems</link></para>
- </listitem>
-
- <listitem>
<para><link linkend="HDRWQ41">Getting Started on Linux Systems</link></para>
</listitem>
</itemizedlist></para>
</sect1>
- <sect1 id="HDRWQ21">
- <title>Getting Started on AIX Systems</title>
+ <sect1 id="HDRWQ41">
+ <title>Getting Started on Linux Systems</title>
+
+ <indexterm>
+ <primary>replacing fsck program</primary>
+
+ <secondary>not necessary on Linux</secondary>
+ </indexterm>
+
+ <indexterm>
+ <primary>fsck program</primary>
+
+ <secondary>on first AFS machine</secondary>
+
+ <tertiary>Linux</tertiary>
+ </indexterm>
+
+ <indexterm>
+ <primary>first AFS machine</primary>
+
+ <secondary>fsck program</secondary>
+
+ <tertiary>on Linux</tertiary>
+ </indexterm>
- <para>Begin by running the AFS initialization script to call the AIX kernel extension facility, which dynamically loads AFS
- modifications into the kernel. Then use the <emphasis role="bold">SMIT</emphasis> program to configure partitions for storing
- AFS volumes, and replace the AIX <emphasis role="bold">fsck</emphasis> program helper with a version that correctly handles AFS
- volumes. If the machine is to remain an AFS client machine, incorporate AFS into the AIX secondary authentication system.
<indexterm>
+ <primary>Linux</primary>
+
+ <secondary>fsck program replacement not necessary</secondary>
+ </indexterm>
+
+ <para>Since this guide was originally written, the procedure for starting
+ OpenAFS has diverged significantly between different Linux distributions.
+ The instructions that follow are appropriate for both the Fedora and
+ RedHat Enterprise Linux packages distributed by OpenAFS. Additional
+ instructions are provided for those building from source.</para>
+
+ <para>Begin by running the AFS client startup scripts, which call the
+ <emphasis role="bold">modprobe</emphasis> program to dynamically
+ load the AFS modifications into the kernel. Then create partitions for
+ storing AFS volumes. You do not need to replace the Linux <emphasis
+ role="bold">fsck</emphasis> program. If the machine is to remain an
+ AFS client machine, incorporate AFS into the machine's Pluggable
+ Authentication Module (PAM) scheme. <indexterm>
<primary>incorporating AFS kernel extensions</primary>
<secondary>first AFS machine</secondary>
- <tertiary>AIX</tertiary>
+ <tertiary>Linux</tertiary>
</indexterm> <indexterm>
<primary>AFS kernel extensions</primary>
<secondary>on first AFS machine</secondary>
- <tertiary>AIX</tertiary>
+ <tertiary>Linux</tertiary>
</indexterm> <indexterm>
<primary>first AFS machine</primary>
<secondary>AFS kernel extensions</secondary>
- <tertiary>on AIX</tertiary>
+ <tertiary>on Linux</tertiary>
</indexterm> <indexterm>
- <primary>AIX</primary>
+ <primary>Linux</primary>
<secondary>AFS kernel extensions</secondary>
<tertiary>on first AFS machine</tertiary>
</indexterm></para>
- <sect2 id="HDRWQ22">
- <title>Loading AFS into the AIX Kernel</title>
+ <sect2 id="HDRWQ42">
+ <title>Loading AFS into the Linux Kernel</title>
- <para>The AIX kernel extension facility is the dynamic kernel loader provided by IBM Corporation. AIX does not support
+ <para>The <emphasis role="bold">modprobe</emphasis> program is the dynamic kernel loader for Linux. Linux does not support
incorporation of AFS modifications during a kernel build.</para>
- <para>For AFS to function correctly, the kernel extension facility must run each time the machine reboots, so the AFS
- initialization script (included in the AFS distribution) invokes it automatically. In this section you copy the script to the
- conventional location and edit it to select the appropriate options depending on whether NFS is also to run.</para>
+ <para>For AFS to function correctly, the <emphasis role="bold">modprobe</emphasis> program must run each time the machine
+ reboots, so your distribution's AFS initialization script invokes it automatically. The script also includes
+ commands that select the appropriate AFS library file automatically. In this section you run the script.</para>
- <para>After editing the script, you run it to incorporate AFS into the kernel. In later sections you verify that the script
- correctly initializes all AFS components, then configure the AIX <emphasis role="bold">inittab</emphasis> file so that the
- script runs automatically at reboot. <orderedlist>
+ <para>In later sections you verify that the script correctly initializes all AFS components, then activate a configuration
+ variable, which results in the script being incorporated into the Linux startup and shutdown sequence.</para>
+
+ <para>The procedure for starting up OpenAFS depends upon your distribution</para>
+ <sect3>
+ <title>Fedora and RedHat Enterprise Linux</title>
+ <para>OpenAFS provides RPMS for all current Fedora and
+ RedHat Enterprise Linux (RHEL) releases prior to EL7 on the
+ OpenAFS web site and the OpenAFS yum repository.
+ <orderedlist>
<listitem>
- <para>Mount the AFS CD-ROM for AIX on the local <emphasis role="bold">/cdrom</emphasis> directory. For instructions on
- mounting CD-ROMs (either locally or remotely via NFS), see your AIX documentation. Then change directory as indicated.
- <programlisting>
- # <emphasis role="bold">cd /cdrom/rs_aix42/root.client/usr/vice/etc</emphasis>
-</programlisting></para>
+ <para>Browse to
+ http://dl.openafs.org/dl/openafs/<replaceable>VERSION</replaceable>,
+ where VERSION is the latest stable release of
+ OpenAFS for Unix. Download the
+ openafs-repository-<replaceable>VERSION</replaceable>.noarch.rpm
+ file for Fedora systems or the
+ openafs-repository-rhel-<replaceable>VERSION</replaceable>.noarch.rpm
+ file for RedHat-based systems.
+ </para>
</listitem>
-
<listitem>
- <para>Copy the AFS kernel library files to the local <emphasis role="bold">/usr/vice/etc/dkload</emphasis> directory,
- and the AFS initialization script to the <emphasis role="bold">/etc</emphasis> directory. <programlisting>
- # <emphasis role="bold">cp -rp dkload /usr/vice/etc</emphasis>
- # <emphasis role="bold">cp -p rc.afs /etc/rc.afs</emphasis>
-</programlisting></para>
+ <para>Install the downloaded RPM file using the following command:
+ <programlisting>
+# rpm -U openafs-repository*.rpm
+ </programlisting>
+ </para>
</listitem>
-
<listitem>
- <para>Edit the <emphasis role="bold">/etc/rc.afs</emphasis> script, setting the <computeroutput>NFS</computeroutput>
- variable as indicated.</para>
-
- <para>If the machine is not to function as an NFS/AFS Translator, set the <computeroutput>NFS</computeroutput> variable
- as follows.</para>
-
- <programlisting>
- NFS=$NFS_NONE
-</programlisting>
-
- <para>If the machine is to function as an NFS/AFS Translator and is running AIX 4.2.1 or higher, set the
- <computeroutput>NFS</computeroutput> variable as follows. Note that NFS must already be loaded into the kernel, which
- happens automatically on systems running AIX 4.1.1 and later, as long as the file <emphasis
- role="bold">/etc/exports</emphasis> exists.</para>
-
- <programlisting>
- NFS=$NFS_IAUTH
+ <para>Install the RPM set for your operating system using the yum command as follows:
+ <programlisting>
+# yum -y install openafs-client openafs-server openafs-krb5 kmod-openafs
+ </programlisting>
+
+ </para>
+ <para>Alternatively, you may use dynamically-compiled kernel
+ modules if you have the kernel headers, a compiler, and the
+ dkms package from
+ <ulink url="http://fedoraproject.org/wiki/EPEL"><citetitle>EPEL</citetitle></ulink> installed.
+
+ </para>
+ <para>To use dynamically-compiled kernel modules instead of statically compiled modules, use the following command instead of the kmod-openafs as shown above:
+ <programlisting>
+# yum install openafs-client openafs-server openafs-krb5 dkms-openafs
+ </programlisting>
+ </para>
+ </listitem>
+<!-- If you do this with current RHEL and Fedora releases you end up with
+ a dynroot'd client running - this breaks setting up the root.afs volume
+ as described later in this guide
+ <listitem>
+ <para>Run the AFS initialization script to load AFS extensions into
+ the kernel. You can ignore any error messages about the inability
+ to start the BOS Server or the Cache Manager or AFS client.</para>
+<programlisting>
+ # <emphasis role="bold">/etc/rc.d/init.d/openafs-client start</emphasis>
</programlisting>
</listitem>
+-->
+ </orderedlist>
+ </para>
+ </sect3>
+ <sect3>
+ <title>Debian and Ubuntu Linux</title>
+ <para>OpenAFS is available as binary packages from the Debian
+ linux distribution and its derivatives such as Ubuntu.
+ <orderedlist>
+ <listitem>
+ <para>Install the client and server packages using the following command:
+ <programlisting>
+# apt-get install openafs-client openafs-modules-dkms openafs-krb5 \
+ openafs-fileserver openafs-dbserver
+ </programlisting>
+ You will be prompted by debconf to select your cell name and
+ the size of your local cache.
+ </para>
+ </listitem>
+ </orderedlist>
+ </para>
+ <para>The Debian package also includes helper scripts
+ <literal>afs-newcell</literal> and <literal>afs-rootvol</literal>,
+ which can automate much of the remainder of this document.
+ </para>
+ </sect3>
+ <sect3>
+ <title>Systems built from source</title>
+ <para>If you are running a system where
+ you have built the system from
+ source yourself, you need to install the relevant components by hand:
+ </para>
+ <orderedlist>
+
+ <listitem>
+ <para>Unpack the distribution tarball. The examples below assume
+ that you have extracted and built OpenAFS in the
+ <emphasis role="bold">/tmp/afsdist</emphasis> directory. If you
+ pick a different location, substitute this in all of the following
+ examples. Once you have compiled the distribution,
+ change to the source directory as indicated.
+<programlisting>
+ # <emphasis role="bold">cd /tmp/afsdist</emphasis>
+</programlisting></para>
+ </listitem>
+
+ <listitem>
+ <para>Copy the AFS kernel library files to the local <emphasis role="bold">/usr/vice/etc/modload</emphasis> directory.
+ The filenames for the libraries have the format <emphasis
+ role="bold">libafs-</emphasis><replaceable>version</replaceable><emphasis role="bold">.o</emphasis>, where
+ <replaceable>version</replaceable> indicates the kernel build level. The string <emphasis role="bold">.mp</emphasis> in
+ the <replaceable>version</replaceable> indicates that the file is appropriate for machines running a multiprocessor
+ kernel. <programlisting>
+ # <emphasis role="bold">mkdir -p /usr/vice/etc/modload</emphasis>
+ # <emphasis role="bold">cp -rp src/libafs/*.ko /usr/vice/etc/modload</emphasis>
+</programlisting></para>
+ </listitem>
<listitem>
- <para>Invoke the <emphasis role="bold">/etc/rc.afs</emphasis> script to load AFS modifications into the kernel. You can
- ignore any error messages about the inability to start the BOS Server or the Cache Manager or AFS client.
- <programlisting>
- # <emphasis role="bold">/etc/rc.afs</emphasis>
+ <para>Copy the AFS initialization script to the local directory for initialization files (by convention, <emphasis
+ role="bold">/etc/rc.d/init.d</emphasis> on Linux machines). Note the removal of the <emphasis role="bold">.rc</emphasis>
+ extension as you copy the script. <programlisting>
+ # <emphasis role="bold">cp -p src/afsd/afs.rc.linux /etc/rc.d/init.d/afs</emphasis>
</programlisting></para>
</listitem>
- </orderedlist></para>
+
+ </orderedlist>
<indexterm>
<primary>configuring</primary>
-
+
<secondary>AFS server partition on first AFS machine</secondary>
- <tertiary>AIX</tertiary>
+ <tertiary>Linux</tertiary>
</indexterm>
<indexterm>
<secondary>configuring on first AFS machine</secondary>
- <tertiary>AIX</tertiary>
+ <tertiary>Linux</tertiary>
</indexterm>
<indexterm>
<secondary>AFS server partition</secondary>
- <tertiary>on AIX</tertiary>
+ <tertiary>on Linux</tertiary>
</indexterm>
<indexterm>
- <primary>AIX</primary>
+ <primary>Linux</primary>
<secondary>AFS server partition</secondary>
<tertiary>on first AFS machine</tertiary>
</indexterm>
+ </sect3>
</sect2>
- <sect2 id="HDRWQ23">
- <title>Configuring Server Partitions on AIX Systems</title>
+ <sect2 id="HDRWQ43">
+ <title>Configuring Server Partitions on Linux Systems</title>
<para>Every AFS file server machine must have at least one partition or logical volume dedicated to storing AFS volumes. Each
server partition is mounted at a directory named <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>, where
<replaceable>xx</replaceable> is one or two lowercase letters. The <emphasis
role="bold">/vicep</emphasis><replaceable>xx</replaceable> directories must reside in the file server machine's root
directory, not in one of its subdirectories (for example, <emphasis role="bold">/usr/vicepa</emphasis> is not an acceptable
- directory location). For additional information, see <link linkend="HDRWQ20">Performing Platform-Specific
- Procedures</link>.</para>
-
- <para>To configure server partitions on an AIX system, perform the following procedures: <orderedlist>
+ directory location). For additional information, see <link linkend="HDRWQ20">Performing Platform-Specific Procedures</link>.
+ <orderedlist>
<listitem>
<para>Create a directory called <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable> for each AFS server
partition you are configuring (there must be at least one). Repeat the command for each partition. <programlisting>
</listitem>
<listitem>
- <para>Use the <emphasis role="bold">SMIT</emphasis> program to create a journaling file system on each partition to be
- configured as an AFS server partition.</para>
- </listitem>
-
- <listitem>
- <para>Mount each partition at one of the <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>
- directories. Choose one of the following three methods: <itemizedlist>
- <listitem>
- <para>Use the <emphasis role="bold">SMIT</emphasis> program</para>
- </listitem>
-
- <listitem>
- <para>Use the <emphasis role="bold">mount -a</emphasis> command to mount all partitions at once</para>
- </listitem>
+ <para>Add a line with the following format to the file systems registry file, <emphasis
+ role="bold">/etc/fstab</emphasis>, for each directory just created. The entry maps the directory name to the disk
+ partition to be mounted on it. <programlisting>
+ /dev/<replaceable>disk</replaceable> /vicep<replaceable>xx</replaceable> ext2 defaults 0 2
+</programlisting></para>
- <listitem>
- <para>Use the <emphasis role="bold">mount</emphasis> command on each partition in turn</para>
- </listitem>
- </itemizedlist></para>
+ <para>The following is an example for the first partition being configured.</para>
- <para>Also configure the partitions so that they are mounted automatically at each reboot. For more information, refer
- to the AIX documentation.</para>
+ <programlisting>
+ /dev/sda8 /vicepa ext2 defaults 0 2
+</programlisting>
</listitem>
- </orderedlist></para>
-
- <indexterm>
- <primary>replacing fsck program</primary>
-
- <secondary>first AFS machine</secondary>
- <tertiary>AIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>fsck program</primary>
-
- <secondary>on first AFS machine</secondary>
-
- <tertiary>AIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>first AFS machine</primary>
-
- <secondary>fsck program</secondary>
-
- <tertiary>on AIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>AIX</primary>
-
- <secondary>fsck program</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm>
- </sect2>
-
- <sect2 id="HDRWQ24">
- <title>Replacing the fsck Program Helper on AIX Systems</title>
-
- <para>In this section, you make modifications to guarantee that the appropriate <emphasis role="bold">fsck</emphasis> program
- runs on AFS server partitions. The <emphasis role="bold">fsck</emphasis> program provided with the operating system must never
- run on AFS server partitions. Because it does not recognize the structures that the File Server uses to organize volume data,
- it removes all of the data. To repeat:</para>
-
- <para><emphasis role="bold">Never run the standard fsck program on AFS server partitions. It discards AFS
- volumes.</emphasis></para>
-
- <para>On AIX systems, you do not replace the <emphasis role="bold">fsck</emphasis> binary itself, but rather the
- <emphasis>program helper</emphasis> file included in the AIX distribution as <emphasis
- role="bold">/sbin/helpers/v3fshelper</emphasis>. <orderedlist>
<listitem>
- <para>Move the AIX <emphasis role="bold">fsck</emphasis> program helper to a safe location and install the version from
- the AFS distribution in its place. The AFS CD-ROM must still be mounted at the <emphasis role="bold">/cdrom</emphasis>
- directory. <programlisting>
- # <emphasis role="bold">cd /sbin/helpers</emphasis>
- # <emphasis role="bold">mv v3fshelper v3fshelper.noafs</emphasis>
- # <emphasis role="bold">cp -p /cdrom/rs_aix42/root.server/etc/v3fshelper v3fshelper</emphasis>
+ <para>Create a file system on each partition that is to be mounted at a <emphasis
+ role="bold">/vicep</emphasis><replaceable>xx</replaceable> directory. The following command is probably appropriate, but
+ consult the Linux documentation for more information. <programlisting>
+ # <emphasis role="bold">mkfs -v /dev/</emphasis><replaceable>disk</replaceable>
</programlisting></para>
</listitem>
<listitem>
+ <para>Mount each partition by issuing either the <emphasis role="bold">mount -a</emphasis> command to mount all
+ partitions at once or the <emphasis role="bold">mount</emphasis> command to mount each partition in turn.</para>
+ </listitem>
+
+ <listitem>
<para>If you plan to retain client functionality on this machine after completing the installation, proceed to <link
- linkend="HDRWQ25">Enabling AFS Login on AIX Systems</link>. Otherwise, proceed to <link linkend="HDRWQ50">Starting the
+ linkend="HDRWQ44">Enabling AFS Login on Linux Systems</link>. Otherwise, proceed to <link linkend="HDRWQ50">Starting the
BOS Server</link>.</para>
</listitem>
</orderedlist></para>
<secondary>file server machine</secondary>
- <tertiary>AIX</tertiary>
+ <tertiary>Linux</tertiary>
</indexterm>
<indexterm>
<secondary>on file server machine</secondary>
- <tertiary>AIX</tertiary>
+ <tertiary>Linux</tertiary>
</indexterm>
<indexterm>
<secondary>AFS login</secondary>
- <tertiary>on AIX</tertiary>
+ <tertiary>on Linux</tertiary>
</indexterm>
<indexterm>
- <primary>AIX</primary>
+ <primary>Linux</primary>
<secondary>AFS login</secondary>
</indexterm>
<indexterm>
- <primary>secondary authentication system (AIX)</primary>
+ <primary>PAM</primary>
+
+ <secondary>on Linux</secondary>
- <secondary>server machine</secondary>
+ <tertiary>file server machine</tertiary>
</indexterm>
</sect2>
- <sect2 id="HDRWQ25">
- <title>Enabling AFS Login on AIX Systems</title>
-
- <note>
- <para>If you plan to remove client functionality from this machine after completing the installation, skip this section and
- proceed to <link linkend="HDRWQ50">Starting the BOS Server</link>.</para>
- </note>
-
- <para>Follow the instructions in this section to incorporate AFS modifications into the AIX secondary authentication system.
- <orderedlist>
- <listitem>
- <para>Issue the <emphasis role="bold">ls</emphasis> command to verify that the <emphasis
- role="bold">afs_dynamic_auth</emphasis> and <emphasis role="bold">afs_dynamic_kerbauth</emphasis> programs are installed
- in the local <emphasis role="bold">/usr/vice/etc</emphasis> directory. <programlisting>
- # <emphasis role="bold">ls /usr/vice/etc</emphasis>
-</programlisting></para>
-
- <para>If the files do not exist, mount the AFS CD-ROM for AIX (if it is not already), change directory as indicated, and
- copy them.</para>
-
- <programlisting>
- # <emphasis role="bold">cd /cdrom/rs_aix42/root.client/usr/vice/etc</emphasis>
- # <emphasis role="bold">cp -p afs_dynamic* /usr/vice/etc</emphasis>
-</programlisting>
- </listitem>
-
- <listitem>
- <para>Edit the local <emphasis role="bold">/etc/security/user</emphasis> file, making changes to the indicated stanzas:
- <itemizedlist>
- <listitem>
- <para>In the default stanza, set the <computeroutput>registry</computeroutput> attribute to <emphasis
- role="bold">DCE</emphasis> (not to <emphasis role="bold">AFS</emphasis>), as follows: <programlisting>
- registry = DCE
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>In the default stanza, set the <computeroutput>SYSTEM</computeroutput> attribute as indicated.</para>
-
- <para>If the machine is an AFS client only, set the following value:</para>
-
- <programlisting>
- SYSTEM = "AFS OR (AFS[UNAVAIL] AND compat[SUCCESS])"
-</programlisting>
-
- <para>If the machine is both an AFS and a DCE client, set the following value (it must appear on a single line in
- the file):</para>
-
- <programlisting>
- SYSTEM = "DCE OR DCE[UNAVAIL] OR AFS OR (AFS[UNAVAIL] \
- AND compat[SUCCESS])"
-</programlisting>
- </listitem>
-
- <listitem>
- <para>In the <computeroutput>root</computeroutput> stanza, set the <computeroutput>registry</computeroutput>
- attribute as follows. It enables the local superuser <emphasis role="bold">root</emphasis> to log into the local
- file system only, based on the password listed in the local password file. <programlisting>
- root:
- registry = files
-</programlisting></para>
- </listitem>
- </itemizedlist></para>
- </listitem>
-
- <listitem>
- <para>Edit the local <emphasis role="bold">/etc/security/login.cfg</emphasis> file, creating or editing the indicated
- stanzas: <itemizedlist>
- <listitem>
- <para>In the <computeroutput>DCE</computeroutput> stanza, set the <computeroutput>program</computeroutput>
- attribute as follows.</para>
-
- <para>If you use the AFS Authentication Server (<emphasis role="bold">kaserver</emphasis> process):</para>
-
- <programlisting>
- DCE:
- program = /usr/vice/etc/afs_dynamic_auth
-</programlisting>
-
- <para>If you use a Kerberos implementation of AFS authentication:</para>
+ <sect2 id="HDRWQ44">
+ <title>Enabling AFS Login on Linux Systems</title>
- <programlisting>
- DCE:
- program = /usr/vice/etc/afs_dynamic_kerbauth
-</programlisting>
- </listitem>
-
- <listitem>
- <para>In the <computeroutput>AFS</computeroutput> stanza, set the <computeroutput>program</computeroutput>
- attribute as follows.</para>
-
- <para>If you use the AFS Authentication Server (<emphasis role="bold">kaserver</emphasis> process):</para>
-
- <programlisting>
- AFS:
- program = /usr/vice/etc/afs_dynamic_auth
-</programlisting>
-
- <para>If you use a Kerberos implementation of AFS authentication:</para>
-
- <programlisting>
- AFS:
- program = /usr/vice/etc/afs_dynamic_kerbauth
-</programlisting>
- </listitem>
- </itemizedlist></para>
- </listitem>
-
- <listitem>
- <para>Proceed to <link linkend="HDRWQ50">Starting the BOS Server</link> (or if referring to these instructions while
- installing an additional file server machine, return to <link linkend="HDRWQ108">Starting Server
- Programs</link>).</para>
- </listitem>
- </orderedlist></para>
- </sect2>
- </sect1>
-
- <sect1 id="HDRWQ26">
- <title>Getting Started on Digital UNIX Systems</title>
-
- <para>Begin by either building AFS modifications into a new static kernel or by setting up to dynamically load the AFS kernel
- module. Then create partitions for storing AFS volumes, and replace the Digital UNIX <emphasis role="bold">fsck</emphasis>
- program with a version that correctly handles AFS volumes. If the machine is to remain an AFS client machine, incorporate AFS
- into the machine's Security Integration Architecture (SIA) matrix. <indexterm>
- <primary>incorporating AFS kernel extensions</primary>
-
- <secondary>first AFS machine</secondary>
-
- <tertiary>Digital UNIX</tertiary>
- </indexterm> <indexterm>
- <primary>AFS kernel extensions</primary>
-
- <secondary>on first AFS machine</secondary>
-
- <tertiary>Digital UNIX</tertiary>
- </indexterm> <indexterm>
- <primary>first AFS machine</primary>
-
- <secondary>AFS kernel extensions</secondary>
-
- <tertiary>on Digital UNIX</tertiary>
- </indexterm> <indexterm>
- <primary>Digital UNIX</primary>
-
- <secondary>AFS-modified kernel</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm></para>
-
- <sect2 id="HDRWQ27a">
- <title>Loading AFS into the Digital UNIX Kernel</title>
-
- <para>The <emphasis role="bold">sysconfig</emphasis> program is the dynamic kernel loader provided for Digital UNIX
- systems.</para>
-
- <para>For AFS to function correctly, the <emphasis role="bold">sysconfig</emphasis> program must run each time the machine
- reboots, so the AFS initialization script (included on the AFS CD-ROM) invokes it automatically. In this section you copy the
- appropriate AFS library file to the location where the <emphasis role="bold">sysconfig</emphasis> program accesses it and then
- run the script.</para>
-
- <para>Mount the AFS CD-ROM for Digital UNIX on the local <emphasis role="bold">/cdrom</emphasis> directory. For instructions
- on mounting CD-ROMs (either locally or remotely via NFS), see your Digital UNIX documentation. Then change directory as
- indicated.</para>
-
- <programlisting>
- # <emphasis role="bold">cd /cdrom/alpha_dux40/root.client</emphasis>
-</programlisting>
-
- <para>Copy the AFS initialization script to the local directory for initialization files (by convention, <emphasis
- role="bold">/sbin/init.d</emphasis> on Digital UNIX machines). Note the removal of the <emphasis role="bold">.rc</emphasis>
- extension as you copy the script.</para>
-
- <programlisting>
- # <emphasis role="bold">cp usr/vice/etc/afs.rc /sbin/init.d/afs</emphasis>
-</programlisting>
-
- <para>Copy the AFS kernel module to the local <emphasis role="bold">/subsys</emphasis> directory.</para>
-
- <programlisting>
- # <emphasis role="bold">cp bin/afs.mod /subsys/afs.mod</emphasis>
-</programlisting>
-
- <para>Set up the system to load the module at startup.</para>
-
- <programlisting>
- # <emphasis role="bold">/sbin/init.d/autosysconfig add afs</emphasis>
-</programlisting>
-
- <para>Reboot the machine to start using the new kernel, and login again as the superuser <emphasis
- role="bold">root</emphasis>.</para>
-
- <programlisting>
- # <emphasis role="bold">cd /</emphasis>
- # <emphasis role="bold">shutdown -r now</emphasis>
- login: <emphasis role="bold">root</emphasis>
- Password: <replaceable>root_password</replaceable>
-</programlisting>
- </sect2>
-
- <sect2 id="HDRWQ27">
- <title>Building AFS into the Digital UNIX Kernel</title>
-
- <para>Use the following instructions to build AFS modifications into the kernel on a Digital UNIX system. <orderedlist>
- <listitem>
- <para>Create a copy called <emphasis role="bold">AFS</emphasis> of the basic kernel configuration file included in the
- Digital UNIX distribution as <emphasis role="bold">/usr/sys/conf/</emphasis><replaceable>machine_name</replaceable>,
- where <replaceable>machine_name</replaceable> is the machine's hostname in all uppercase letters. <programlisting>
- # <emphasis role="bold">cd /usr/sys/conf</emphasis>
- # <emphasis role="bold">cp</emphasis> <replaceable>machine_name</replaceable> <emphasis role="bold">AFS</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Add AFS to the list of options in the configuration file you created in the previous step, so that the result
- looks like the following: <programlisting>
- . .
- . .
- options UFS
- options NFS
- options AFS
- . .
- . .
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Add an entry for AFS to two places in the file <emphasis role="bold">/usr/sys/conf/files</emphasis>. <itemizedlist>
- <listitem>
- <para>Add a line for AFS to the list of <computeroutput>OPTIONS</computeroutput>, so that the result looks like
- the following: <programlisting>
- . . .
- . . .
- OPTIONS/nfs optional nfs
- OPTIONS/afs optional afs
- OPTIONS/nfs_server optional nfs_server
- . . .
- . . .
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Add an entry for AFS to the list of <computeroutput>MODULES</computeroutput>, so that the result looks like
- the following: <programlisting>
- . . . .
- . . . .
- #
- MODULE/nfs_server optional nfs_server Binary
- nfs/nfs_server.c module nfs_server optimize -g3
- nfs/nfs3_server.c module nfs_server optimize -g3
- #
- MODULE/afs optional afs Binary
- afs/libafs.c module afs
- #
-</programlisting></para>
- </listitem>
- </itemizedlist></para>
- </listitem>
-
- <listitem>
- <para>Add an entry for AFS to two places in the file <emphasis role="bold">/usr/sys/vfs/vfs_conf.c</emphasis>.
- <itemizedlist>
- <listitem>
- <para>Add AFS to the list of defined file systems, so that the result looks like the following: <programlisting>
- . .
- . .
- #include <afs.h>
- #if defined(AFS) && AFS
- extern struct vfsops afs_vfsops;
- #endif
- . .
- . .
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Put a declaration for AFS in the <emphasis role="bold">vfssw[]</emphasis> table's MOUNT_ADDON slot, so that
- the result looks like the following: <programlisting>
- . . .
- . . .
- &fdfs_vfsops, "fdfs", /* 12 = MOUNT_FDFS */
- #if defined(AFS)
- &afs_vfsops, "afs",
- #else
- (struct vfsops *)0, "", /* 13 = MOUNT_ADDON */
- #endif
- #if NFS && INFS_DYNAMIC
- &nfs3_vfsops, "nfsv3", /* 14 = MOUNT_NFS3 */
-</programlisting></para>
- </listitem>
- </itemizedlist></para>
- </listitem>
-
- <listitem>
- <para>Mount the AFS CD-ROM for Digital UNIX on the local <emphasis role="bold">/cdrom</emphasis> directory. For
- instructions on mounting CD-ROMs (either locally or remotely via NFS), see your Digital UNIX documentation. Then change
- directory as indicated. <programlisting>
- # <emphasis role="bold">cd /cdrom/alpha_dux40/root.client</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Copy the AFS initialization script to the local directory for initialization files (by convention, <emphasis
- role="bold">/sbin/init.d</emphasis> on Digital UNIX machines). Note the removal of the <emphasis
- role="bold">.rc</emphasis> extension as you copy the script. <programlisting>
- # <emphasis role="bold">cp usr/vice/etc/afs.rc /sbin/init.d/afs</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Copy the AFS kernel module to the local <emphasis role="bold">/usr/sys/BINARY</emphasis> directory.</para>
-
- <para>If the machine's kernel supports NFS server functionality:</para>
-
- <programlisting>
- # <emphasis role="bold">cp bin/libafs.o /usr/sys/BINARY/afs.mod</emphasis>
-</programlisting>
-
- <para>If the machine's kernel does not support NFS server functionality:</para>
-
- <programlisting>
- # <emphasis role="bold">cp bin/libafs.nonfs.o /usr/sys/BINARY/afs.mod</emphasis>
-</programlisting>
- </listitem>
-
- <listitem>
- <para>Configure and build the kernel. Respond to any prompts by pressing <<emphasis
- role="bold">Return</emphasis>>. The resulting kernel resides in the file <emphasis
- role="bold">/sys/AFS/vmunix</emphasis>. <programlisting>
- # <emphasis role="bold">doconfig -c AFS</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Rename the existing kernel file and copy the new, AFS-modified file to the standard location. <programlisting>
- # <emphasis role="bold">mv /vmunix /vmunix_noafs</emphasis>
- # <emphasis role="bold">cp /sys/AFS/vmunix /vmunix</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Reboot the machine to start using the new kernel, and login again as the superuser <emphasis
- role="bold">root</emphasis>. <programlisting>
- # <emphasis role="bold">cd /</emphasis>
- # <emphasis role="bold">shutdown -r now</emphasis>
- login: <emphasis role="bold">root</emphasis>
- Password: <replaceable>root_password</replaceable>
-</programlisting></para>
- </listitem>
- </orderedlist></para>
-
- <indexterm>
- <primary>configuring</primary>
-
- <secondary>AFS server partition on first AFS machine</secondary>
-
- <tertiary>Digital UNIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>AFS server partition</primary>
-
- <secondary>configuring on first AFS machine</secondary>
-
- <tertiary>Digital UNIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>first AFS machine</primary>
-
- <secondary>AFS server partition</secondary>
-
- <tertiary>on Digital UNIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>Digital UNIX</primary>
-
- <secondary>AFS server partition</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm>
- </sect2>
-
- <sect2 id="HDRWQ28">
- <title>Configuring Server Partitions on Digital UNIX Systems</title>
-
- <para>Every AFS file server machine must have at least one partition or logical volume dedicated to storing AFS volumes. Each
- server partition is mounted at a directory named <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>, where
- <replaceable>xx</replaceable> is one or two lowercase letters. The <emphasis
- role="bold">/vicep</emphasis><replaceable>xx</replaceable> directories must reside in the file server machine's root
- directory, not in one of its subdirectories (for example, <emphasis role="bold">/usr/vicepa</emphasis> is not an acceptable
- directory location). For additional information, see <link linkend="HDRWQ20">Performing Platform-Specific Procedures</link>.
- <orderedlist>
- <listitem>
- <para>Create a directory called <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable> for each AFS server
- partition you are configuring (there must be at least one). Repeat the command for each partition. <programlisting>
- # <emphasis role="bold">mkdir /vicep</emphasis><replaceable>xx</replaceable>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Add a line with the following format to the file systems registry file, <emphasis
- role="bold">/etc/fstab</emphasis>, for each directory just created. The entry maps the directory name to the disk
- partition to be mounted on it. <programlisting>
- /dev/<replaceable>disk</replaceable> /vicep<replaceable>xx</replaceable> ufs rw 0 2
-</programlisting></para>
-
- <para>The following is an example for the first partition being configured.</para>
-
- <programlisting>
- /dev/rz3a /vicepa ufs rw 0 2
-</programlisting>
- </listitem>
-
- <listitem>
- <para>Create a file system on each partition that is to be mounted at a <emphasis
- role="bold">/vicep</emphasis><replaceable>xx</replaceable> directory. The following command is probably appropriate, but
- consult the Digital UNIX documentation for more information. <programlisting>
- # <emphasis role="bold">newfs -v /dev/</emphasis><replaceable>disk</replaceable>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Mount each partition by issuing either the <emphasis role="bold">mount -a</emphasis> command to mount all
- partitions at once or the <emphasis role="bold">mount</emphasis> command to mount each partition in turn.</para>
- </listitem>
- </orderedlist></para>
-
- <indexterm>
- <primary>replacing fsck program</primary>
-
- <secondary>first AFS machine</secondary>
-
- <tertiary>Digital UNIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>fsck program</primary>
-
- <secondary>on first AFS machine</secondary>
-
- <tertiary>Digital UNIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>first AFS machine</primary>
-
- <secondary>fsck program</secondary>
-
- <tertiary>on Digital UNIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>Digital UNIX</primary>
-
- <secondary>fsck program</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm>
- </sect2>
-
- <sect2 id="HDRWQ29">
- <title>Replacing the fsck Program on Digital UNIX Systems</title>
-
- <para>In this section, you make modifications to guarantee that the appropriate <emphasis role="bold">fsck</emphasis> program
- runs on AFS server partitions. The <emphasis role="bold">fsck</emphasis> program provided with the operating system must never
- run on AFS server partitions. Because it does not recognize the structures that the File Server uses to organize volume data,
- it removes all of the data. To repeat:</para>
-
- <para><emphasis role="bold">Never run the standard fsck program on AFS server partitions. It discards AFS
- volumes.</emphasis></para>
-
- <para>On Digital UNIX systems, the files <emphasis role="bold">/sbin/fsck</emphasis> and <emphasis
- role="bold">/usr/sbin/fsck</emphasis> are driver programs. Rather than replacing either of them, you replace the actual binary
- included in the Digital UNIX distribution as <emphasis role="bold">/sbin/ufs_fsck</emphasis> and <emphasis
- role="bold">/usr/sbin/ufs_fsck</emphasis>. <orderedlist>
- <listitem>
- <para>Install the <emphasis role="bold">vfsck</emphasis> binary to the <emphasis role="bold">/sbin</emphasis> and
- <emphasis role="bold">/usr/sbin</emphasis> directories. The AFS CD-ROM must still be mounted at the <emphasis
- role="bold">/cdrom</emphasis> directory. <programlisting>
- # <emphasis role="bold">cd /cdrom/alpha_dux40/root.server/etc</emphasis>
- # <emphasis role="bold">cp vfsck /sbin/vfsck</emphasis>
- # <emphasis role="bold">cp vfsck /usr/sbin/vfsck</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Rename the Digital UNIX <emphasis role="bold">fsck</emphasis> binaries and create symbolic links to the <emphasis
- role="bold">vfsck</emphasis> program. <programlisting>
- # <emphasis role="bold">cd /sbin</emphasis>
- # <emphasis role="bold">mv ufs_fsck ufs_fsck.noafs</emphasis>
- # <emphasis role="bold">ln -s vfsck ufs_fsck</emphasis>
- # <emphasis role="bold">cd /usr/sbin</emphasis>
- # <emphasis role="bold">mv ufs_fsck ufs_fsck.noafs</emphasis>
- # <emphasis role="bold">ln -s vfsck ufs_fsck</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>If you plan to retain client functionality on this machine after completing the installation, proceed to <link
- linkend="HDRWQ30">Enabling AFS Login on Digital UNIX Systems</link>. Otherwise, proceed to <link
- linkend="HDRWQ50">Starting the BOS Server</link>.</para>
- </listitem>
- </orderedlist></para>
-
- <indexterm>
- <primary>enabling AFS login</primary>
-
- <secondary>file server machine</secondary>
-
- <tertiary>Digital UNIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>AFS login</primary>
-
- <secondary>on file server machine</secondary>
-
- <tertiary>Digital UNIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>first AFS machine</primary>
-
- <secondary>AFS login</secondary>
-
- <tertiary>on Digital UNIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>Digital UNIX</primary>
-
- <secondary>AFS login</secondary>
-
- <tertiary>on file server machine</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>SIA (Digital UNIX)</primary>
-
- <secondary>file server machine</secondary>
- </indexterm>
-
- <indexterm>
- <primary>Security Integration Architecture</primary>
-
- <see>SIA</see>
- </indexterm>
- </sect2>
-
- <sect2 id="HDRWQ30">
- <title>Enabling AFS Login on Digital UNIX Systems</title>
-
- <note>
- <para>If you plan to remove client functionality from this machine after completing the installation, skip this section and
- proceed to <link linkend="HDRWQ50">Starting the BOS Server</link>.</para>
- </note>
-
- <para>On Digital UNIX systems, the AFS initialization script automatically incorporates the AFS authentication library file
- into the Security Integration Architecture (SIA) matrix on the machine, so that users with AFS accounts obtain a token at
- login. In this section you copy the library file to the appropriate location.</para>
-
- <para>For more information on SIA, see the Digital UNIX reference page for <emphasis role="bold">matrix.conf</emphasis>, or
- consult the section on security in your Digital UNIX documentation.</para>
-
- <note>
- <para>If the machine runs both the DCE and AFS client software, AFS must start after DCE. Consult the AFS initialization
- script for suggested symbolic links to create for correct ordering. Also, the system startup script order must initialize
- SIA before any long-running process that uses authentication.</para>
- </note>
-
- <para>Perform the following steps to enable AFS login. <orderedlist>
- <listitem>
- <para>Mount the AFS CD-ROM for Digital UNIX on the local <emphasis role="bold">/cdrom</emphasis> directory, if it is not
- already. Change directory as indicated. <programlisting>
- # <emphasis role="bold">cd /cdrom/alpha_dux40/lib/afs</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Copy the appropriate AFS authentication library file to the local <emphasis role="bold">/usr/shlib</emphasis>
- directory.</para>
-
- <para>If you use the AFS Authentication Server (<emphasis role="bold">kaserver</emphasis> process) in the cell:</para>
-
- <programlisting>
- # <emphasis role="bold">cp libafssiad.so /usr/shlib</emphasis>
-</programlisting>
-
- <para>If you use a Kerberos implementation of AFS authentication, rename the library file as you copy it:</para>
-
- <programlisting>
- # <emphasis role="bold">cp libafssiad.krb.so /usr/shlib/libafssiad.so</emphasis>
-</programlisting>
- </listitem>
-
- <listitem>
- <para>Proceed to <link linkend="HDRWQ50">Starting the BOS Server</link> (or if referring to these instructions while
- installing an additional file server machine, return to <link linkend="HDRWQ108">Starting Server
- Programs</link>).</para>
- </listitem>
- </orderedlist></para>
- </sect2>
- </sect1>
-
- <sect1 id="HDRWQ31">
- <title>Getting Started on HP-UX Systems</title>
-
- <para>Begin by building AFS modifications into a new kernel; HP-UX does not support dynamic loading. Then create partitions for
- storing AFS volumes, and install and configure the AFS-modified <emphasis role="bold">fsck</emphasis> program to run on AFS
- server partitions. If the machine is to remain an AFS client machine, incorporate AFS into the machine's Pluggable
- Authentication Module (PAM) scheme. <indexterm>
- <primary>incorporating AFS kernel extensions</primary>
-
- <secondary>first AFS machine</secondary>
-
- <tertiary>HP-UX</tertiary>
- </indexterm> <indexterm>
- <primary>AFS kernel extensions</primary>
-
- <secondary>on first AFS machine</secondary>
-
- <tertiary>HP-UX</tertiary>
- </indexterm> <indexterm>
- <primary>first AFS machine</primary>
-
- <secondary>AFS kernel extensions</secondary>
-
- <tertiary>on HP-UX</tertiary>
- </indexterm> <indexterm>
- <primary>HP-UX</primary>
-
- <secondary>AFS-modified kernel</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm></para>
-
- <sect2 id="HDRWQ32">
- <title>Building AFS into the HP-UX Kernel</title>
-
- <para>Use the following instructions to build AFS modifications into the kernel on an HP-UX system. <orderedlist>
- <listitem>
- <para>Move the existing kernel-related files to a safe location. <programlisting>
- # <emphasis role="bold">cp /stand/vmunix /stand/vmunix.noafs</emphasis>
- # <emphasis role="bold">cp /stand/system /stand/system.noafs</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Mount the AFS CD-ROM for HP-UX on the local <emphasis role="bold">/cdrom</emphasis> directory. For instructions on
- mounting CD-ROMs (either locally or remotely via NFS), see your HP-UX documentation. Then change directory as indicated.
- <programlisting>
- # <emphasis role="bold">cd /cdrom/hp_ux110/root.client</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Copy the AFS initialization file to the local directory for initialization files (by convention, <emphasis
- role="bold">/sbin/init.d</emphasis> on HP-UX machines). Note the removal of the <emphasis role="bold">.rc</emphasis>
- extension as you copy the file. <programlisting>
- # <emphasis role="bold">cp usr/vice/etc/afs.rc /sbin/init.d/afs</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Copy the file <emphasis role="bold">afs.driver</emphasis> to the local <emphasis
- role="bold">/usr/conf/master.d</emphasis> directory, changing its name to <emphasis role="bold">afs</emphasis> as you
- do. <programlisting>
- # <emphasis role="bold">cp usr/vice/etc/afs.driver /usr/conf/master.d/afs</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Copy the AFS kernel module to the local <emphasis role="bold">/usr/conf/lib</emphasis> directory.</para>
-
- <para>If the machine's kernel supports NFS server functionality:</para>
-
- <programlisting>
- # <emphasis role="bold">cp bin/libafs.a /usr/conf/lib</emphasis>
-</programlisting>
-
- <para>If the machine's kernel does not support NFS server functionality, change the file's name as you copy it:</para>
-
- <programlisting>
- # <emphasis role="bold">cp bin/libafs.nonfs.a /usr/conf/lib/libafs.a</emphasis>
-</programlisting>
- </listitem>
-
- <listitem>
- <para>Incorporate the AFS driver into the kernel, either using the <emphasis role="bold">SAM</emphasis> program or a
- series of individual commands. <itemizedlist>
- <listitem>
- <para>To use the <emphasis role="bold">SAM</emphasis> program: <orderedlist>
- <listitem>
- <para>Invoke the <emphasis role="bold">SAM</emphasis> program, specifying the hostname of the local machine
- as <replaceable>local_hostname</replaceable>. The <emphasis role="bold">SAM</emphasis> graphical user
- interface pops up. <programlisting>
- # <emphasis role="bold">sam -display</emphasis> <replaceable>local_hostname</replaceable><emphasis role="bold">:0</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Choose the <emphasis role="bold">Kernel Configuration</emphasis> icon, then the <emphasis
- role="bold">Drivers</emphasis> icon. From the list of drivers, select <emphasis
- role="bold">afs</emphasis>.</para>
- </listitem>
-
- <listitem>
- <para>Open the pull-down <emphasis role="bold">Actions</emphasis> menu and choose the <emphasis
- role="bold">Add Driver to Kernel</emphasis> option.</para>
- </listitem>
-
- <listitem>
- <para>Open the <emphasis role="bold">Actions</emphasis> menu again and choose the <emphasis
- role="bold">Create a New Kernel</emphasis> option.</para>
- </listitem>
-
- <listitem>
- <para>Confirm your choices by choosing <emphasis role="bold">Yes</emphasis> and <emphasis
- role="bold">OK</emphasis> when prompted by subsequent pop-up windows. The <emphasis
- role="bold">SAM</emphasis> program builds the kernel and reboots the system.</para>
- </listitem>
-
- <listitem>
- <para>Login again as the superuser <emphasis role="bold">root</emphasis>. <programlisting>
- login: <emphasis role="bold">root</emphasis>
- Password: <replaceable>root_password</replaceable>
-</programlisting></para>
- </listitem>
- </orderedlist></para>
- </listitem>
-
- <listitem>
- <para>To use individual commands: <orderedlist>
- <listitem>
- <para>Edit the file <emphasis role="bold">/stand/system</emphasis>, adding an entry for <emphasis
- role="bold">afs</emphasis> to the <computeroutput>Subsystems</computeroutput> section.</para>
- </listitem>
-
- <listitem>
- <para>Change to the <emphasis role="bold">/stand/build</emphasis> directory and issue the <emphasis
- role="bold">mk_kernel</emphasis> command to build the kernel. <programlisting>
- # <emphasis role="bold">cd /stand/build</emphasis>
- # <emphasis role="bold">mk_kernel</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Move the new kernel to the standard location (<emphasis role="bold">/stand/vmunix</emphasis>), reboot
- the machine to start using it, and login again as the superuser <emphasis role="bold">root</emphasis>.
- <programlisting>
- # <emphasis role="bold">mv /stand/build/vmunix_test /stand/vmunix</emphasis>
- # <emphasis role="bold">cd /</emphasis>
- # <emphasis role="bold">shutdown -r now</emphasis>
- login: <emphasis role="bold">root</emphasis>
- Password: <replaceable>root_password</replaceable>
-</programlisting></para>
- </listitem>
- </orderedlist></para>
- </listitem>
- </itemizedlist></para>
- </listitem>
- </orderedlist></para>
-
- <indexterm>
- <primary>configuring</primary>
-
- <secondary>AFS server partition on first AFS machine</secondary>
-
- <tertiary>HP-UX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>AFS server partition</primary>
-
- <secondary>configuring on first AFS machine</secondary>
-
- <tertiary>HP-UX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>first AFS machine</primary>
-
- <secondary>AFS server partition</secondary>
-
- <tertiary>on HP-UX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>HP-UX</primary>
-
- <secondary>AFS server partition</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm>
- </sect2>
-
- <sect2 id="HDRWQ33">
- <title>Configuring Server Partitions on HP-UX Systems</title>
-
- <para>Every AFS file server machine must have at least one partition or logical volume dedicated to storing AFS volumes. Each
- server partition is mounted at a directory named <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>, where
- <replaceable>xx</replaceable> is one or two lowercase letters. The <emphasis
- role="bold">/vicep</emphasis><replaceable>xx</replaceable> directories must reside in the file server machine's root
- directory, not in one of its subdirectories (for example, <emphasis role="bold">/usr/vicepa</emphasis> is not an acceptable
- directory location). For additional information, see <link linkend="HDRWQ20">Performing Platform-Specific Procedures</link>.
- <orderedlist>
- <listitem>
- <para>Create a directory called <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable> for each AFS server
- partition you are configuring (there must be at least one). Repeat the command for each partition. <programlisting>
- # <emphasis role="bold">mkdir /vicep</emphasis><replaceable>xx</replaceable>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Use the <emphasis role="bold">SAM</emphasis> program to create a file system on each partition. For instructions,
- consult the HP-UX documentation.</para>
- </listitem>
-
- <listitem>
- <para>On some HP-UX systems that use logical volumes, the <emphasis role="bold">SAM</emphasis> program automatically
- mounts the partitions. If it has not, mount each partition by issuing either the <emphasis role="bold">mount
- -a</emphasis> command to mount all partitions at once or the <emphasis role="bold">mount</emphasis> command to mount
- each partition in turn.</para>
- </listitem>
- </orderedlist></para>
-
- <indexterm>
- <primary>replacing fsck program</primary>
-
- <secondary>first AFS machine</secondary>
-
- <tertiary>HP-UX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>fsck program</primary>
-
- <secondary>on first AFS machine</secondary>
-
- <tertiary>HP-UX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>first AFS machine</primary>
-
- <secondary>fsck program</secondary>
-
- <tertiary>on HP-UX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>HP-UX</primary>
-
- <secondary>fsck program</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm>
- </sect2>
-
- <sect2 id="HDRWQ34">
- <title>Configuring the AFS-modified fsck Program on HP-UX Systems</title>
-
- <para>In this section, you make modifications to guarantee that the appropriate <emphasis role="bold">fsck</emphasis> program
- runs on AFS server partitions. The <emphasis role="bold">fsck</emphasis> program provided with the operating system must never
- run on AFS server partitions. Because it does not recognize the structures that the File Server uses to organize volume data,
- it removes all of the data. To repeat:</para>
-
- <para><emphasis role="bold">Never run the standard fsck program on AFS server partitions. It discards AFS
- volumes.</emphasis></para>
-
- <para>On HP-UX systems, there are several configuration files to install in addition to the AFS-modified <emphasis
- role="bold">fsck</emphasis> program (the <emphasis role="bold">vfsck</emphasis> binary). <orderedlist>
- <listitem>
- <para>Create the command configuration file <emphasis role="bold">/sbin/lib/mfsconfig.d/afs</emphasis>. Use a text
- editor to place the indicated two lines in it: <programlisting>
- format_revision 1
- fsck 0 m,P,p,d,f,b:c:y,n,Y,N,q,
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Create and change directory to an AFS-specific command directory called <emphasis
- role="bold">/sbin/fs/afs</emphasis>. <programlisting>
- # <emphasis role="bold">mkdir /sbin/fs/afs</emphasis>
- # <emphasis role="bold">cd /sbin/fs/afs</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Copy the AFS-modified version of the <emphasis role="bold">fsck</emphasis> program (the <emphasis
- role="bold">vfsck</emphasis> binary) and related files from the distribution directory to the new AFS-specific command
- directory. <programlisting>
- # <emphasis role="bold">cp -p /cdrom/hp_ux110/root.server/etc/* .</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Change the <emphasis role="bold">vfsck</emphasis> binary's name to <emphasis role="bold">fsck</emphasis> and set
- the mode bits appropriately on all of the files in the <emphasis role="bold">/sbin/fs/afs</emphasis> directory.
- <programlisting>
- # <emphasis role="bold">mv vfsck fsck</emphasis>
- # <emphasis role="bold">chmod 755 *</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Edit the <emphasis role="bold">/etc/fstab</emphasis> file, changing the file system type for each AFS server
- partition from <computeroutput>hfs</computeroutput> to <computeroutput>afs</computeroutput>. This ensures that the
- AFS-modified <emphasis role="bold">fsck</emphasis> program runs on the appropriate partitions.</para>
-
- <para>The sixth line in the following example of an edited file shows an AFS server partition, <emphasis
- role="bold">/vicepa</emphasis>.</para>
-
- <programlisting>
- /dev/vg00/lvol1 / hfs defaults 0 1
- /dev/vg00/lvol4 /opt hfs defaults 0 2
- /dev/vg00/lvol5 /tmp hfs defaults 0 2
- /dev/vg00/lvol6 /usr hfs defaults 0 2
- /dev/vg00/lvol8 /var hfs defaults 0 2
- /dev/vg00/lvol9 /vicepa afs defaults 0 2
- /dev/vg00/lvol7 /usr/vice/cache hfs defaults 0 2
-</programlisting>
- </listitem>
-
- <listitem>
- <para>If you plan to retain client functionality on this machine after completing the installation, proceed to <link
- linkend="HDRWQ35">Enabling AFS Login on HP-UX Systems</link>. Otherwise, proceed to <link linkend="HDRWQ50">Starting the
- BOS Server</link>.</para>
- </listitem>
- </orderedlist></para>
-
- <indexterm>
- <primary>enabling AFS login</primary>
-
- <secondary>file server machine</secondary>
-
- <tertiary>HP-UX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>AFS login</primary>
-
- <secondary>on file server machine</secondary>
-
- <tertiary>HP-UX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>first AFS machine</primary>
-
- <secondary>AFS login</secondary>
-
- <tertiary>on HP-UX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>HP-UX</primary>
-
- <secondary>AFS login</secondary>
-
- <tertiary>on file server machine</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>PAM</primary>
-
- <secondary>on HP-UX</secondary>
-
- <tertiary>file server machine</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>Pluggable Authentication Module</primary>
-
- <see>PAM</see>
- </indexterm>
- </sect2>
-
- <sect2 id="HDRWQ35">
- <title>Enabling AFS Login on HP-UX Systems</title>
-
- <note>
- <para>If you plan to remove client functionality from this machine after completing the installation, skip this section and
- proceed to <link linkend="HDRWQ50">Starting the BOS Server</link>.</para>
- </note>
-
- <para>At this point you incorporate AFS into the operating system's Pluggable Authentication Module (PAM) scheme. PAM
- integrates all authentication mechanisms on the machine, including login, to provide the security infrastructure for
- authenticated access to and from the machine.</para>
-
- <para>Explaining PAM is beyond the scope of this document. It is assumed that you understand the syntax and meanings of
- settings in the PAM configuration file (for example, how the <computeroutput>other</computeroutput> entry works, the effect of
- marking an entry as <computeroutput>required</computeroutput>, <computeroutput>optional</computeroutput>, or
- <computeroutput>sufficient</computeroutput>, and so on).</para>
-
- <para>The following instructions explain how to alter the entries in the PAM configuration file for each service for which you
- wish to use AFS authentication. Other configurations possibly also work, but the instructions specify the recommended and
- tested configuration.</para>
-
- <note>
- <para>The instructions specify that you mark each entry as <computeroutput>optional</computeroutput>. However, marking some
- modules as optional can mean that they grant access to the corresponding service even when the user does not meet all of the
- module's requirements. In some operating system revisions, for example, if you mark as optional the module that controls
- login via a dial-up connection, it allows users to login without providing a password. See the <emphasis>IBM AFS Release
- Notes</emphasis> for a discussion of any limitations that apply to this operating system.</para>
-
- <para>Also, with some operating system versions you must install patches for PAM to interact correctly with certain
- authentication programs. For details, see the <emphasis>IBM AFS Release Notes</emphasis>.</para>
- </note>
-
- <para>The recommended AFS-related entries in the PAM configuration file make use of one or more of the following three
- attributes. <variablelist>
- <varlistentry>
- <term><emphasis role="bold"><computeroutput>try_first_pass</computeroutput></emphasis></term>
-
- <listitem>
- <para>This is a standard PAM attribute that can be included on entries after the first one for a service; it directs
- the module to use the password that was provided to the first module. For the AFS module, it means that AFS
- authentication succeeds if the password provided to the module listed first is the user's correct AFS password. For
- further discussion of this attribute and its alternatives, see the operating system's PAM documentation.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><emphasis role="bold"><computeroutput>ignore_root</computeroutput></emphasis></term>
-
- <listitem>
- <para>This attribute, specific to the AFS PAM module, directs it to ignore not only the local superuser <emphasis
- role="bold">root</emphasis>, but also any user with UID 0 (zero).</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><emphasis role="bold"><computeroutput>setenv_password_expires</computeroutput></emphasis></term>
-
- <listitem>
- <para>This attribute, specific to the AFS PAM module, sets the environment variable PASSWORD_EXPIRES to the expiration
- date of the user's AFS password, which is recorded in the Authentication Database.</para>
- </listitem>
- </varlistentry>
- </variablelist></para>
-
- <para>Perform the following steps to enable AFS login. <orderedlist>
- <listitem>
- <para>Mount the AFS CD-ROM for HP-UX on the <emphasis role="bold">/cdrom</emphasis> directory, if it is not already.
- Then change directory as indicated. <programlisting>
- # <emphasis role="bold">cd /usr/lib/security</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Copy the AFS authentication library file to the <emphasis role="bold">/usr/lib/security</emphasis> directory. Then
- create a symbolic link to it whose name does not mention the version. Omitting the version eliminates the need to edit
- the PAM configuration file if you later update the library file.</para>
-
- <para>If you use the AFS Authentication Server (<emphasis role="bold">kaserver</emphasis> process) in the cell:</para>
-
- <programlisting>
- # <emphasis role="bold">cp /cdrom/hp_ux110/lib/pam_afs.so.1 .</emphasis>
- # <emphasis role="bold">ln -s pam_afs.so.1 pam_afs.so</emphasis>
-</programlisting>
-
- <para>If you use a Kerberos implementation of AFS authentication:</para>
-
- <programlisting>
- # <emphasis role="bold">cp /cdrom/hp_ux110/lib/pam_afs.krb.so.1 .</emphasis>
- # <emphasis role="bold">ln -s pam_afs.krb.so.1 pam_afs.so</emphasis>
-</programlisting>
- </listitem>
-
- <listitem>
- <para>Edit the <computeroutput>Authentication management</computeroutput> section of the HP-UX PAM configuration file,
- <emphasis role="bold">/etc/pam.conf</emphasis> by convention. The entries in this section have the value
- <computeroutput>auth</computeroutput> in their second field.</para>
-
- <para>First edit the standard entries, which refer to the HP-UX PAM module (usually, the file <emphasis
- role="bold">/usr/lib/security/libpam_unix.1</emphasis>) in their fourth field. For each service for which you want to
- use AFS authentication, edit the third field of its entry to read <computeroutput>optional</computeroutput>. The
- <emphasis role="bold">pam.conf</emphasis> file in the HP-UX distribution usually includes standard entries for the
- <emphasis role="bold">login</emphasis> and <emphasis role="bold">ftp</emphasis> services, for instance.</para>
-
- <para>If there are services for which you want to use AFS authentication, but for which the <emphasis
- role="bold">pam.conf</emphasis> file does not already include a standard entry, you must create that entry and place the
- value <computeroutput>optional</computeroutput> in its third field. For instance, the HP-UX <emphasis
- role="bold">pam.conf</emphasis> file does not usually include standard entries for the <emphasis
- role="bold">remsh</emphasis> or <emphasis role="bold">telnet</emphasis> services.</para>
-
- <para>Then create an AFS-related entry for each service, placing it immediately below the standard entry. The following
- example shows what the <computeroutput>Authentication Management</computeroutput> section looks like after you have you
- edited or created entries for the services mentioned previously. Note that the example AFS entries appear on two lines
- only for legibility.</para>
-
- <programlisting>
- login auth optional /usr/lib/security/libpam_unix.1
- login auth optional /usr/lib/security/pam_afs.so \
- try_first_pass ignore_root setenv_password_expires
- ftp auth optional /usr/lib/security/libpam_unix.1
- ftp auth optional /usr/lib/security/pam_afs.so \
- try_first_pass ignore_root
- remsh auth optional /usr/lib/security/libpam_unix.1
- remsh auth optional /usr/lib/security/pam_afs.so \
- try_first_pass ignore_root
- telnet auth optional /usr/lib/security/libpam_unix.1
- telnet auth optional /usr/lib/security/pam_afs.so \
- try_first_pass ignore_root setenv_password_expires
-</programlisting>
- </listitem>
-
- <listitem>
- <para>If you use the Common Desktop Environment (CDE) on the machine and want users to obtain an AFS token as they log
- in, also add or edit the following four entries in the <computeroutput>Authentication management</computeroutput>
- section. Note that the AFS-related entries appear on two lines here only for legibility. <programlisting>
- dtlogin auth optional /usr/lib/security/libpam_unix.1
- dtlogin auth optional /usr/lib/security/pam_afs.so \
- try_first_pass ignore_root
- dtaction auth optional /usr/lib/security/libpam_unix.1
- dtaction auth optional /usr/lib/security/pam_afs.so \
- try_first_pass ignore_root
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Proceed to <link linkend="HDRWQ50">Starting the BOS Server</link> (or if referring to these instructions while
- installing an additional file server machine, return to <link linkend="HDRWQ108">Starting Server
- Programs</link>).</para>
- </listitem>
- </orderedlist></para>
- </sect2>
- </sect1>
-
- <sect1 id="HDRWQ36">
- <title>Getting Started on IRIX Systems</title>
-
- <indexterm>
- <primary>incorporating AFS kernel extensions</primary>
-
- <secondary>first AFS machine</secondary>
-
- <tertiary>IRIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>AFS kernel extensions</primary>
-
- <secondary>on first AFS machine</secondary>
-
- <tertiary>IRIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>first AFS machine</primary>
-
- <secondary>AFS kernel extensions</secondary>
-
- <tertiary>on IRIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>replacing fsck program</primary>
-
- <secondary>not necessary on IRIX</secondary>
- </indexterm>
-
- <indexterm>
- <primary>fsck program</primary>
-
- <secondary>on first AFS machine</secondary>
-
- <tertiary>IRIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>first AFS machine</primary>
-
- <secondary>fsck program</secondary>
-
- <tertiary>on IRIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>IRIX</primary>
-
- <secondary>fsck program replacement not necessary</secondary>
- </indexterm>
-
- <para>To incorporate AFS into the kernel on IRIX systems, choose one of two methods: <itemizedlist>
- <listitem>
- <para>Run the AFS initialization script to invoke the <emphasis role="bold">ml</emphasis> program distributed by Silicon
- Graphics, Incorporated (SGI), which dynamically loads AFS modifications into the kernel</para>
- </listitem>
-
- <listitem>
- <para>Build a new static kernel</para>
- </listitem>
- </itemizedlist></para>
-
- <para>Then create partitions for storing AFS volumes. You do not need to replace the IRIX <emphasis role="bold">fsck</emphasis>
- program because SGI has already modified it to handle AFS volumes properly. If the machine is to remain an AFS client machine,
- verify that the IRIX login utility installed on the machine grants an AFS token.</para>
-
- <para>In preparation for either dynamic loading or kernel building, perform the following procedures: <orderedlist>
- <listitem>
- <para>Mount the AFS CD-ROM for IRIX on the <emphasis role="bold">/cdrom</emphasis> directory. For instructions on mounting
- CD-ROMs (either locally or remotely via NFS), see your IRIX documentation. Then change directory as indicated.
- <programlisting>
- # <emphasis role="bold">cd /cdrom/sgi_65/root.client</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Copy the AFS initialization script to the local directory for initialization files (by convention, <emphasis
- role="bold">/etc/init.d</emphasis> on IRIX machines). Note the removal of the <emphasis role="bold">.rc</emphasis>
- extension as you copy the script. <programlisting>
- # <emphasis role="bold">cp -p usr/vice/etc/afs.rc /etc/init.d/afs</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Issue the <emphasis role="bold">uname -m</emphasis> command to determine the machine's CPU board type. The <emphasis
- role="bold">IP</emphasis><replaceable>xx</replaceable> value in the output must match one of the supported CPU board types
- listed in the <emphasis>IBM AFS Release Notes</emphasis> for the current version of AFS. <programlisting>
- # <emphasis role="bold">uname -m</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Proceed to either <link linkend="HDRWQ37">Loading AFS into the IRIX Kernel</link> or <link
- linkend="HDRWQ38">Building AFS into the IRIX Kernel</link>.</para>
- </listitem>
- </orderedlist></para>
-
- <indexterm>
- <primary>IRIX</primary>
-
- <secondary>AFS kernel extensions</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>afsml variable (IRIX)</primary>
-
- <secondary>first AFS machine</secondary>
- </indexterm>
-
- <indexterm>
- <primary>variables</primary>
-
- <secondary>afsml (IRIX)</secondary>
-
- <tertiary>first AFS machine</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>IRIX</primary>
-
- <secondary>afsml variable</secondary>
-
- <tertiary>first AFS machine</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>afsxnfs variable (IRIX)</primary>
-
- <secondary>first AFS machine</secondary>
- </indexterm>
-
- <indexterm>
- <primary>variables</primary>
-
- <secondary>afsxnfs (IRIX)</secondary>
-
- <tertiary>first AFS machine</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>IRIX</primary>
-
- <secondary>afsxnfs variable</secondary>
-
- <tertiary>first AFS machine</tertiary>
- </indexterm>
-
- <sect2 id="HDRWQ37">
- <title>Loading AFS into the IRIX Kernel</title>
-
- <para>The <emphasis role="bold">ml</emphasis> program is the dynamic kernel loader provided by SGI for IRIX systems. If you
- use it rather than building AFS modifications into a static kernel, then for AFS to function correctly the <emphasis
- role="bold">ml</emphasis> program must run each time the machine reboots. Therefore, the AFS initialization script (included
- on the AFS CD-ROM) invokes it automatically when the <emphasis role="bold">afsml</emphasis> configuration variable is
- activated. In this section you activate the variable and run the script.</para>
-
- <para>In later sections you verify that the script correctly initializes all AFS components, then create the links that
- incorporate AFS into the IRIX startup and shutdown sequence. <orderedlist>
- <listitem>
- <para>Create the local <emphasis role="bold">/usr/vice/etc/sgiload</emphasis> directory to house the AFS kernel library
- file. <programlisting>
- # <emphasis role="bold">mkdir /usr/vice/etc/sgiload</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Copy the appropriate AFS kernel library file to the <emphasis role="bold">/usr/vice/etc/sgiload</emphasis>
- directory. The <emphasis role="bold">IP</emphasis><replaceable>xx</replaceable> portion of the library file name must
- match the value previously returned by the <emphasis role="bold">uname -m</emphasis> command. Also choose the file
- appropriate to whether the machine's kernel supports NFS server functionality (NFS must be supported for the machine to
- act as an NFS/AFS Translator). Single- and multiprocessor machines use the same library file.</para>
-
- <para>(You can choose to copy all of the kernel library files into the <emphasis
- role="bold">/usr/vice/etc/sgiload</emphasis> directory, but they require a significant amount of space.)</para>
-
- <para>If the machine's kernel supports NFS server functionality:</para>
-
- <programlisting>
- # <emphasis role="bold">cp -p usr/vice/etc/sgiload/libafs.IP</emphasis><replaceable>xx</replaceable><emphasis role="bold">.o /usr/vice/etc/sgiload</emphasis>
-</programlisting>
-
- <para>If the machine's kernel does not support NFS server functionality:</para>
-
- <programlisting>
- # <emphasis role="bold">cp -p usr/vice/etc/sgiload/libafs.IP</emphasis><replaceable>xx</replaceable><emphasis role="bold">.nonfs.o</emphasis> \
- <emphasis role="bold">/usr/vice/etc/sgiload</emphasis>
-</programlisting>
- </listitem>
-
- <listitem>
- <para>Issue the <emphasis role="bold">chkconfig</emphasis> command to activate the <emphasis
- role="bold">afsml</emphasis> configuration variable. <programlisting>
- # <emphasis role="bold">/etc/chkconfig -f afsml on</emphasis>
-</programlisting></para>
-
- <para>If the machine is to function as an NFS/AFS Translator and the kernel supports NFS server functionality, activate
- the <emphasis role="bold">afsxnfs</emphasis> variable.</para>
-
- <programlisting>
- # <emphasis role="bold">/etc/chkconfig -f afsxnfs on</emphasis>
-</programlisting>
- </listitem>
-
- <listitem>
- <para>Run the <emphasis role="bold">/etc/init.d/afs</emphasis> script to load AFS extensions into the kernel. The script
- invokes the <emphasis role="bold">ml</emphasis> command, automatically determining which kernel library file to use
- based on this machine's CPU type and the activation state of the <emphasis role="bold">afsxnfs</emphasis>
- variable.</para>
-
- <para>You can ignore any error messages about the inability to start the BOS Server or the Cache Manager or AFS
- client.</para>
-
- <programlisting>
- # <emphasis role="bold">/etc/init.d/afs start</emphasis>
-</programlisting>
- </listitem>
-
- <listitem>
- <para>Proceed to <link linkend="HDRWQ39">Configuring Server Partitions on IRIX Systems</link>.</para>
- </listitem>
- </orderedlist></para>
-
- <indexterm>
- <primary>IRIX</primary>
-
- <secondary>AFS-modified kernel</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm>
- </sect2>
-
- <sect2 id="HDRWQ38">
- <title>Building AFS into the IRIX Kernel</title>
-
- <para>Use the following instructions to build AFS modifications into the kernel on an IRIX system. <orderedlist>
- <listitem>
- <para>Copy the kernel initialization file <emphasis role="bold">afs.sm</emphasis> to the local <emphasis
- role="bold">/var/sysgen/system</emphasis> directory, and the kernel master file <emphasis role="bold">afs</emphasis> to
- the local <emphasis role="bold">/var/sysgen/master.d</emphasis> directory. <programlisting>
- # <emphasis role="bold">cp -p bin/afs.sm /var/sysgen/system</emphasis>
- # <emphasis role="bold">cp -p bin/afs /var/sysgen/master.d</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Copy the appropriate AFS kernel library file to the local file <emphasis
- role="bold">/var/sysgen/boot/afs.a</emphasis>; the <emphasis role="bold">IP</emphasis><replaceable>xx</replaceable>
- portion of the library file name must match the value previously returned by the <emphasis role="bold">uname
- -m</emphasis> command. Also choose the file appropriate to whether the machine's kernel supports NFS server
- functionality (NFS must be supported for the machine to act as an NFS/AFS Translator). Single- and multiprocessor
- machines use the same library file.</para>
-
- <para>If the machine's kernel supports NFS server functionality:</para>
-
- <programlisting>
- # <emphasis role="bold">cp -p bin/libafs.IP</emphasis><replaceable>xx</replaceable><emphasis role="bold">.a /var/sysgen/boot/afs.a</emphasis>
-</programlisting>
-
- <para>If the machine's kernel does not support NFS server functionality:</para>
-
- <programlisting>
- # <emphasis role="bold">cp -p bin/libafs.IP</emphasis><replaceable>xx</replaceable><emphasis role="bold">.nonfs.a /var/sysgen/boot/afs.a</emphasis>
-</programlisting>
- </listitem>
-
- <listitem>
- <para>Issue the <emphasis role="bold">chkconfig</emphasis> command to deactivate the <emphasis
- role="bold">afsml</emphasis> configuration variable. <programlisting>
- # <emphasis role="bold">/etc/chkconfig -f afsml off</emphasis>
-</programlisting></para>
-
- <para>If the machine is to function as an NFS/AFS Translator and the kernel supports NFS server functionality, activate
- the <emphasis role="bold">afsxnfs</emphasis> variable.</para>
-
- <programlisting>
- # <emphasis role="bold">/etc/chkconfig -f afsxnfs on</emphasis>
-</programlisting>
- </listitem>
-
- <listitem>
- <para>Copy the existing kernel file, <emphasis role="bold">/unix</emphasis>, to a safe location. Compile the new kernel,
- which is created in the file <emphasis role="bold">/unix.install</emphasis>. It overwrites the existing <emphasis
- role="bold">/unix</emphasis> file when the machine reboots in the next step. <programlisting>
- # <emphasis role="bold">cp /unix /unix_noafs</emphasis>
- # <emphasis role="bold">autoconfig</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Reboot the machine to start using the new kernel, and login again as the superuser <emphasis
- role="bold">root</emphasis>. <programlisting>
- # <emphasis role="bold">cd /</emphasis>
- # <emphasis role="bold">shutdown -i6 -g0 -y</emphasis>
- login: <emphasis role="bold">root</emphasis>
- Password: <replaceable>root_password</replaceable>
-</programlisting></para>
- </listitem>
- </orderedlist></para>
-
- <indexterm>
- <primary>configuring</primary>
-
- <secondary>AFS server partition on first AFS machine</secondary>
-
- <tertiary>IRIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>AFS server partition</primary>
-
- <secondary>configuring on first AFS machine</secondary>
-
- <tertiary>IRIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>first AFS machine</primary>
-
- <secondary>AFS server partition</secondary>
-
- <tertiary>on IRIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>IRIX</primary>
-
- <secondary>AFS server partition</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm>
- </sect2>
-
- <sect2 id="HDRWQ39">
- <title>Configuring Server Partitions on IRIX Systems</title>
-
- <para>Every AFS file server machine must have at least one partition or logical volume dedicated to storing AFS volumes. Each
- server partition is mounted at a directory named <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>, where
- <replaceable>xx</replaceable> is one or two lowercase letters. The <emphasis
- role="bold">/vicep</emphasis><replaceable>xx</replaceable> directories must reside in the file server machine's root
- directory, not in one of its subdirectories (for example, <emphasis role="bold">/usr/vicepa</emphasis> is not an acceptable
- directory location). For additional information, see <link linkend="HDRWQ20">Performing Platform-Specific
- Procedures</link>.</para>
-
- <para>AFS supports use of both EFS and XFS partitions for housing AFS volumes. SGI encourages use of XFS partitions.
- <orderedlist>
- <listitem>
- <para>Create a directory called <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable> for each AFS server
- partition you are configuring (there must be at least one). Repeat the command for each partition. <programlisting>
- # <emphasis role="bold">mkdir /vicep</emphasis><replaceable>xx</replaceable>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Add a line with the following format to the file systems registry file, <emphasis
- role="bold">/etc/fstab</emphasis>, for each partition (or logical volume created with the XLV volume manager) to be
- mounted on one of the directories created in the previous step.</para>
-
- <para>For an XFS partition or logical volume:</para>
-
- <programlisting>
- /dev/dsk/<replaceable>disk</replaceable> /vicep<replaceable>xx</replaceable> xfs rw,raw=/dev/rdsk/<replaceable>disk</replaceable> 0 0
-</programlisting>
-
- <para>For an EFS partition:</para>
-
- <programlisting>
- /dev/dsk/<replaceable>disk</replaceable> /vicep<replaceable>xx</replaceable> efs rw,raw=/dev/rdsk/<replaceable>disk</replaceable> 0 0
-</programlisting>
-
- <para>The following are examples of an entry for each file system type:</para>
-
- <programlisting>
- /dev/dsk/dks0d2s6 /vicepa xfs rw,raw=/dev/rdsk/dks0d2s6 0 0
- /dev/dsk/dks0d3s1 /vicepb efs rw,raw=/dev/rdsk/dks0d3s1 0 0
-</programlisting>
- </listitem>
-
- <listitem>
- <para>Create a file system on each partition that is to be mounted on a <emphasis
- role="bold">/vicep</emphasis><replaceable>xx</replaceable> directory. The following commands are probably appropriate,
- but consult the IRIX documentation for more information. In both cases, <replaceable>raw_device</replaceable> is a raw
- device name like <emphasis role="bold">/dev/rdsk/dks0d0s0</emphasis> for a single disk partition or <emphasis
- role="bold">/dev/rxlv/xlv0</emphasis> for a logical volume.</para>
-
- <para>For XFS file systems, include the indicated options to configure the partition or logical volume with inodes large
- enough to accommodate AFS-specific information:</para>
-
- <programlisting>
- # <emphasis role="bold">mkfs -t xfs -i size=512 -l size=4000b</emphasis> <replaceable>raw_device</replaceable>
-</programlisting>
-
- <para>For EFS file systems:</para>
-
- <programlisting>
- # <emphasis role="bold">mkfs -t efs</emphasis> <replaceable>raw_device</replaceable>
-</programlisting>
- </listitem>
-
- <listitem>
- <para>Mount each partition by issuing either the <emphasis role="bold">mount -a</emphasis> command to mount all
- partitions at once or the <emphasis role="bold">mount</emphasis> command to mount each partition in turn.</para>
- </listitem>
-
- <listitem>
- <para><emphasis role="bold">(Optional)</emphasis> If you have configured partitions or logical volumes to use XFS, issue
- the following command to verify that the inodes are configured properly (are large enough to accommodate AFS-specific
- information). If the configuration is correct, the command returns no output. Otherwise, it specifies the command to run
- in order to configure each partition or logical volume properly. <programlisting>
- # <emphasis role="bold">/usr/afs/bin/xfs_size_check</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>If you plan to retain client functionality on this machine after completing the installation, proceed to <link
- linkend="HDRWQ40">Enabling AFS Login on IRIX Systems</link>. Otherwise, proceed to <link linkend="HDRWQ50">Starting the
- BOS Server</link>.</para>
- </listitem>
- </orderedlist></para>
-
- <indexterm>
- <primary>enabling AFS login</primary>
-
- <secondary>file server machine</secondary>
-
- <tertiary>IRIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>AFS login</primary>
-
- <secondary>on file server machine</secondary>
-
- <tertiary>IRIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>first AFS machine</primary>
-
- <secondary>AFS login</secondary>
-
- <tertiary>on IRIX</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>IRIX</primary>
-
- <secondary>AFS login</secondary>
- </indexterm>
- </sect2>
-
- <sect2 id="HDRWQ40">
- <title>Enabling AFS Login on IRIX Systems</title>
-
- <note>
- <para>If you plan to remove client functionality from this machine after completing the installation, skip this section and
- proceed to <link linkend="HDRWQ50">Starting the BOS Server</link>.</para>
- </note>
-
- <para>The standard IRIX command-line <emphasis role="bold">login</emphasis> program and the graphical <emphasis
- role="bold">xdm</emphasis> login program both automatically grant an AFS token when AFS is incorporated into the machine's
- kernel. However, some IRIX distributions use another login utility by default, and it does not necessarily incorporate the
- required AFS modifications. If that is the case, you must disable the default utility if you want AFS users to obtain AFS
- tokens at login. For further discussion, see the <emphasis>IBM AFS Release Notes</emphasis>.</para>
-
- <para>If you configure the machine to use an AFS-modified login utility, then the <emphasis
- role="bold">afsauthlib.so</emphasis> and <emphasis role="bold">afskauthlib.so</emphasis> files (included in the AFS
- distribution) must reside in the <emphasis role="bold">/usr/vice/etc</emphasis> directory. Issue the <emphasis
- role="bold">ls</emphasis> command to verify.</para>
-
- <programlisting>
- # <emphasis role="bold">ls /usr/vice/etc</emphasis>
-</programlisting>
-
- <para>If the files do not exist, mount the AFS CD-ROM for IRIX (if it is not already), change directory as indicated, and copy
- them.</para>
-
- <programlisting>
- # <emphasis role="bold">cd /cdrom/sgi_65/root.client/usr/vice/etc</emphasis>
- # <emphasis role="bold">cp -p *authlib* /usr/vice/etc</emphasis>
-</programlisting>
-
- <para>After taking any necessary action, proceed to <link linkend="HDRWQ50">Starting the BOS Server</link>.</para>
- </sect2>
- </sect1>
-
- <sect1 id="HDRWQ41">
- <title>Getting Started on Linux Systems</title>
-
- <indexterm>
- <primary>replacing fsck program</primary>
-
- <secondary>not necessary on Linux</secondary>
- </indexterm>
-
- <indexterm>
- <primary>fsck program</primary>
-
- <secondary>on first AFS machine</secondary>
-
- <tertiary>Linux</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>first AFS machine</primary>
-
- <secondary>fsck program</secondary>
-
- <tertiary>on Linux</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>Linux</primary>
-
- <secondary>fsck program replacement not necessary</secondary>
- </indexterm>
-
- <para>Begin by running the AFS initialization script to call the <emphasis role="bold">insmod</emphasis> program, which
- dynamically loads AFS modifications into the kernel. Then create partitions for storing AFS volumes. You do not need to replace
- the Linux <emphasis role="bold">fsck</emphasis> program. If the machine is to remain an AFS client machine, incorporate AFS into
- the machine's Pluggable Authentication Module (PAM) scheme. <indexterm>
- <primary>incorporating AFS kernel extensions</primary>
-
- <secondary>first AFS machine</secondary>
-
- <tertiary>Linux</tertiary>
- </indexterm> <indexterm>
- <primary>AFS kernel extensions</primary>
-
- <secondary>on first AFS machine</secondary>
-
- <tertiary>Linux</tertiary>
- </indexterm> <indexterm>
- <primary>first AFS machine</primary>
-
- <secondary>AFS kernel extensions</secondary>
-
- <tertiary>on Linux</tertiary>
- </indexterm> <indexterm>
- <primary>Linux</primary>
-
- <secondary>AFS kernel extensions</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm></para>
-
- <sect2 id="HDRWQ42">
- <title>Loading AFS into the Linux Kernel</title>
-
- <para>The <emphasis role="bold">insmod</emphasis> program is the dynamic kernel loader for Linux. Linux does not support
- incorporation of AFS modifications during a kernel build.</para>
-
- <para>For AFS to function correctly, the <emphasis role="bold">insmod</emphasis> program must run each time the machine
- reboots, so the AFS initialization script (included on the AFS CD-ROM) invokes it automatically. The script also includes
- commands that select the appropriate AFS library file automatically. In this section you run the script.</para>
-
- <para>In later sections you verify that the script correctly initializes all AFS components, then activate a configuration
- variable, which results in the script being incorporated into the Linux startup and shutdown sequence. <orderedlist>
- <listitem>
- <para>Mount the AFS CD-ROM for Linux on the local <emphasis role="bold">/cdrom</emphasis> directory. For instructions on
- mounting CD-ROMs (either locally or remotely via NFS), see your Linux documentation. Then change directory as indicated.
- <programlisting>
- # <emphasis role="bold">cd /cdrom/i386_linux22/root.client/usr/vice/etc</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Copy the AFS kernel library files to the local <emphasis role="bold">/usr/vice/etc/modload</emphasis> directory.
- The filenames for the libraries have the format <emphasis
- role="bold">libafs-</emphasis><replaceable>version</replaceable><emphasis role="bold">.o</emphasis>, where
- <replaceable>version</replaceable> indicates the kernel build level. The string <emphasis role="bold">.mp</emphasis> in
- the <replaceable>version</replaceable> indicates that the file is appropriate for machines running a multiprocessor
- kernel. <programlisting>
- # <emphasis role="bold">cp -rp modload /usr/vice/etc</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Copy the AFS initialization script to the local directory for initialization files (by convention, <emphasis
- role="bold">/etc/rc.d/init.d</emphasis> on Linux machines). Note the removal of the <emphasis role="bold">.rc</emphasis>
- extension as you copy the script. <programlisting>
- # <emphasis role="bold">cp -p afs.rc /etc/rc.d/init.d/afs</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Run the AFS initialization script to load AFS extensions into the kernel. You can ignore any error messages about
- the inability to start the BOS Server or the Cache Manager or AFS client. <programlisting>
- # <emphasis role="bold">/etc/rc.d/init.d/afs start</emphasis>
-</programlisting></para>
- </listitem>
- </orderedlist></para>
-
- <indexterm>
- <primary>configuring</primary>
-
- <secondary>AFS server partition on first AFS machine</secondary>
-
- <tertiary>Linux</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>AFS server partition</primary>
-
- <secondary>configuring on first AFS machine</secondary>
-
- <tertiary>Linux</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>first AFS machine</primary>
-
- <secondary>AFS server partition</secondary>
-
- <tertiary>on Linux</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>Linux</primary>
-
- <secondary>AFS server partition</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm>
- </sect2>
-
- <sect2 id="HDRWQ43">
- <title>Configuring Server Partitions on Linux Systems</title>
-
- <para>Every AFS file server machine must have at least one partition or logical volume dedicated to storing AFS volumes. Each
- server partition is mounted at a directory named <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>, where
- <replaceable>xx</replaceable> is one or two lowercase letters. The <emphasis
- role="bold">/vicep</emphasis><replaceable>xx</replaceable> directories must reside in the file server machine's root
- directory, not in one of its subdirectories (for example, <emphasis role="bold">/usr/vicepa</emphasis> is not an acceptable
- directory location). For additional information, see <link linkend="HDRWQ20">Performing Platform-Specific Procedures</link>.
- <orderedlist>
- <listitem>
- <para>Create a directory called <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable> for each AFS server
- partition you are configuring (there must be at least one). Repeat the command for each partition. <programlisting>
- # <emphasis role="bold">mkdir /vicep</emphasis><replaceable>xx</replaceable>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Add a line with the following format to the file systems registry file, <emphasis
- role="bold">/etc/fstab</emphasis>, for each directory just created. The entry maps the directory name to the disk
- partition to be mounted on it. <programlisting>
- /dev/<replaceable>disk</replaceable> /vicep<replaceable>xx</replaceable> ext2 defaults 0 2
-</programlisting></para>
-
- <para>The following is an example for the first partition being configured.</para>
-
- <programlisting>
- /dev/sda8 /vicepa ext2 defaults 0 2
-</programlisting>
- </listitem>
-
- <listitem>
- <para>Create a file system on each partition that is to be mounted at a <emphasis
- role="bold">/vicep</emphasis><replaceable>xx</replaceable> directory. The following command is probably appropriate, but
- consult the Linux documentation for more information. <programlisting>
- # <emphasis role="bold">mkfs -v /dev/</emphasis><replaceable>disk</replaceable>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Mount each partition by issuing either the <emphasis role="bold">mount -a</emphasis> command to mount all
- partitions at once or the <emphasis role="bold">mount</emphasis> command to mount each partition in turn.</para>
- </listitem>
-
- <listitem>
- <para>If you plan to retain client functionality on this machine after completing the installation, proceed to <link
- linkend="HDRWQ44">Enabling AFS Login on Linux Systems</link>. Otherwise, proceed to <link linkend="HDRWQ50">Starting the
- BOS Server</link>.</para>
- </listitem>
- </orderedlist></para>
-
- <indexterm>
- <primary>enabling AFS login</primary>
-
- <secondary>file server machine</secondary>
-
- <tertiary>Linux</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>AFS login</primary>
-
- <secondary>on file server machine</secondary>
-
- <tertiary>Linux</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>first AFS machine</primary>
-
- <secondary>AFS login</secondary>
-
- <tertiary>on Linux</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>Linux</primary>
-
- <secondary>AFS login</secondary>
-
- <tertiary>on file server machine</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>PAM</primary>
-
- <secondary>on Linux</secondary>
-
- <tertiary>file server machine</tertiary>
- </indexterm>
- </sect2>
-
- <sect2 id="HDRWQ44">
- <title>Enabling AFS Login on Linux Systems</title>
-
- <note>
- <para>If you plan to remove client functionality from this machine after completing the installation, skip this section and
- proceed to <link linkend="HDRWQ50">Starting the BOS Server</link>.</para>
- </note>
-
- <para>At this point you incorporate AFS into the operating system's Pluggable Authentication Module (PAM) scheme. PAM
- integrates all authentication mechanisms on the machine, including login, to provide the security infrastructure for
- authenticated access to and from the machine.</para>
-
- <para>Explaining PAM is beyond the scope of this document. It is assumed that you understand the syntax and meanings of
- settings in the PAM configuration file (for example, how the <computeroutput>other</computeroutput> entry works, the effect of
- marking an entry as <computeroutput>required</computeroutput>, <computeroutput>optional</computeroutput>, or
- <computeroutput>sufficient</computeroutput>, and so on).</para>
-
- <para>The following instructions explain how to alter the entries in the PAM configuration file for each service for which you
- wish to use AFS authentication. Other configurations possibly also work, but the instructions specify the recommended and
- tested configuration.</para>
-
- <para>The recommended AFS-related entries in the PAM configuration file make use of one or more of the following three
- attributes. <variablelist>
- <varlistentry>
- <term><emphasis role="bold"><computeroutput>try_first_pass</computeroutput></emphasis></term>
-
- <listitem>
- <para>This is a standard PAM attribute that can be included on entries after the first one for a service; it directs
- the module to use the password that was provided to the first module. For the AFS module, it means that AFS
- authentication succeeds if the password provided to the module listed first is the user's correct AFS password. For
- further discussion of this attribute and its alternatives, see the operating system's PAM documentation.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><emphasis role="bold"><computeroutput>ignore_root</computeroutput></emphasis></term>
-
- <listitem>
- <para>This attribute, specific to the AFS PAM module, directs it to ignore not only the local superuser <emphasis
- role="bold">root</emphasis>, but also any user with UID 0 (zero).</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><emphasis role="bold"><computeroutput>setenv_password_expires</computeroutput></emphasis></term>
-
- <listitem>
- <para>This attribute, specific to the AFS PAM module, sets the environment variable PASSWORD_EXPIRES to the expiration
- date of the user's AFS password, which is recorded in the Authentication Database.</para>
- </listitem>
- </varlistentry>
- </variablelist></para>
-
- <para>Perform the following steps to enable AFS login. <orderedlist>
- <listitem>
- <para>Mount the AFS CD-ROM for Linux on the <emphasis role="bold">/cdrom</emphasis> directory, if it is not already.
- Then change to the directory for PAM modules, which depends on which Linux distribution you are using.</para>
-
- <para>If you are using a Linux distribution from Red Hat Software:</para>
-
- <programlisting>
- # <emphasis role="bold">cd /lib/security</emphasis>
-</programlisting>
-
- <para>If you are using another Linux distribution:</para>
-
- <programlisting>
- # <emphasis role="bold">cd /usr/lib/security</emphasis>
-</programlisting>
- </listitem>
-
- <listitem>
- <para>Copy the appropriate AFS authentication library file to the directory to which you changed in the previous step.
- Create a symbolic link whose name does not mention the version. Omitting the version eliminates the need to edit the PAM
- configuration file if you later update the library file.</para>
-
- <para>If you use the AFS Authentication Server (<emphasis role="bold">kaserver</emphasis> process):</para>
-
- <programlisting>
- # <emphasis role="bold">cp /cdrom/i386_linux22/lib/pam_afs.so.1 .</emphasis>
- # <emphasis role="bold">ln -s pam_afs.so.1 pam_afs.so</emphasis>
-</programlisting>
-
- <para>If you use a Kerberos implementation of AFS authentication:</para>
-
- <programlisting>
- # <emphasis role="bold">cp /cdrom/i386_linux22/lib/pam_afs.krb.so.1 .</emphasis>
- # <emphasis role="bold">ln -s pam_afs.krb.so.1 pam_afs.so</emphasis>
-</programlisting>
- </listitem>
-
- <listitem>
- <para>For each service with which you want to use AFS authentication, insert an entry for the AFS PAM module into the
- <computeroutput>auth</computeroutput> section of the service's PAM configuration file. (Linux uses a separate
- configuration file for each service, unlike some other operating systems which list all services in a single file.) Mark
- the entry as <computeroutput>sufficient</computeroutput> in the second field.</para>
-
- <para>Place the AFS entry below any entries that impose conditions under which you want the service to fail for a user
- who does not meet the entry's requirements. Mark these entries <computeroutput>required</computeroutput>. Place the AFS
- entry above any entries that need to execute only if AFS authentication fails.</para>
-
- <para>Insert the following AFS entry if using the Red Hat distribution:</para>
-
- <programlisting>
- auth sufficient /lib/security/pam_afs.so try_first_pass ignore_root
-</programlisting>
-
- <para>Insert the following AFS entry if using another distribution:</para>
-
- <programlisting>
- auth sufficient /usr/lib/security/pam_afs.so try_first_pass ignore_root
-</programlisting>
-
- <para>The following example illustrates the recommended configuration of the configuration file for the <emphasis
- role="bold">login</emphasis> service (<emphasis role="bold">/etc/pam.d/login</emphasis>) on a machine using the Red Hat
- distribution.</para>
-
- <programlisting>
- #%PAM-1.0
- auth required /lib/security/pam_securetty.so
- auth required /lib/security/pam_nologin.so
- auth sufficient /lib/security/pam_afs.so try_first_pass ignore_root
- auth required /lib/security/pam_pwdb.so shadow nullok
- account required /lib/security/pam_pwdb.so
- password required /lib/security/pam_cracklib.so
- password required /lib/security/pam_pwdb.so shadow nullok use_authtok
- session required /lib/security/pam_pwdb.so
-</programlisting>
- </listitem>
-
- <listitem>
- <para>Proceed to <link linkend="HDRWQ50">Starting the BOS Server</link> (or if referring to these instructions while
- installing an additional file server machine, return to <link linkend="HDRWQ108">Starting Server
- Programs</link>).</para>
- </listitem>
- </orderedlist></para>
+ <note>
+ <para>If you plan to remove client functionality from this machine
+ after completing the installation, skip this section and proceed
+ to <link linkend="HDRWQ50">Starting the BOS Server</link>.</para>
+ </note>
+
+ <para>At this point you incorporate AFS into the operating system's
+ Pluggable Authentication Module (PAM) scheme. PAM integrates all
+ authentication mechanisms on the machine, including login, to provide
+ the security infrastructure for authenticated access to and from the
+ machine.</para>
+
+ <para>You should first configure your system to obtain Kerberos v5
+ tickets as part of the authentication process, and then run an AFS PAM
+ module to obtain tokens from those tickets after authentication. Many
+ Linux distributions come with a Kerberos v5 PAM module (usually called
+ pam-krb5 or pam_krb5), or you can download and install <ulink
+ url="http://www.eyrie.org/~eagle/software/pam-krb5">Russ Allbery's
+ Kerberos v5 PAM module</ulink>, which is tested regularly with AFS.
+ See the instructions of whatever PAM module you use for how to
+ configure it.</para>
+
+ <para>Some Kerberos v5 PAM modules do come with native AFS support
+ (usually requiring the Heimdal Kerberos implementation rather than the
+ MIT Kerberos implementation). If you are using one of those PAM
+ modules, you can configure it to obtain AFS tokens. It's more common,
+ however, to separate the AFS token acquisition into a separate PAM
+ module.</para>
+
+ <para>The recommended AFS PAM module is <ulink
+ url="http://www.eyrie.org/~eagle/software/pam-afs-session/">Russ
+ Allbery's pam-afs-session module</ulink>. It should work with any of
+ the Kerberos v5 PAM modules. To add it to the PAM configuration, you
+ often only need to add configuration to the session group:</para>
+
+ <example>
+ <title>Linux PAM session example</title>
+ <literallayout>session required pam_afs_session.so</literallayout>
+ </example>
+
+ <para>If you also want to obtain AFS tokens for <command>scp</command>
+ and similar commands that don't open a session, you will also need to
+ add the AFS PAM module to the auth group so that the PAM
+ <function>setcred</function> call will obtain tokens. The
+ <literal>pam_afs_session</literal> module will always return success
+ for authentication so that it can be added to the auth group only for
+ <function>setcred</function>, so make sure that it's not marked as
+ <literal>sufficient</literal>.</para>
+
+ <example>
+ <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>
+ </example>
+
+ <para>This example will work if you want to try Kerberos v5 first and
+ then fall back to regular Unix authentication.
+ <literal>success=ok</literal> for the Kerberos PAM module followed by
+ <literal>default=done</literal> for the AFS PAM module will cause a
+ successful Kerberos login to run the AFS PAM module and then skip the
+ Unix authentication module. <literal>default=1</literal> on the
+ Kerberos PAM module causes failure of that module to skip the next
+ module (the AFS PAM module) and fall back to the Unix module. If you
+ want to try Unix authentication first and rearrange the order, be sure
+ to use <literal>default=die</literal> instead.</para>
+
+ <para>The PAM configuration is stored in different places in different
+ Linux distributions. On Red Hat, look in
+ <filename>/etc/pam.d/system-auth</filename>. On Debian and
+ derivatives, look in <filename>/etc/pam.d/common-session</filename>
+ and <filename>/etc/pam.d/common-auth</filename>.</para>
+
+ <para>For additional configuration examples and the configuration
+ options of the AFS PAM module, see its documentation. For more
+ details on the available options for the PAM configuration, see the
+ Linux PAM documentation.</para>
+
+ <para>Sites which still require the deprecated
+ <command>kaserver</command> or
+ external Kerberos v4 authentication should consult <link
+ linkend="KAS015">Enabling kaserver based AFS Login on Linux
+ Systems</link> for details of how to enable AFS login on Linux.</para>
+
+ <para>Proceed to <link linkend="HDRWQ50">Starting the BOS
+ Server</link> (or if referring to these instructions while installing
+ an additional file server machine, return to <link
+ linkend="HDRWQ108">Starting Server Programs</link>).</para>
</sect2>
</sect1>
<para>In later sections you verify that the script correctly initializes all AFS components, then create the links that
incorporate AFS into the Solaris startup and shutdown sequence. <orderedlist>
<listitem>
- <para>Mount the AFS CD-ROM for Solaris on the <emphasis role="bold">/cdrom</emphasis> directory. For instructions on
- mounting CD-ROMs (either locally or remotely via NFS), see your Solaris documentation. Then change directory as
- indicated. <programlisting>
- # <emphasis role="bold">cd /cdrom/sun4x_56/root.client/usr/vice/etc</emphasis>
+ <para>Unpack the OpenAFS Solaris distribution tarball. The examples
+ below assume that you have unpacked the files into the
+ <emphasis role="bold">/tmp/afsdist</emphasis> directory. If you
+ pick a diferent location, substitute this in all of the following
+ exmaples. Once you have unpacked the distribution, change directory
+ as indicated.
+<programlisting>
+ # <emphasis role="bold">cd /tmp/afsdist/sun4x_56/dest/root.client/usr/vice/etc</emphasis>
</programlisting></para>
</listitem>
<para>Copy the appropriate AFS kernel library file to the local file <emphasis
role="bold">/kernel/fs/afs</emphasis>.</para>
+ <para>If the machine is running Solaris 11 on the x86_64 platform:</para>
+
+ <programlisting>
+ # <emphasis role="bold">cp -p modload/libafs64.o /kernel/drv/amd64/afs</emphasis>
+</programlisting>
+
+ <para>If the machine is running Solaris 10 on the x86_64 platform:</para>
+
+ <programlisting>
+ # <emphasis role="bold">cp -p modload/libafs64.o /kernel/fs/amd64/afs</emphasis>
+</programlisting>
+
<para>If the machine is running Solaris 2.6 or the 32-bit version of Solaris 7, its kernel supports NFS server
functionality, and the <emphasis role="bold">nfsd</emphasis> process is running:</para>
<listitem>
<para>Copy the <emphasis role="bold">vfsck</emphasis> binary to the newly created directory, changing the name as you do
so. <programlisting>
- # <emphasis role="bold">cp /cdrom/sun4x_56/root.server/etc/vfsck fsck</emphasis>
+ # <emphasis role="bold">cp /tmp/afsdist/sun4x_56/dest/root.server/etc/vfsck fsck</emphasis>
</programlisting></para>
</listitem>
proceed to <link linkend="HDRWQ50">Starting the BOS Server</link>.</para>
</listitem>
</orderedlist></para>
+ </sect2>
+ <sect2 id="HDRWQ49">
+ <title>Enabling AFS Login on Solaris Systems</title>
<indexterm>
<primary>enabling AFS login</primary>
<tertiary>file server machine</tertiary>
</indexterm>
+ <note>
+ <para>If you plan to remove client functionality from this machine after completing the installation, skip this section and
+ proceed to <link linkend="HDRWQ50">Starting the BOS Server</link>.</para>
+ </note>
+
+ <para>At this point you incorporate AFS into the operating system's
+ Pluggable Authentication Module (PAM) scheme. PAM integrates all
+ authentication mechanisms on the machine, including login, to provide
+ the security infrastructure for authenticated access to and from the
+ machine.</para>
+
+ <para>Explaining PAM is beyond the scope of this document. It is
+ assumed that you understand the syntax and meanings of settings in the
+ PAM configuration file (for example, how the
+ <computeroutput>other</computeroutput> entry works, the effect of
+ marking an entry as <computeroutput>required</computeroutput>,
+ <computeroutput>optional</computeroutput>, or
+ <computeroutput>sufficient</computeroutput>, and so on).</para>
+
+ <para>You should first configure your system to obtain Kerberos v5
+ tickets as part of the authentication process, and then run an AFS PAM
+ module to obtain tokens from those tickets after authentication.
+ Current versions of Solaris come with a Kerberos v5 PAM module that
+ will work, or you can download and install <ulink
+ url="http://www.eyrie.org/~eagle/software/pam-krb5">Russ Allbery's
+ Kerberos v5 PAM module</ulink>, which is tested regularly with AFS.
+ See the instructions of whatever PAM module you use for how to
+ configure it.</para>
+
+ <para>Some Kerberos v5 PAM modules do come with native AFS support
+ (usually requiring the Heimdal Kerberos implementation rather than the
+ MIT Kerberos implementation). If you are using one of those PAM
+ modules, you can configure it to obtain AFS tokens. It's more common,
+ however, to separate the AFS token acquisition into a separate PAM
+ module.</para>
+
+ <para>The recommended AFS PAM module is <ulink
+ url="http://www.eyrie.org/~eagle/software/pam-afs-session/">Russ
+ Allbery's pam-afs-session module</ulink>. It should work with any of
+ the Kerberos v5 PAM modules. To add it to the PAM configuration, you
+ often only need to add configuration to the session group in
+ <filename>pam.conf</filename>:</para>
+
+ <example>
+ <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.
+ You may want to add a similar line for the ssh service and for any
+ other login service that you use, including possibly the
+ <literal>other</literal> service (which serves as a catch-all). You
+ may also want to add options to the AFS PAM session module
+ (particularly <literal>retain_after_close</literal>, which is
+ necessary for some versions of Solaris.</para>
+
+ <para>For additional configuration examples and the configuration
+ options of the AFS PAM module, see its documentation. For more
+ details on the available options for the PAM configuration, see the
+ <filename>pam.conf</filename> manual page.</para>
+
+ <para>Sites which still require <emphasis
+ role="bold">kaserver</emphasis> or external Kerberos v4 authentication
+ should consult <link linkend="KAS016">"Enabling kaserver based AFS
+ Login on Solaris Systems"</link> for details of how to enable AFS
+ login on Solaris.</para>
+
+ <para>Proceed to <link linkend="HDRWQ49a">Editing the File Systems
+ Clean-up Script on Solaris Systems</link></para>
+ </sect2>
+ <sect2 id="HDRWQ49a">
+ <title>Editing the File Systems Clean-up Script on Solaris Systems</title>
<indexterm>
<primary>Solaris</primary>
<tertiary>file server machine</tertiary>
</indexterm>
- </sect2>
-
- <sect2 id="HDRWQ49">
- <title>Enabling AFS Login and Editing the File Systems Clean-up Script on Solaris Systems</title>
-
- <note>
- <para>If you plan to remove client functionality from this machine after completing the installation, skip this section and
- proceed to <link linkend="HDRWQ50">Starting the BOS Server</link>.</para>
- </note>
-
- <para>At this point you incorporate AFS into the operating system's Pluggable Authentication Module (PAM) scheme. PAM
- integrates all authentication mechanisms on the machine, including login, to provide the security infrastructure for
- authenticated access to and from the machine.</para>
-
- <para>Explaining PAM is beyond the scope of this document. It is assumed that you understand the syntax and meanings of
- settings in the PAM configuration file (for example, how the <computeroutput>other</computeroutput> entry works, the effect of
- marking an entry as <computeroutput>required</computeroutput>, <computeroutput>optional</computeroutput>, or
- <computeroutput>sufficient</computeroutput>, and so on).</para>
-
- <para>The following instructions explain how to alter the entries in the PAM configuration file for each service for which you
- wish to use AFS authentication. Other configurations possibly also work, but the instructions specify the recommended and
- tested configuration.</para>
-
- <note>
- <para>The instructions specify that you mark each entry as <computeroutput>optional</computeroutput>. However, marking some
- modules as optional can mean that they grant access to the corresponding service even when the user does not meet all of the
- module's requirements. In some operating system revisions, for example, if you mark as optional the module that controls
- login via a dial-up connection, it allows users to login without providing a password. See the <emphasis>IBM AFS Release
- Notes</emphasis> for a discussion of any limitations that apply to this operating system.</para>
-
- <para>Also, with some operating system versions you must install patches for PAM to interact correctly with certain
- authentication programs. For details, see the <emphasis>IBM AFS Release Notes</emphasis>.</para>
- </note>
-
- <para>The recommended AFS-related entries in the PAM configuration file make use of one or more of the following three
- attributes. <variablelist>
- <varlistentry>
- <term><emphasis role="bold"><computeroutput>try_first_pass</computeroutput></emphasis></term>
-
- <listitem>
- <para>This is a standard PAM attribute that can be included on entries after the first one for a service; it directs
- the module to use the password that was provided to the first module. For the AFS module, it means that AFS
- authentication succeeds if the password provided to the module listed first is the user's correct AFS password. For
- further discussion of this attribute and its alternatives, see the operating system's PAM documentation.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><emphasis role="bold"><computeroutput>ignore_root</computeroutput></emphasis></term>
-
- <listitem>
- <para>This attribute, specific to the AFS PAM module, directs it to ignore not only the local superuser <emphasis
- role="bold">root</emphasis>, but also any user with UID 0 (zero).</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><emphasis role="bold"><computeroutput>setenv_password_expires</computeroutput></emphasis></term>
-
- <listitem>
- <para>This attribute, specific to the AFS PAM module, sets the environment variable PASSWORD_EXPIRES to the expiration
- date of the user's AFS password, which is recorded in the Authentication Database.</para>
- </listitem>
- </varlistentry>
- </variablelist></para>
-
- <para>Perform the following steps to enable AFS login. <orderedlist>
- <listitem>
- <para>Mount the AFS CD-ROM for Solaris on the <emphasis role="bold">/cdrom</emphasis> directory, if it is not already.
- Then change directory as indicated. <programlisting>
- # <emphasis role="bold">cd /usr/lib/security</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Copy the AFS authentication library file to the <emphasis role="bold">/usr/lib/security</emphasis> directory. Then
- create a symbolic link to it whose name does not mention the version. Omitting the version eliminates the need to edit
- the PAM configuration file if you later update the library file.</para>
-
- <para>If you use the AFS Authentication Server (<emphasis role="bold">kaserver</emphasis> process):</para>
-
- <programlisting>
- # <emphasis role="bold">cp /cdrom/sun4x_56/lib/pam_afs.so.1 .</emphasis>
- # <emphasis role="bold">ln -s pam_afs.so.1 pam_afs.so</emphasis>
-</programlisting>
-
- <para>If you use a Kerberos implementation of AFS authentication:</para>
-
- <programlisting>
- # <emphasis role="bold">cp /cdrom/sun4x_56/lib/pam_afs.krb.so.1 .</emphasis>
- # <emphasis role="bold">ln -s pam_afs.krb.so.1 pam_afs.so</emphasis>
-</programlisting>
- </listitem>
-
- <listitem>
- <para>Edit the <computeroutput>Authentication management</computeroutput> section of the Solaris PAM configuration file,
- <emphasis role="bold">/etc/pam.conf</emphasis> by convention. The entries in this section have the value
- <computeroutput>auth</computeroutput> in their second field.</para>
-
- <para>First edit the standard entries, which refer to the Solaris PAM module (usually, the file <emphasis
- role="bold">/usr/lib/security/pam_unix.so.1</emphasis>) in their fourth field. For each service for which you want to
- use AFS authentication, edit the third field of its entry to read <computeroutput>optional</computeroutput>. The
- <emphasis role="bold">pam.conf</emphasis> file in the Solaris distribution usually includes standard entries for the
- <emphasis role="bold">login</emphasis>, <emphasis role="bold">rlogin</emphasis>, and <emphasis
- role="bold">rsh</emphasis> services, for instance.</para>
-
- <para>If there are services for which you want to use AFS authentication, but for which the <emphasis
- role="bold">pam.conf</emphasis> file does not already include a standard entry, you must create that entry and place the
- value <computeroutput>optional</computeroutput> in its third field. For instance, the Solaris <emphasis
- role="bold">pam.conf</emphasis> file does not usually include standard entries for the <emphasis
- role="bold">ftp</emphasis> or <emphasis role="bold">telnet</emphasis> services.</para>
-
- <para>Then create an AFS-related entry for each service, placing it immediately below the standard entry. The following
- example shows what the <computeroutput>Authentication Management</computeroutput> section looks like after you have you
- edited or created entries for the services mentioned previously. Note that the example AFS entries appear on two lines
- only for legibility.</para>
-
- <programlisting>
- login auth optional /usr/lib/security/pam_unix.so.1
- login auth optional /usr/lib/security/pam_afs.so \
- try_first_pass ignore_root setenv_password_expires
- rlogin auth optional /usr/lib/security/pam_unix.so.1
- rlogin auth optional /usr/lib/security/pam_afs.so \
- try_first_pass ignore_root setenv_password_expires
- rsh auth optional /usr/lib/security/pam_unix.so.1
- rsh auth optional /usr/lib/security/pam_afs.so \
- try_first_pass ignore_root
- ftp auth optional /usr/lib/security/pam_unix.so.1
- ftp auth optional /usr/lib/security/pam_afs.so \
- try_first_pass ignore_root
- telnet auth optional /usr/lib/security/pam_unix.so.1
- telnet auth optional /usr/lib/security/pam_afs.so \
- try_first_pass ignore_root setenv_password_expires
-</programlisting>
- </listitem>
-
- <listitem>
- <para>If you use the Common Desktop Environment (CDE) on the machine and want users to obtain an AFS token as they log
- in, also add or edit the following four entries in the <computeroutput>Authentication management</computeroutput>
- section. Note that the AFS-related entries appear on two lines here only for legibility. <programlisting>
- dtlogin auth optional /usr/lib/security/pam_unix.so.1
- dtlogin auth optional /usr/lib/security/pam_afs.so \
- try_first_pass ignore_root
- dtsession auth optional /usr/lib/security/pam_unix.so.1
- dtsession auth optional /usr/lib/security/pam_afs.so \
- try_first_pass ignore_root
-</programlisting></para>
- </listitem>
+
+ <orderedlist>
<listitem>
<para>Some Solaris distributions include a script that locates and removes unneeded files from various file systems. Its
conventional location is <emphasis role="bold">/usr/lib/fs/nfs/nfsfind</emphasis>. The script generally uses an argument
installing an additional file server machine, return to <link linkend="HDRWQ108">Starting Server
Programs</link>).</para>
</listitem>
- </orderedlist></para>
+ </orderedlist>
<indexterm>
<primary>Basic OverSeer Server</primary>
<sect1 id="HDRWQ50">
<title>Starting the BOS Server</title>
- <para>You are now ready to start the AFS server processes on this machine. Begin by copying the AFS server binaries from the
- CD-ROM to the conventional local disk location, the <emphasis role="bold">/usr/afs/bin</emphasis> directory. The following
- instructions also create files in other subdirectories of the <emphasis role="bold">/usr/afs</emphasis> directory.</para>
-
- <para>Then issue the <emphasis role="bold">bosserver</emphasis> command to initialize the Basic OverSeer (BOS) Server, which
- monitors and controls other AFS server processes on its server machine. Include the <emphasis role="bold">-noauth</emphasis>
- flag to disable authorization checking. Because you have not yet configured your cell's AFS authentication and authorization
- mechanisms, the BOS Server cannot perform authorization checking as it does during normal operation. In no-authorization mode,
- it does not verify the identity or privilege of the issuer of a <emphasis role="bold">bos</emphasis> command, and so performs
- any operation for anyone.</para>
-
- <para>Disabling authorization checking gravely compromises cell security. You must complete all subsequent steps in one
- uninterrupted pass and must not leave the machine unattended until you restart the BOS Server with authorization checking
- enabled, in <link linkend="HDRWQ72">Verifying the AFS Initialization Script</link>.</para>
+ <para>You are now ready to start the AFS server processes on this machine.
+ If you are not working from a packaged distribution, begin by installing the
+ AFS server binaries to the conventional local disk
+ location, the <emphasis role="bold">/usr/afs/bin</emphasis> directory. The
+ following instructions also create files in other subdirectories of the
+ <emphasis role="bold">/usr/afs</emphasis> directory.</para>
+
+ <para>Then obtain a krb5 keytab for use by the servers in the cell.
+ Once the keytab is in place, issue the
+ <emphasis role="bold">bosserver</emphasis> command to initialize
+ the Basic OverSeer (BOS) Server, which
+ monitors and controls other AFS server processes on its server machine.
+ Because you have not yet configured your cell's AFS authentication and authorization
+ mechanisms, you must always use the
+ <emphasis role="bold">-localauth</emphasis> flag to commands, to use a
+ printed token that does not correspond to a normal krb5 identity.</para>
+ <para>Older versions of these instructions used the
+ <emphasis role="bold">-noauth</emphasis> flag, which completely disables
+ all authentication and authorization checking, allowing anyone at all
+ to control the system. Do not use this flag! It is highly insecure,
+ and is no longer needed.</para>
<para>As it initializes for the first time, the BOS Server creates the following directories and files, setting the owner to the
local superuser <emphasis role="bold">root</emphasis> and the mode bits to limit the ability to write (and in some cases, read)
- them. For a description of the contents and function of these directories and files, see the chapter in the <emphasis>IBM AFS
+ them. For a description of the contents and function of these directories and files, see the chapter in the <emphasis>OpenAFS
Administration Guide</emphasis> about administering server machines. For further discussion of the mode bit settings, see <link
linkend="HDRWQ96">Protecting Sensitive AFS Directories</link>. <indexterm>
- <primary>CD-ROM</primary>
+ <primary>Binary Distribution</primary>
<secondary>copying server files from</secondary>
role="bold">ThisCell</emphasis> files in the <emphasis role="bold">/usr/vice/etc</emphasis> directory because they generally run
on client machines. On machines that are AFS servers only (as this machine currently is), the files reside only in the <emphasis
role="bold">/usr/afs/etc</emphasis> directory; the links enable the command interpreters to retrieve the information they need.
- Later instructions for installing the client functionality replace the links with actual files. <orderedlist>
- <listitem>
- <para>On the local <emphasis role="bold">/cdrom</emphasis> directory, mount the AFS CD-ROM for this machine's system type,
- if it is not already. For instructions on mounting CD-ROMs (either locally or remotely via NFS), consult the operating
- system documentation.</para>
- </listitem>
+ Later instructions for installing the client functionality replace the links with actual files.</para>
+ <sect2>
+ <title>Generating the Cell's Kerberos V5 Keys</title>
+
+ <para>This guide uses krb5 for authentication; do not use the
+ legacy <emphasis role="bold">kaserver</emphasis> for new
+ installations.</para>
+ <para>This section creates only the cell-wide shared secret key;
+ administrative users will be created later in the procedure.
+ This cell-wide key has the principal name
+ <emphasis role="bold">afs/<replaceable>cell</replaceable></emphasis>.
+ No user logs in under this identity, but it is used to encrypt the
+ server tickets that the KDC grants to AFS clients for presentation
+ to server processes during mutual authentication. (The
+ chapter in the <emphasis>OpenAFS Administration Guide</emphasis>
+ about cell configuration and administration describes the
+ role of server encryption keys in mutual authentication.)</para>
+ <para>The OpenAFS 1.8.x series stores the cell-wide shared keys in
+ the file <emphasis role="bold">/usr/afs/etc/KeyFileExt</emphasis>,
+ whereas the 1.6.x series uses a krb5 keytab format file in
+ <emphasis role="bold">/usr/afs/etc/rxkad.keytab</emphasis>.
+ These instructions create both files, but populating the
+ <emphasis role="bold">KeyFileExt</emphasis> file will only succeed
+ using the version of <emphasis role="bold">asetkey</emphasis>
+ from OpenAFS 1.8.x.</para>
+ <para>The examples below assume you are using MIT Kerberos. Please refer
+ to the documentation for your KDC's administrative interface if you are
+ using a different vendor</para>
+
+ <orderedlist>
+ <listitem>
+ <para>Enter <emphasis role="bold">kadmin</emphasis> interactive mode.
+ <programlisting>
+ # <emphasis role="bold">kadmin</emphasis>
+ Authenticating as principal <replaceable>you</replaceable>/admin@<replaceable>YOUR REALM</replaceable> with password
+ Password for <replaceable>you/admin@REALM</replaceable>: <replaceable>your_password</replaceable>
+ </programlisting> <indexterm>
+ <primary>server encryption key</primary>
+
+ <secondary>in Kerberos Database</secondary>
+ </indexterm> <indexterm>
+ <primary>creating</primary>
+
+ <secondary>server encryption key</secondary>
+
+ <tertiary>Kerberos Database</tertiary>
+ </indexterm></para>
+ </listitem>
+
+ <listitem>
+ <para>Issue the
+ <emphasis role="bold">add_principal</emphasis> command to create
+ a Kerberos Database entry for
+ <emphasis role="bold">afs/<<replaceable>cell name</replaceable>></emphasis>.</para>
+
+ <para>Note that when creating the
+ <emphasis role="bold">afs/<<replaceable>cell name</replaceable>></emphasis>
+ entry, the encryption type list does not include any single-DES
+ encryption types. If such encryption types are included,
+ additional <emphasis role="bold">asetkey</emphasis> commands
+ will be needed to place those keys in the legacy
+ <emphasis role="bold">KeyFile</emphasis> and ensure proper
+ operation of the cell.
+ For more details regarding encryption types, see the documentation
+ for your Kerberos installation.
+
+ <programlisting>
+ kadmin: <emphasis role="bold">add_principal -randkey -e aes256-cts-hmac-sha1-96:normal,aes128-cts-hmac-sha1-96:normal afs/</emphasis><<replaceable>cell name</replaceable>>
+ Principal "afs/<replaceable>cell name</replaceable>@<replaceable>REALM</replaceable>" created.
+ </programlisting>
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>Extract the newly created key for
+ <emphasis role="bold">afs/<replaceable>cell</replaceable></emphasis>
+ to a keytab on the local machine.</para>
+
+ <para>The keytab contains the key material that ensures the security of your AFS cell. You should ensure that it is kept in a secure location at all times.</para>
+
+ <programlisting>
+ kadmin: <emphasis role="bold">ktadd -k /usr/afs/etc/rxkad.keytab -e aes256-cts-hmac-sha1-96:normal,aes128-cts-hmac-sha1-96:normal afs/<<replaceable>cell name</replaceable>></emphasis>
+ Entry for principal afs/<<replaceable>cell name</replaceable>> with kvno 2, encryption type aes256-cts-hmac-sha1-96 added to keytab WRFILE:/usr/afs/etc/rxkad.keytab
+ Entry for principal afs/<<replaceable>cell name</replaceable>> with kvno 2, encryption type aes128-cts-hmac-sha1-96 added to keytab WRFILE:/usr/afs/etc/rxkad.keytab
+ </programlisting>
+ <para>Make a note of the key version number (kvno) given in the
+ response, as you will need it to load the key into
+ the <emphasis role="bold">KeyFileExt</emphasis> in a later
+ step</para>
+
+ <note><para>Note that each time you run
+ <emphasis role="bold">ktadd</emphasis> a new key is generated
+ for the item being extracted. This means that you cannot run ktadd
+ multiple times and end up with the same key material each time.
+ </para></note>
+
+ </listitem>
+ <listitem>
+ <para>Issue the <emphasis role="bold">quit</emphasis> command to leave <emphasis role="bold">kadmin</emphasis>
+ interactive mode. <programlisting>
+ kadmin: <emphasis role="bold">quit</emphasis>
+ </programlisting></para>
+ </listitem>
+
+ <listitem id="LIWQ58">
+ <para>Issue the
+ <emphasis role="bold">asetkey</emphasis> command to set the AFS
+ server encryption key in the
+ <emphasis role="bold">/usr/afs/etc/KeyFileExt</emphasis> file.
+ This key
+ is created from the <emphasis role="bold">rxkad.keytab</emphasis>
+ file created earlier.</para>
+
+ <para>asetkey requires the key version number (or kvno) of the
+ <emphasis role="bold">afs/</emphasis><replaceable>cell</replaceable>
+ key, as well as the encryption type number of the key.
+ You should have made note of the kvno when creating the key
+ earlier. The key version number can also be found by running the
+ <emphasis role="bold">kvno</emphasis> command</para>
+ <programlisting>
+ # <emphasis role="bold">kvno -kt /usr/afs/etc/rxkad.keytab</emphasis>
+ </programlisting>
+ <para>The encryption type numbers can be found in the local krb5
+ headers or the IANA registry. The most common numbers are
+ 18 for <emphasis role="bold">aes256-cts-hmac-sha1-96</emphasis> and
+ 17 for <emphasis role="bold">aes128-cts-hmac-sha1-96</emphasis>.
+ </para>
+
+ <para>Once the kvno and enctypes are known, the keys
+ can then be extracted using asetkey</para>
+ <programlisting>
+ # <emphasis role="bold">asetkey add rxkad_krb5</emphasis> <<replaceable>kvno</replaceable>> <emphasis role="bold">18 /usr/afs/etc/rxkad.keytab afs/</emphasis><<replaceable>cell name</replaceable>>
+ # <emphasis role="bold">asetkey add rxkad_krb5</emphasis> <<replaceable>kvno</replaceable>> <emphasis role="bold">17 /usr/afs/etc/rxkad.keytab afs/</emphasis><<replaceable>cell name</replaceable>>
+ </programlisting>
+ </listitem>
+ </orderedlist>
+ </sect2>
+ <sect2>
+ <title>Starting the Server Processes</title>
+ <para>Now that the keys are in place, proceed to start the server
+ processes:
+ <orderedlist>
<listitem>
- <para>Copy files from the CD-ROM to the local <emphasis role="bold">/usr/afs</emphasis> directory. <programlisting>
- # <emphasis role="bold">cd /cdrom/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/root.server/usr/afs</emphasis>
- # <emphasis role="bold">cp -rp * /usr/afs</emphasis>
-</programlisting> <indexterm>
+ <para>If you are building from source, you need to install the
+ compiled files to the local
+ <emphasis role="bold">/usr/afs</emphasis> directory. <indexterm>
<primary>commands</primary>
<secondary>bosserver</secondary>
</listitem>
<listitem>
- <para>Issue the <emphasis role="bold">bosserver</emphasis> command. Include the <emphasis role="bold">-noauth</emphasis>
- flag to disable authorization checking. <programlisting>
- # <emphasis role="bold">/usr/afs/bin/bosserver -noauth &</emphasis>
+ <para>Issue the <emphasis role="bold">bosserver</emphasis> command.
+ <programlisting>
+ # <emphasis role="bold">/usr/afs/bin/bosserver</emphasis>
</programlisting></para>
</listitem>
<secondary>first AFS machine as database server</secondary>
</indexterm>
+ </sect2>
</sect1>
<sect1 id="HDRWQ51">
<title>Defining Cell Name and Membership for Server Processes</title>
- <para>Now assign your cell's name. The chapter in the <emphasis>IBM AFS Administration Guide</emphasis> about cell configuration
+ <para>Now assign your cell's name. The chapter in the <emphasis>OpenAFS Administration Guide</emphasis> about cell configuration
and administration issues discusses the important considerations, explains why changing the name is difficult, and outlines the
restrictions on name format. Two of the most important restrictions are that the name cannot include uppercase letters or more
than 64 characters.</para>
</listitem>
</itemizedlist> <note>
<para>In the following and every instruction in this guide, for the <replaceable>machine name</replaceable> argument
- substitute the fully-qualified hostname (such as <emphasis role="bold">fs1.abc.com</emphasis>) of the machine you are
+ substitute the fully-qualified hostname (such as <emphasis role="bold">fs1.example.com</emphasis>) of the machine you are
installing. For the <replaceable>cell name</replaceable> argument substitute your cell's complete name (such as <emphasis
- role="bold">abc.com</emphasis>).</para>
+ role="bold">example.com</emphasis>).</para>
</note></para>
<indexterm>
<orderedlist>
<listitem>
- <para>Issue the <emphasis role="bold">bos setcellname</emphasis> command to set the cell name. <programlisting>
- # <emphasis role="bold">cd /usr/afs/bin</emphasis>
- # <emphasis role="bold">./bos setcellname</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>cell name</replaceable>> <emphasis
- role="bold">-noauth</emphasis>
-</programlisting></para>
+ <para>If necessary, add the directory containing the <emphasis role="bold">bos</emphasis> command to your path.
+ <programlisting>
+ # <emphasis role="bold">export PATH=$PATH:/usr/afs/bin</emphasis>
+ </programlisting>
+ </para>
+ </listitem>
- <para>Because you are not authenticated and authorization checking is disabled, the <emphasis role="bold">bos</emphasis>
- command interpreter possibly produces error messages about being unable to obtain tickets and running unauthenticated. You
- can safely ignore the messages. <indexterm>
+ <listitem>
+ <para>Issue the <emphasis role="bold">bos setcellname</emphasis> command to set the cell name. <programlisting>
+ # <emphasis role="bold">bos setcellname</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>cell name</replaceable>> <emphasis
+ role="bold">-localauth</emphasis>
+</programlisting></para> <indexterm>
<primary>commands</primary>
<secondary>bos listhosts</secondary>
<primary>displaying</primary>
<secondary>CellServDB file (server) entries</secondary>
- </indexterm></para>
+ </indexterm>
</listitem>
<listitem>
<para>Issue the <emphasis role="bold">bos listhosts</emphasis> command to verify that the machine you are installing is now
registered as the cell's first database server machine. <programlisting>
- # <emphasis role="bold">./bos listhosts</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">-noauth</emphasis>
+ # <emphasis role="bold">bos listhosts</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">-localauth</emphasis>
Cell name is <replaceable>cell_name</replaceable>
Host 1 is <replaceable>machine_name</replaceable>
</programlisting></para>
</indexterm>
<indexterm>
- <primary>Authentication Server</primary>
-
- <secondary>starting</secondary>
-
- <tertiary>first AFS machine</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>first AFS machine</primary>
-
- <secondary>Authentication Server</secondary>
- </indexterm>
-
- <indexterm>
- <primary>kaserver process</primary>
-
- <see>Authentication Server</see>
- </indexterm>
-
- <indexterm>
- <primary>starting</primary>
-
- <secondary>Authentication Server</secondary>
-
- <tertiary>first AFS machine</tertiary>
- </indexterm>
-
- <indexterm>
<primary>Backup Server</primary>
<secondary>starting</secondary>
<sect1 id="HDRWQ52">
<title>Starting the Database Server Processes</title>
- <para>Next use the <emphasis role="bold">bos create</emphasis> command to create entries for the four database server processes
- in the <emphasis role="bold">/usr/afs/local/BosConfig</emphasis> file and start them running. The four processes run on database
+ <para>Next use the <emphasis role="bold">bos create</emphasis> command to create entries for the three database server processes
+ in the <emphasis role="bold">/usr/afs/local/BosConfig</emphasis> file and start them running. The three processes run on database
server machines only: <itemizedlist>
- <listitem>
- <para>The Authentication Server (the <emphasis role="bold">kaserver</emphasis> process) maintains the Authentication
- Database</para>
- </listitem>
-
- <listitem>
- <para>The Backup Server (the <emphasis role="bold">buserver</emphasis> process) maintains the Backup Database</para>
- </listitem>
<listitem>
<para>The Protection Server (the <emphasis role="bold">ptserver</emphasis> process) maintains the Protection
<para>The Volume Location (VL) Server (the <emphasis role="bold">vlserver</emphasis> process) maintains the Volume
Location Database (VLDB)</para>
</listitem>
+
+ <listitem>
+ <para>The optional Backup Server (the <emphasis role="bold">buserver</emphasis> process) maintains the Backup Database</para>
+ </listitem>
</itemizedlist></para>
<indexterm>
</indexterm>
<note>
- <para>AFS's authentication and authorization software is based on algorithms and other procedures known as
- <emphasis>Kerberos</emphasis>, as originally developed by Project Athena at the Massachusetts Institute of Technology. Some
- cells choose to replace the AFS Authentication Server and other security-related protocols with Kerberos as obtained directly
- from Project Athena or other sources. If you wish to do this, contact the AFS Product Support group now to learn about
- necessary modifications to the installation.</para>
+ <para>AFS ships with an additional database server named 'kaserver', which
+ was historically used to provide authentication services to AFS cells.
+ kaserver was based on <emphasis>Kerberos v4</emphasis>, as such, it is
+ not recommended for new cells. This guide assumes you have already
+ configured a Kerberos v5 realm for your site, and details the procedures
+ required to use AFS with this realm. If you do wish to use
+ <emphasis role="bold">kaserver</emphasis>, please see the modifications
+ to these instructions detailed in
+ <link linkend="KAS006">Starting the kaserver Database Server Process</link>
+ </para>
</note>
<para>The remaining instructions in this chapter include the <emphasis role="bold">-cell</emphasis> argument on all applicable
<secondary>create</secondary>
</indexterm> <orderedlist>
<listitem>
- <para>Issue the <emphasis role="bold">bos create</emphasis> command to start the Authentication Server. The current
- working directory is still <emphasis role="bold">/usr/afs/bin</emphasis>. <programlisting>
- # <emphasis role="bold">./bos create</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">kaserver simple /usr/afs/bin/kaserver</emphasis> \
- <emphasis role="bold"> -cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis role="bold">-noauth</emphasis>
-</programlisting></para>
-
- <para>You can safely ignore the messages that tell you to add Kerberos to the <emphasis
- role="bold">/etc/services</emphasis> file; AFS uses a default value that makes the addition unnecessary. You can also
- ignore messages about the failure of authentication.</para>
- </listitem>
-
- <listitem>
- <para>Issue the <emphasis role="bold">bos create</emphasis> command to start the Backup Server. <programlisting>
- # <emphasis role="bold">./bos create</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">buserver simple /usr/afs/bin/buserver</emphasis> \
- <emphasis role="bold"> -cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis role="bold">-noauth</emphasis>
+ <para>Issue the <emphasis role="bold">bos create</emphasis> command to start the Protection Server. <programlisting>
+ # <emphasis role="bold">./bos create</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">ptserver simple /usr/afs/bin/ptserver</emphasis> <emphasis role="bold">-localauth</emphasis>
</programlisting></para>
</listitem>
<listitem>
- <para>Issue the <emphasis role="bold">bos create</emphasis> command to start the Protection Server. <programlisting>
- # <emphasis role="bold">./bos create</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">ptserver simple /usr/afs/bin/ptserver</emphasis> \
- <emphasis role="bold"> -cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis role="bold">-noauth</emphasis>
+ <para>Issue the <emphasis role="bold">bos create</emphasis> command to start the VL Server. <programlisting>
+ # <emphasis role="bold">./bos create</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">vlserver simple /usr/afs/bin/vlserver</emphasis> <emphasis role="bold">-localauth</emphasis>
</programlisting></para>
</listitem>
<listitem>
- <para>Issue the <emphasis role="bold">bos create</emphasis> command to start the VL Server. <programlisting>
- # <emphasis role="bold">./bos create</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">vlserver simple /usr/afs/bin/vlserver</emphasis> \
- <emphasis role="bold"> -cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis role="bold">-noauth</emphasis>
+ <para>Optionally, issue the <emphasis role="bold">bos create</emphasis> command to start the Backup Server. <programlisting>
+ # <emphasis role="bold">./bos create</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">buserver simple /usr/afs/bin/buserver</emphasis> <emphasis role="bold">-localauth</emphasis>
</programlisting></para>
</listitem>
</orderedlist></para>
</indexterm>
<indexterm>
- <primary>afs entry in Authentication Database</primary>
+ <primary>afs entry in Kerberos Database</primary>
</indexterm>
<indexterm>
- <primary>Authentication Database</primary>
+ <primary>Kerberos Database</primary>
</indexterm>
<indexterm>
<primary>creating</primary>
- <secondary>afs entry in Authentication Database</secondary>
+ <secondary>afs entry in Kerberos Database</secondary>
</indexterm>
<indexterm>
<primary>creating</primary>
- <secondary>admin account in Authentication Database</secondary>
+ <secondary>admin account in Kerberos Database</secondary>
</indexterm>
<indexterm>
</sect1>
<sect1 id="HDRWQ53">
- <title>Initializing Cell Security</title>
+ <title>Initializing Cell Security </title>
- <para>Now initialize the cell's security mechanisms. Begin by creating the following two initial entries in the Authentication
- Database: <itemizedlist>
+ <para>If you are working with an existing cell which uses
+ <emphasis role="bold">kaserver</emphasis> or Kerberos v4 for authentication,
+ please see
+ <link linkend="HDRWQ53">Initializing Cell Security with kaserver</link>
+ for installation instructions which replace this section.</para>
+
+ <para>Now finish initializing the cell's security mechanisms. Begin by creating the following entry in your site's Kerberos database: <itemizedlist>
<listitem>
<para>A generic administrative account, called <emphasis role="bold">admin</emphasis> by convention. If you choose to
assign a different name, substitute it throughout the remainder of this document.</para>
latter scheme implies somewhat more overhead, but provides a more informative audit trail for administrative
operations.</para>
</listitem>
-
- <listitem>
- <para>The entry for AFS server processes, called <emphasis role="bold">afs</emphasis>. No user logs in under this
- identity, but the Authentication Server's Ticket Granting Service (TGS) module uses the associated key to encrypt the
- server tickets that it grants to AFS clients for presentation to server processes during mutual authentication. (The
- chapter in the <emphasis>IBM AFS Administration Guide</emphasis> about cell configuration and administration describes the
- role of server encryption keys in mutual authentication.)</para>
-
- <para>In Step <link linkend="LIWQ58">7</link>, you also place the initial AFS server encryption key into the <emphasis
- role="bold">/usr/afs/etc/KeyFile</emphasis> file. The AFS server processes refer to this file to learn the server
- encryption key when they need to decrypt server tickets.</para>
- </listitem>
</itemizedlist></para>
<para>You also issue several commands that enable the new <emphasis role="bold">admin</emphasis> user to issue privileged
commands in all of the AFS suites.</para>
<para>The following instructions do not configure all of the security mechanisms related to the AFS Backup System. See the
- chapter in the <emphasis>IBM AFS Administration Guide</emphasis> about configuring the Backup System. <orderedlist>
- <indexterm>
- <primary>commands</primary>
-
- <secondary>kas (interactive)</secondary>
- </indexterm>
-
- <indexterm>
- <primary>kas commands</primary>
-
- <secondary>interactive mode, entering</secondary>
- </indexterm>
-
- <indexterm>
- <primary>interactive mode for kas</primary>
+ chapter in the <emphasis>OpenAFS Administration Guide</emphasis> about configuring the Backup System.</para>
- <secondary>entering</secondary>
- </indexterm>
+ <para>The examples below assume you are using MIT Kerberos. Please refer
+ to the documentation for your KDC's administrative interface if you are
+ using a different vendor</para>
+ <orderedlist>
<listitem>
- <para>Enter <emphasis role="bold">kas</emphasis> interactive mode. Because the machine is in no-authorization checking
- mode, include the <emphasis role="bold">-noauth</emphasis> flag to suppress the Authentication Server's usual prompt for a
- password. <programlisting>
- # <emphasis role="bold">kas -cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis role="bold">-noauth</emphasis>
- ka>
-</programlisting> <indexterm>
- <primary>commands</primary>
-
- <secondary>kas create</secondary>
- </indexterm> <indexterm>
- <primary>kas commands</primary>
-
- <secondary>create</secondary>
- </indexterm> <indexterm>
- <primary>server encryption key</primary>
-
- <secondary>in Authentication Database</secondary>
- </indexterm> <indexterm>
- <primary>creating</primary>
-
- <secondary>server encryption key</secondary>
-
- <tertiary>Authentication Database</tertiary>
- </indexterm></para>
+ <para>Enter <emphasis role="bold">kadmin</emphasis> interactive mode.
+<programlisting>
+ # <emphasis role="bold">kadmin</emphasis>
+Authenticating as principal <replaceable>you</replaceable>/admin@<replaceable>YOUR REALM</replaceable> with password
+Password for <replaceable>you/admin@REALM</replaceable>: <replaceable>your_password</replaceable>
+</programlisting> </para>
</listitem>
<listitem>
- <para><anchor id="LIWQ54" />Issue the <emphasis role="bold">kas create</emphasis> command to create Authentication
- Database entries called <emphasis role="bold">admin</emphasis> and <emphasis role="bold">afs</emphasis>.</para>
-
- <para>Do not provide passwords on the command line. Instead provide them as <replaceable>afs_passwd</replaceable> and
- <replaceable>admin_passwd</replaceable> in response to the <emphasis role="bold">kas</emphasis> command interpreter's
- prompts as shown, so that they do not appear on the standard output stream.</para>
+ <para>Issue the
+ <emphasis role="bold">add_principal</emphasis> command to create
+ the Kerberos Database entry for
+ <emphasis role="bold">admin</emphasis>.</para>
- <para>You need to enter the <replaceable>afs_passwd</replaceable> string only in this step and in Step <link
- linkend="LIWQ58">7</link>, so provide a value that is as long and complex as possible, preferably including numerals,
- punctuation characters, and both uppercase and lowercase letters. Also make the <replaceable>admin_passwd</replaceable> as
- long and complex as possible, but keep in mind that administrators need to enter it often. Both passwords must be at least
- six characters long.</para>
-
- <programlisting>
- ka> <emphasis role="bold">create afs</emphasis>
- initial_password: <replaceable>afs_passwd</replaceable>
- Verifying, please re-enter initial_password: <replaceable>afs_passwd</replaceable>
- ka> <emphasis role="bold">create admin</emphasis>
- initial_password: <replaceable>admin_passwd</replaceable>
- Verifying, please re-enter initial_password: <replaceable>admin_passwd</replaceable>
+ <para>You should make the <replaceable>admin_passwd</replaceable> as
+ long and complex as possible, but keep in mind that administrators
+ need to enter it often. It must be at least six characters long.
+<programlisting>
+ kadmin: <emphasis role="bold">add_principal admin</emphasis>
+ Enter password for principal "admin@<replaceable>REALM</replaceable>": <emphasis role="bold"><replaceable>admin_password</replaceable></emphasis>
+ Principal "admin@<replaceable>REALM</replaceable>" created.
</programlisting>
-
- <indexterm>
- <primary>commands</primary>
-
- <secondary>kas examine</secondary>
- </indexterm>
-
- <indexterm>
- <primary>kas commands</primary>
-
- <secondary>examine</secondary>
- </indexterm>
+ </para>
<indexterm>
<primary>displaying</primary>
</listitem>
<listitem>
- <para><anchor id="LIWQ55" />Issue the <emphasis role="bold">kas examine</emphasis> command to display the <emphasis
- role="bold">afs</emphasis> entry. The output includes a checksum generated by encrypting a constant with the server
- encryption key derived from the <replaceable>afs_passwd</replaceable> string. In Step <link linkend="LIWQ59">8</link> you
- issue the <emphasis role="bold">bos listkeys</emphasis> command to verify that the checksum in its output matches the
- checksum in this output. <programlisting>
- ka> <emphasis role="bold">examine afs</emphasis>
- User data for afs
- key (0) cksum is <replaceable>checksum</replaceable> . . .
-</programlisting> <indexterm>
- <primary>commands</primary>
-
- <secondary>kas setfields</secondary>
- </indexterm> <indexterm>
- <primary>kas commands</primary>
-
- <secondary>setfields</secondary>
- </indexterm> <indexterm>
- <primary>admin account</primary>
-
- <secondary>setting ADMIN flag on Auth. DB entry</secondary>
- </indexterm></para>
- </listitem>
-
- <listitem>
- <para><anchor id="LIWQ56" />Issue the <emphasis role="bold">kas setfields</emphasis> command to turn on the
- <computeroutput>ADMIN</computeroutput> flag in the <emphasis role="bold">admin</emphasis> entry. This enables the
- <emphasis role="bold">admin</emphasis> user to issue privileged <emphasis role="bold">kas</emphasis> commands. Then issue
- the <emphasis role="bold">kas examine</emphasis> command to verify that the <computeroutput>ADMIN</computeroutput> flag
- appears in parentheses on the first line of the output, as shown in the example. <programlisting>
- ka> <emphasis role="bold">setfields admin -flags admin</emphasis>
- ka> <emphasis role="bold">examine admin</emphasis>
- User data for admin (ADMIN) . . .
-</programlisting> <indexterm>
- <primary>commands</primary>
-
- <secondary>kas quit</secondary>
- </indexterm> <indexterm>
- <primary>kas commands</primary>
-
- <secondary>quit</secondary>
- </indexterm> <indexterm>
- <primary>interactive mode for kas</primary>
-
- <secondary>quitting</secondary>
- </indexterm></para>
- </listitem>
-
- <listitem>
- <para>Issue the <emphasis role="bold">kas quit</emphasis> command to leave <emphasis role="bold">kas</emphasis>
+ <para>Issue the <emphasis role="bold">quit</emphasis> command to leave <emphasis role="bold">kadmin</emphasis>
interactive mode. <programlisting>
- ka> <emphasis role="bold">quit</emphasis>
+ kadmin: <emphasis role="bold">quit</emphasis>
</programlisting> <indexterm>
<primary>commands</primary>
</indexterm></para>
</listitem>
- <listitem>
- <para><anchor id="LIWQ57" />Issue the <emphasis role="bold">bos adduser</emphasis> command to add the <emphasis
+ <listitem id="LIWQ57">
+ <para>Issue the <emphasis role="bold">bos adduser</emphasis> command to add the <emphasis
role="bold">admin</emphasis> user to the <emphasis role="bold">/usr/afs/etc/UserList</emphasis> file. This enables the
<emphasis role="bold">admin</emphasis> user to issue privileged <emphasis role="bold">bos</emphasis> and <emphasis
role="bold">vos</emphasis> commands. <programlisting>
- # <emphasis role="bold">./bos adduser</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">admin -cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis
- role="bold">-noauth</emphasis>
-</programlisting> <indexterm>
- <primary>commands</primary>
-
- <secondary>bos addkey</secondary>
- </indexterm> <indexterm>
- <primary>bos commands</primary>
-
- <secondary>addkey</secondary>
- </indexterm> <indexterm>
- <primary>creating</primary>
-
- <secondary>server encryption key</secondary>
-
- <tertiary>KeyFile file</tertiary>
- </indexterm> <indexterm>
- <primary>server encryption key</primary>
-
- <secondary>in KeyFile file</secondary>
- </indexterm></para>
- </listitem>
-
- <listitem>
- <para><anchor id="LIWQ58" />Issue the <emphasis role="bold">bos addkey</emphasis> command to define the AFS server
- encryption key in the <emphasis role="bold">/usr/afs/etc/KeyFile</emphasis> file.</para>
-
- <para>Do not provide the password on the command line. Instead provide it as <replaceable>afs_passwd</replaceable> in
- response to the <emphasis role="bold">bos</emphasis> command interpreter's prompts, as shown. Provide the same string as
- in Step <link linkend="LIWQ54">2</link>.</para>
-
- <programlisting>
- # <emphasis role="bold">./bos addkey</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">-kvno 0 -cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis
- role="bold">-noauth</emphasis>
- Input key: <replaceable>afs_passwd</replaceable>
- Retype input key: <replaceable>afs_passwd</replaceable>
-</programlisting>
-
- <indexterm>
- <primary>commands</primary>
-
- <secondary>bos listkeys</secondary>
- </indexterm>
-
- <indexterm>
- <primary>bos commands</primary>
-
- <secondary>listkeys</secondary>
- </indexterm>
-
- <indexterm>
- <primary>displaying</primary>
-
- <secondary>server encryption key</secondary>
-
- <tertiary>KeyFile file</tertiary>
- </indexterm>
- </listitem>
-
- <listitem>
- <para><anchor id="LIWQ59" />Issue the <emphasis role="bold">bos listkeys</emphasis> command to verify that the checksum
- for the new key in the <emphasis role="bold">KeyFile</emphasis> file is the same as the checksum for the key in the
- Authentication Database's <emphasis role="bold">afs</emphasis> entry, which you displayed in Step <link
- linkend="LIWQ55">3</link>. <programlisting>
- # <emphasis role="bold">./bos listkeys</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">-cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis
- role="bold">-noauth</emphasis>
- key 0 has cksum <replaceable>checksum</replaceable>
-</programlisting></para>
-
- <para>You can safely ignore any error messages indicating that <emphasis role="bold">bos</emphasis> failed to get tickets
- or that authentication failed.</para>
-
- <para>If the keys are different, issue the following commands, making sure that the <replaceable>afs_passwd</replaceable>
- string is the same in each case. The <replaceable>checksum</replaceable> strings reported by the <emphasis role="bold">kas
- examine</emphasis> and <emphasis role="bold">bos listkeys</emphasis> commands must match; if they do not, repeat these
- instructions until they do, using the <emphasis role="bold">-kvno</emphasis> argument to increment the key version number
- each time.</para>
-
- <programlisting>
- # <emphasis role="bold">./kas -cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis role="bold">-noauth</emphasis>
- ka> <emphasis role="bold">setpassword afs -kvno 1</emphasis>
- new_password: <replaceable>afs_passwd</replaceable>
- Verifying, please re-enter initial_password: <replaceable>afs_passwd</replaceable>
- ka> <emphasis role="bold">examine afs</emphasis>
- User data for afs
- key (1) cksum is <replaceable>checksum</replaceable> . . .
- ka> <emphasis role="bold">quit</emphasis>
- # <emphasis role="bold">./bos addkey</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">-kvno 1 -cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis
- role="bold">-noauth</emphasis>
- Input key: <replaceable>afs_passwd</replaceable>
- Retype input key: <replaceable>afs_passwd</replaceable>
- # <emphasis role="bold">./bos listkeys</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">-cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis
- role="bold">-noauth</emphasis>
- key 1 has cksum <replaceable>checksum</replaceable>
-</programlisting>
-
+ # <emphasis role="bold">./bos adduser</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">admin -localauth</emphasis>
+</programlisting>
+ <indexterm>
+ <primary>commands</primary>
+ <secondary>asetkey</secondary>
+ </indexterm>
+ <indexterm>
+ <primary>creating</primary>
+ <secondary>server encryption key</secondary>
+ <tertiary>KeyFile file</tertiary>
+ </indexterm>
+ <indexterm>
+ <primary>server encryption key</primary>
+ <secondary>in KeyFile file</secondary>
+ </indexterm></para>
+ </listitem>
+ </orderedlist>
+ </sect1>
+ <sect1 id="HDRWQ53a">
+ <title>Initializing the Protection Database</title>
+
+ <para>Now continue to configure your cell's security systems by
+ populating the Protection Database with the newly created
+ <emphasis role="bold">admin</emphasis> user, and permitting it
+ to issue priviledged commands on the AFS filesystem.
+ There is nothing special about the name "admin"; it is just a
+ convenient name for these instructions. An other name could
+ be used throughout this document, or multiple privileged
+ accounts created.</para>
+
+ <orderedlist>
+ <listitem>
+ <para>Issue the <emphasis role="bold">pts createuser</emphasis> command to create a Protection Database entry for the
+ <emphasis role="bold">admin</emphasis> user.
<indexterm>
<primary>commands</primary>
-
<secondary>pts createuser</secondary>
</indexterm>
<indexterm>
<primary>pts commands</primary>
-
<secondary>createuser</secondary>
</indexterm>
<indexterm>
<primary>Protection Database</primary>
- </indexterm>
- </listitem>
-
- <listitem>
- <para>Issue the <emphasis role="bold">pts createuser</emphasis> command to create a Protection Database entry for the
- <emphasis role="bold">admin</emphasis> user.</para>
+ </indexterm></para>
<para>By default, the Protection Server assigns AFS UID 1 (one) to the <emphasis role="bold">admin</emphasis> user,
because it is the first user entry you are creating. If the local password file (<emphasis
to accept the default.</para>
<programlisting>
- # <emphasis role="bold">./pts createuser -name admin -cell</emphasis> <<replaceable>cell name</replaceable>> [<emphasis
- role="bold">-id</emphasis> <<replaceable>AFS UID</replaceable>>] <emphasis role="bold">-noauth</emphasis>
+ # <emphasis role="bold">pts createuser -name admin</emphasis> [<emphasis
+ role="bold">-id</emphasis> <<replaceable>AFS UID</replaceable>>] <emphasis role="bold">-localauth</emphasis>
User admin has id <replaceable>AFS UID</replaceable>
</programlisting>
<indexterm>
<primary>commands</primary>
-
<secondary>pts adduser</secondary>
</indexterm>
<indexterm>
<primary>pts commands</primary>
-
<secondary>adduser</secondary>
</indexterm>
<indexterm>
<primary>admin account</primary>
-
<secondary>adding</secondary>
-
<tertiary>to system:administrators group</tertiary>
</indexterm>
</listitem>
membership</emphasis> command to verify the new membership. Membership in the group enables the <emphasis
role="bold">admin</emphasis> user to issue privileged <emphasis role="bold">pts</emphasis> commands and some privileged
<emphasis role="bold">fs</emphasis> commands. <programlisting>
- # <emphasis role="bold">./pts adduser admin system:administrators -cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis
- role="bold">-noauth</emphasis>
- # <emphasis role="bold">./pts membership admin -cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis
- role="bold">-noauth</emphasis>
+ # <emphasis role="bold">./pts adduser admin system:administrators</emphasis> <emphasis role="bold">-localauth</emphasis>
+ # <emphasis role="bold">./pts membership admin</emphasis> <emphasis role="bold">-localauth</emphasis>
Groups admin (id: 1) is a member of:
system:administrators
</programlisting> <indexterm>
<primary>commands</primary>
-
<secondary>bos restart</secondary>
-
<tertiary>on first AFS machine</tertiary>
</indexterm> <indexterm>
<primary>bos commands</primary>
-
<secondary>restart</secondary>
-
<tertiary>on first AFS machine</tertiary>
</indexterm> <indexterm>
<primary>restarting server process</primary>
-
<secondary>on first AFS machine</secondary>
</indexterm> <indexterm>
<primary>server process</primary>
-
<secondary>restarting</secondary>
-
<tertiary>on first AFS machine</tertiary>
</indexterm></para>
</listitem>
-
- <listitem>
- <para>Issue the <emphasis role="bold">bos restart</emphasis> command with the <emphasis role="bold">-all</emphasis> flag
- to restart the database server processes, so that they start using the new server encryption key. <programlisting>
- # <emphasis role="bold">./bos restart</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">-all -cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis
- role="bold">-noauth</emphasis>
-</programlisting></para>
- </listitem>
- </orderedlist></para>
+ </orderedlist>
<indexterm>
<primary>File Server</primary>
</sect1>
<sect1 id="HDRWQ60">
- <title>Starting the File Server, Volume Server, and Salvager</title>
-
- <para>Start the <emphasis role="bold">fs</emphasis> process, which consists of the File Server, Volume Server, and Salvager
- (<emphasis role="bold">fileserver</emphasis>, <emphasis role="bold">volserver</emphasis> and <emphasis
- role="bold">salvager</emphasis> processes). <orderedlist>
- <listitem>
- <para>Issue the <emphasis role="bold">bos create</emphasis> command to start the <emphasis role="bold">fs</emphasis>
- process. The command appears here on multiple lines only for legibility. <programlisting>
- # <emphasis role="bold">./bos create</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">fs fs /usr/afs/bin/fileserver</emphasis> \
- <emphasis role="bold">/usr/afs/bin/volserver /usr/afs/bin/salvager</emphasis> \
- <emphasis role="bold">-cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis role="bold">-noauth</emphasis>
-</programlisting></para>
+ <title>Starting the File Server processes</title>
+
+ <para>Start the
+ <emphasis role="bold">dafs</emphasis> process.
+ The <emphasis role="bold">dafs</emphasis> process consists of the
+ Demand-Attach File Server, Volume Server, Salvage Server, and Salvager (<emphasis role="bold">dafileserver</emphasis>,
+ <emphasis role="bold"> davolserver</emphasis>, <emphasis role="bold">salvageserver</emphasis>, and <emphasis
+ role="bold">dasalvager</emphasis> processes). Most sites should run the
+ Demand-Attach File Server, but the traditional/legacy File Server remains
+ an option. If you are uncertain whether to run the legacy File Server,
+ see <link linkend="DAFS">Appendix C, The Demand-Attach File Server</link>.
+ <orderedlist>
+ <listitem>
+ <para>Issue the <emphasis role="bold">bos create</emphasis> command to start the
+ <emphasis role="bold">dafs</emphasis> process. The commands appear here on multiple lines only for legibility.
+
+ <itemizedlist>
+ <listitem>
+ <para>Create the <emphasis
+ role="bold">dafs</emphasis> process:
+ <programlisting>
+ # <emphasis role="bold">./bos create</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">dafs dafs /usr/afs/bin/dafileserver</emphasis> \
+ <emphasis role="bold">/usr/afs/bin/davolserver /usr/afs/bin/salvageserver</emphasis> \
+ <emphasis role="bold">/usr/afs/bin/dasalvager</emphasis> <emphasis role="bold">-localauth</emphasis>
+</programlisting></para>
+ </listitem>
+ </itemizedlist>
+ </para>
<para>Sometimes a message about Volume Location Database (VLDB) initialization appears, along with one or more instances
of an error message similar to the following:</para>
<secondary>status</secondary>
</indexterm></para>
- <para>You can verify that the <emphasis role="bold">fs</emphasis> process has started successfully by issuing the
- <emphasis role="bold">bos status</emphasis> command. Its output mentions two <computeroutput>proc
+ <para>You can verify that the <emphasis role="bold">dafs</emphasis> process has started
+ successfully by issuing the <emphasis role="bold">bos status</emphasis> command. Its output mentions two <computeroutput>proc
starts</computeroutput>.</para>
+ <para>
<programlisting>
- # <emphasis role="bold">./bos status</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">fs -long -noauth</emphasis>
-</programlisting>
+ # <emphasis role="bold">./bos status</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">dafs -long -localauth</emphasis>
+</programlisting></para>
</listitem>
<listitem>
<programlisting>
# <emphasis role="bold">./vos create</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>partition name</replaceable>> <emphasis
role="bold">root.afs</emphasis> \
- <emphasis role="bold">-cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis role="bold">-noauth</emphasis>
+ <emphasis role="bold">-localauth</emphasis>
</programlisting>
- <para>The Volume Server produces a message confirming that it created the volume on the specified partition. You can
- ignore error messages indicating that tokens are missing, or that authentication failed. <indexterm>
+ <para>The Volume Server produces a message confirming that it created the volume on the specified partition. <indexterm>
<primary>commands</primary>
<secondary>vos syncvldb</secondary>
<secondary>syncserv</secondary>
</indexterm></para>
</listitem>
-
- <listitem>
- <para>If there are existing AFS file server machines and volumes in the cell, issue the <emphasis role="bold">vos
- syncvldb</emphasis> and <emphasis role="bold">vos syncserv</emphasis> commands to synchronize the VLDB with the
- actual state of volumes on the local machine. To follow the progress of the synchronization operation, which can
- take several minutes, use the <emphasis role="bold">-verbose</emphasis> flag. <programlisting>
- # <emphasis role="bold">./vos syncvldb</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">-cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis
- role="bold">-verbose -noauth</emphasis>
- # <emphasis role="bold">./vos syncserv</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">-cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis
- role="bold">-verbose -noauth</emphasis>
-</programlisting></para>
-
- <para>You can ignore error messages indicating that tokens are missing, or that authentication failed.</para>
- </listitem>
</itemizedlist></para>
</listitem>
</orderedlist></para>
</indexterm>
</sect1>
- <sect1 id="HDRWQ61">
- <title>Starting the Server Portion of the Update Server</title>
-
- <para>Start the server portion of the Update Server (the <emphasis role="bold">upserver</emphasis> process), to distribute the
- contents of directories on this machine to other server machines in the cell. It becomes active when you configure the client
- portion of the Update Server on additional server machines.</para>
-
- <para>Distributing the contents of its <emphasis role="bold">/usr/afs/etc</emphasis> directory makes this machine the cell's
- <emphasis>system control machine</emphasis>. The other server machines in the cell run the <emphasis
- role="bold">upclientetc</emphasis> process (an instance of the client portion of the Update Server) to retrieve the
- configuration files. Use the <emphasis role="bold">-crypt</emphasis> argument to the <emphasis role="bold">upserver</emphasis>
- initialization command to specify that the Update Server distributes the contents of the <emphasis
- role="bold">/usr/afs/etc</emphasis> directory only in encrypted form, as shown in the following instruction. Several of the
- files in the directory, particularly the <emphasis role="bold">KeyFile</emphasis> file, are crucial to cell security and so must
- never cross the network unencrypted.</para>
-
- <para>(You can choose not to configure a system control machine, in which case you must update the configuration files in each
- server machine's <emphasis role="bold">/usr/afs/etc</emphasis> directory individually. The <emphasis role="bold">bos</emphasis>
- commands used for this purpose also encrypt data before sending it across the network.)</para>
-
- <para>Distributing the contents of its <emphasis role="bold">/usr/afs/bin</emphasis> directory to other server machines of its
- system type makes this machine a <emphasis>binary distribution machine</emphasis>. The other server machines of its system type
- run the <emphasis role="bold">upclientbin</emphasis> process (an instance of the client portion of the Update Server) to
- retrieve the binaries.</para>
-
- <para>The binaries in the <emphasis role="bold">/usr/afs/bin</emphasis> directory are not sensitive, so it is not necessary to
- encrypt them before transfer across the network. Include the <emphasis role="bold">-clear</emphasis> argument to the <emphasis
- role="bold">upserver</emphasis> initialization command to specify that the Update Server distributes the contents of the
- <emphasis role="bold">/usr/afs/bin</emphasis> directory in unencrypted form unless an <emphasis
- role="bold">upclientbin</emphasis> process requests encrypted transfer.</para>
-
- <para>Note that the server and client portions of the Update Server always mutually authenticate with one another, regardless of
- whether you use the <emphasis role="bold">-clear</emphasis> or <emphasis role="bold">-crypt</emphasis> arguments. This protects
- their communications from eavesdropping to some degree.</para>
-
- <para>For more information on the <emphasis role="bold">upclient</emphasis> and <emphasis role="bold">upserver</emphasis>
- processes, see their reference pages in the <emphasis>IBM AFS Administration Reference</emphasis>. The commands appear on
- multiple lines here only for legibility. <orderedlist>
- <listitem>
- <para>Issue the <emphasis role="bold">bos create</emphasis> command to start the <emphasis role="bold">upserver</emphasis>
- process. <programlisting>
- # <emphasis role="bold">./bos create</emphasis> <<replaceable>machine name></replaceable> <emphasis role="bold">upserver simple</emphasis> \
- <emphasis role="bold">"/usr/afs/bin/upserver -crypt /usr/afs/etc</emphasis> \
- <emphasis role="bold">-clear /usr/afs/bin" -cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis
- role="bold">-noauth</emphasis>
-</programlisting></para>
- </listitem>
- </orderedlist></para>
-
- <indexterm>
- <primary>runntp process</primary>
-
- <secondary>first AFS machine</secondary>
- </indexterm>
-
- <indexterm>
- <primary>starting</primary>
-
- <secondary>runntp process</secondary>
-
- <tertiary>first AFS machine</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>first AFS machine</primary>
-
- <secondary>runntp process</secondary>
- </indexterm>
-
- <indexterm>
- <primary>NTPD</primary>
-
- <secondary>first AFS machine</secondary>
- </indexterm>
-
- <indexterm>
- <primary>time synchronization</primary>
- </indexterm>
-
- <indexterm>
- <primary>clock synchronization</primary>
- </indexterm>
- </sect1>
-
<sect1 id="HDRWQ62">
- <title>Starting the Controller for NTPD</title>
+ <title>Clock Sync Considerations</title>
<para>Keeping the clocks on all server and client machines in your cell synchronized is crucial to several functions, and in
- particular to the correct operation of AFS's distributed database technology, Ubik. The chapter in the <emphasis>IBM AFS
+ particular to the correct operation of AFS's distributed database technology, Ubik. The chapter in the <emphasis>OpenAFS
Administration Guide</emphasis> about administering server machines explains how time skew can disturb Ubik's performance and
cause service outages in your cell.</para>
- <para>The AFS distribution includes a version of the Network Time Protocol Daemon (NTPD) for synchronizing the clocks on server
- machines. If a time synchronization program is not already running on the machine, then in this section you start the <emphasis
- role="bold">runntp</emphasis> process to configure NTPD for use with AFS.</para>
-
- <note>
- <para>Do not run the <emphasis role="bold">runntp</emphasis> process if NTPD or another time synchronization protocol is
- already running on the machine. Some versions of some operating systems run a time synchronization program by default, as
- detailed in the <emphasis>IBM AFS Release Notes</emphasis>.</para>
-
- <para>Attempting to run multiple instances of the NTPD causes an error. Running NTPD together with another time
- synchronization protocol is unnecessary and can cause instability in the clock setting.</para>
- </note>
-
- <para>If you run the <emphasis role="bold">runntp</emphasis> process and your cell has reliable network connectivity to machines
- outside your cell, then it is conventional to configure the first AFS machine to refer to a time source outside the cell. When
- you later install the <emphasis role="bold">runntp</emphasis> program on other server machines in the cell, it configures NTPD
- to choose a time source at random from among the database server machines listed in the <emphasis
- role="bold">/usr/afs/etc/CellServDB</emphasis> file. Time synchronization therefore works in a chained manner: this database
- server machine refers to a time source outside the cell, the database server machines refer to the machine among them that has
- access to the most accurate time (NTPD itself includes code for determining this), and each non-database server machine refers
- to a local database server machine chosen at random from the <emphasis role="bold">/usr/afs/etc/CellServDB</emphasis> file. If
- you ever decide to remove database server functionality from this machine, it is best to transfer responsibility for consulting
- an external time source to a remaining database server machine.</para>
-
- <para>If your cell does not have network connectivity to external machines, or if the connectivity is not reliable, include the
- <emphasis role="bold">-localclock</emphasis> flag to the <emphasis role="bold">runntp</emphasis> command as indicated in the
- following instructions. The flag tells NTPD to rely on the machine's internal clock when all external time sources are
- inaccessible. The <emphasis role="bold">runntp</emphasis> command has other arguments that are possibly useful given your cell
- configuration; see the <emphasis>IBM AFS Administration Reference</emphasis>.</para>
-
- <para>Choosing an appropriate external time source is important, but involves more considerations than can be discussed here. If
- you need help in selecting a source, contact the AFS Product Support group.</para>
-
- <para>As the <emphasis role="bold">runntp</emphasis> process initializes NTPD, trace messages sometimes appear on the standard
- output stream. You can ignore them, but they can be informative if you understand how NTPD works. <orderedlist>
- <listitem>
- <para>Issue the <emphasis role="bold">bos create</emphasis> command to start the <emphasis role="bold">runntp</emphasis>
- process. For the <replaceable>host</replaceable> argument, substitute the fully-qualified hostname or IP address of one or
- more machines outside the cell that are to serve as time sources. Separate each name with a space. <itemizedlist>
- <listitem>
- <para>If your cell usually has reliable network connectivity to an external time source, use the following command:
- <programlisting>
- # <emphasis role="bold">./bos create</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">runntp simple</emphasis> \
- <emphasis role="bold">"/usr/afs/bin/runntp</emphasis> <<replaceable>host</replaceable>>+<emphasis role="bold">" -cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis
- role="bold">-noauth</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>If your cell does not have network connectivity to an external time source, use the following command:
- <programlisting>
- # <emphasis role="bold">./bos create</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">runntp simple</emphasis> \
- <emphasis role="bold">"/usr/afs/bin/runntp -localclock"</emphasis> <emphasis role="bold">-cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis
- role="bold">-noauth</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>If your cell has network connectivity to an external time source, but the network connection is frequently
- interrupted, use the following command: <programlisting>
- # <emphasis role="bold">./bos create</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">runntp simple</emphasis> \
- <emphasis role="bold">"/usr/afs/bin/runntp -localclock</emphasis> <<replaceable>host</replaceable>>+<emphasis
- role="bold">"</emphasis> \
- <emphasis role="bold">-cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis role="bold">-noauth</emphasis>
-</programlisting></para>
- </listitem>
- </itemizedlist></para>
- </listitem>
- </orderedlist></para>
+ <para>You should install and configure your time service independently of
+ AFS. Your Kerberos realm will also require a reliable time source, so your site
+ may already have one available.</para>
<indexterm>
<primary>overview</primary>
<sect1 id="HDRWQ63">
<title>Overview: Installing Client Functionality</title>
- <para>The machine you are installing is now an AFS file server machine, database server machine, system control machine, and
- binary distribution machine. Now make it a client machine by completing the following tasks: <orderedlist>
+ <para>The machine you are installing is now an AFS file server machine
+ and database server machine.
+ Now make it a client machine by completing the following tasks:
+ <orderedlist>
<listitem>
<para>Define the machine's cell membership for client processes</para>
</listitem>
</orderedlist></para>
<indexterm>
- <primary>CD-ROM</primary>
+ <primary>Distribution</primary>
<secondary>copying client files from</secondary>
<sect1 id="HDRWQ64">
<title>Copying Client Files to the Local Disk</title>
- <para>Before installing and configuring the AFS client, copy the necessary files from the AFS CD-ROM to the local <emphasis
+ <para>You need only undertake the steps in this section, if you are using
+ a tar file distribution, or one built from scratch. Packaged distributions,
+ such as RPMs or DEBs will already have installed the necessary files in
+ the correct locations.</para>
+
+ <para>Before installing and configuring the AFS client, copy the necessary files from the tarball to the local <emphasis
role="bold">/usr/vice/etc</emphasis> directory. <orderedlist>
<listitem>
- <para>On the local <emphasis role="bold">/cdrom</emphasis> directory, mount the AFS CD-ROM for this machine's system type,
- if it is not already. For instructions on mounting CD-ROMs (either locally or remotely via NFS), consult the operating
- system documentation.</para>
+ <para>If you have not already done so, unpack the distribution
+ tarball for this machine's system type into a suitable location on
+ the filesystem, such as <emphasis role="bold">/tmp/afsdist</emphasis>.
+ If you use a different location, substitue that in the examples that
+ follow.</para>
</listitem>
<listitem>
role="bold">cp</emphasis> command.</para>
<programlisting>
- # <emphasis role="bold">cd /cdrom/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/root.client/usr/vice/etc</emphasis>
+ # <emphasis role="bold">cd /tmp/afsdist/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/root.client/usr/vice/etc</emphasis>
# <emphasis role="bold">cp -p * /usr/vice/etc</emphasis>
# <emphasis role="bold">cp -rp C /usr/vice/etc</emphasis>
</programlisting>
<para>Among other functions, the <emphasis role="bold">ThisCell</emphasis> file on a client machine determines the following:
<itemizedlist>
<listitem>
- <para>The cell in which users authenticate when they log onto the machine, assuming it is using an AFS-modified login
- utility</para>
+ <para>The cell in which users gain tokens when they log onto the
+ machine, assuming it is using an AFS-modified login utility</para>
</listitem>
<listitem>
- <para>The cell in which users authenticate by default when they issue the <emphasis role="bold">klog</emphasis>
- command</para>
+ <para>The cell in which users gain tokens by default when they issue
+ the <emphasis role="bold">aklog</emphasis> command</para>
</listitem>
<listitem>
- <para>The cell membership of the AFS server processes that the AFS command interpreters on this machine contact by
- default</para>
+ <para>The cell membership of the AFS server processes that the AFS
+ command interpreters on this machine contact by default</para>
</listitem>
- </itemizedlist> <orderedlist>
+ </itemizedlist>
+ <orderedlist>
<listitem>
<para>Change to the <emphasis role="bold">/usr/vice/etc</emphasis> directory and remove the symbolic link created in <link
linkend="HDRWQ50">Starting the BOS Server</link>. <programlisting>
<para>The <emphasis role="bold">/usr/vice/etc/CellServDB</emphasis> file on a client machine's local disk lists the database
server machines for each cell that the local Cache Manager can contact. If there is no entry in the file for a cell, or if the
list of database server machines is wrong, then users working on this machine cannot access the cell. The chapter in the
- <emphasis>IBM AFS Administration Guide</emphasis> about administering client machines explains how to maintain the file after
+ <emphasis>OpenAFS Administration Guide</emphasis> about administering client machines explains how to maintain the file after
creating it.</para>
<para>As the <emphasis role="bold">afsd</emphasis> program initializes the Cache Manager, it copies the contents of the
<emphasis role="bold">CellServDB</emphasis> file into kernel memory. The Cache Manager always consults the list in kernel memory
rather than the <emphasis role="bold">CellServDB</emphasis> file itself. Between reboots of the machine, you can use the
<emphasis role="bold">fs newcell</emphasis> command to update the list in kernel memory directly; see the chapter in the
- <emphasis>IBM AFS Administration Guide</emphasis> about administering client machines.</para>
-
- <para>The AFS distribution includes the file <emphasis role="bold">CellServDB.sample</emphasis>, and you have already copied it
- to the <emphasis role="bold">/usr/vice/etc</emphasis> directory. It includes an entry for all AFS cells that agreed to share
- their database server machine information at the time your AFS CD-ROM was created. The AFS Product Support group also maintains
- a copy of the file, updating it as necessary. If you are interested in participating in the global AFS namespace, it is a good
- policy to consult the file occasionally for updates. Ask the AFS Product Support group for a pointer to its location.</para>
-
- <para>The <emphasis role="bold">CellServDB.sample</emphasis> file can be a good basis for the client <emphasis
- role="bold">CellServDB</emphasis> file, because all of the entries in it use the correct format. You can add or remove cell
- entries as you see fit. Later (in <link linkend="HDRWQ91">Enabling Access to Foreign Cells</link>) you perform additional steps
- that enable the Cache Manager actually to reach the cells.</para>
+ <emphasis>OpenAFS Administration Guide</emphasis> about administering client machines.</para>
+
+ <para>The AFS distribution includes the file
+ <emphasis role="bold">CellServDB.dist</emphasis>. It includes an entry for
+ all AFS cells that agreed to share their database server machine
+ information at the time the distribution was
+ created. The definitive copy of this file is maintained at
+ grand.central.org, and updates may be obtained from
+ /afs/grand.central.org/service/CellServDB or
+ <ulink url="http://grand.central.org/dl/cellservdb/CellServDB">
+ http://grand.central.org/dl/cellservdb/CellServDB</ulink></para>
+
+ <para>The <emphasis role="bold">CellServDB.dist</emphasis> file can be a
+ good basis for the client <emphasis role="bold">CellServDB</emphasis> file,
+ because all of the entries in it use the correct format. You can add or
+ remove cell entries as you see fit. Depending on your cache manager
+ configuration, additional steps (as detailed in
+ <link linkend="HDRWQ91">Enabling Access to Foreign Cells</link>) may be
+ required to enable the Cache Manager to actually reach the cells.</para>
<para>In this section, you add an entry for the local cell to the local <emphasis role="bold">CellServDB</emphasis> file. The
current working directory is still <emphasis role="bold">/usr/vice/etc</emphasis>. <orderedlist>
</programlisting></para>
<para>where <replaceable>cell_name</replaceable> is the cell's complete Internet domain name (for example, <emphasis
- role="bold">abc.com</emphasis>) and <replaceable>organization</replaceable> is an optional field that follows any
+ role="bold">example.com</emphasis>) and <replaceable>organization</replaceable> is an optional field that follows any
number of spaces and the number sign (<computeroutput>#</computeroutput>). By convention it names the organization
- to which the cell corresponds (for example, the ABC Corporation).</para>
+ to which the cell corresponds (for example, the Example Corporation).</para>
</listitem>
<listitem>
<para>where <replaceable>IP_address</replaceable> is the machine's IP address in dotted decimal format (for example,
192.12.105.3). Following any number of spaces and the number sign (<computeroutput>#</computeroutput>) is
<replaceable>machine_name</replaceable>, the machine's fully-qualified hostname (for example, <emphasis
- role="bold">db1.abc.com</emphasis>). In this case, the number sign does not indicate a comment;
+ role="bold">db1.example.com</emphasis>). In this case, the number sign does not indicate a comment;
<replaceable>machine_name</replaceable> is a required field.</para>
</listitem>
</itemizedlist></para>
<para>The following example shows entries for two cells, each of which has three database server machines:</para>
<programlisting>
- >abc.com #ABC Corporation (home cell)
- 192.12.105.3 #db1.abc.com
- 192.12.105.4 #db2.abc.com
- 192.12.105.55 #db3.abc.com
- >stateu.edu #State University cell
- 138.255.68.93 #serverA.stateu.edu
- 138.255.68.72 #serverB.stateu.edu
- 138.255.33.154 #serverC.stateu.edu
+ >example.com #Example Corporation (home cell)
+ 192.12.105.3 #db1.example.com
+ 192.12.105.4 #db2.example.com
+ 192.12.105.55 #db3.example.com
+ >example.org #Example Organization cell
+ 138.255.68.93 #serverA.example.org
+ 138.255.68.72 #serverB.example.org
+ 138.255.33.154 #serverC.example.org
</programlisting>
<indexterm>
</listitem>
<listitem>
- <para>The maximum supported cache size can vary in each AFS release; see the <emphasis>IBM AFS Release Notes</emphasis>
+ <para>The maximum supported cache size can vary in each AFS release; see the <emphasis>OpenAFS Release Notes</emphasis>
for the current version.</para>
</listitem>
<para>For a disk cache, you cannot specify a value in the third field that exceeds 95% of the space available on the
partition mounted at the directory named in the second field. If you violate this restriction, the <emphasis
role="bold">afsd</emphasis> program exits without starting the Cache Manager and prints an appropriate message on the
- standard output stream. A value of 90% is more appropriate on most machines. Some operating systems (such as AIX) do not
+ standard output stream. A value of 90% is more appropriate on most machines. Some operating systems do not
automatically reserve some space to prevent the partition from filling completely; for them, a smaller value (say, 80% to
85% of the space available) is more appropriate.</para>
</listitem>
<note>
<para>Not all file system types that an operating system supports are necessarily supported for use as the cache partition.
- For possible restrictions, see the <emphasis>IBM AFS Release Notes</emphasis>.</para>
+ For possible restrictions, see the <emphasis>OpenAFS Release Notes</emphasis>.</para>
</note>
<para>To configure the disk cache, perform the following procedures: <orderedlist>
to override the parameters' default values and to change the number of some of the daemons. Depending on the machine's cache
size, its amount of RAM, and how many people work on it, you can sometimes improve Cache Manager performance by overriding the
default values. For a discussion of all of the <emphasis role="bold">afsd</emphasis> command's arguments, see its reference page
- in the <emphasis>IBM AFS Administration Reference</emphasis>.</para>
+ in the <emphasis>OpenAFS Administration Reference</emphasis>.</para>
- <para>The <emphasis role="bold">afsd</emphasis> command line in the AFS initialization script on each system type includes an
+ <para>On platforms using the standard 'afs' initialisation script (this does not apply to Fedora or RHEL based distributions), the <emphasis role="bold">afsd</emphasis> command line in the AFS initialization script on each system type includes an
<computeroutput>OPTIONS</computeroutput> variable. You can use it to set nondefault values for the command's arguments, in one
of the following ways: <itemizedlist>
<listitem>
role="bold">afsd</emphasis> command line in the script, or set no arguments (and so accept default values for all Cache
Manager parameters).</para>
</listitem>
- </itemizedlist> <orderedlist>
+ </itemizedlist>
+
+ <note>
+ <para>If you are running on a Fedora or RHEL based system, the
+ openafs-client initialization script behaves differently from that
+ described above. It sources /etc/sysconfig/openafs, in which the
+ AFSD_ARGS variable may be set to contain any, or all, of the afsd options
+ detailed. Note that this script does not support setting an OPTIONS
+ variable, or the SMALL, MEDIUM and LARGE methods of defining cache size
+ </para>
+ </note>
+
+ <orderedlist>
<listitem>
<para>Create the local directory on which to mount the AFS filespace, by convention <emphasis role="bold">/afs</emphasis>.
If the directory already exists, verify that it is empty. <programlisting>
</listitem>
<listitem>
- <para>On AIX systems, add the following line to the <emphasis role="bold">/etc/vfs</emphasis> file. It enables AIX to
- unmount AFS correctly during shutdown. <programlisting>
- afs 4 none none
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>On Linux systems, copy the <emphasis role="bold">afsd</emphasis> options file from the <emphasis
+ <para>On non-package based Linux systems, copy the <emphasis role="bold">afsd</emphasis> options file from the <emphasis
role="bold">/usr/vice/etc</emphasis> directory to the <emphasis role="bold">/etc/sysconfig</emphasis> directory, removing
the <emphasis role="bold">.conf</emphasis> extension as you do so. <programlisting>
# <emphasis role="bold">cp /usr/vice/etc/afs.conf /etc/sysconfig/afs</emphasis>
<para>Edit the machine's AFS initialization script or <emphasis role="bold">afsd</emphasis> options file to set
appropriate values for <emphasis role="bold">afsd</emphasis> command parameters. The script resides in the indicated
location on each system type: <itemizedlist>
- <listitem>
- <para>On AIX systems, <emphasis role="bold">/etc/rc.afs</emphasis></para>
- </listitem>
-
- <listitem>
- <para>On Digital UNIX systems, <emphasis role="bold">/sbin/init.d/afs</emphasis></para>
- </listitem>
-
- <listitem>
- <para>On HP-UX systems, <emphasis role="bold">/sbin/init.d/afs</emphasis></para>
+ <listitem>
+ <para>On Fedora and RHEL systems, <emphasis role="bold">/etc/sysconfg/openafs</emphasis></para>
</listitem>
-
- <listitem>
- <para>On IRIX systems, <emphasis role="bold">/etc/init.d/afs</emphasis></para>
- </listitem>
-
+
<listitem>
- <para>On Linux systems, <emphasis role="bold">/etc/sysconfig/afs</emphasis> (the <emphasis
+ <para>On non-package based Linux systems, <emphasis role="bold">/etc/sysconfig/afs</emphasis> (the <emphasis
role="bold">afsd</emphasis> options file)</para>
</listitem>
role="bold">afsd</emphasis> command line. If you intend for the machine to remain an AFS client, also set any
performance-related arguments you wish. <itemizedlist>
<listitem>
- <para>Add the <emphasis role="bold">-nosettime</emphasis> flag, because this is a file server machine that is also a
- client. The flag prevents the machine from picking a file server machine in the cell as its source for the correct
- time, which client machines normally do. File server machines instead use NTPD (as controlled by the <emphasis
- role="bold">runntp</emphasis> process) or another protocol to synchronize their clocks.</para>
- </listitem>
-
- <listitem>
<para>Add the <emphasis role="bold">-memcache</emphasis> flag if the machine is to use a memory cache.</para>
</listitem>
</listitem>
</itemizedlist></para>
</listitem>
- </orderedlist></para>
+ </orderedlist>
+ <note><para>In order to successfully complete the instructions in the
+ remainder of this guide, it is important that the machine does not have
+ a synthetic root (as discussed in <link linkend="HDRWQ91">Enabling Access
+ to Foreign Cells</link>). As some distributions ship with this enabled, it
+ may be necessary to remove any occurences of the
+ <emphasis role="bold">-dynroot</emphasis> and
+ <emphasis role="bold">-afsdb</emphasis> options from both the AFS
+ initialisation script and options file. If this functionality is
+ required it may be renabled as detailed in
+ <link linkend="HDRWQ91">Enabling Access to Foreign Cells</link>.
+ </para></note>
+ </para>
<indexterm>
<primary>overview</primary>
<secondary>first AFS machine</secondary>
</indexterm>
- <indexterm>
- <primary>invoking AFS init. script</primary>
-
- <see>running</see>
- </indexterm>
- </sect1>
-
- <sect1 id="HDRWQ72">
- <title>Verifying the AFS Initialization Script</title>
-
- <para>At this point you run the AFS initialization script to verify that it correctly invokes all of the necessary programs and
- AFS processes, and that they start correctly. The following are the relevant commands: <itemizedlist>
- <listitem>
- <para>The command that dynamically loads AFS modifications into the kernel, on some system types (not applicable if the
- kernel has AFS modifications built in)</para>
- </listitem>
-
- <listitem>
- <para>The <emphasis role="bold">bosserver</emphasis> command, which starts the BOS Server; it in turn starts the server
- processes for which you created entries in the <emphasis role="bold">/usr/afs/local/BosConfig</emphasis> file</para>
- </listitem>
-
- <listitem>
- <para>The <emphasis role="bold">afsd</emphasis> command, which initializes the Cache Manager</para>
- </listitem>
- </itemizedlist></para>
-
- <para>On system types that use a dynamic loader program, you must reboot the machine before running the initialization script,
- so that it can freshly load AFS modifications into the kernel.</para>
-
- <para>If there are problems during the initialization, attempt to resolve them. The AFS Product Support group can provide
- assistance if necessary. <orderedlist>
- <indexterm>
- <primary>commands</primary>
-
- <secondary>bos shutdown</secondary>
- </indexterm>
-
- <indexterm>
- <primary>bos commands</primary>
-
- <secondary>shutdown</secondary>
- </indexterm>
-
- <listitem>
- <para>Issue the <emphasis role="bold">bos shutdown</emphasis> command to shut down the AFS server processes other than the
- BOS Server. Include the <emphasis role="bold">-wait</emphasis> flag to delay return of the command shell prompt until all
- processes shut down completely. <programlisting>
- # <emphasis role="bold">/usr/afs/bin/bos shutdown</emphasis> <<replaceable>machine name</replaceable>> <emphasis
- role="bold">-wait</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Issue the <emphasis role="bold">ps</emphasis> command to learn the <emphasis role="bold">bosserver</emphasis>
- process's process ID number (PID), and then the <emphasis role="bold">kill</emphasis> command to stop it. <programlisting>
- # <emphasis role="bold">ps</emphasis> <replaceable>appropriate_ps_options</replaceable> <emphasis role="bold">| grep bosserver</emphasis>
- # <emphasis role="bold">kill</emphasis> <replaceable>bosserver_PID</replaceable>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Issue the appropriate commands to run the AFS initialization script for this system type.</para>
-
- <indexterm>
- <primary>AIX</primary>
-
- <secondary>AFS initialization script</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm>
-
- <para><emphasis role="bold">On AIX systems:</emphasis> <orderedlist>
- <listitem>
- <para>Reboot the machine and log in again as the local superuser <emphasis role="bold">root</emphasis>.
- <programlisting>
- # <emphasis role="bold">cd /</emphasis>
- # <emphasis role="bold">shutdown -r now</emphasis>
- login: <emphasis role="bold">root</emphasis>
- Password: <replaceable>root_password</replaceable>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Run the AFS initialization script. <programlisting>
- # <emphasis role="bold">/etc/rc.afs</emphasis>
-</programlisting></para>
- </listitem>
- </orderedlist></para>
-
- <indexterm>
- <primary>Digital UNIX</primary>
-
- <secondary>AFS initialization script</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm>
-
- <para><emphasis role="bold">On Digital UNIX systems:</emphasis> <orderedlist>
- <listitem>
- <para>Run the AFS initialization script. <programlisting>
- # <emphasis role="bold">/sbin/init.d/afs start</emphasis>
-</programlisting></para>
- </listitem>
- </orderedlist></para>
-
- <indexterm>
- <primary>HP-UX</primary>
-
- <secondary>AFS initialization script</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm>
-
- <para><emphasis role="bold">On HP-UX systems:</emphasis> <orderedlist>
- <listitem>
- <para>Run the AFS initialization script. <programlisting>
- # <emphasis role="bold">/sbin/init.d/afs start</emphasis>
-</programlisting></para>
- </listitem>
- </orderedlist></para>
-
- <indexterm>
- <primary>IRIX</primary>
-
- <secondary>AFS initialization script</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>afsclient variable (IRIX)</primary>
-
- <secondary>first AFS machine</secondary>
- </indexterm>
-
- <indexterm>
- <primary>variables</primary>
-
- <secondary>afsclient (IRIX)</secondary>
-
- <tertiary>first AFS machine</tertiary>
- </indexterm>
-
- <indexterm>
- <primary>IRIX</primary>
+ <indexterm>
+ <primary>invoking AFS init. script</primary>
- <secondary>afsclient variable</secondary>
+ <see>running</see>
+ </indexterm>
+ </sect1>
- <tertiary>first AFS machine</tertiary>
- </indexterm>
+ <sect1 id="HDRWQ72">
+ <title>Verifying the AFS Initialization Script</title>
- <indexterm>
- <primary>afsserver variable (IRIX)</primary>
+ <para>At this point you run the AFS initialization script to verify that it correctly invokes all of the necessary programs and
+ AFS processes, and that they start correctly. The following are the relevant commands: <itemizedlist>
+ <listitem>
+ <para>The command that dynamically loads AFS modifications into the kernel, on some system types (not applicable if the
+ kernel has AFS modifications built in)</para>
+ </listitem>
- <secondary>first AFS machine</secondary>
- </indexterm>
+ <listitem>
+ <para>The <emphasis role="bold">bosserver</emphasis> command, which starts the BOS Server; it in turn starts the server
+ processes for which you created entries in the <emphasis role="bold">/usr/afs/local/BosConfig</emphasis> file</para>
+ </listitem>
- <indexterm>
- <primary>variables</primary>
+ <listitem>
+ <para>The <emphasis role="bold">afsd</emphasis> command, which initializes the Cache Manager</para>
+ </listitem>
+ </itemizedlist></para>
- <secondary>afsserver (IRIX)</secondary>
+ <para>On system types that use a dynamic loader program, you must reboot the machine before running the initialization script,
+ so that it can freshly load AFS modifications into the kernel.</para>
- <tertiary>first AFS machine</tertiary>
- </indexterm>
+ <para>If there are problems during the initialization, attempt to resolve them. The OpenAFS mailing lists can provide assistance if necessary.
- <indexterm>
- <primary>IRIX</primary>
+ <orderedlist>
+ <indexterm>
+ <primary>commands</primary>
- <secondary>afsserver variable</secondary>
+ <secondary>bos shutdown</secondary>
+ </indexterm>
- <tertiary>first AFS machine</tertiary>
- </indexterm>
+ <indexterm>
+ <primary>bos commands</primary>
- <para><emphasis role="bold">On IRIX systems:</emphasis> <orderedlist>
- <listitem>
- <para>If you have configured the machine to use the <emphasis role="bold">ml</emphasis> dynamic loader program,
- reboot the machine and log in again as the local superuser <emphasis role="bold">root</emphasis>. <programlisting>
- # <emphasis role="bold">cd /</emphasis>
- # <emphasis role="bold">shutdown -i6 -g0 -y</emphasis>
- login: <emphasis role="bold">root</emphasis>
- Password: <replaceable>root_password</replaceable>
-</programlisting></para>
- </listitem>
+ <secondary>shutdown</secondary>
+ </indexterm>
- <listitem>
- <para>Issue the <emphasis role="bold">chkconfig</emphasis> command to activate the <emphasis
- role="bold">afsserver</emphasis> and <emphasis role="bold">afsclient</emphasis> configuration variables.
- <programlisting>
- # <emphasis role="bold">/etc/chkconfig -f afsserver on</emphasis>
- # <emphasis role="bold">/etc/chkconfig -f afsclient on</emphasis>
+ <listitem>
+ <para>Issue the <emphasis role="bold">bos shutdown</emphasis> command to shut down the AFS server processes other than the
+ BOS Server. Include the <emphasis role="bold">-wait</emphasis> flag to delay return of the command shell prompt until all
+ processes shut down completely. <programlisting>
+ # <emphasis role="bold">/usr/afs/bin/bos shutdown</emphasis> <<replaceable>machine name</replaceable>> <emphasis
+ role="bold">-wait</emphasis>
</programlisting></para>
- </listitem>
+ </listitem>
- <listitem>
- <para>Run the AFS initialization script. <programlisting>
- # <emphasis role="bold">/etc/init.d/afs start</emphasis>
+ <listitem>
+ <para>Issue the <emphasis role="bold">ps</emphasis> command to learn the <emphasis role="bold">bosserver</emphasis>
+ process's process ID number (PID), and then the <emphasis role="bold">kill</emphasis> command to stop it. <programlisting>
+ # <emphasis role="bold">ps</emphasis> <replaceable>appropriate_ps_options</replaceable> <emphasis role="bold">| grep bosserver</emphasis>
+ # <emphasis role="bold">kill</emphasis> <replaceable>bosserver_PID</replaceable>
</programlisting></para>
- </listitem>
- </orderedlist></para>
-
- <indexterm>
- <primary>Linux</primary>
-
- <secondary>AFS initialization script</secondary>
+ </listitem>
- <tertiary>on first AFS machine</tertiary>
- </indexterm>
+ <listitem>
+ <para>Issue the appropriate commands to run the AFS initialization script for this system type.</para>
<para><emphasis role="bold">On Linux systems:</emphasis> <orderedlist>
<listitem>
</listitem>
<listitem>
- <para>Run the AFS initialization script. <programlisting>
- # <emphasis role="bold">/etc/rc.d/init.d/afs start</emphasis>
+ <para>Run the AFS initialization scripts.
+<programlisting>
+ # <emphasis role="bold">/etc/rc.d/init.d/openafs-client start</emphasis>
+ # <emphasis role="bold">/etc/rc.d/init.d/openafs-server start</emphasis>
</programlisting></para>
</listitem>
</orderedlist></para>
</programlisting></para>
</listitem>
</orderedlist></para>
-
- <indexterm>
- <primary>commands</primary>
-
- <secondary>klog</secondary>
- </indexterm>
-
- <indexterm>
- <primary>klog command</primary>
- </indexterm>
</listitem>
<listitem>
role="bold">V</emphasis><replaceable>n</replaceable> files in the cache directory. Subsequent Cache Manager
initializations do not take nearly as long, because the <emphasis role="bold">V</emphasis><replaceable>n</replaceable>
files already exist.</para>
+ </listitem>
+ <listitem>
+
+ <indexterm>
+ <primary>commands</primary>
+ <secondary>aklog</secondary>
+ </indexterm>
- <para>As a basic test of correct AFS functioning, issue the <emphasis role="bold">klog</emphasis> command to authenticate
- as the <emphasis role="bold">admin</emphasis> user. Provide the password (<replaceable>admin_passwd</replaceable>) you
+ <indexterm>
+ <primary>aklog command</primary>
+ </indexterm>
+
+ <para>If you are working with an existing cell which uses
+ <emphasis role="bold">kaserver</emphasis> for authentication,
+ please recall the note in
+ <link linkend="KAS003">Using this Appendix</link> detailing the
+ substitution of <emphasis role="bold">kinit</emphasis> and
+ <emphasis role="bold">aklog</emphasis> with
+ <emphasis role="bold">klog</emphasis>.</para>
+
+ <para>As a basic test of correct AFS functioning, issue the
+ <emphasis role="bold">kinit</emphasis> and
+ <emphasis role="bold">aklog</emphasis> commands to authenticate
+ as the <emphasis role="bold">admin</emphasis> user.
+ Provide the password (<replaceable>admin_passwd</replaceable>) you
defined in <link linkend="HDRWQ53">Initializing Cell Security</link>.</para>
<programlisting>
- # <emphasis role="bold">/usr/afs/bin/klog admin</emphasis>
+ # <emphasis role="bold">kinit admin</emphasis>
Password: <replaceable>admin_passwd</replaceable>
+ # <emphasis role="bold">aklog</emphasis>
</programlisting>
<indexterm>
</listitem>
<listitem>
- <para>Issue the <emphasis role="bold">tokens</emphasis> command to verify that the <emphasis role="bold">klog</emphasis>
+ <para>Issue the <emphasis role="bold">tokens</emphasis> command to
+ verify that the <emphasis role="bold">aklog</emphasis>
command worked correctly. If it did, the output looks similar to the following example for the <emphasis
- role="bold">abc.com</emphasis> cell, where <emphasis role="bold">admin</emphasis>'s AFS UID is 1. If the output does not
- seem correct, resolve the problem. Changes to the AFS initialization script are possibly necessary. The AFS Product
- Support group can provide assistance as necessary. <programlisting>
- # <emphasis role="bold">/usr/afs/bin/tokens</emphasis>
+ role="bold">example.com</emphasis> cell, where <emphasis role="bold">admin</emphasis>'s AFS UID is 1. If the output does not
+ seem correct, resolve the problem. Changes to the AFS initialization script are possibly necessary. The OpenAFS mailing lists can provide assistance as necessary. <programlisting>
+ # <emphasis role="bold">tokens</emphasis>
Tokens held by the Cache Manager:
- User's (AFS ID 1) tokens for afs@abc.com [Expires May 22 11:52]
+ User's (AFS ID 1) tokens for afs@example.com [Expires May 22 11:52]
--End of list--
</programlisting></para>
</listitem>
<para>Now that you have confirmed that the AFS initialization script works correctly, take the action necessary to have it run
automatically at each reboot. Proceed to the instructions for your system type: <itemizedlist>
<listitem>
- <para><link linkend="HDRWQ74">Activating the Script on AIX Systems</link></para>
- </listitem>
-
- <listitem>
- <para><link linkend="HDRWQ75">Activating the Script on Digital UNIX Systems</link></para>
- </listitem>
-
- <listitem>
- <para><link linkend="HDRWQ76">Activating the Script on HP-UX Systems</link></para>
- </listitem>
-
- <listitem>
- <para><link linkend="HDRWQ77">Activating the Script on IRIX Systems</link></para>
- </listitem>
-
- <listitem>
<para><link linkend="HDRWQ78">Activating the Script on Linux Systems</link></para>
</listitem>
<para><link linkend="HDRWQ79">Activating the Script on Solaris Systems</link></para>
</listitem>
</itemizedlist></para>
-
- <indexterm>
- <primary>AIX</primary>
-
- <secondary>AFS initialization script</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm>
-
- <sect2 id="HDRWQ74">
- <title>Activating the Script on AIX Systems</title>
-
- <orderedlist>
- <listitem>
- <para>Edit the AIX initialization file, <emphasis role="bold">/etc/inittab</emphasis>, adding the following line to invoke
- the AFS initialization script. Place it just after the line that starts NFS daemons. <programlisting>
- rcafs:2:wait:/etc/rc.afs > /dev/console 2>&1 # Start AFS services
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para><emphasis role="bold">(Optional)</emphasis> There are now copies of the AFS initialization file in both the
- <emphasis role="bold">/usr/vice/etc</emphasis> and <emphasis role="bold">/etc</emphasis> directories. If you want to avoid
- potential confusion by guaranteeing that they are always the same, create a link between them. You can always retrieve the
- original script from the AFS CD-ROM if necessary. <programlisting>
- # <emphasis role="bold">cd /usr/vice/etc</emphasis>
- # <emphasis role="bold">rm rc.afs</emphasis>
- # <emphasis role="bold">ln -s /etc/rc.afs</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Proceed to <link linkend="HDRWQ80">Configuring the Top Levels of the AFS Filespace</link>.</para>
- </listitem>
- </orderedlist>
-
- <indexterm>
- <primary>Digital UNIX</primary>
-
- <secondary>AFS initialization script</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm>
- </sect2>
-
- <sect2 id="HDRWQ75">
- <title>Activating the Script on Digital UNIX Systems</title>
-
- <orderedlist>
- <listitem>
- <para>Change to the <emphasis role="bold">/sbin/init.d</emphasis> directory and issue the <emphasis role="bold">ln
- -s</emphasis> command to create symbolic links that incorporate the AFS initialization script into the Digital UNIX
- startup and shutdown sequence. <programlisting>
- # <emphasis role="bold">cd /sbin/init.d</emphasis>
- # <emphasis role="bold">ln -s ../init.d/afs /sbin/rc3.d/S67afs</emphasis>
- # <emphasis role="bold">ln -s ../init.d/afs /sbin/rc0.d/K66afs</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para><emphasis role="bold">(Optional)</emphasis> There are now copies of the AFS initialization file in both the
- <emphasis role="bold">/usr/vice/etc</emphasis> and <emphasis role="bold">/sbin/init.d</emphasis> directories. If you want
- to avoid potential confusion by guaranteeing that they are always the same, create a link between them. You can always
- retrieve the original script from the AFS CD-ROM if necessary. <programlisting>
- # <emphasis role="bold">cd /usr/vice/etc</emphasis>
- # <emphasis role="bold">rm afs.rc</emphasis>
- # <emphasis role="bold">ln -s /sbin/init.d/afs afs.rc</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Proceed to <link linkend="HDRWQ80">Configuring the Top Levels of the AFS Filespace</link>.</para>
- </listitem>
- </orderedlist>
-
- <indexterm>
- <primary>HP-UX</primary>
-
- <secondary>AFS initialization script</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm>
- </sect2>
-
- <sect2 id="HDRWQ76">
- <title>Activating the Script on HP-UX Systems</title>
-
- <orderedlist>
- <listitem>
- <para>Change to the <emphasis role="bold">/sbin/init.d</emphasis> directory and issue the <emphasis role="bold">ln
- -s</emphasis> command to create symbolic links that incorporate the AFS initialization script into the HP-UX startup and
- shutdown sequence. <programlisting>
- # <emphasis role="bold">cd /sbin/init.d</emphasis>
- # <emphasis role="bold">ln -s ../init.d/afs /sbin/rc2.d/S460afs</emphasis>
- # <emphasis role="bold">ln -s ../init.d/afs /sbin/rc2.d/K800afs</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para><emphasis role="bold">(Optional)</emphasis> There are now copies of the AFS initialization file in both the
- <emphasis role="bold">/usr/vice/etc</emphasis> and <emphasis role="bold">/sbin/init.d</emphasis> directories. If you want
- to avoid potential confusion by guaranteeing that they are always the same, create a link between them. You can always
- retrieve the original script from the AFS CD-ROM if necessary. <programlisting>
- # <emphasis role="bold">cd /usr/vice/etc</emphasis>
- # <emphasis role="bold">rm afs.rc</emphasis>
- # <emphasis role="bold">ln -s /sbin/init.d/afs afs.rc</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Proceed to <link linkend="HDRWQ80">Configuring the Top Levels of the AFS Filespace</link>.</para>
- </listitem>
- </orderedlist>
-
- <indexterm>
- <primary>IRIX</primary>
-
- <secondary>AFS initialization script</secondary>
-
- <tertiary>on first AFS machine</tertiary>
- </indexterm>
- </sect2>
-
- <sect2 id="HDRWQ77">
- <title>Activating the Script on IRIX Systems</title>
-
- <orderedlist>
- <listitem>
- <para>Change to the <emphasis role="bold">/etc/init.d</emphasis> directory and issue the <emphasis role="bold">ln
- -s</emphasis> command to create symbolic links that incorporate the AFS initialization script into the IRIX startup and
- shutdown sequence. <programlisting>
- # <emphasis role="bold">cd /etc/init.d</emphasis>
- # <emphasis role="bold">ln -s ../init.d/afs /etc/rc2.d/S35afs</emphasis>
- # <emphasis role="bold">ln -s ../init.d/afs /etc/rc0.d/K35afs</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para><emphasis role="bold">(Optional)</emphasis> There are now copies of the AFS initialization file in both the
- <emphasis role="bold">/usr/vice/etc</emphasis> and <emphasis role="bold">/etc/init.d</emphasis> directories. If you want
- to avoid potential confusion by guaranteeing that they are always the same, create a link between them. You can always
- retrieve the original script from the AFS CD-ROM if necessary. <programlisting>
- # <emphasis role="bold">cd /usr/vice/etc</emphasis>
- # <emphasis role="bold">rm afs.rc</emphasis>
- # <emphasis role="bold">ln -s /etc/init.d/afs afs.rc</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
- <para>Proceed to <link linkend="HDRWQ80">Configuring the Top Levels of the AFS Filespace</link>.</para>
- </listitem>
- </orderedlist>
-
<indexterm>
<primary>Linux</primary>
<tertiary>on first AFS machine</tertiary>
</indexterm>
- </sect2>
<sect2 id="HDRWQ78">
<title>Activating the Script on Linux Systems</title>
<orderedlist>
<listitem>
- <para>Issue the <emphasis role="bold">chkconfig</emphasis> command to activate the <emphasis role="bold">afs</emphasis>
- configuration variable. Based on the instruction in the AFS initialization file that begins with the string
+ <para>Issue the <emphasis role="bold">chkconfig</emphasis> command to activate the <emphasis role="bold">openafs-client</emphasis> and <emphasis role="bold">openafs-server</emphasis>
+ configuration variables. Based on the instruction in the AFS initialization file that begins with the string
<computeroutput>#chkconfig</computeroutput>, the command automatically creates the symbolic links that incorporate the
script into the Linux startup and shutdown sequence. <programlisting>
- # <emphasis role="bold">/sbin/chkconfig --add afs</emphasis>
+ # <emphasis role="bold">/sbin/chkconfig --add openafs-client</emphasis>
+ # <emphasis role="bold">/sbin/chkconfig --add openafs-server</emphasis>
</programlisting></para>
</listitem>
read/write mount point enables you to access the read/write version of replicated volumes when necessary. Creating both mount
points essentially creates separate read-only and read-write copies of your filespace, and enables the Cache Manager to traverse
the filespace on a read-only path or read/write path as appropriate. For further discussion of these concepts, see the chapter
- in the <emphasis>IBM AFS Administration Guide</emphasis> about administering volumes. <indexterm>
+ in the <emphasis>OpenAFS Administration Guide</emphasis> about administering volumes. <indexterm>
<primary>root.afs volume</primary>
<secondary>replicating</secondary>
role="bold">system:administrators</emphasis> group. It is a default entry that AFS places on every new volume's root
directory.</para>
+ <para>The top-level AFS directory, typically /afs, is a special case:
+ when the client is configured to run in dynroot mode (e.g.
+ <emphasis role="bold">afsd -dynroot</emphasis>, attempts to set
+ the ACL on this directory will return <emphasis role="bold">
+ Connection timed out</emphasis>. This is because the dynamically-
+ generated root directory is not a part of the global AFS space,
+ and cannot have an access control list set on it.</para>
+
<programlisting>
# <emphasis role="bold">/usr/afs/bin/fs setacl /afs system:anyuser rl</emphasis>
</programlisting>
</indexterm>
</listitem>
- <listitem>
- <para><anchor id="LIWQ81" />Issue the <emphasis role="bold">vos create</emphasis> command to create the <emphasis
+ <listitem id="LIWQ81">
+ <para>Issue the <emphasis role="bold">vos create</emphasis> command to create the <emphasis
role="bold">root.cell</emphasis> volume. Then issue the <emphasis role="bold">fs mkmount</emphasis> command to mount it as
a subdirectory of the <emphasis role="bold">/afs</emphasis> directory, where it serves as the root of your cell's local
AFS filespace. Finally, issue the <emphasis role="bold">fs setacl</emphasis> command to create an ACL entry for the
<para>For the <replaceable>partition name</replaceable> argument, substitute the name of one of the machine's AFS server
partitions (such as <emphasis role="bold">/vicepa</emphasis>). For the <replaceable>cellname</replaceable> argument,
- substitute your cell's fully-qualified Internet domain name (such as <emphasis role="bold">abc.com</emphasis>).</para>
+ substitute your cell's fully-qualified Internet domain name (such as <emphasis role="bold">example.com</emphasis>).</para>
<programlisting>
# <emphasis role="bold">/usr/afs/bin/vos create</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>partition name</replaceable>> <emphasis
<listitem>
<para><emphasis role="bold">(Optional)</emphasis> Create a symbolic link to a shortened cell name, to reduce the length of
- pathnames for users in the local cell. For example, in the <emphasis role="bold">abc.com</emphasis> cell, <emphasis
- role="bold">/afs/abc</emphasis> is a link to <emphasis role="bold">/afs/abc.com</emphasis>. <programlisting>
+ pathnames for users in the local cell. For example, in the <emphasis role="bold">example.com</emphasis> cell, <emphasis
+ role="bold">/afs/example</emphasis> is a link to <emphasis role="bold">/afs/example.com</emphasis>. <programlisting>
# <emphasis role="bold">cd /afs</emphasis>
# <emphasis role="bold">ln -s</emphasis> <replaceable>full_cellname</replaceable> <replaceable>short_cellname</replaceable>
</programlisting> <indexterm>
</indexterm>
</listitem>
- <listitem>
- <para><anchor id="LIWQ82" />Issue the <emphasis role="bold">vos addsite</emphasis> command to define a replication site
+ <listitem id="LIWQ82">
+ <para>Issue the <emphasis role="bold">vos addsite</emphasis> command to define a replication site
for both the <emphasis role="bold">root.afs</emphasis> and <emphasis role="bold">root.cell</emphasis> volumes. In each
case, substitute for the <replaceable>partition name</replaceable> argument the partition where the volume's read/write
version resides. When you install additional file server machines, it is a good idea to create replication sites on them
<sect1 id="HDRWQ83">
<title>Storing AFS Binaries in AFS</title>
+ <note><para>Sites with existing binary distribution mechanisms, including
+ those which use packaging systems such as RPM, may wish to skip this step,
+ and use tools native to their operating system to manage AFS configuration
+ information.</para></note>
+
<para>In the conventional configuration, you make AFS client binaries and configuration files available in the subdirectories of
the <emphasis role="bold">/usr/afsws</emphasis> directory on client machines (<emphasis role="bold">afsws</emphasis> is an
acronym for <emphasis role="bold">AFS w</emphasis><emphasis>ork</emphasis><emphasis
<para>In this section you create the necessary volumes. The conventional location to which to link <emphasis
role="bold">/usr/afsws</emphasis> is <emphasis role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
role="bold">/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/usr/afsws</emphasis>, where
- <replaceable>sysname</replaceable> is the appropriate system type name as specified in the <emphasis>IBM AFS Release
+ <replaceable>sysname</replaceable> is the appropriate system type name as specified in the <emphasis>OpenAFS Release
Notes</emphasis>. The instructions in <link linkend="HDRWQ133">Installing Additional Client Machines</link> assume that you have
followed the instructions in this section.</para>
<tertiary>volume for AFS binaries</tertiary>
</indexterm>
- <listitem>
- <para><anchor id="LIWQ84" />Issue the <emphasis role="bold">vos create</emphasis> command to create volumes for storing
+ <listitem id="LIWQ84">
+ <para>Issue the <emphasis role="bold">vos create</emphasis> command to create volumes for storing
the AFS client binaries for this system type. The following example instruction creates volumes called
<replaceable>sysname</replaceable>, <replaceable>sysname</replaceable>.<emphasis role="bold">usr</emphasis>, and
- <replaceable>sysname</replaceable>.<emphasis role="bold">usr.afsws</emphasis>. Refer to the <emphasis>IBM AFS Release
+ <replaceable>sysname</replaceable>.<emphasis role="bold">usr.afsws</emphasis>. Refer to the <emphasis>OpenAFS Release
Notes</emphasis> to learn the proper value of <replaceable>sysname</replaceable> for this system type. <programlisting>
# <emphasis role="bold">vos create</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>partition name</replaceable>> <replaceable>sysname</replaceable>
# <emphasis role="bold">vos create</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>partition name</replaceable>> <replaceable>sysname</replaceable><emphasis
</indexterm></para>
</listitem>
- <listitem>
- <para><anchor id="LIWQ85" />Issue the <emphasis role="bold">fs setquota</emphasis> command to set an unlimited quota on
+ <listitem id="LIWQ85">
+ <para>Issue the <emphasis role="bold">fs setquota</emphasis> command to set an unlimited quota on
the volume mounted at the <emphasis role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
role="bold">/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/usr/afsws</emphasis> directory. This
enables you to copy all of the appropriate files from the CD-ROM into the volume without exceeding the volume's
</listitem>
<listitem>
- <para>Mount the AFS CD-ROM for this machine's system type on the local <emphasis role="bold">/cdrom</emphasis> directory,
- if it is not already. For instructions on mounting CD-ROMs (either locally or remotely via NFS), consult the operating
- system documentation. <indexterm>
+ <para>Unpack the distribution tarball into the <emphasis role="bold">/tmp/afsdist</emphasis> directory,
+ if it is not already. <indexterm>
<primary>copying</primary>
<secondary>AFS binaries into volume</secondary>
</listitem>
<listitem>
- <para>Copy the contents of the indicated directories from the CD-ROM into the <emphasis
+ <para>Copy the contents of the indicated directories from the
+ distribution into the <emphasis
role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
role="bold">/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/usr/afsws</emphasis> directory.
<programlisting>
# <emphasis role="bold">cd /afs/.</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/</emphasis><replaceable>sysname</replaceable><emphasis
role="bold">/usr/afsws</emphasis>
- # <emphasis role="bold">cp -rp /cdrom/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/bin .</emphasis>
- # <emphasis role="bold">cp -rp /cdrom/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/etc .</emphasis>
- # <emphasis role="bold">cp -rp /cdrom/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/include .</emphasis>
- # <emphasis role="bold">cp -rp /cdrom/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/lib .</emphasis>
-</programlisting> <indexterm>
- <primary>requirements</primary>
-
- <secondary>protecting binaries per AFS license</secondary>
- </indexterm> <indexterm>
- <primary>licensing requirements</primary>
- </indexterm></para>
- </listitem>
-
- <listitem>
- <para>Issue the <emphasis role="bold">fs setacl</emphasis> command to set the ACL on each directory appropriately. To
- comply with the terms of your AFS License agreement, you must prevent unauthorized users from accessing AFS software. To
- enable access for locally authenticated users only, set the ACL on the <emphasis role="bold">etc</emphasis>, <emphasis
- role="bold">include</emphasis>, and <emphasis role="bold">lib</emphasis> subdirectories to grant the <emphasis
- role="bold">l</emphasis> and <emphasis role="bold">r</emphasis> permissions to the <emphasis
- role="bold">system:authuser</emphasis> group rather than the <emphasis role="bold">system:anyuser</emphasis> group. The
- <emphasis role="bold">system:anyuser</emphasis> group must retain the <emphasis role="bold">l</emphasis> and <emphasis
- role="bold">r</emphasis> permissions on the <emphasis role="bold">bin</emphasis> subdirectory to enable unauthenticated
- users to access the <emphasis role="bold">klog</emphasis> binary. To ensure that unauthorized users are not accessing AFS
- software, check periodically that the ACLs on these directories are set properly. <programlisting>
- # <emphasis role="bold">cd /afs/.</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/</emphasis><replaceable>sysname</replaceable><emphasis
- role="bold">/usr/afsws</emphasis>
- # <emphasis role="bold">fs setacl -dir etc include lib -acl system:authuser rl</emphasis> \
- <emphasis role="bold">system:anyuser none</emphasis>
-</programlisting> <indexterm>
+ # <emphasis role="bold">cp -rp /tmp/afsdist/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/bin .</emphasis>
+ # <emphasis role="bold">cp -rp /tmp/afsdist/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/etc .</emphasis>
+ # <emphasis role="bold">cp -rp /tmp/afsdist/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/include .</emphasis>
+ # <emphasis role="bold">cp -rp /tmp/afsdist/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/lib .</emphasis>
+</programlisting>
+<indexterm>
<primary>creating</primary>
<secondary>symbolic link</secondary>
</indexterm></para>
</listitem>
- <listitem>
- <para><anchor id="LIWQ86" />Create <emphasis role="bold">/usr/afsws</emphasis> on the local disk as a symbolic link to the
+ <listitem id="LIWQ86">
+ <para>Create <emphasis role="bold">/usr/afsws</emphasis> on the local disk as a symbolic link to the
directory <emphasis role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
role="bold">/@sys/usr/afsws</emphasis>. You can specify the actual system name instead of <emphasis
role="bold">@sys</emphasis> if you wish, but the advantage of using <emphasis role="bold">@sys</emphasis> is that it
<para>The AFS distribution includes the following documents: <itemizedlist>
<listitem>
- <para><emphasis>IBM AFS Release Notes</emphasis></para>
+ <para><emphasis>OpenAFS Release Notes</emphasis></para>
</listitem>
<listitem>
- <para><emphasis>IBM AFS Quick Beginnings</emphasis></para>
+ <para><emphasis>OpenAFS Quick Beginnings</emphasis></para>
</listitem>
<listitem>
- <para><emphasis>IBM AFS User Guide</emphasis></para>
+ <para><emphasis>OpenAFS User Guide</emphasis></para>
</listitem>
<listitem>
- <para><emphasis>IBM AFS Administration Reference</emphasis></para>
+ <para><emphasis>OpenAFS Administration Reference</emphasis></para>
</listitem>
<listitem>
- <para><emphasis>IBM AFS Administration Guide</emphasis></para>
+ <para><emphasis>OpenAFS Administration Guide</emphasis></para>
</listitem>
</itemizedlist></para>
- <para>The AFS CD-ROM for each system type has a top-level <emphasis role="bold">Documentation</emphasis> directory, with a
- subdirectory for each document format provided. The different formats are suitable for online viewing, printing, or both.</para>
+ <note><para>OpenAFS Documentation is not currently provided with all
+ distributions, but may be downloaded separately from the OpenAFS
+ website</para></note>
+
+ <para>The OpenAFS Documentation Distribution has a directory for each
+ document format provided. The different formats are suitable for online
+ viewing, printing, or both.</para>
<para>This section explains how to create and mount a volume to house the documents, making them available to your users. The
recommended mount point for the volume is <emphasis role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
role="bold">/afsdoc</emphasis>. If you wish, you can create a link to the mount point on each client machine's local disk,
called <emphasis role="bold">/usr/afsdoc</emphasis>. Alternatively, you can create a link to the mount point in each user's home
- directory. You can also choose to permit users to access only certain documents (most probably, the <emphasis>IBM AFS User
+ directory. You can also choose to permit users to access only certain documents (most probably, the <emphasis>OpenAFS User
Guide</emphasis>) by creating different mount points or setting different ACLs on different document directories.</para>
<para>The current working directory is still <emphasis role="bold">/usr/afs/bin</emphasis>, which houses the <emphasis
</listitem>
<listitem>
- <para>Mount the AFS CD-ROM for any system type on the local <emphasis role="bold">/cdrom</emphasis> directory, if one is
- not already. For instructions on mounting CD-ROMs (either locally or remotely via NFS), consult the operating system
- documentation. <indexterm>
+ <para>Unpack the OpenAFS documentation distribution into the
+ <emphasis role="bold">/tmp/afsdocs</emphasis> directory. You may use
+ a different directory, in which case the location you use should be
+ subsituted in the following examples. For instructions on unpacking
+ the distribution, consult the documentation for your operating
+ system's <emphasis role="bold">tar</emphasis> command.
+ <indexterm>
<primary>copying</primary>
- <secondary>AFS documentation from CD-ROM</secondary>
+ <secondary>AFS documentation from distribution</secondary>
</indexterm> <indexterm>
- <primary>CD-ROM</primary>
+ <primary>OpenAFS Distribution</primary>
<secondary>copying AFS documentation from</secondary>
</indexterm> <indexterm>
<secondary>copying</secondary>
- <tertiary>AFS documentation from CD-ROM</tertiary>
+ <tertiary>AFS documentation from OpenAFS distribution</tertiary>
</indexterm> <indexterm>
<primary>index.htm file</primary>
</indexterm> <indexterm>
</listitem>
<listitem>
- <para>Copy the AFS documents in one or more formats from the CD-ROM into subdirectories of the <emphasis
+ <para>Copy the AFS documents in one or more formats from the unpacked distribution into subdirectories of the <emphasis
role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/afsdoc</emphasis> directory. Repeat
the commands for each format. <programlisting>
# <emphasis role="bold">mkdir</emphasis> <replaceable>format_name</replaceable>
# <emphasis role="bold">cd</emphasis> <replaceable>format_name</replaceable>
- # <emphasis role="bold">cp -rp /cdrom/Documentation/</emphasis><replaceable>format</replaceable> <emphasis role="bold">.</emphasis>
+ # <emphasis role="bold">cp -rp /tmp/afsdocs/</emphasis><replaceable>format</replaceable> <emphasis role="bold">.</emphasis>
</programlisting></para>
<para>If you choose to store the HTML version of the documents in AFS, note that in addition to a subdirectory for each
<sect1 id="HDRWQ91">
<title>Enabling Access to Foreign Cells</title>
-
+
+ <para>With current OpenAFS releases, there exist a number of mechanisms for
+ providing access to foreign cells. You may add mount points in your AFS
+ filespace for each foreign cell you wish users to access, or you can
+ enable a 'synthetic' AFS root, which contains mountpoints for either all
+ AFS cells defined in the client machine's local
+ <emphasis role="bold">/usr/vice/etc/CellServDB</emphasis>, or for all cells
+ providing location information in the DNS.
+ </para>
+
+ <sect2>
+ <title>Enabling a Synthetic AFS root</title>
+
+ <para>When a synthetic root is enabled, the client cache machine creates its
+ own root.afs volume, rather than using the one provided with your cell. This
+ allows clients to access all cells in the
+ <emphasis role="bold">CellServDB</emphasis> file and, optionally, all cells
+ registered in the DNS, without requiring system administrator action to
+ enable this access. Using a synthetic root has the additional advantage that
+ it allows a client to start its AFS service without a network available, as
+ it is no longer necessary to contact a fileserver to obtain the root volume.
+ </para>
+
+ <para>OpenAFS supports two complimentary mechanisms for creating the
+ synthetic root. Starting the cache manager with the
+ <emphasis role="bold">-dynroot</emphasis> option adds all cells listed
+ in <emphasis role="bold">/usr/vice/etc/CellServDB</emphasis> to the client's
+ AFS root. Adding the <emphasis role="bold">-afsdb</emphasis> option in
+ addition to this enables DNS lookups for any cells that are not found in
+ the client's CellServDB file. Both of these options are added to the AFS
+ initialisation script, or options file, as detailed in
+ <link linkend="HDRWQ70">Configuring the Cache Manager</link>.</para>
+ </sect2>
+ <sect2>
+ <title>Adding foreign cells to a conventional root volume</title>
+
<para>In this section you create a mount point in your AFS filespace for the <emphasis role="bold">root.cell</emphasis> volume
of each foreign cell that you want to enable your users to access. For users working on a client machine to access the cell,
there must in addition be an entry for it in the client machine's local <emphasis
the cells that had agreed to participate in the AFS global namespace at the time your AFS CD-ROM was created. As mentioned in
that section, the AFS Product Support group also maintains a copy of the file, updating it as necessary.)</para>
- <para>The chapter in the <emphasis>IBM AFS Administration Guide</emphasis> about cell administration and configuration issues
+ <para>The chapter in the <emphasis>OpenAFS Administration Guide</emphasis> about cell administration and configuration issues
discusses the implications of participating in the global AFS namespace. The chapter about administering client machines
explains how to maintain knowledge of foreign cells on client machines, and includes suggestions for maintaining a central
version of the file in AFS. <orderedlist>
</indexterm>
</listitem>
- <listitem>
- <para><anchor id="LIWQ92" />If this machine is going to remain an AFS client after you complete the installation, verify
+ <listitem id="LIWQ92">
+ <para>If this machine is going to remain an AFS client after you complete the installation, verify
that the local <emphasis role="bold">/usr/vice/etc/CellServDB</emphasis> file includes an entry for each foreign
cell.</para>
# <emphasis role="bold">ls /afs/</emphasis><replaceable>foreign_cell</replaceable>
</programlisting></para>
</listitem>
-
+
+ <listitem>
+ <para>If you wish to participate in the global AFS namespace, and only
+ intend running one database server, please
+ register your cell with grand.central.org at this time.
+ To do so, email the <emphasis role="bold">CellServDB</emphasis> fragment
+ describing your cell, together with a contact name and email address
+ for any queries, to cellservdb@grand.central.org. If you intend
+ on deploying multiple database servers, please wait until you have
+ installed all of them before registering your cell.</para>
+ </listitem>
<listitem>
- <para>Please register your cell with the AFS Product Support group at this time. If you do not want to participate in the
- global AFS namespace, they list your cell in a private <emphasis role="bold">CellServDB</emphasis> file that is not
- available to other AFS cells.</para>
+ <para>If you wish to allow your cell to be located through DNS lookups,
+ at this time you should also add the necessary configuration to your
+ DNS.</para>
+
+ <para>AFS database servers may be located by creating AFSDB records
+ in the DNS for the domain name corresponding to the name of your cell.
+ It's outside the scope of this guide to give an indepth description of
+ managing, or configuring, your site's DNS. You should consult the
+ documentation for your DNS server for further details on AFSDB
+ records.</para>
</listitem>
</orderedlist></para>
+ </sect2>
+ </sect1>
+
+ <sect1 id="HDRWQ93">
+ <title>Improving Cell Security</title>
<indexterm>
<primary>cell</primary>
<secondary>controlling access by root superuser</secondary>
</indexterm>
- </sect1>
-
- <sect1 id="HDRWQ93">
- <title>Improving Cell Security</title>
- <para>This section discusses ways to improve the security of AFS data in your cell. Also see the chapter in the <emphasis>IBM
- AFS Administration Guide</emphasis> about configuration and administration issues.</para>
+ <para>This section discusses ways to improve the security of AFS data
+ in your cell. Also see the chapter in the <emphasis>OpenAFS
+ Administration Guide</emphasis> about configuration and administration
+ issues.</para>
<sect2 id="HDRWQ94">
<title>Controlling root Access</title>
<para>Following are suggestions for managing AFS administrative privilege: <itemizedlist>
<listitem>
- <para>Create an administrative account for each administrator named something like
- <replaceable>username</replaceable><emphasis role="bold">.admin</emphasis>. Administrators authenticate under these
- identities only when performing administrative tasks, and destroy the administrative tokens immediately after finishing
- the task (either by issuing the <emphasis role="bold">unlog</emphasis> command, or the <emphasis
- role="bold">klog</emphasis> command to adopt their regular identity).</para>
+ <para>Create an administrative account for each administrator named
+ something like
+ <replaceable>username</replaceable><emphasis role="bold">.admin</emphasis>.
+ Administrators authenticate under these identities only when
+ performing administrative tasks, and destroy the administrative
+ tokens immediately after finishing the task (either by issuing the
+ <emphasis role="bold">unlog</emphasis> command, or the
+ <emphasis role="bold">kinit</emphasis> and
+ <emphasis role="bold">aklog</emphasis> commands to adopt their
+ regular identity).</para>
</listitem>
<listitem>
- <para>Set a short ticket lifetime for administrator accounts (for example, 20 minutes) by using the <emphasis
- role="bold">-lifetime</emphasis> argument to the <emphasis role="bold">kas setfields</emphasis> command, which is
- described in the <emphasis>IBM AFS Administration Reference</emphasis>. Do not however, use a short lifetime for users
+ <para>Set a short ticket lifetime for administrator accounts (for example, 20 minutes) by using the
+ facilities of your KDC. For instance, with a MIT Kerberos KDC, this
+ can be performed using the
+ <emphasis role="bold">--max-ticket-life</emphasis> argument to
+ the <emphasis role="bold">kadmin modify_principal</emphasis>
+ command. Do not however, use a short lifetime for users
who issue long-running <emphasis role="bold">backup</emphasis> commands.</para>
</listitem>
</listitem>
<listitem>
- <para>On IRIX systems, issue the <emphasis role="bold">chkconfig</emphasis> command to deactivate the <emphasis
- role="bold">afsclient</emphasis> configuration variable. <programlisting>
- # <emphasis role="bold">/etc/chkconfig -f afsclient off</emphasis>
-</programlisting></para>
- </listitem>
-
- <listitem>
<para>Reboot the machine. Most system types use the <emphasis role="bold">shutdown</emphasis> command, but the appropriate
options vary. <programlisting>
# <emphasis role="bold">cd /</emphasis>
</listitem>
</orderedlist></para>
</sect1>
-</chapter>
\ No newline at end of file
+</chapter>
git://git.openafs.org / openafs.git / blobdiff