2006-09-16 02:13:22 +01:00
<?xml version="1.0" encoding="UTF-8"?>
<chapter id= "HDRWQ133" >
<title > Installing Additional Client Machines</title>
2011-06-07 19:26:11 +01:00
<para >
2006-09-16 02:13:22 +01:00
<indexterm >
<primary > instructions</primary>
<secondary > client machine</secondary>
</indexterm>
<indexterm >
<primary > installing</primary>
<secondary > client functionality</secondary>
<tertiary > client machine</tertiary>
</indexterm>
2011-06-07 19:26:11 +01:00
This chapter describes how to install AFS client machines after you have installed the first AFS machine. Some parts of the
2006-09-16 02:13:22 +01:00
installation differ depending on whether or not the new client is of the same AFS system type (uses the same AFS binaries) as a
previously installed client machine. <indexterm >
<primary > overview</primary>
<secondary > installing client machine</secondary>
</indexterm> </para>
<sect1 id= "Header_116" >
<title > Summary of Procedures</title>
<orderedlist >
<listitem >
<para > Incorporate AFS into the machine's kernel</para>
</listitem>
<listitem >
<para > Define the machine's cell membership</para>
</listitem>
<listitem >
<para > Define cache location and size</para>
</listitem>
<listitem >
<para > Create the <emphasis role= "bold" > /usr/vice/etc/CellServDB</emphasis> file, which determines which foreign cells the
client can access in addition to the local cell</para>
</listitem>
<listitem >
<para > Create the <emphasis role= "bold" > /afs</emphasis> directory and start the Cache Manager</para>
</listitem>
<listitem >
<para > Create and mount volumes for housing AFS client binaries (necessary only for clients of a new system type)</para>
</listitem>
<listitem >
<para > Create a link from the local <emphasis role= "bold" > /usr/afsws</emphasis> directory to the AFS directory housing the
AFS client binaries</para>
</listitem>
<listitem >
<para > Modify the machine's authentication system to enable AFS users to obtain tokens at login</para>
</listitem>
</orderedlist>
<indexterm >
2007-04-24 05:37:52 +01:00
<primary > Binary Distribution</primary>
2006-09-16 02:13:22 +01:00
2007-04-24 05:37:52 +01:00
<secondary > creating /tmp/afsdist directory</secondary>
2006-09-16 02:13:22 +01:00
<tertiary > client machine</tertiary>
</indexterm>
<indexterm >
2007-04-24 05:37:52 +01:00
<primary > afsdist directory</primary>
2006-09-16 02:13:22 +01:00
<secondary > client machine</secondary>
</indexterm>
<indexterm >
<primary > client machine</primary>
2007-04-24 05:37:52 +01:00
<secondary > /tmp/afsdist directory</secondary>
2006-09-16 02:13:22 +01:00
</indexterm>
<indexterm >
<primary > creating</primary>
2007-04-24 05:37:52 +01:00
<secondary > /tmp/afsdist directory</secondary>
2006-09-16 02:13:22 +01:00
<tertiary > client machine</tertiary>
</indexterm>
<indexterm >
<primary > usr/vice/etc directory</primary>
<secondary > client machine</secondary>
</indexterm>
<indexterm >
<primary > client machine</primary>
<secondary > /usr/vice/etc directory</secondary>
</indexterm>
<indexterm >
<primary > creating</primary>
<secondary > /usr/vice/etc directory</secondary>
<tertiary > client machine</tertiary>
</indexterm>
</sect1>
<sect1 id= "HDRWQ134" >
<title > Creating AFS Directories on the Local Disk</title>
2007-04-24 05:37:52 +01:00
<para > If you are not installing from a packaged distribution, create the <emphasis role= "bold" > /usr/vice/etc</emphasis> directory on the local disk, to house client binaries and
configuration files. Subsequent instructions copy files from the OpenAFS binary distribution into them. Create the <emphasis
role="bold">/tmp/afsdist</emphasis> directory as a location to uncompress this distribution, if it does not already exist.</para>
2006-09-16 02:13:22 +01:00
<programlisting >
# <emphasis role= "bold" > mkdir /usr/vice</emphasis>
# <emphasis role= "bold" > mkdir /usr/vice/etc</emphasis>
2007-04-24 05:37:52 +01:00
# <emphasis role= "bold" > mkdir /tmp/afsdist</emphasis>
2006-09-16 02:13:22 +01:00
</programlisting>
</sect1>
<sect1 id= "HDRWQ135" >
<title > Performing Platform-Specific Procedures</title>
<para > Every AFS client machine's kernel must incorporate AFS modifications. Some system types use a dynamic kernel loader
program, whereas on other system types you build AFS modifications into a static kernel. Some system types support both
methods.</para>
<para > Also 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
2007-04-24 05:37:52 +01:00
must perform a two or three step login procedure (login to the local system, obtain Kerberos credentials, and then issue the <emphasis role= "bold" > klog</emphasis>
2006-12-02 03:56:17 +00:00
command). For further discussion of AFS authentication, see the chapter in the <emphasis > OpenAFS Administration Guide</emphasis>
2006-09-16 02:13:22 +01:00
about cell configuration and administration issues.</para>
<para > For convenience, the following sections group the two procedures by system type. Proceed to the appropriate section.
<itemizedlist >
<listitem >
<para > <link linkend= "HDRWQ136" > Getting Started on AIX Systems</link> </para>
</listitem>
<listitem >
<para > <link linkend= "HDRWQ138" > Getting Started on HP-UX Systems</link> </para>
</listitem>
<listitem >
<para > <link linkend= "HDRWQ139" > Getting Started on IRIX Systems</link> </para>
</listitem>
<listitem >
<para > <link linkend= "HDRWQ143" > Getting Started on Linux Systems</link> </para>
</listitem>
<listitem >
<para > <link linkend= "HDRWQ144" > Getting Started on Solaris Systems</link> </para>
</listitem>
</itemizedlist> </para>
<indexterm >
<primary > incorporating AFS kernel extensions</primary>
<secondary > client machine</secondary>
<tertiary > AIX</tertiary>
</indexterm>
<indexterm >
<primary > AFS kernel extensions</primary>
<secondary > on client machine</secondary>
<tertiary > AIX</tertiary>
</indexterm>
<indexterm >
<primary > client machine</primary>
<secondary > AFS kernel extensions</secondary>
<tertiary > on AIX</tertiary>
</indexterm>
<indexterm >
<primary > AIX</primary>
<secondary > AFS kernel extensions</secondary>
<tertiary > on client machine</tertiary>
</indexterm>
<indexterm >
<primary > enabling AFS login</primary>
<secondary > client machine</secondary>
<tertiary > AIX</tertiary>
</indexterm>
<indexterm >
<primary > AFS login</primary>
<secondary > on client machine</secondary>
<tertiary > AIX</tertiary>
</indexterm>
<indexterm >
<primary > client machine</primary>
<secondary > AFS login</secondary>
<tertiary > on AIX</tertiary>
</indexterm>
<indexterm >
<primary > AIX</primary>
<secondary > AFS login</secondary>
<tertiary > on client machine</tertiary>
</indexterm>
<indexterm >
<primary > secondary authentication system (AIX)</primary>
<secondary > client machine</secondary>
</indexterm>
</sect1>
<sect1 id= "HDRWQ136" >
<title > Getting Started on AIX Systems</title>
<para > In this section you load AFS into the AIX kernel. Then incorporate AFS modifications into the machine's secondary
authentication system, if you wish to enable AFS login.</para>
<sect2 id= "Header_120" >
<title > Loading AFS into the AIX Kernel</title>
<para > The AIX kernel extension facility is the dynamic kernel loader provided by IBM Corporation. AIX 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 > After editing the script, you run it to incorporate AFS into the kernel. In a later section you verify that the script
correctly initializes the Cache Manager, then configure the AIX <emphasis role= "bold" > inittab</emphasis> file so that the
script runs automatically at reboot. <orderedlist >
<listitem >
2007-04-24 05:37:52 +01:00
<para > Unpack the 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 different location, substitute this in all of the following
examples. Once you have unpacked the distribution,
change directory as indicated.
<programlisting >
# <emphasis role= "bold" > cd /tmp/afsdist/rs_aix42/root.client/usr/vice/etc</emphasis>
2006-09-16 02:13:22 +01:00
</programlisting> </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>
</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
</programlisting>
</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>
</programlisting> </para>
</listitem>
</orderedlist> </para>
</sect2>
<sect2 id= "Header_121" >
<title > Enabling AFS Login on AIX Systems</title>
2007-04-24 05:37:52 +01:00
<para > In modern AFS installations, you should be using Kerberos v5
for user login, and obtaining AFS tokens following this authentication
step.</para>
<para > There are currently no instructions available on configuring AIX to
automatically obtain AFS tokens at login. Following login, users can
obtain tokens by running the <emphasis role= "bold" > aklog</emphasis>
command</para>
2006-09-16 02:13:22 +01:00
2007-04-24 05:37:52 +01:00
<para > Sites which still require <emphasis role= "bold" > kaserver</emphasis>
or external Kerberos v4 authentication should consult
<link linkend= "KAS012" > Enabling kaserver based AFS Login on AIX Systems</link>
for details of how to enable AIX login.</para>
2006-09-16 02:13:22 +01:00
2007-04-24 05:37:52 +01:00
<para > <orderedlist >
2006-09-16 02:13:22 +01:00
<listitem >
<para > Proceed to <link linkend= "HDRWQ145" > Loading and Creating Client Files</link> .</para>
</listitem>
</orderedlist> </para>
<indexterm >
<primary > incorporating AFS kernel extensions</primary>
<secondary > client machine</secondary>
<tertiary > HP-UX</tertiary>
</indexterm>
<indexterm >
<primary > AFS kernel extensions</primary>
<secondary > on client machine</secondary>
<tertiary > HP-UX</tertiary>
</indexterm>
<indexterm >
<primary > client 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 client machine</tertiary>
</indexterm>
<indexterm >
<primary > enabling AFS login</primary>
<secondary > client machine</secondary>
<tertiary > HP-UX</tertiary>
</indexterm>
<indexterm >
<primary > AFS login</primary>
<secondary > on client machine</secondary>
<tertiary > HP-UX</tertiary>
</indexterm>
<indexterm >
<primary > client machine</primary>
<secondary > AFS login</secondary>
<tertiary > on HP-UX</tertiary>
</indexterm>
<indexterm >
<primary > HP-UX</primary>
<secondary > AFS login</secondary>
<tertiary > on client machine</tertiary>
</indexterm>
<indexterm >
<primary > PAM</primary>
<secondary > on HP-UX</secondary>
<tertiary > client machine</tertiary>
</indexterm>
</sect2>
</sect1>
<sect1 id= "HDRWQ138" >
<title > Getting Started on HP-UX Systems</title>
<para > In this section you build AFS into the HP-UX kernel. Then incorporate AFS modifications into the machine's Pluggable
Authentication Module (PAM) system, if you wish to enable AFS login.</para>
<sect2 id= "Header_126" >
<title > Building AFS into the HP-UX Kernel</title>
<para > On HP-UX systems, you must build AFS modifications into a new static kernel; HP-UX does not support dynamic loading. If
the machine's hardware and software configuration exactly matches another HP-UX machine on which AFS is already built into the
kernel, you can choose to copy the kernel from that machine to this one. In general, however, it is better to build AFS
modifications into the kernel on each machine according to the following instructions. <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 >
2007-04-24 05:37:52 +01:00
<para > Unpack the OpenAFS HP-UX 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 different location, substitute this in all of the following
examples. Once you have unpacked the distribution, change directory
as indicated.
2006-09-16 02:13:22 +01:00
<programlisting >
2007-04-24 05:37:52 +01:00
# <emphasis role= "bold" > cd /tmp/afsdist/hp_ux110/root.client</emphasis>
2006-09-16 02:13:22 +01:00
</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>
</sect2>
<sect2 id= "Header_127" >
<title > Enabling AFS Login on HP-UX Systems</title>
<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>
2007-04-24 05:37:52 +01:00
<para > In modern AFS installations, you should be using Kerberos v5
for user login, and obtaining AFS tokens subsequent to this authentication
step. OpenAFS does not currently distribute a PAM module allowing AFS
tokens to be automatically gained at login. Whilst there are a number of
third party modules providing this functionality, it is not know if these
have been tested with HP/UX.</para>
<para > Following login, users can
obtain tokens by running the <emphasis role= "bold" > aklog</emphasis>
command</para>
<para > If you are at a site which still requires
<emphasis role= "bold" > kaserver</emphasis> or external Kerberos v4 based
authentication, please consult
<link linkend= "KAS014" > Enabling kaserver based AFS Login on HP-UX systems</link>
for further installation instructions.
<orderedlist >
2006-09-16 02:13:22 +01:00
<listitem >
<para > Proceed to <link linkend= "HDRWQ145" > Loading and Creating Client Files</link> .</para>
</listitem>
2007-04-24 05:37:52 +01:00
</orderedlist>
</para>
2006-09-16 02:13:22 +01:00
<indexterm >
<primary > incorporating AFS kernel extensions</primary>
<secondary > client machine</secondary>
<tertiary > IRIX</tertiary>
</indexterm>
<indexterm >
<primary > AFS kernel extensions</primary>
<secondary > on client machine</secondary>
<tertiary > IRIX</tertiary>
</indexterm>
<indexterm >
<primary > client machine</primary>
<secondary > AFS kernel extensions</secondary>
<tertiary > on IRIX</tertiary>
</indexterm>
</sect2>
</sect1>
<sect1 id= "HDRWQ139" >
<title > Getting Started on IRIX Systems</title>
<para > In this section you incorporate AFS into the IRIX kernel, choosing one of two methods: <itemizedlist >
<listitem >
<para > Dynamic loading using the <emphasis role= "bold" > ml</emphasis> program distributed by Silicon Graphics, Incorporated
(SGI).</para>
</listitem>
<listitem >
<para > Building a new static kernel.</para>
</listitem>
</itemizedlist> </para>
<para > Then see <link linkend= "HDRWQ142" > Enabling AFS Login on IRIX Systems</link> to read about integrated AFS login on IRIX
systems.</para>
<para > In preparation for either dynamic loading or kernel building, perform the following procedures: <orderedlist >
<listitem >
2007-04-24 05:37:52 +01:00
<para > Unpack the OpenAFS IRIX 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 different location, substitue this in all of the following
examples. Once you have unpacked the distribution, change directory
as indicated.
<programlisting >
# <emphasis role= "bold" > cd /tmp/afsdist/sgi_65/root.client</emphasis>
2006-09-16 02:13:22 +01:00
</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
2006-12-02 03:56:17 +00:00
listed in the <emphasis > OpenAFS Release Notes</emphasis> for the current version of AFS. <programlisting >
2006-09-16 02:13:22 +01:00
# <emphasis role= "bold" > uname -m</emphasis>
</programlisting> </para>
</listitem>
<listitem >
<para > Proceed to either <link linkend= "HDRWQ140" > Loading AFS into the IRIX Kernel</link> or <link
linkend="HDRWQ141">Building AFS into the IRIX Kernel</link> .</para>
</listitem>
</orderedlist> </para>
<indexterm >
<primary > IRIX</primary>
<secondary > AFS kernel extensions</secondary>
<tertiary > on client machine</tertiary>
</indexterm>
<indexterm >
<primary > afsml variable (IRIX)</primary>
<secondary > client machine</secondary>
</indexterm>
<indexterm >
<primary > variables</primary>
<secondary > afsml (IRIX)</secondary>
<tertiary > client machine</tertiary>
</indexterm>
<indexterm >
<primary > IRIX</primary>
<secondary > afsml variable</secondary>
<tertiary > client machine</tertiary>
</indexterm>
<indexterm >
<primary > afsxnfs variable (IRIX)</primary>
<secondary > client machine</secondary>
</indexterm>
<indexterm >
<primary > variables</primary>
<secondary > afsxnfs (IRIX)</secondary>
<tertiary > client machine</tertiary>
</indexterm>
<indexterm >
<primary > IRIX</primary>
<secondary > afsxnfs variable</secondary>
<tertiary > client machine</tertiary>
</indexterm>
<sect2 id= "HDRWQ140" >
<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
2007-04-24 05:37:52 +01:00
in the OpenAFS Binary Distribution) invokes it automatically when the <emphasis role= "bold" > afsml</emphasis> configuration variable is
2006-09-16 02:13:22 +01:00
activated. In this section you activate the variable and run the script.</para>
<para > In a later section you verify that the script correctly initializes the Cache Manager, 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= "HDRWQ142" > Enabling AFS Login on IRIX Systems</link> .</para>
</listitem>
</orderedlist> </para>
<indexterm >
<primary > IRIX</primary>
<secondary > AFS-modified kernel</secondary>
<tertiary > on client machine</tertiary>
</indexterm>
</sect2>
<sect2 id= "HDRWQ141" >
<title > Building AFS into the IRIX Kernel</title>
<para > If you prefer to build a kernel, and the machine's hardware and software configuration exactly matches another IRIX
machine on which AFS is already built into the kernel, you can choose to copy the kernel from that machine to this one. In
general, however, it is better to build AFS modifications into the kernel on each machine according to the following
instructions. <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>
<listitem >
<para > Proceed to <link linkend= "HDRWQ142" > Enabling AFS Login on IRIX Systems</link> .</para>
</listitem>
</orderedlist> </para>
<indexterm >
<primary > enabling AFS login</primary>
<secondary > client machine</secondary>
<tertiary > IRIX</tertiary>
</indexterm>
<indexterm >
<primary > AFS login</primary>
<secondary > on client machine</secondary>
<tertiary > IRIX</tertiary>
</indexterm>
<indexterm >
<primary > client machine</primary>
<secondary > AFS login</secondary>
<tertiary > on IRIX</tertiary>
</indexterm>
</sect2>
<sect2 id= "HDRWQ142" >
<title > Enabling AFS Login on IRIX Systems</title>
2007-04-24 05:37:52 +01:00
<para > Whilst the standard IRIX command-line
<emphasis role= "bold" > login</emphasis> program and the
graphical <emphasis role= "bold" > xdm</emphasis> login program both have
the ability to grant AFS tokens, this ability relies upon the deprecated
kaserver authentication system. As this system is not recommended for
new installations, this is not documented here.</para>
<para > Users who have been successfully authenticated via Kerberos 5
authentication may obtain AFS tokens following login by running the
<emphasis role= "bold" > aklog</emphasis> command.</para>
<para > If you are at a site which still requires
<emphasis role= "bold" > kaserver</emphasis> or external Kerberos v4 based
authentication, please consult
<link linkend= "KAS014" > Enabling kaserver based AFS Login on Linux Systems</link>
for further installation instructions.</para>
<para > Proceed to <link linkend= "HDRWQ145" > Loading and Creating Client Files</link> .
2006-09-16 02:13:22 +01:00
<indexterm >
<primary > incorporating AFS kernel extensions</primary>
<secondary > client machine</secondary>
<tertiary > Linux</tertiary>
</indexterm> <indexterm >
<primary > AFS kernel extensions</primary>
<secondary > on client machine</secondary>
<tertiary > Linux</tertiary>
</indexterm> <indexterm >
<primary > client machine</primary>
<secondary > AFS kernel extensions</secondary>
<tertiary > on Linux</tertiary>
</indexterm> <indexterm >
<primary > Linux</primary>
<secondary > AFS kernel extensions</secondary>
<tertiary > on client machine</tertiary>
</indexterm> <indexterm >
<primary > enabling AFS login</primary>
<secondary > client machine</secondary>
<tertiary > Linux</tertiary>
</indexterm> <indexterm >
<primary > AFS login</primary>
<secondary > on client machine</secondary>
<tertiary > Linux</tertiary>
</indexterm> <indexterm >
<primary > client machine</primary>
<secondary > AFS login</secondary>
<tertiary > on Linux</tertiary>
</indexterm> <indexterm >
<primary > Linux</primary>
<secondary > AFS login</secondary>
<tertiary > on client machine</tertiary>
</indexterm> <indexterm >
<primary > PAM</primary>
<secondary > on Linux</secondary>
<tertiary > client machine</tertiary>
</indexterm> </para>
</sect2>
</sect1>
<sect1 id= "HDRWQ143" >
<title > Getting Started on Linux Systems</title>
<para > In this section you load AFS into the Linux kernel. Then incorporate AFS modifications into the machine's Pluggable
Authentication Module (PAM) system, if you wish to enable AFS login.</para>
<sect2 id= "Header_133" >
<title > Loading AFS into the Linux Kernel</title>
2007-04-24 05:37:52 +01:00
<para > The <emphasis role= "bold" > modprobe</emphasis> program is the dynamic kernel loader for Linux. Linux does not support
2006-09-16 02:13:22 +01:00
incorporation of AFS modifications during a kernel build.</para>
2007-04-24 05:37:52 +01:00
<para > For AFS to function correctly, the <emphasis role= "bold" > modprobe</emphasis> program must run each time the machine
reboots, so your distributions's AFS initialization script invokes it automatically. The script also includes
2006-09-16 02:13:22 +01:00
commands that select the appropriate AFS library file automatically. In this section you run the script.</para>
<para > In a later section you also verify that the script correctly initializes the Cache Manager, then activate a
2007-04-24 05:37:52 +01:00
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 ships RPMS for all current Fedora and RHEL releases.
<orderedlist >
<listitem >
<para > Download and install the RPM set for your operating system.
RPMs are available from the OpenAFS web site. You will need the
2010-10-05 17:46:35 +01:00
<emphasis role= "bold" > openafs</emphasis> , <emphasis role= "bold" > openafs-server</emphasis> ,
<emphasis role= "bold" > openafs-client</emphasis> and
<emphasis role= "bold" > openafs-krb5</emphasis> packages, along
with an <emphasis role= "bold" > kmod-openafs</emphasis> package
2007-04-24 05:37:52 +01:00
matching your current, running ,kernel.</para>
<para > You can find the version of your current kernel by running
<programlisting >
# uname -r
<replaceable > 2.6.20-1.2933.fc6</replaceable>
</programlisting> </para>
<para > Once downloaded, the packages may be installed with the
<emphasis role= "bold" > rpm</emphasis> command
<programlisting >
2010-10-05 17:46:35 +01:00
# rpm -U openafs-* openafs-client-* openafs-server-* openafs-krb5-* kmod-openafs-*
2007-04-24 05:37:52 +01:00
</programlisting> </para>
</listitem>
</orderedlist>
</para>
</sect3>
<sect3 >
<title > Systems packaged as tar files</title>
<para > If you are running a system where the OpenAFS Binary Distribution
is provided as a tar file, or 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 unpacked the files into 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 unpacked the distribution,
change directory as indicated.
<programlisting >
# <emphasis role= "bold" > cd /tmp/afsdist/linux/root.client/usr/vice/etc</emphasis>
2006-09-16 02:13:22 +01:00
</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>
2007-04-24 05:37:52 +01:00
<!--
2006-09-16 02:13:22 +01:00
<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>
2007-04-24 05:37:52 +01:00
-->
</orderedlist>
</sect3>
2006-09-16 02:13:22 +01:00
</sect2>
<sect2 id= "Header_134" >
<title > Enabling AFS Login on Linux Systems</title>
<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>
2007-04-24 05:37:52 +01:00
<para > At this time, we recommend that new sites requiring AFS credentials
to be gained as part of PAM authentication use Russ Alberry's
pam_afs_session, rather than utilising the bundled pam_afs2 module.
A typical PAM stack should authenticate the user using an external
Kerberos V service, and then use the AFS PAM module to obtain AFS
credentials in the <computeroutput > session</computeroutput> section</para>
2006-09-16 02:13:22 +01:00
2007-04-24 05:37:52 +01:00
<para > If you are at a site which still requires
<emphasis role= "bold" > kaserver</emphasis> or external Kerberos v4 based
authentication, please consult
<link linkend= "KAS015" > Enabling kaserver based AFS Login on Linux Systems</link>
for further installation instructions.</para>
<para > Proceed to
<link linkend= "HDRWQ145" > Loading and Creating Client Files</link> .</para>
2006-09-16 02:13:22 +01:00
<indexterm >
<primary > incorporating AFS kernel extensions</primary>
<secondary > client machine</secondary>
<tertiary > Solaris</tertiary>
</indexterm>
<indexterm >
<primary > AFS kernel extensions</primary>
<secondary > on client machine</secondary>
<tertiary > Solaris</tertiary>
</indexterm>
<indexterm >
<primary > client machine</primary>
<secondary > AFS kernel extensions</secondary>
<tertiary > on Solaris</tertiary>
</indexterm>
<indexterm >
<primary > Solaris</primary>
<secondary > AFS kernel extensions</secondary>
<tertiary > on client machine</tertiary>
</indexterm>
<indexterm >
<primary > enabling AFS login</primary>
<secondary > client machine</secondary>
<tertiary > Solaris</tertiary>
</indexterm>
<indexterm >
<primary > AFS login</primary>
<secondary > on client machine</secondary>
<tertiary > Solaris</tertiary>
</indexterm>
<indexterm >
<primary > client machine</primary>
<secondary > AFS login</secondary>
<tertiary > on Solaris</tertiary>
</indexterm>
<indexterm >
<primary > Solaris</primary>
<secondary > AFS login</secondary>
<tertiary > on client machine</tertiary>
</indexterm>
<indexterm >
<primary > PAM</primary>
<secondary > on Solaris</secondary>
<tertiary > client machine</tertiary>
</indexterm>
<indexterm >
<primary > Solaris</primary>
<secondary > file systems clean-up script</secondary>
<tertiary > on client machine</tertiary>
</indexterm>
<indexterm >
<primary > file systems clean-up script (Solaris)</primary>
<secondary > client machine</secondary>
</indexterm>
<indexterm >
<primary > scripts</primary>
<secondary > file systems clean-up (Solaris)</secondary>
<tertiary > client machine</tertiary>
</indexterm>
</sect2>
</sect1>
<sect1 id= "HDRWQ144" >
<title > Getting Started on Solaris Systems</title>
<para > In this section you load AFS into the Solaris kernel. Then incorporate AFS modifications into the machine's Pluggable
Authentication Module (PAM) system, if you wish to enable AFS login.</para>
<sect2 id= "Header_136" >
<title > Loading AFS into the Solaris Kernel</title>
<para > The <emphasis role= "bold" > modload</emphasis> program is the dynamic kernel loader provided by Sun Microsystems for
Solaris systems. Solaris does not support incorporation of AFS modifications during a kernel build.</para>
<para > For AFS to function correctly, the <emphasis role= "bold" > modload</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" > modload</emphasis> program accesses it and then
run the script.</para>
<para > In a later section you verify that the script correctly initializes the Cache Manager, then create the links that
incorporate AFS into the Solaris startup and shutdown sequence. <orderedlist >
<listitem >
2007-04-24 05:37:52 +01:00
<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/root.client/usr/vice/etc</emphasis>
2006-09-16 02:13:22 +01:00
</programlisting> </para>
2007-04-24 05:37:52 +01:00
</listitem>
2006-09-16 02:13:22 +01:00
<listitem >
<para > Copy the AFS initialization script to the local directory for initialization files (by convention, <emphasis
role="bold">/etc/init.d</emphasis> on Solaris 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/init.d/afs</emphasis>
</programlisting> </para>
</listitem>
<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 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>
<programlisting >
# <emphasis role= "bold" > cp -p modload/libafs.o /kernel/fs/afs</emphasis>
</programlisting>
<para > If the machine is running Solaris 2.6 or the 32-bit version of Solaris 7, and its kernel does not support NFS
server functionality or the <emphasis role= "bold" > nfsd</emphasis> process is not running:</para>
<programlisting >
# <emphasis role= "bold" > cp -p modload/libafs.nonfs.o /kernel/fs/afs</emphasis>
</programlisting>
<para > If the machine is running the 64-bit version of Solaris 7, its kernel supports NFS server functionality, and the
<emphasis role= "bold" > nfsd</emphasis> process is running:</para>
<programlisting >
# <emphasis role= "bold" > cp -p modload/libafs64.o /kernel/fs/sparcv9/afs</emphasis>
</programlisting>
<para > If the machine is running the 64-bit version of Solaris 7, and its kernel does not support NFS server
functionality or the <emphasis role= "bold" > nfsd</emphasis> process is not running:</para>
<programlisting >
# <emphasis role= "bold" > cp -p modload/libafs64.nonfs.o /kernel/fs/sparcv9/afs</emphasis>
</programlisting>
</listitem>
<listitem >
<para > Run the AFS initialization 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/init.d/afs start</emphasis>
</programlisting> </para>
<para > When an entry called <computeroutput > afs</computeroutput> does not already exist in the local <emphasis
role="bold">/etc/name_to_sysnum</emphasis> file, the script automatically creates it and reboots the machine to start
using the new version of the file. If this happens, log in again as the superuser <emphasis role= "bold" > root</emphasis>
after the reboot and run the initialization script again. This time the required entry exists in the <emphasis
role="bold">/etc/name_to_sysnum</emphasis> file, and the <emphasis role= "bold" > modload</emphasis> program runs.</para>
<programlisting >
login: <emphasis role= "bold" > root</emphasis>
Password: <replaceable > root_password</replaceable>
# <emphasis role= "bold" > /etc/init.d/afs start</emphasis>
</programlisting>
</listitem>
</orderedlist> </para>
</sect2>
<sect2 id= "Header_137" >
<title > Enabling AFS Login on Solaris Systems</title>
<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>
2007-04-24 05:37:52 +01:00
<para > In modern AFS installations, you should be using Kerberos v5
for user login, and obtaining AFS tokens subsequent to this authentication
step. OpenAFS does not currently distribute a PAM module allowing AFS
2007-04-24 05:48:04 +01:00
tokens to be automatically gained at login. Some of these, such as
pam-krb5 and pam-afs-session from http://www.eyrie.org/~eagle/software/
or pam_afs2 from ftp://achilles.ctd.anl.gov/pub/DEE/pam_afs2-0.1.tar,
2007-04-24 05:37:52 +01:00
have been tested with Solaris.</para>
<para > If you are at a site which still requires
<emphasis role= "bold" > kaserver</emphasis> or external Kerberos v4 based
authentication, please consult
<link linkend= "KAS016" > Enabling kaserver based AFS Login on Solaris Systems</link>
for further installation instructions.</para>
</sect2>
<sect2 id= "Header_137a" >
<title > Editing the File Systems Clean-up Script on Solaris Systems</title>
<para >
<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 to the
<emphasis role= "bold" > find</emphasis> command to define which file
systems to search. In this step you modify the
command to exclude the <emphasis role= "bold" > /afs</emphasis>
directory. Otherwise, the command traverses the AFS
2006-09-16 02:13:22 +01:00
filespace of every cell that is accessible from the machine, which can take many hours. The following alterations are
possibilities, but you must verify that they are appropriate for your cell.</para>
<para > The first possible alteration is to add the <emphasis role= "bold" > -local</emphasis> flag to the existing command,
so that it looks like the following:</para>
<programlisting >
find $dir -local -name .nfs\* -mtime +7 -mount -exec rm -f {} \;
</programlisting>
<para > Another alternative is to exclude any directories whose names begin with the lowercase letter <emphasis
role="bold">a</emphasis> or a non-alphabetic character.</para>
<programlisting >
find /[A-Zb-z]* <replaceable > remainder of existing command</replaceable>
</programlisting>
<para > Do not use the following command, which still searches under the <emphasis role= "bold" > /afs</emphasis> directory,
looking for a subdirectory of type <emphasis role= "bold" > 4.2</emphasis> .</para>
<programlisting >
find / -fstype 4.2 /* <replaceable > do not use</replaceable> */
</programlisting>
</listitem>
<listitem >
<para > Proceed to <link linkend= "HDRWQ145" > Loading and Creating Client Files</link> .</para>
</listitem>
</orderedlist> </para>
<indexterm >
2007-04-24 05:37:52 +01:00
<primary > Binary Distribution</primary>
2006-09-16 02:13:22 +01:00
<secondary > copying client files from</secondary>
<tertiary > client machine</tertiary>
</indexterm>
<indexterm >
<primary > client machine</primary>
<secondary > copying client files to local disk</secondary>
</indexterm>
<indexterm >
<primary > copying</primary>
<secondary > client files to local disk</secondary>
<tertiary > client machine</tertiary>
</indexterm>
<indexterm >
<primary > cell name</primary>
<secondary > setting in client ThisCell file</secondary>
<tertiary > client machine</tertiary>
</indexterm>
<indexterm >
<primary > setting</primary>
<secondary > cell name in client ThisCell file</secondary>
<tertiary > client machine</tertiary>
</indexterm>
<indexterm >
<primary > client machine</primary>
<secondary > cell membership</secondary>
</indexterm>
<indexterm >
<primary > client machine</primary>
<secondary > ThisCell file</secondary>
</indexterm>
<indexterm >
<primary > ThisCell file (client)</primary>
<secondary > client machine</secondary>
</indexterm>
<indexterm >
<primary > CellServDB file (client)</primary>
<secondary > creating</secondary>
<tertiary > on client machine</tertiary>
</indexterm>
<indexterm >
<primary > database server machine</primary>
<secondary > entry in client CellServDB file</secondary>
<tertiary > on client machine</tertiary>
</indexterm>
<indexterm >
<primary > creating</primary>
<secondary > CellServDB file (client)</secondary>
<tertiary > client machine</tertiary>
</indexterm>
<indexterm >
<primary > client machine</primary>
<secondary > CellServDB file</secondary>
<tertiary > creating during initial installation</tertiary>
</indexterm>
</sect2>
</sect1>
<sect1 id= "HDRWQ145" >
<title > Loading and Creating Client Files</title>
2007-04-24 05:37:52 +01:00
<para > If you are using a non-packaged distribution (that is, one provided as
a tarball) you should now copy files from the istribution to the
<emphasis role= "bold" > /usr/vice/etc</emphasis> directory. On some platforms
that use a dynamic loader program to incorporate AFS modifications into the
kernel, you have already copied over some the files.
2006-09-16 02:13:22 +01:00
Copying them again does no harm.</para>
<para > Every AFS client machine has a copy of the <emphasis role= "bold" > /usr/vice/etc/ThisCell</emphasis> file on its local disk
to define the machine's cell membership for the AFS client programs that run on it. Among other functions, this file 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>
</listitem>
<listitem >
2007-04-24 05:37:52 +01:00
<para > The cell in which users authenticate by default when they issue the <emphasis role= "bold" > aklog</emphasis>
2006-09-16 02:13:22 +01:00
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>
</listitem>
</itemizedlist> </para>
<para > Similarly, the <emphasis role= "bold" > /usr/vice/etc/CellServDB</emphasis> file on a client machine's local disk lists the
database server machines in each cell that the local Cache Manager can contact. If there is no entry in the file for a cell, or
the list of database server machines is wrong, then users working on this machine cannot access the cell. The chapter in the
2006-12-02 03:56:17 +00:00
<emphasis > OpenAFS Administration Guide</emphasis> about administering client machines explains how to maintain the file after
2006-09-16 02:13:22 +01:00
creating it. A version of the client <emphasis role= "bold" > CellServDB</emphasis> file was created during the installation of
your cell's first machine (in <link linkend= "HDRWQ66" > Creating the Client CellServDB File</link> ). It is probably also
appropriate for use on this machine.</para>
<para > Remember that the Cache Manager consults the <emphasis role= "bold" > /usr/vice/etc/CellServDB</emphasis> file only at
reboot, when it copies the information into the kernel. For the Cache Manager to perform properly, the <emphasis
2006-12-02 03:56:17 +00:00
role="bold">CellServDB</emphasis> file must be accurate at all times. Refer to the chapter in the <emphasis > OpenAFS
2006-09-16 02:13:22 +01:00
Administration Guide</emphasis> about administering client machines for instructions on updating this file, with or without
rebooting. <orderedlist >
<listitem >
2007-04-24 05:37:52 +01:00
<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>
2006-09-16 02:13:22 +01:00
</listitem>
<listitem >
<para > Copy files to the local <emphasis role= "bold" > /usr/vice/etc</emphasis> directory.</para>
<para > This step places a copy of the AFS initialization script (and related files, if applicable) into the <emphasis
role="bold">/usr/vice/etc</emphasis> directory. In the preceding instructions for incorporating AFS into the kernel, you
copied the script directly to the operating system's conventional location for initialization files. When you incorporate
AFS into the machine's startup sequence in a later step, you can choose to link the two files.</para>
<para > On some system types that use a dynamic kernel loader program, you previously copied AFS library files into a
subdirectory of the <emphasis role= "bold" > /usr/vice/etc</emphasis> directory. On other system types, you copied the
appropriate AFS library file directly to the directory where the operating system accesses it. The following commands do
not copy or recopy the AFS library files into the <emphasis role= "bold" > /usr/vice/etc</emphasis> directory, because on
some system types the library files consume a large amount of space. If you want to copy them, add the <emphasis
role="bold">-r</emphasis> flag to the first <emphasis role= "bold" > cp</emphasis> command and skip the second <emphasis
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" > cp -p * /usr/vice/etc</emphasis>
# <emphasis role= "bold" > cp -rp C /usr/vice/etc</emphasis>
</programlisting>
</listitem>
<listitem >
<para > Create the <emphasis role= "bold" > /usr/vice/etc/ThisCell</emphasis> file. <programlisting >
# <emphasis role= "bold" > echo "</emphasis> <replaceable > cellname</replaceable> <emphasis role= "bold" > " > /usr/vice/etc/ThisCell</emphasis>
</programlisting> </para>
</listitem>
<listitem >
2007-04-24 05:37:52 +01:00
<para > Create the
<emphasis role= "bold" > /usr/vice/etc/CellServDB</emphasis> file. Use a
network file transfer program such as
<emphasis role= "bold" > sftp</emphasis> or
<emphasis role= "bold" > scp</emphasis> to copy it from one of the
following sources, which are listed in decreasing order of
preference: <itemizedlist >
2006-09-16 02:13:22 +01:00
<listitem >
<para > Your cell's central <emphasis role= "bold" > CellServDB</emphasis> source file (the conventional location is
<emphasis role= "bold" > /afs/</emphasis> <replaceable > cellname</replaceable> <emphasis
role="bold">/common/etc/CellServDB</emphasis> )</para>
</listitem>
<listitem >
2007-04-24 05:37:52 +01:00
<para > The global <emphasis role= "bold" > CellServDB</emphasis>
file maintained at grand.central.org</para>
2006-09-16 02:13:22 +01:00
</listitem>
<listitem >
<para > An existing client machine in your cell</para>
</listitem>
<listitem >
2007-04-24 05:37:52 +01:00
<para > The <emphasis role= "bold" > CellServDB.sample</emphasis>
file included in the
<replaceable > sysname</replaceable> <emphasis role= "bold" > /root.client/usr/vice/etc</emphasis>
directory of each OpenAFS distribution; add an entry for the
local cell by following the instructions in
<link linkend= "HDRWQ66" > Creating the Client CellServDB File</link>
</para>
2006-09-16 02:13:22 +01:00
</listitem>
</itemizedlist> </para>
</listitem>
</orderedlist> </para>
<indexterm >
<primary > client cache</primary>
<see > cache</see>
</indexterm>
<indexterm >
<primary > AFS cache</primary>
<see > cache</see>
</indexterm>
<indexterm >
<primary > disk cache</primary>
<see > cache</see>
</indexterm>
<indexterm >
<primary > memory cache</primary>
<see > cache</see>
</indexterm>
<indexterm >
<primary > cache</primary>
<secondary > requirements</secondary>
</indexterm>
<indexterm >
<primary > cache</primary>
<secondary > choosing size</secondary>
</indexterm>
<indexterm >
<primary > requirements</primary>
<secondary > cache</secondary>
</indexterm>
<indexterm >
<primary > usr/vice/etc/cacheinfo</primary>
<see > cacheinfo file</see>
</indexterm>
<indexterm >
<primary > cacheinfo file</primary>
</indexterm>
<indexterm >
<primary > files</primary>
<secondary > cacheinfo</secondary>
</indexterm>
<indexterm >
<primary > usr/vice/cache directory</primary>
</indexterm>
<indexterm >
<primary > directories</primary>
<secondary > /usr/vice/cache</secondary>
</indexterm>
<indexterm >
<primary > cache</primary>
<secondary > configuring</secondary>
<tertiary > client machine</tertiary>
</indexterm>
<indexterm >
<primary > configuring</primary>
<secondary > cache</secondary>
<tertiary > client machine</tertiary>
</indexterm>
<indexterm >
<primary > setting</primary>
<secondary > cache size and location</secondary>
<tertiary > client machine</tertiary>
</indexterm>
<indexterm >
<primary > client machine</primary>
<secondary > cache size and location</secondary>
</indexterm>
</sect1>
<sect1 id= "HDRWQ146" >
<title > Configuring the Cache</title>
<para > The Cache Manager uses a cache on the local disk or in machine memory to store local copies of files fetched from file
server machines. As the <emphasis role= "bold" > afsd</emphasis> program initializes the Cache Manager, it sets basic cache
configuration parameters according to definitions in the local <emphasis role= "bold" > /usr/vice/etc/cacheinfo</emphasis> file.
The file has three fields: <orderedlist >
<listitem >
<para > The first field names the local directory on which to mount the AFS filespace. The conventional location is the
<emphasis role= "bold" > /afs</emphasis> directory.</para>
</listitem>
<listitem >
<para > The second field defines the local disk directory to use for the disk cache. The conventional location is the
<emphasis role= "bold" > /usr/vice/cache</emphasis> directory, but you can specify an alternate directory if another
partition has more space available. There must always be a value in this field, but the Cache Manager ignores it if the
machine uses a memory cache.</para>
</listitem>
<listitem >
<para > The third field specifies the number of kilobyte (1024 byte) blocks to allocate for the cache.</para>
</listitem>
</orderedlist> </para>
<para > The values you define must meet the following requirements. <itemizedlist >
<listitem >
<para > On a machine using a disk cache, the Cache Manager expects always to be able to use the amount of space specified in
the third field. Failure to meet this requirement can cause serious problems, some of which can be repaired only by
rebooting. You must prevent non-AFS processes from filling up the cache partition. The simplest way is to devote a
partition to the cache exclusively.</para>
</listitem>
<listitem >
<para > The amount of space available in memory or on the partition housing the disk cache directory imposes an absolute
limit on cache size.</para>
</listitem>
<listitem >
2006-12-02 03:56:17 +00:00
<para > The maximum supported cache size can vary in each AFS release; see the <emphasis > OpenAFS Release Notes</emphasis>
2006-09-16 02:13:22 +01:00
for the current version.</para>
</listitem>
<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
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>
<listitem >
<para > For a memory cache, you must leave enough memory for other processes and applications to run. If you try to allocate
more memory than is actually available, the <emphasis role= "bold" > afsd</emphasis> program exits without initializing the
Cache Manager and produces the following message on the standard output stream. <programlisting >
afsd: memCache allocation failure at <replaceable > number</replaceable> KB
</programlisting> </para>
<para > The <replaceable > number</replaceable> value is how many kilobytes were allocated just before the failure, and so
indicates the approximate amount of memory available.</para>
</listitem>
</itemizedlist> </para>
<para > Within these hard limits, the factors that determine appropriate cache size include the number of users working on the
machine, the size of the files with which they work, and (for a memory cache) the number of processes that run on the machine.
The higher the demand from these factors, the larger the cache needs to be to maintain good performance.</para>
<para > Disk caches smaller than 10 MB do not generally perform well. Machines serving multiple users usually perform better with
a cache of at least 60 to 70 MB. The point at which enlarging the cache further does not really improve performance depends on
the factors mentioned previously and is difficult to predict.</para>
<para > Memory caches smaller than 1 MB are nonfunctional, and the performance of caches smaller than 5 MB is usually
unsatisfactory. Suitable upper limits are similar to those for disk caches but are probably determined more by the demands on
memory from other sources on the machine (number of users and processes). Machines running only a few processes possibly can use
a smaller memory cache.</para>
<sect2 id= "HDRWQ147" >
<title > Configuring a Disk Cache</title>
<note >
<para > Not all file system types that an operating system supports are necessarily supported for use as the cache partition.
2006-12-02 03:56:17 +00:00
For possible restrictions, see the <emphasis > OpenAFS Release Notes</emphasis> .</para>
2006-09-16 02:13:22 +01:00
</note>
<para > To configure the disk cache, perform the following procedures: <orderedlist >
<listitem >
<para > Create the local directory to use for caching. The following instruction shows the conventional location,
<emphasis role= "bold" > /usr/vice/cache</emphasis> . If you are devoting a partition exclusively to caching, as
recommended, you must also configure it, make a file system on it, and mount it at the directory created in this step.
<programlisting >
# <emphasis role= "bold" > mkdir /usr/vice/cache</emphasis>
</programlisting> </para>
</listitem>
<listitem >
<para > Create the <emphasis role= "bold" > cacheinfo</emphasis> file to define the configuration parameters discussed
previously. The following instruction shows the standard mount location, <emphasis role= "bold" > /afs</emphasis> , and the
standard cache location, <emphasis role= "bold" > /usr/vice/cache</emphasis> . <programlisting >
# <emphasis role= "bold" > echo "/afs:/usr/vice/cache:</emphasis> <replaceable > #blocks</replaceable> <emphasis role= "bold" > " > /usr/vice/etc/cacheinfo</emphasis>
</programlisting> </para>
<para > The following example defines the disk cache size as 50,000 KB:</para>
<programlisting >
# <emphasis role= "bold" > echo "/afs:/usr/vice/cache:50000" > /usr/vice/etc/cacheinfo</emphasis>
</programlisting>
</listitem>
</orderedlist> </para>
</sect2>
<sect2 id= "HDRWQ148" >
<title > Configuring a Memory Cache</title>
<para > To configure a memory cache, create the <emphasis role= "bold" > cacheinfo</emphasis> file to define the configuration
parameters discussed previously. The following instruction shows the standard mount location, <emphasis
role="bold">/afs</emphasis> , and the standard cache location, <emphasis role= "bold" > /usr/vice/cache</emphasis> (though the
exact value of the latter is irrelevant for a memory cache).</para>
<programlisting >
# <emphasis role= "bold" > echo "/afs:/usr/vice/cache:</emphasis> <replaceable > #blocks</replaceable> <emphasis role= "bold" > " > /usr/vice/etc/cacheinfo</emphasis>
</programlisting>
<para > The following example allocates 25,000 KB of memory for the cache.</para>
<programlisting >
# <emphasis role= "bold" > echo "/afs:/usr/vice/cache:25000" > /usr/vice/etc/cacheinfo</emphasis>
</programlisting>
<indexterm >
<primary > afs (/afs) directory</primary>
<secondary > creating</secondary>
<tertiary > client machine</tertiary>
</indexterm>
<indexterm >
<primary > afs (/afs) directory</primary>
<secondary > as root of AFS filespace</secondary>
</indexterm>
<indexterm >
<primary > AFS filespace</primary>
<secondary > root at /afs directory</secondary>
</indexterm>
<indexterm >
<primary > directories</primary>
<secondary > /afs</secondary>
</indexterm>
<indexterm >
<primary > afsd</primary>
<secondary > options file (Linux)</secondary>
</indexterm>
<indexterm >
<primary > files</primary>
<secondary > afsd options file (Linux)</secondary>
</indexterm>
<indexterm >
<primary > files</primary>
<secondary > afs</secondary>
<tertiary > afsd options file (Linux)</tertiary>
</indexterm>
<indexterm >
<primary > afs file</primary>
<secondary > afsd options file (Linux)</secondary>
</indexterm>
<indexterm >
<primary > etc/sysconfig/afs</primary>
<see > afs file</see>
</indexterm>
<indexterm >
<primary > Linux</primary>
<secondary > afsd options file</secondary>
</indexterm>
<indexterm >
<primary > client machine</primary>
<secondary > afsd options file (Linux)</secondary>
</indexterm>
<indexterm >
<primary > afsd</primary>
<secondary > command in AFS init. script</secondary>
</indexterm>
<indexterm >
<primary > commands</primary>
<secondary > afsd</secondary>
</indexterm>
<indexterm >
<primary > OPTIONS variable in AFS initialization file</primary>
</indexterm>
<indexterm >
<primary > files</primary>
<secondary > AFS initialization</secondary>
<see > AFS initialization script</see>
</indexterm>
<indexterm >
<primary > scripts</primary>
<secondary > AFS initialization</secondary>
<see > AFS initialization script</see>
</indexterm>
<indexterm >
<primary > AFS initialization script</primary>
<secondary > setting afsd parameters</secondary>
<tertiary > client machine</tertiary>
</indexterm>
<indexterm >
<primary > client machine</primary>
<secondary > afsd command parameters</secondary>
</indexterm>
<indexterm >
<primary > variables</primary>
<secondary > OPTIONS (in AFS initialization file)</secondary>
</indexterm>
<indexterm >
<primary > environment variables</primary>
<see > variables</see>
</indexterm>
<indexterm >
<primary > Cache Manager</primary>
<secondary > client machine</secondary>
</indexterm>
<indexterm >
<primary > configuring</primary>
<secondary > Cache Manager</secondary>
<tertiary > client machine</tertiary>
</indexterm>
<indexterm >
<primary > client machine</primary>
<secondary > Cache Manager</secondary>
</indexterm>
<indexterm >
<primary > files</primary>
<secondary > vfs (AIX)</secondary>
</indexterm>
<indexterm >
<primary > vfs file</primary>
</indexterm>
<indexterm >
<primary > etc/vfs file</primary>
</indexterm>
<indexterm >
<primary > AIX</primary>
<secondary > editing /etc/vfs file</secondary>
</indexterm>
<indexterm >
<primary > client machine</primary>
<secondary > vfs file (AIX)</secondary>
</indexterm>
</sect2>
</sect1>
<sect1 id= "HDRWQ149" >
<title > Configuring the Cache Manager</title>
<para > By convention, the Cache Manager mounts the AFS filespace on the local <emphasis role= "bold" > /afs</emphasis> directory. In
this section you create that directory.</para>
<para > The <emphasis role= "bold" > afsd</emphasis> program sets several cache configuration parameters as it initializes the Cache
Manager, and starts daemons that improve performance. You can use the <emphasis role= "bold" > afsd</emphasis> command's arguments
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
2006-12-02 03:56:17 +00:00
in the <emphasis > OpenAFS Administration Reference</emphasis> .</para>
2006-09-16 02:13:22 +01:00
2007-04-24 05:37:52 +01:00
<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
2006-09-16 02:13:22 +01:00
of the following ways: <itemizedlist >
<listitem >
<para > You can create an <emphasis role= "bold" > afsd</emphasis> <emphasis > options file</emphasis> that sets values for
arguments to the <emphasis role= "bold" > afsd</emphasis> command. If the file exists, its contents are automatically
substituted for the <computeroutput > OPTIONS</computeroutput> variable in the AFS initialization script. The AFS
distribution for some system types includes an options file; on other system types, you must create it.</para>
<para > You use two variables in the AFS initialization script to specify the path to the options file:
<computeroutput > CONFIG</computeroutput> and <computeroutput > AFSDOPT</computeroutput> . On system types that define a
conventional directory for configuration files, the <computeroutput > CONFIG</computeroutput> variable indicates it by
default; otherwise, the variable indicates an appropriate location.</para>
<para > List the desired <emphasis role= "bold" > afsd</emphasis> options on a single line in the options file, separating each
option with one or more spaces. The following example sets the <emphasis role= "bold" > -stat</emphasis> argument to 2500,
the <emphasis role= "bold" > -daemons</emphasis> argument to 4, and the <emphasis role= "bold" > -volumes</emphasis> argument to
100.</para>
<programlisting >
-stat 2500 -daemons 4 -volumes 100
</programlisting>
</listitem>
<listitem >
<para > On a machine that uses a disk cache, you can set the <computeroutput > OPTIONS</computeroutput> variable in the AFS
initialization script to one of <computeroutput > $SMALL</computeroutput> , <computeroutput > $MEDIUM</computeroutput> , or
<computeroutput > $LARGE</computeroutput> . The AFS initialization script uses one of these settings if the <emphasis
role="bold">afsd</emphasis> options file named by the <computeroutput > AFSDOPT</computeroutput> variable does not exist. In
the script as distributed, the <computeroutput > OPTIONS</computeroutput> variable is set to the value
<computeroutput > $MEDIUM</computeroutput> .</para>
<note >
<para > Do not set the <computeroutput > OPTIONS</computeroutput> variable to <computeroutput > $SMALL</computeroutput> ,
<computeroutput > $MEDIUM</computeroutput> , or <computeroutput > $LARGE</computeroutput> on a machine that uses a memory
cache. The arguments it sets are appropriate only on a machine that uses a disk cache.</para>
</note>
<para > The script (or on some system types the <emphasis role= "bold" > afsd</emphasis> options file named by the
<computeroutput > AFSDOPT</computeroutput> variable) defines a value for each of <computeroutput > SMALL</computeroutput> ,
<computeroutput > MEDIUM</computeroutput> , and <computeroutput > LARGE</computeroutput> that sets <emphasis
role="bold">afsd</emphasis> command arguments appropriately for client machines of different sizes: <itemizedlist >
<listitem >
<para > <computeroutput > SMALL</computeroutput> is suitable for a small machine that serves one or two users and has
approximately 8 MB of RAM and a 20-MB cache</para>
</listitem>
<listitem >
<para > <computeroutput > MEDIUM</computeroutput> is suitable for a medium-sized machine that serves two to six users
and has 16 MB of RAM and a 40-MB cache</para>
</listitem>
<listitem >
<para > <computeroutput > LARGE</computeroutput> is suitable for a large machine that serves five to ten users and has
32 MB of RAM and a 100-MB cache</para>
</listitem>
</itemizedlist> </para>
</listitem>
<listitem >
<para > You can choose not to create an <emphasis role= "bold" > afsd</emphasis> options file and to set the
<computeroutput > OPTIONS</computeroutput> variable in the initialization script to a null value rather than to the default
<computeroutput > $MEDIUM</computeroutput> value. You can then either set arguments directly on the <emphasis
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>
2007-04-24 05:37:52 +01:00
</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
<emphasis role= "bold" > /etc/sysconfig/openafs</emphasis> , in which the
AFSD_ARGS variable may be set to contain any, or all, of the afsd
options detailed above. Note that this script does not support setting
an <computeroutput > OPTIONS</computeroutput> variable, or the
<computeroutput > SMALL</computeroutput> ,
<computeroutput > MEDIUM</computeroutput> and
<computeroutput > LARGE</computeroutput> methods of defining cache size.
</para>
</note>
<orderedlist >
2006-09-16 02:13:22 +01:00
<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 >
# <emphasis role= "bold" > mkdir /afs</emphasis>
</programlisting> </para>
</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 >
2007-04-24 05:37:52 +01:00
<para > On non-package based Linux systems, copy the <emphasis role= "bold" > afsd</emphasis> options file from the <emphasis
2006-09-16 02:13:22 +01:00
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>
</programlisting> </para>
</listitem>
<listitem >
<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 appropriate file for each system type
is as follows: <itemizedlist >
<listitem >
<para > On AIX systems, <emphasis role= "bold" > /etc/rc.afs</emphasis> </para>
</listitem>
<listitem >
<para > On HP-UX systems, <emphasis role= "bold" > /sbin/init.d/afs</emphasis> </para>
</listitem>
<listitem >
<para > On IRIX systems, <emphasis role= "bold" > /etc/init.d/afs</emphasis> </para>
</listitem>
2007-04-24 05:37:52 +01:00
<listitem >
<para > On Fedora and RHEL systems, <emphasis role= "bold" > /etc/sysconfig/openafs</emphasis> </para>
</listitem>
2006-09-16 02:13:22 +01:00
<listitem >
<para > On Linux systems, <emphasis role= "bold" > /etc/sysconfig/afs</emphasis> (the <emphasis
role="bold">afsd</emphasis> options file)</para>
</listitem>
<listitem >
<para > On Solaris systems, <emphasis role= "bold" > /etc/init.d/afs</emphasis> </para>
</listitem>
</itemizedlist> </para>
<para > Use one of the methods described in the introduction to this section to add the following flags to the <emphasis
role="bold">afsd</emphasis> command line. Also set any performance-related arguments you wish. <itemizedlist >
<listitem >
<para > Add the <emphasis role= "bold" > -memcache</emphasis> flag if the machine is to use a memory cache.</para>
</listitem>
<listitem >
<para > Add the <emphasis role= "bold" > -verbose</emphasis> flag to display a trace of the Cache Manager's
initialization on the standard output stream.</para>
</listitem>
</itemizedlist> </para>
</listitem>
</orderedlist> </para>
<indexterm >
<primary > AFS initialization script</primary>
<secondary > running</secondary>
<tertiary > client machine</tertiary>
</indexterm>
<indexterm >
<primary > client machine</primary>
<secondary > AFS initialization script</secondary>
</indexterm>
<indexterm >
<primary > running AFS init. script</primary>
<secondary > client machine</secondary>
</indexterm>
<indexterm >
<primary > installing</primary>
<secondary > AFS initialization script</secondary>
<tertiary > client machine</tertiary>
</indexterm>
<indexterm >
<primary > AFS initialization script</primary>
<secondary > adding to machine startup sequence</secondary>
<tertiary > client machine</tertiary>
</indexterm>
</sect1>
<sect1 id= "HDRWQ150" >
<title > Starting the Cache Manager and Installing the AFS Initialization Script</title>
<para > In this section you run the AFS initialization script to start the Cache Manager. If the script works correctly, perform
the steps that incorporate it into the machine's startup and shutdown sequence. If there are problems during the initialization,
attempt to resolve them. The AFS Product Support group can provide assistance if necessary.</para>
<para > On machines that use a disk cache, it can take a while for the <emphasis role= "bold" > afsd</emphasis> program to run the
first time on a machine, because it must create all of the <emphasis 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>
<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 > Proceed to the instructions for your system type:</para>
<itemizedlist >
<listitem >
<para > <link linkend= "HDRWQ151" > Running the Script on AIX Systems</link> </para>
</listitem>
<listitem >
<para > <link linkend= "HDRWQ153" > Running the Script on HP-UX Systems</link> </para>
</listitem>
<listitem >
<para > <link linkend= "HDRWQ154" > Running the Script on IRIX Systems</link> </para>
</listitem>
<listitem >
<para > <link linkend= "HDRWQ155" > Running the Script on Linux Systems</link> </para>
</listitem>
<listitem >
<para > <link linkend= "HDRWQ156" > Running the Script on Solaris Systems</link> </para>
</listitem>
</itemizedlist>
<indexterm >
<primary > AIX</primary>
<secondary > AFS initialization script</secondary>
<tertiary > on client machine</tertiary>
</indexterm>
<indexterm >
<primary > rc.afs file (AFS init. file for AIX)</primary>
</indexterm>
<indexterm >
<primary > files</primary>
<secondary > rc.afs</secondary>
</indexterm>
<indexterm >
<primary > etc/rc.afs</primary>
<see > rc.afs file</see>
</indexterm>
<sect2 id= "HDRWQ151" >
<title > Running the Script on AIX Systems</title>
<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>
<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 > If a volume for housing AFS binaries for this machine's system type does not already exist, proceed to <link
linkend="HDRWQ157">Setting Up Volumes and Loading Binaries into AFS</link> . Otherwise, the installation is
complete.</para>
</listitem>
</orderedlist>
<indexterm >
<primary > afs file</primary>
<secondary > AFS initialization file</secondary>
</indexterm>
<indexterm >
<primary > files</primary>
<secondary > afs</secondary>
<tertiary > AFS initialization file</tertiary>
</indexterm>
<indexterm >
<primary > HP-UX</primary>
<secondary > AFS initialization script</secondary>
<tertiary > on client machine</tertiary>
</indexterm>
</sect2>
<sect2 id= "HDRWQ153" >
<title > Running the Script on HP-UX Systems</title>
<orderedlist >
<listitem >
<para > Run the AFS initialization script. <programlisting >
# <emphasis role= "bold" > /sbin/init.d/afs start</emphasis>
</programlisting> </para>
</listitem>
<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 > If a volume for housing AFS binaries for this machine's system type does not already exist, proceed to <link
linkend="HDRWQ157">Setting Up Volumes and Loading Binaries into AFS</link> . Otherwise, the installation is
complete.</para>
</listitem>
</orderedlist>
<indexterm >
<primary > afs file</primary>
<secondary > AFS initialization file</secondary>
</indexterm>
<indexterm >
<primary > files</primary>
<secondary > afs</secondary>
<tertiary > AFS initialization file</tertiary>
</indexterm>
<indexterm >
<primary > IRIX</primary>
<secondary > AFS initialization script</secondary>
<tertiary > on client machine</tertiary>
</indexterm>
<indexterm >
<primary > etc/init.d/afs</primary>
<see > afs file</see>
</indexterm>
<indexterm >
<primary > afsclient variable (IRIX)</primary>
<secondary > client machine</secondary>
</indexterm>
<indexterm >
<primary > variables</primary>
<secondary > afsclient (IRIX)</secondary>
<tertiary > client machine</tertiary>
</indexterm>
<indexterm >
<primary > IRIX</primary>
<secondary > afsclient variable</secondary>
<tertiary > client machine</tertiary>
</indexterm>
</sect2>
<sect2 id= "HDRWQ154" >
<title > Running the Script on IRIX Systems</title>
<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>
<listitem >
<para > Issue the <emphasis role= "bold" > chkconfig</emphasis> command to activate the <emphasis
role="bold">afsclient</emphasis> configuration variable. <programlisting >
# <emphasis role= "bold" > /etc/chkconfig -f afsclient on</emphasis>
</programlisting> </para>
</listitem>
<listitem >
<para > Run the AFS initialization script. <programlisting >
# <emphasis role= "bold" > /etc/init.d/afs start</emphasis>
</programlisting> </para>
</listitem>
<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 > If a volume for housing AFS binaries for this machine's system type does not already exist, proceed to <link
linkend="HDRWQ157">Setting Up Volumes and Loading Binaries into AFS</link> . Otherwise, the installation is
complete.</para>
</listitem>
</orderedlist>
<indexterm >
<primary > afs file</primary>
<secondary > AFS initialization file</secondary>
</indexterm>
<indexterm >
<primary > files</primary>
<secondary > afs</secondary>
<tertiary > AFS initialization file</tertiary>
</indexterm>
<indexterm >
<primary > etc/rc.d/init.d/afs</primary>
<see > afs file</see>
</indexterm>
<indexterm >
<primary > Linux</primary>
<secondary > AFS initialization script</secondary>
<tertiary > on client machine</tertiary>
</indexterm>
</sect2>
2007-04-24 05:37:52 +01:00
<sect2 >
<title > Running the Script on Fedora / RHEL Systems</title>
<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.d/init.d/openafs-client start</emphasis>
</programlisting> </para>
</listitem>
<listitem >
<para > Issue the <emphasis role= "bold" > chkconfig</emphasis> command to activate the <emphasis role= "bold" > openafs-client</emphasis>
configuration variable. 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 openafs-client</emphasis>
</programlisting> </para>
</listitem>
</orderedlist>
</sect2>
2006-09-16 02:13:22 +01:00
<sect2 id= "HDRWQ155" >
2007-04-24 05:37:52 +01:00
<title > Running the Script on other Linux Systems</title>
2006-09-16 02:13:22 +01:00
<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.d/init.d/afs start</emphasis>
</programlisting> </para>
</listitem>
<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
<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>
</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/rc.d/init.d</emphasis> directories, and
copies of the <emphasis role= "bold" > afsd</emphasis> options file in both the <emphasis
role="bold">/usr/vice/etc</emphasis> and <emphasis role= "bold" > /etc/sysconfig</emphasis> directories. If you want to avoid
potential confusion by guaranteeing that the two copies of each file are always the same, create a link between them. You
can always retrieve the original script or options file from the AFS CD-ROM if necessary. <programlisting >
# <emphasis role= "bold" > cd /usr/vice/etc</emphasis>
# <emphasis role= "bold" > rm afs.rc afs.conf</emphasis>
# <emphasis role= "bold" > ln -s /etc/rc.d/init.d/afs afs.rc</emphasis>
# <emphasis role= "bold" > ln -s /etc/sysconfig/afs afs.conf</emphasis>
</programlisting> </para>
</listitem>
<listitem >
<para > If a volume for housing AFS binaries for this machine's system type does not already exist, proceed to <link
linkend="HDRWQ157">Setting Up Volumes and Loading Binaries into AFS</link> . Otherwise, the installation is
complete.</para>
</listitem>
</orderedlist>
<indexterm >
<primary > afs file</primary>
<secondary > AFS initialization file</secondary>
</indexterm>
<indexterm >
<primary > files</primary>
<secondary > afs</secondary>
<tertiary > AFS initialization file</tertiary>
</indexterm>
<indexterm >
<primary > Solaris</primary>
<secondary > AFS initialization script</secondary>
<tertiary > on client machine</tertiary>
</indexterm>
</sect2>
<sect2 id= "HDRWQ156" >
<title > Running the Script on Solaris Systems</title>
<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 -i6 -g0 -y</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/init.d/afs start</emphasis>
</programlisting> </para>
</listitem>
<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 Solaris startup and
shutdown sequence. <programlisting >
# <emphasis role= "bold" > cd /etc/init.d</emphasis>
# <emphasis role= "bold" > ln -s ../init.d/afs /etc/rc3.d/S99afs</emphasis>
# <emphasis role= "bold" > ln -s ../init.d/afs /etc/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" > /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
2007-04-24 05:37:52 +01:00
retrieve the original script from the OpenAFS Binary Distribution if necessary. <programlisting >
2006-09-16 02:13:22 +01:00
# <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 > If a volume for housing AFS binaries for this machine's system type does not already exist, proceed to <link
linkend="HDRWQ157">Setting Up Volumes and Loading Binaries into AFS</link> . Otherwise, the installation is
complete.</para>
</listitem>
</orderedlist>
<indexterm >
<primary > storing</primary>
<secondary > AFS binaries in volumes</secondary>
</indexterm>
<indexterm >
<primary > creating</primary>
<secondary > volume</secondary>
<tertiary > for AFS binaries</tertiary>
</indexterm>
<indexterm >
<primary > volume</primary>
<secondary > for AFS binaries</secondary>
</indexterm>
<indexterm >
<primary > binaries</primary>
<secondary > storing AFS in volume</secondary>
</indexterm>
<indexterm >
<primary > usr/afsws directory</primary>
</indexterm>
<indexterm >
<primary > directories</primary>
<secondary > /usr/afsws</secondary>
</indexterm>
</sect2>
</sect1>
<sect1 id= "HDRWQ157" >
<title > Setting Up Volumes and Loading Binaries into AFS</title>
2007-04-24 05:37:52 +01:00
<note > <para > If you are using an operating system which uses packaged
binaries, such as .rpms or .debs, you should allow these package management
systems to maintain your AFS binaries, rather than following the
instructions in this section.</para> </note>
2006-09-16 02:13:22 +01:00
<para > In this section, you link <emphasis role= "bold" > /usr/afsws</emphasis> on the local disk to the directory in AFS that
houses AFS binaries for this system type. The conventional name for the AFS directory is <emphasis
role="bold">/afs/</emphasis> <replaceable > cellname</replaceable> <emphasis
role="bold">/</emphasis> <replaceable > sysname</replaceable> <emphasis role= "bold" > /usr/afsws</emphasis> .</para>
<para > If this machine is an existing system type, the AFS directory presumably already exists. You can simply create a link from
the local <emphasis role= "bold" > /usr/afsws</emphasis> directory to it. Follow the instructions in <link
linkend="HDRWQ158">Linking /usr/afsws on an Existing System Type</link> .</para>
<para > If this machine is a new system type (there are no AFS machines of this type in your cell), you must first create and
mount volumes to store its AFS binaries, and then create the link from <emphasis role= "bold" > /usr/afsws</emphasis> to the new
directory. See <link linkend= "HDRWQ159" > Creating Binary Volumes for a New System Type</link> .</para>
<para > You can also store UNIX system binaries (the files normally stored in local disk directories such as <emphasis
role="bold">/bin</emphasis> , <emphasis role= "bold" > /etc</emphasis> , and <emphasis role= "bold" > /lib</emphasis> ) in volumes
mounted under <emphasis role= "bold" > /afs/</emphasis> <replaceable > cellname</replaceable> <emphasis
role="bold">/</emphasis> <replaceable > sysname</replaceable> . See <link linkend= "HDRWQ88" > Storing System Binaries in AFS</link>
.</para>
<sect2 id= "HDRWQ158" >
<title > Linking /usr/afsws on an Existing System Type</title>
<para > If this client machine is an existing system type, there is already a volume mounted in the AFS filespace that houses
AFS client binaries for it. <orderedlist >
<listitem >
<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 remains valid if you upgrade this machine to a different system type.
<programlisting >
# <emphasis role= "bold" > ln -s /afs/</emphasis> <replaceable > cellname</replaceable> <emphasis role= "bold" > /@sys/usr/afsws /usr/afsws</emphasis>
</programlisting> </para>
</listitem>
<listitem >
<para > <emphasis role= "bold" > (Optional)</emphasis> If you believe it is helpful to your users to access the AFS documents
in a certain format via a local disk directory, create <emphasis role= "bold" > /usr/afsdoc</emphasis> on the local disk as
a symbolic link to the documentation directory in AFS (<emphasis
role="bold">/afs/</emphasis> <replaceable > cellname</replaceable> <emphasis
role="bold">/afsdoc/</emphasis> <replaceable > format_name</replaceable> ). <programlisting >
# <emphasis role= "bold" > ln -s /afs/</emphasis> <replaceable > cellname</replaceable> <emphasis role= "bold" > /afsdoc/</emphasis> <replaceable > format_name</replaceable> <emphasis
role="bold">/usr/afsdoc</emphasis>
</programlisting> </para>
<para > An alternative is to create a link in each user's home directory to the <emphasis
role="bold">/afs/</emphasis> <replaceable > cellname</replaceable> <emphasis
role="bold">/afsdoc/</emphasis> <replaceable > format_name</replaceable> directory.</para>
</listitem>
</orderedlist> </para>
</sect2>
<sect2 id= "HDRWQ159" >
<title > Creating Binary Volumes for a New System Type</title>
<para > If this client machine is a new system type, you must create and mount volumes for its binaries before you can link the
local <emphasis role= "bold" > /usr/afsws</emphasis> directory to an AFS directory.</para>
2007-04-24 05:37:52 +01:00
<para > To create and mount the volumes, you use the
<emphasis role= "bold" > kinit</emphasis> command to authenticate as an
administrator, followed by the <emphasis role= "bold" > aklog</emphasis>
command to gain tokens, and then issue commands from the
<emphasis role= "bold" > vos</emphasis> and
<emphasis role= "bold" > fs</emphasis> command suites. However, the
command binaries are not yet available on this machine (by convention,
they are accessible via the <emphasis role= "bold" > /usr/afsws</emphasis>
link that you are about to create). You have two choices:
<itemizedlist >
2006-09-16 02:13:22 +01:00
<listitem >
<para > Perform all steps except the last one (Step <link linkend= "LIWQ162" > 10</link> ) on an existing AFS machine. On a
2007-04-24 05:37:52 +01:00
file server machine, the <emphasis role= "bold" > aklog</emphasis> , <emphasis role= "bold" > fs</emphasis> and <emphasis
2006-09-16 02:13:22 +01:00
role="bold">vos</emphasis> binaries reside in the <emphasis role= "bold" > /usr/afs/bin</emphasis> directory. On client
2007-04-24 05:37:52 +01:00
machines, the <emphasis role= "bold" > aklog</emphasis> and <emphasis role= "bold" > fs</emphasis> binaries reside in the
2006-09-16 02:13:22 +01:00
<emphasis role= "bold" > /usr/afsws/bin</emphasis> directory and the <emphasis role= "bold" > vos</emphasis> binary in the
<emphasis role= "bold" > /usr/afsws/etc</emphasis> directory. Depending on how your PATH environment variable is set, you
possibly need to precede the command names with a pathname.</para>
<para > If you work on another AFS machine, be sure to substitute the new system type name for the
<replaceable > sysname</replaceable> argument in the following commands, not the system type of the machine on which you
are issuing the commands.</para>
</listitem>
<listitem >
<para > Copy the necessary command binaries to a temporary location on the local disk, which enables you to perform the
steps on the local machine. The following procedure installs them in the <emphasis role= "bold" > /tmp</emphasis> directory
and removes them at the end. Depending on how your PATH environment variable is set, you possibly need to precede the
command names with a pathname.</para>
</listitem>
</itemizedlist> </para>
<para > Perform the following steps to create a volume for housing AFS binaries. <orderedlist >
<listitem >
2007-04-24 05:37:52 +01:00
<para > Working either on the local machine or another AFS machine,
extract the Open AFS distribtion tarball onto a directory on that
machine. The following instructions assume that you are using the
<emphasis role= "bold" > /tmp/afsdist</emphasis> directory.</para>
2006-09-16 02:13:22 +01:00
</listitem>
<listitem >
<para > If working on the local machine, copy the necessary binaries to a temporary location on the local disk. Substitute
a different directory name for <emphasis role= "bold" > /tmp</emphasis> if you wish. <programlisting >
2007-04-24 05:37:52 +01:00
# <emphasis role= "bold" > cd /tmp/afsdist/</emphasis> <replaceable > new_sysname</replaceable> <emphasis role= "bold" > /root.server/usr/afs/bin</emphasis>
# <emphasis role= "bold" > cp -p aklog /tmp</emphasis>
2006-09-16 02:13:22 +01:00
# <emphasis role= "bold" > cp -p fs /tmp</emphasis>
# <emphasis role= "bold" > cp -p vos /tmp</emphasis>
</programlisting> </para>
</listitem>
<listitem >
2007-04-24 05:37:52 +01:00
<para > Authenticate as the user <emphasis role= "bold" > admin</emphasis> .
<programlisting >
# <emphasis role= "bold" > kinit admin</emphasis>
2006-09-16 02:13:22 +01:00
Password: <replaceable > admin_password</replaceable>
2007-04-24 05:37:52 +01:00
# <emphasis role= "bold" > aklog</emphasis>
2006-09-16 02:13:22 +01:00
</programlisting> </para>
</listitem>
2011-06-07 19:26:11 +01:00
<listitem id= "LIWQ160" >
<para > Issue the <emphasis role= "bold" > vos create</emphasis> command to create volumes for storing
2006-09-16 02:13:22 +01:00
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
2006-12-02 03:56:17 +00:00
<replaceable > sysname</replaceable> .<emphasis role= "bold" > usr.afsws</emphasis> . Refer to the <emphasis > OpenAFS Release
2006-09-16 02:13:22 +01:00
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
role="bold">.usr</emphasis>
# <emphasis role= "bold" > vos create</emphasis> < <replaceable > machine name</replaceable> > < <replaceable > partition name</replaceable> > <replaceable > sysname</replaceable> <emphasis
role="bold">.usr.afsws</emphasis>
</programlisting> </para>
</listitem>
<listitem >
<para > Issue the <emphasis role= "bold" > fs mkmount</emphasis> command to mount the newly created volumes. Because the
<emphasis role= "bold" > root.cell</emphasis> volume is replicated, you must precede the <emphasis > cellname</emphasis> part
of the pathname with a period to specify the read/write mount point, as shown. Then issue the <emphasis role= "bold" > vos
release</emphasis> command to release a new replica of the <emphasis role= "bold" > root.cell</emphasis> volume, and the
<emphasis role= "bold" > fs checkvolumes</emphasis> command to force the local Cache Manager to access them.
<programlisting >
# <emphasis role= "bold" > fs mkmount -dir /afs/.</emphasis> <replaceable > cellname</replaceable> <emphasis role= "bold" > /</emphasis> <replaceable > sysname</replaceable> <emphasis
role="bold">-vol</emphasis> <replaceable > sysname</replaceable>
# <emphasis role= "bold" > fs mkmount -dir /afs/.</emphasis> <replaceable > cellname</replaceable> <emphasis role= "bold" > /</emphasis> <replaceable > sysname</replaceable> <emphasis
role="bold">/usr</emphasis> <emphasis role= "bold" > -vol</emphasis> <replaceable > sysname</replaceable> <emphasis
role="bold">.usr</emphasis>
# <emphasis role= "bold" > fs mkmount -dir /afs/.</emphasis> <replaceable > cellname</replaceable> <emphasis role= "bold" > /</emphasis> <replaceable > sysname</replaceable> <emphasis
role="bold">/usr/afsws</emphasis> <emphasis role= "bold" > -vol</emphasis> <replaceable > sysname</replaceable> <emphasis
role="bold">.usr.afsws</emphasis>
# <emphasis role= "bold" > vos release root.cell</emphasis>
# <emphasis role= "bold" > fs checkvolumes</emphasis>
</programlisting> </para>
</listitem>
<listitem >
<para > Issue the <emphasis role= "bold" > fs setacl</emphasis> command to grant the <emphasis role= "bold" > l</emphasis>
(<emphasis role= "bold" > lookup</emphasis> ) and <emphasis role= "bold" > r</emphasis> (<emphasis role= "bold" > read</emphasis> )
permissions to the <emphasis role= "bold" > system:anyuser</emphasis> group on each new directory's ACL. <programlisting >
# <emphasis role= "bold" > cd /afs/.</emphasis> <replaceable > cellname</replaceable> <emphasis role= "bold" > /</emphasis> <replaceable > sysname</replaceable>
# <emphasis role= "bold" > fs setacl -dir . usr usr/afsws -acl system:anyuser rl</emphasis>
</programlisting> </para>
</listitem>
<listitem >
<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
quota.</para>
<para > If you wish, you can set the volume's quota to a finite value after you complete the copying operation. At that
point, use the <emphasis role= "bold" > vos examine</emphasis> command to determine how much space the volume is occupying.
Then issue the <emphasis role= "bold" > fs setquota</emphasis> command to set a quota that is slightly larger.</para>
<programlisting >
# <emphasis role= "bold" > fs setquota /afs/.</emphasis> <replaceable > cellname</replaceable> <emphasis role= "bold" > /</emphasis> <replaceable > sysname</replaceable> <emphasis
role="bold">/usr/afsws 0</emphasis>
</programlisting>
</listitem>
2011-06-07 19:26:11 +01:00
<listitem id= "LIWQ161" >
<para > Copy the contents of the indicated
2007-04-24 05:37:52 +01:00
directories from the OpenAFS binary distribution into the
<emphasis role= "bold" > /afs/</emphasis> <replaceable > cellname</replaceable> <emphasis
2006-09-16 02:13:22 +01:00
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> </para>
</listitem>
<listitem >
2007-04-24 05:37:52 +01:00
<para > Issue the <emphasis role= "bold" > fs setacl</emphasis> command
to set the ACL on each directory appropriately. If you wish to
enable access to the software 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" > aklog</emphasis> binary.
<programlisting >
2006-09-16 02:13:22 +01:00
# <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> </para>
</listitem>
2011-06-07 19:26:11 +01:00
<listitem id= "LIWQ162" >
<para > Perform this step on the new client machine even if you have performed the previous steps
2006-09-16 02:13:22 +01:00
on another machine. 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
remains valid if you upgrade this machine to a different system type. <programlisting >
# <emphasis role= "bold" > ln -s /afs/</emphasis> <replaceable > cellname</replaceable> <emphasis role= "bold" > /@sys/usr/afsws /usr/afsws</emphasis>
</programlisting> </para>
</listitem>
<listitem >
<para > <emphasis role= "bold" > (Optional)</emphasis> To enable users to issue commands from the AFS suites (such as
<emphasis role= "bold" > fs</emphasis> ) without having to specify a pathname to their binaries, include the <emphasis
role="bold">/usr/afsws/bin</emphasis> and <emphasis role= "bold" > /usr/afsws/etc</emphasis> directories in the PATH
environment variable you define in each user's shell initialization file (such as <emphasis
role="bold">.cshrc</emphasis> ).</para>
</listitem>
<listitem >
<para > <emphasis role= "bold" > (Optional)</emphasis> If you believe it is helpful to your users to access the AFS documents
in a certain format via a local disk directory, create <emphasis role= "bold" > /usr/afsdoc</emphasis> on the local disk as
a symbolic link to the documentation directory in AFS (<emphasis
role="bold">/afs/</emphasis> <replaceable > cellname</replaceable> <emphasis
role="bold">/afsdoc/</emphasis> <replaceable > format_name</replaceable> ). <programlisting >
# <emphasis role= "bold" > ln -s /afs/</emphasis> <replaceable > cellname</replaceable> <emphasis role= "bold" > /afsdoc/</emphasis> <replaceable > format_name</replaceable> <emphasis
role="bold">/usr/afsdoc</emphasis>
</programlisting> </para>
<para > An alternative is to create a link in each user's home directory to the <emphasis
role="bold">/afs/</emphasis> <replaceable > cellname</replaceable> <emphasis
role="bold">/afsdoc/</emphasis> <replaceable > format_name</replaceable> directory.</para>
</listitem>
<listitem >
<para > <emphasis role= "bold" > (Optional)</emphasis> If working on the local machine, remove the AFS binaries from the
temporary location. They are now accessible in the <emphasis role= "bold" > /usr/afsws</emphasis> directory.
<programlisting >
# <emphasis role= "bold" > cd /tmp</emphasis>
# <emphasis role= "bold" > rm klog fs vos</emphasis>
</programlisting> </para>
</listitem>
</orderedlist> </para>
</sect2>
</sect1>
2006-12-02 03:56:17 +00:00
</chapter>
