1 <?xml version="1.0" encoding="UTF-8"?>
3 <title>Installing the First AFS Machine</title>
7 <primary>file server machine</primary>
9 <seealso>first AFS machine</seealso>
11 <seealso>file server machine, additional</seealso>
15 <primary>instructions</primary>
17 <secondary>first AFS machine</secondary>
21 <primary>installing</primary>
23 <secondary>first AFS machine</secondary>
26 This chapter describes how to install the first AFS machine in your cell, configuring it as both a file server machine and a
27 client machine. After completing all procedures in this chapter, you can remove the client functionality if you wish, as described
28 in <link linkend="HDRWQ98">Removing Client Functionality</link>.</para>
30 <para>To install additional file server machines after completing this chapter, see <link linkend="HDRWQ99">Installing Additional
31 Server Machines</link>.</para>
33 <para>To install additional client machines after completing this chapter, see <link linkend="HDRWQ133">Installing Additional
34 Client Machines</link>. <indexterm>
35 <primary>requirements</primary>
37 <secondary>first AFS machine</secondary>
40 <sect1 id="Header_29">
41 <title>Requirements and Configuration Decisions</title>
43 <para>The instructions in this chapter assume that you meet the following requirements.
46 <para>You are logged onto the machine's console as the local superuser <emphasis role="bold">root</emphasis></para>
50 <para>A standard version of one of the operating systems supported by the current version of AFS is running on the
55 <para>You have either installed the provided OpenAFS packages for
56 your system, have access to a binary distribution tarball, or have
57 successfully built OpenAFS from source</para>
61 <para>You have a Kerberos v5 realm running for your site. If you are
62 working with an existing cell which uses
63 <emphasis role="bold">kaserver</emphasis> or Kerberos v4 for
64 authentication, please see
65 <link linkend="KAS001">kaserver and Legacy Kerberos v4 Authentication</link>
66 for the modifications required to this installation procedure.</para>
70 <para>You have a NTP, or similar, time service deployed to ensure
71 rough clock syncronistation between your clients and servers. If you
72 wish to use AFS's built in timeservice (which is deprecated) please
73 see Appendix B for the necessary modifications to this installation
76 </itemizedlist></para>
78 <para>You must make the following configuration decisions while installing the first AFS machine. To speed the installation
79 itself, it is best to make the decisions before beginning. See the chapter in the <emphasis>OpenAFS Administration
80 Guide</emphasis> about issues in cell administration and configuration for detailed guidelines. <indexterm>
81 <primary>cell name</primary>
83 <secondary>choosing</secondary>
84 </indexterm> <indexterm>
85 <primary>AFS filespace</primary>
87 <secondary>deciding how to configure</secondary>
88 </indexterm> <indexterm>
89 <primary>filespace</primary>
91 <see>AFS filespace</see>
92 </indexterm> <itemizedlist>
94 <para>Select the first AFS machine</para>
98 <para>Select the cell name</para>
102 <para>Decide which partitions or logical volumes to configure as AFS server partitions, and choose the directory names on
103 which to mount them</para>
107 <para>Decide how big to make the client cache</para>
111 <para>Decide how to configure the top levels of your cell's AFS filespace</para>
113 </itemizedlist></para>
115 <para>This chapter is divided into three large sections corresponding to the three parts of installing the first AFS machine.
116 Perform all of the steps in the order they appear. Each functional section begins with a summary of the procedures to perform.
117 The sections are as follows: <itemizedlist>
119 <para>Installing server functionality (begins in <link linkend="HDRWQ18">Overview: Installing Server
120 Functionality</link>)</para>
124 <para>Installing client functionality (begins in <link linkend="HDRWQ63">Overview: Installing Client
125 Functionality</link>)</para>
129 <para>Configuring your cell's filespace, establishing further security mechanisms, and enabling access to foreign cells
130 (begins in <link linkend="HDRWQ71">Overview: Completing the Installation of the First AFS Machine</link>)</para>
132 </itemizedlist></para>
135 <primary>overview</primary>
137 <secondary>installing server functionality on first AFS machine</secondary>
141 <primary>first AFS machine</primary>
143 <secondary>server functionality</secondary>
147 <primary>installing</primary>
149 <secondary>server functionality</secondary>
151 <tertiary>first AFS machine</tertiary>
156 <title>Overview: Installing Server Functionality</title>
158 <para>In the first phase of installing your cell's first AFS machine, you install file server and database server functionality
159 by performing the following procedures:
162 <para>Choose which machine to install as the first AFS machine</para>
166 <para>Create AFS-related directories on the local disk</para>
170 <para>Incorporate AFS modifications into the machine's kernel</para>
174 <para>Configure partitions or logical volumes for storing AFS volumes</para>
178 <para>On some system types, install and configure an AFS-modified version of the <emphasis role="bold">fsck</emphasis>
183 <para>If the machine is to remain a client machine, incorporate AFS into its authentication system</para>
187 <para>Start the Basic OverSeer (BOS) Server</para>
191 <para>Define the cell name and the machine's cell membership</para>
195 <para>Start the database server processes: Backup Server, Protection Server, and Volume Location
200 <para>Configure initial security mechanisms</para>
204 <para>Start the <emphasis role="bold">fs</emphasis> process, which incorporates three component processes: the File
205 Server, Volume Server, and Salvager</para>
209 <para>Optionally, start the server portion of the Update Server</para>
212 </orderedlist></para>
216 <title>Choosing the First AFS Machine</title>
218 <para>The first AFS machine you install must have sufficient disk space to store AFS volumes. To take best advantage of AFS's
219 capabilities, store client-side binaries as well as user files in volumes. When you later install additional file server
220 machines in your cell, you can distribute these volumes among the different machines as you see fit.</para>
222 <para>These instructions configure the first AFS machine as a <emphasis>database server machine</emphasis>, the <emphasis>binary
223 distribution machine</emphasis> for its system type, and the cell's <emphasis>system control machine</emphasis>. For a
224 description of these roles, see the <emphasis>OpenAFS Administration Guide</emphasis>.</para>
226 <para>Installation of additional machines is simplest if the first machine has the lowest IP address of any database server
227 machine you currently plan to install. If you later install database server functionality on a machine with a lower IP address,
228 you must first update the <emphasis role="bold">/usr/vice/etc/CellServDB</emphasis> file on all of your cell's client machines.
229 For more details, see <link linkend="HDRWQ114">Installing Database Server Functionality</link>.</para>
232 <sect1 id="Header_32">
233 <title>Creating AFS Directories</title>
236 <primary>usr/afs directory</primary>
238 <secondary>first AFS machine</secondary>
242 <primary>first AFS machine</primary>
244 <secondary>/usr/afs directory</secondary>
248 <primary>creating</primary>
250 <secondary>/usr/afs directory</secondary>
252 <tertiary>first AFS machine</tertiary>
256 <primary>usr/vice/etc directory</primary>
258 <secondary>first AFS machine</secondary>
262 <primary>first AFS machine</primary>
264 <secondary>/usr/vice/etc directory</secondary>
268 <primary>creating</primary>
270 <secondary>/usr/vice/etc directory</secondary>
272 <tertiary>first AFS machine</tertiary>
276 <primary>/ as start to file and directory names</primary>
278 <secondary>see alphabetized entries without initial slash</secondary>
281 <para>If you are installing from packages (such as Debian .deb or
282 Fedora/SuSe .rpm files), you should now install all of the available
283 OpenAFS packages for your system type. Typically, these will include
284 packages for client and server functionality, and a seperate package
285 containing a suitable kernel module for your running kernel. Consult
286 the package lists on the OpenAFS website to determine the packages
287 appropriate for your system.</para>
289 <para>If you are installing from a tarfile, or from a locally compiled
290 source tree you should create the <emphasis role="bold">/usr/afs</emphasis>
291 and <emphasis role="bold">/usr/vice/etc</emphasis> directories on the
292 local disk, to house server and client files respectively. Subsequent
293 instructions copy files from the distribution tarfile into them. </para>
295 # <emphasis role="bold">mkdir /usr/afs</emphasis>
296 # <emphasis role="bold">mkdir /usr/vice</emphasis>
297 # <emphasis role="bold">mkdir /usr/vice/etc</emphasis>
302 <title>Performing Platform-Specific Procedures</title>
304 <para>Several of the initial procedures for installing a file server machine differ for each system type. For convenience, the
305 following sections group them together for each system type: <itemizedlist>
307 <primary>kernel extensions</primary>
309 <see>AFS kernel extensions</see>
313 <primary>loading AFS kernel extensions</primary>
315 <see>incorporating</see>
319 <primary>building</primary>
321 <secondary>AFS extensions into kernel</secondary>
323 <see>incorporating AFS kernel extensions</see>
327 <para>Incorporate AFS modifications into the kernel.</para>
329 <para>The kernel on every AFS client machine and, on some systems,
330 the AFS fileservers, must incorporate AFS extensions. On machines
331 that use a dynamic kernel module loader, it is conventional to
332 alter the machine's initialization script to load the AFS extensions
333 at each reboot. <indexterm>
334 <primary>AFS server partition</primary>
336 <secondary>mounted on /vicep directory</secondary>
337 </indexterm> <indexterm>
338 <primary>partition</primary>
340 <see>AFS server partition</see>
341 </indexterm> <indexterm>
342 <primary>logical volume</primary>
344 <see>AFS server partition</see>
345 </indexterm> <indexterm>
346 <primary>requirements</primary>
348 <secondary>AFS server partition name and location</secondary>
349 </indexterm> <indexterm>
350 <primary>naming conventions for AFS server partition</primary>
351 </indexterm> <indexterm>
352 <primary>vicep<emphasis>xx</emphasis> directory</primary>
354 <see>AFS server partition</see>
355 </indexterm> <indexterm>
356 <primary>directories</primary>
358 <secondary>/vicep<emphasis>xx</emphasis></secondary>
360 <see>AFS server partition</see>
365 <para>Configure server partitions or logical volumes to house AFS volumes.</para>
367 <para>Every AFS file server machine must have at least one partition or logical volume dedicated to storing AFS volumes
368 (for convenience, the documentation hereafter refers to partitions only). Each server partition is mounted at a directory
369 named <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>, where <replaceable>xx</replaceable> is one or
370 two lowercase letters. By convention, the first 26 partitions are mounted on the directories called <emphasis
371 role="bold">/vicepa</emphasis> through <emphasis role="bold">/vicepz</emphasis>, the 27th one is mounted on the <emphasis
372 role="bold">/vicepaa</emphasis> directory, and so on through <emphasis role="bold">/vicepaz</emphasis> and <emphasis
373 role="bold">/vicepba</emphasis>, continuing up to the index corresponding to the maximum number of server partitions
374 supported in the current version of AFS (which is specified in the <emphasis>OpenAFS Release Notes</emphasis>).</para>
376 <para>The <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable> directories must reside in the file server
377 machine's root directory, not in one of its subdirectories (for example, <emphasis role="bold">/usr/vicepa</emphasis> is
378 not an acceptable directory location).
380 The <emphasis role="bold">fileserver</emphasis> will refuse to
382 any <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>
383 folders that are not separate partitions. </para>
386 <para>The separate partition requirement may be overridden by
387 creating a file named
388 <emphasis role="bold">/vicep<replaceable>xx</replaceable>/AlwaysAttach</emphasis>;
389 however, mixed-use partitions, whether cache or fileserver,
390 have the risk that a non-AFS use will fill the partition and
391 not leave enough free space for AFS. Even though it is
392 allowed, be wary of configuring a mixed-use partition
393 without understanding the ramifications of doing so with the
394 workload on your filesystem.
396 <primary>AFS server partition</primary>
397 <secondary>AlwaysAttach</secondary>
402 <para>You can also add or remove server partitions on an existing file server machine. For instructions, see the chapter
403 in the <emphasis>OpenAFS Administration Guide</emphasis> about maintaining server machines.</para>
406 <para>Not all file system types supported by an operating system are necessarily supported as AFS server partitions. For
407 possible restrictions, see the <emphasis>OpenAFS Release Notes</emphasis>.</para>
412 <para>On system types using the <emphasis role="bold">inode</emphasis> storage format, install and configure a modified <emphasis role="bold">fsck</emphasis> program which
413 recognizes the structures that the File Server uses to organize volume data on AFS server partitions. The <emphasis
414 role="bold">fsck</emphasis> program provided with the operating system does not understand the AFS data structures, and so
415 removes them to the <emphasis role="bold">lost+found</emphasis> directory.</para>
419 <para>If the machine is to remain an AFS client machine, modify the machine's authentication system so that users obtain
420 an AFS token as they log into the local file system. Using AFS is simpler and more convenient for your users if you make
421 the modifications on all client machines. Otherwise, users must perform a two or three step login procedure (login to the local
422 system, then obtain Kerberos credentials, and then issue the <emphasis role="bold">aklog</emphasis> command). For further discussion of AFS
423 authentication, see the chapter in the <emphasis>OpenAFS Administration Guide</emphasis> about cell configuration and
424 administration issues.</para>
426 </itemizedlist></para>
428 <para>To continue, proceed to the appropriate section: <itemizedlist>
430 <para><link linkend="HDRWQ21">Getting Started on AIX Systems</link></para>
434 <para><link linkend="HDRWQ31">Getting Started on HP-UX Systems</link></para>
438 <para><link linkend="HDRWQ36">Getting Started on IRIX Systems</link></para>
442 <para><link linkend="HDRWQ41">Getting Started on Linux Systems</link></para>
446 <para><link linkend="HDRWQ45">Getting Started on Solaris Systems</link></para>
448 </itemizedlist></para>
452 <title>Getting Started on AIX Systems</title>
454 <para>Begin by running the AFS initialization script to call the AIX kernel extension facility, which dynamically loads AFS
455 modifications into the kernel. Then use the <emphasis role="bold">SMIT</emphasis> program to configure partitions for storing
456 AFS volumes, and replace the AIX <emphasis role="bold">fsck</emphasis> program helper with a version that correctly handles AFS
457 volumes. If the machine is to remain an AFS client machine, incorporate AFS into the AIX secondary authentication system.
459 <primary>incorporating AFS kernel extensions</primary>
461 <secondary>first AFS machine</secondary>
463 <tertiary>AIX</tertiary>
464 </indexterm> <indexterm>
465 <primary>AFS kernel extensions</primary>
467 <secondary>on first AFS machine</secondary>
469 <tertiary>AIX</tertiary>
470 </indexterm> <indexterm>
471 <primary>first AFS machine</primary>
473 <secondary>AFS kernel extensions</secondary>
475 <tertiary>on AIX</tertiary>
476 </indexterm> <indexterm>
477 <primary>AIX</primary>
479 <secondary>AFS kernel extensions</secondary>
481 <tertiary>on first AFS machine</tertiary>
485 <title>Loading AFS into the AIX Kernel</title>
487 <para>The AIX kernel extension facility is the dynamic kernel loader
488 provided by IBM Corporation. AIX does not support incorporation of
489 AFS modifications during a kernel build.</para>
491 <para>For AFS to function correctly, the kernel extension facility must run each time the machine reboots, so the AFS
492 initialization script (included in the AFS distribution) invokes it automatically. In this section you copy the script to the
493 conventional location and edit it to select the appropriate options depending on whether NFS is also to run.</para>
495 <para>After editing the script, you run it to incorporate AFS into the kernel. In later sections you verify that the script
496 correctly initializes all AFS components, then configure the AIX <emphasis role="bold">inittab</emphasis> file so that the
497 script runs automatically at reboot. <orderedlist>
499 <para>Unpack the distribution tarball. The examples below assume
500 that you have unpacked the files into the
501 <emphasis role="bold">/tmp/afsdist</emphasis> directory. If you
502 pick a different location, substitute this in all of the following
503 examples. Once you have unpacked the distribution,
504 change directory as indicated.
506 # <emphasis role="bold">cd /tmp/afsdist/rs_aix42/root.client/usr/vice/etc</emphasis>
507 </programlisting></para>
511 <para>Copy the AFS kernel library files to the local <emphasis role="bold">/usr/vice/etc/dkload</emphasis> directory,
512 and the AFS initialization script to the <emphasis role="bold">/etc</emphasis> directory. <programlisting>
513 # <emphasis role="bold">cp -rp dkload /usr/vice/etc</emphasis>
514 # <emphasis role="bold">cp -p rc.afs /etc/rc.afs</emphasis>
515 </programlisting></para>
519 <para>Edit the <emphasis role="bold">/etc/rc.afs</emphasis> script, setting the <computeroutput>NFS</computeroutput>
520 variable as indicated.</para>
522 <para>If the machine is not to function as an NFS/AFS Translator, set the <computeroutput>NFS</computeroutput> variable
529 <para>If the machine is to function as an NFS/AFS Translator and is running AIX 4.2.1 or higher, set the
530 <computeroutput>NFS</computeroutput> variable as follows. Note that NFS must already be loaded into the kernel, which
531 happens automatically on systems running AIX 4.1.1 and later, as long as the file <emphasis
532 role="bold">/etc/exports</emphasis> exists.</para>
540 <para>Invoke the <emphasis role="bold">/etc/rc.afs</emphasis> script to load AFS modifications into the kernel. You can
541 ignore any error messages about the inability to start the BOS Server or the Cache Manager or AFS client.
543 # <emphasis role="bold">/etc/rc.afs</emphasis>
544 </programlisting></para>
546 </orderedlist></para>
549 <primary>configuring</primary>
551 <secondary>AFS server partition on first AFS machine</secondary>
553 <tertiary>AIX</tertiary>
557 <primary>AFS server partition</primary>
559 <secondary>configuring on first AFS machine</secondary>
561 <tertiary>AIX</tertiary>
565 <primary>first AFS machine</primary>
567 <secondary>AFS server partition</secondary>
569 <tertiary>on AIX</tertiary>
573 <primary>AIX</primary>
575 <secondary>AFS server partition</secondary>
577 <tertiary>on first AFS machine</tertiary>
582 <title>Configuring Server Partitions on AIX Systems</title>
584 <para>Every AFS file server machine must have at least one partition or logical volume dedicated to storing AFS volumes. Each
585 server partition is mounted at a directory named <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>, where
586 <replaceable>xx</replaceable> is one or two lowercase letters. The <emphasis
587 role="bold">/vicep</emphasis><replaceable>xx</replaceable> directories must reside in the file server machine's root
588 directory, not in one of its subdirectories (for example, <emphasis role="bold">/usr/vicepa</emphasis> is not an acceptable
589 directory location). For additional information, see <link linkend="HDRWQ20">Performing Platform-Specific
590 Procedures</link>.</para>
592 <para>To configure server partitions on an AIX system, perform the following procedures: <orderedlist>
594 <para>Create a directory called <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable> for each AFS server
595 partition you are configuring (there must be at least one). Repeat the command for each partition. <programlisting>
596 # <emphasis role="bold">mkdir /vicep</emphasis><replaceable>xx</replaceable>
597 </programlisting></para>
601 <para>Use the <emphasis role="bold">SMIT</emphasis> program to create a journaling file system on each partition to be
602 configured as an AFS server partition.</para>
606 <para>Mount each partition at one of the <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>
607 directories. Choose one of the following three methods: <itemizedlist>
609 <para>Use the <emphasis role="bold">SMIT</emphasis> program</para>
613 <para>Use the <emphasis role="bold">mount -a</emphasis> command to mount all partitions at once</para>
617 <para>Use the <emphasis role="bold">mount</emphasis> command on each partition in turn</para>
619 </itemizedlist></para>
621 <para>Also configure the partitions so that they are mounted automatically at each reboot. For more information, refer
622 to the AIX documentation.</para>
624 </orderedlist></para>
627 <primary>replacing fsck program</primary>
629 <secondary>first AFS machine</secondary>
631 <tertiary>AIX</tertiary>
635 <primary>fsck program</primary>
637 <secondary>on first AFS machine</secondary>
639 <tertiary>AIX</tertiary>
643 <primary>first AFS machine</primary>
645 <secondary>fsck program</secondary>
647 <tertiary>on AIX</tertiary>
651 <primary>AIX</primary>
653 <secondary>fsck program</secondary>
655 <tertiary>on first AFS machine</tertiary>
660 <title>Replacing the fsck Program Helper on AIX Systems</title>
662 <note><para>The AFS modified fsck program is not required on AIX 5.1
663 systems, and the <emphasis role="bold">v3fshelper</emphasis> program
664 refered to below is not shipped for these systems.</para></note>
666 <para>In this section, you make modifications to guarantee that the appropriate <emphasis role="bold">fsck</emphasis> program
667 runs on AFS server partitions. The <emphasis role="bold">fsck</emphasis> program provided with the operating system must never
668 run on AFS server partitions. Because it does not recognize the structures that the File Server uses to organize volume data,
669 it removes all of the data. To repeat:</para>
671 <para><emphasis role="bold">Never run the standard fsck program on AFS server partitions. It discards AFS
672 volumes.</emphasis></para>
674 <para>On AIX systems, you do not replace the <emphasis role="bold">fsck</emphasis> binary itself, but rather the
675 <emphasis>program helper</emphasis> file included in the AIX distribution as <emphasis
676 role="bold">/sbin/helpers/v3fshelper</emphasis>. <orderedlist>
678 <para>Move the AIX <emphasis role="bold">fsck</emphasis> program helper to a safe location and install the version from
679 the AFS distribution in its place.
681 # <emphasis role="bold">cd /sbin/helpers</emphasis>
682 # <emphasis role="bold">mv v3fshelper v3fshelper.noafs</emphasis>
683 # <emphasis role="bold">cp -p /tmp/afsdist/rs_aix42/root.server/etc/v3fshelper v3fshelper</emphasis>
684 </programlisting></para>
688 <para>If you plan to retain client functionality on this machine after completing the installation, proceed to <link
689 linkend="HDRWQ25">Enabling AFS Login on AIX Systems</link>. Otherwise, proceed to <link linkend="HDRWQ50">Starting the
690 BOS Server</link>.</para>
692 </orderedlist></para>
695 <primary>enabling AFS login</primary>
697 <secondary>file server machine</secondary>
699 <tertiary>AIX</tertiary>
703 <primary>AFS login</primary>
705 <secondary>on file server machine</secondary>
707 <tertiary>AIX</tertiary>
711 <primary>first AFS machine</primary>
713 <secondary>AFS login</secondary>
715 <tertiary>on AIX</tertiary>
719 <primary>AIX</primary>
721 <secondary>AFS login</secondary>
723 <tertiary>on file server machine</tertiary>
727 <primary>secondary authentication system (AIX)</primary>
729 <secondary>server machine</secondary>
734 <title>Enabling AFS Login on AIX Systems</title>
737 <para>If you plan to remove client functionality from this machine after completing the installation, skip this section and
738 proceed to <link linkend="HDRWQ50">Starting the BOS Server</link>.</para>
741 <para>In modern AFS installations, you should be using Kerberos v5
742 for user login, and obtaining AFS tokens following this authentication
745 <para>There are currently no instructions available on configuring AIX to
746 automatically obtain AFS tokens at login. Following login, users can
747 obtain tokens by running the <emphasis role="bold">aklog</emphasis>
750 <para>Sites which still require <emphasis role="bold">kaserver</emphasis>
751 or external Kerberos v4 authentication should consult
752 <link linkend="KAS012">Enabling kaserver based AFS login on AIX systems</link>
753 for details of how to enable AIX login.</para>
755 <para>Proceed to <link linkend="HDRWQ50">Starting the BOS Server</link>
756 (or if referring to these instructions while installing an additional
757 file server machine, return to <link linkend="HDRWQ108">Starting Server
758 Programs</link>).</para>
763 <title>Getting Started on HP-UX Systems</title>
765 <para>Begin by building AFS modifications into a new kernel; HP-UX
766 does not support dynamic loading. Then create partitions for storing
767 AFS volumes, and install and configure the AFS-modified <emphasis
768 role="bold">fsck</emphasis> program to run on AFS server
769 partitions. If the machine is to remain an AFS client machine,
770 incorporate AFS into the machine's Pluggable Authentication Module
771 (PAM) scheme. <indexterm>
772 <primary>incorporating AFS kernel extensions</primary>
774 <secondary>first AFS machine</secondary>
776 <tertiary>HP-UX</tertiary>
777 </indexterm> <indexterm>
778 <primary>AFS kernel extensions</primary>
780 <secondary>on first AFS machine</secondary>
782 <tertiary>HP-UX</tertiary>
783 </indexterm> <indexterm>
784 <primary>first AFS machine</primary>
786 <secondary>AFS kernel extensions</secondary>
788 <tertiary>on HP-UX</tertiary>
789 </indexterm> <indexterm>
790 <primary>HP-UX</primary>
792 <secondary>AFS-modified kernel</secondary>
794 <tertiary>on first AFS machine</tertiary>
798 <title>Building AFS into the HP-UX Kernel</title>
800 <para>Use the following instructions to build AFS modifications into the kernel on an HP-UX system. <orderedlist>
802 <para>Move the existing kernel-related files to a safe location. <programlisting>
803 # <emphasis role="bold">cp /stand/vmunix /stand/vmunix.noafs</emphasis>
804 # <emphasis role="bold">cp /stand/system /stand/system.noafs</emphasis>
805 </programlisting></para>
809 <para>Unpack the OpenAFS HP-UX distribution tarball. The examples
810 below assume that you have unpacked the files into the
811 <emphasis role="bold">/tmp/afsdist</emphasis> directory. If you
812 pick a different location, substitute this in all of the following
813 examples. Once you have unpacked the distribution, change directory
816 # <emphasis role="bold">cd /tmp/afsdist/hp_ux110/root.client</emphasis>
817 </programlisting></para>
821 <para>Copy the AFS initialization file to the local directory for initialization files (by convention, <emphasis
822 role="bold">/sbin/init.d</emphasis> on HP-UX machines). Note the removal of the <emphasis role="bold">.rc</emphasis>
823 extension as you copy the file. <programlisting>
824 # <emphasis role="bold">cp usr/vice/etc/afs.rc /sbin/init.d/afs</emphasis>
825 </programlisting></para>
829 <para>Copy the file <emphasis role="bold">afs.driver</emphasis> to the local <emphasis
830 role="bold">/usr/conf/master.d</emphasis> directory, changing its name to <emphasis role="bold">afs</emphasis> as you
832 # <emphasis role="bold">cp usr/vice/etc/afs.driver /usr/conf/master.d/afs</emphasis>
833 </programlisting></para>
837 <para>Copy the AFS kernel module to the local <emphasis role="bold">/usr/conf/lib</emphasis> directory.</para>
839 <para>If the machine's kernel supports NFS server functionality:</para>
842 # <emphasis role="bold">cp bin/libafs.a /usr/conf/lib</emphasis>
845 <para>If the machine's kernel does not support NFS server functionality, change the file's name as you copy it:</para>
848 # <emphasis role="bold">cp bin/libafs.nonfs.a /usr/conf/lib/libafs.a</emphasis>
853 <para>Incorporate the AFS driver into the kernel, either using the <emphasis role="bold">SAM</emphasis> program or a
854 series of individual commands. <itemizedlist>
856 <para>To use the <emphasis role="bold">SAM</emphasis> program: <orderedlist>
858 <para>Invoke the <emphasis role="bold">SAM</emphasis> program, specifying the hostname of the local machine
859 as <replaceable>local_hostname</replaceable>. The <emphasis role="bold">SAM</emphasis> graphical user
860 interface pops up. <programlisting>
861 # <emphasis role="bold">sam -display</emphasis> <replaceable>local_hostname</replaceable><emphasis role="bold">:0</emphasis>
862 </programlisting></para>
866 <para>Choose the <emphasis role="bold">Kernel Configuration</emphasis> icon, then the <emphasis
867 role="bold">Drivers</emphasis> icon. From the list of drivers, select <emphasis
868 role="bold">afs</emphasis>.</para>
872 <para>Open the pull-down <emphasis role="bold">Actions</emphasis> menu and choose the <emphasis
873 role="bold">Add Driver to Kernel</emphasis> option.</para>
877 <para>Open the <emphasis role="bold">Actions</emphasis> menu again and choose the <emphasis
878 role="bold">Create a New Kernel</emphasis> option.</para>
882 <para>Confirm your choices by choosing <emphasis role="bold">Yes</emphasis> and <emphasis
883 role="bold">OK</emphasis> when prompted by subsequent pop-up windows. The <emphasis
884 role="bold">SAM</emphasis> program builds the kernel and reboots the system.</para>
888 <para>Login again as the superuser <emphasis role="bold">root</emphasis>. <programlisting>
889 login: <emphasis role="bold">root</emphasis>
890 Password: <replaceable>root_password</replaceable>
891 </programlisting></para>
893 </orderedlist></para>
897 <para>To use individual commands: <orderedlist>
899 <para>Edit the file <emphasis role="bold">/stand/system</emphasis>, adding an entry for <emphasis
900 role="bold">afs</emphasis> to the <computeroutput>Subsystems</computeroutput> section.</para>
904 <para>Change to the <emphasis role="bold">/stand/build</emphasis> directory and issue the <emphasis
905 role="bold">mk_kernel</emphasis> command to build the kernel. <programlisting>
906 # <emphasis role="bold">cd /stand/build</emphasis>
907 # <emphasis role="bold">mk_kernel</emphasis>
908 </programlisting></para>
912 <para>Move the new kernel to the standard location (<emphasis role="bold">/stand/vmunix</emphasis>), reboot
913 the machine to start using it, and login again as the superuser <emphasis role="bold">root</emphasis>.
915 # <emphasis role="bold">mv /stand/build/vmunix_test /stand/vmunix</emphasis>
916 # <emphasis role="bold">cd /</emphasis>
917 # <emphasis role="bold">shutdown -r now</emphasis>
918 login: <emphasis role="bold">root</emphasis>
919 Password: <replaceable>root_password</replaceable>
920 </programlisting></para>
922 </orderedlist></para>
924 </itemizedlist></para>
926 </orderedlist></para>
929 <primary>configuring</primary>
931 <secondary>AFS server partition on first AFS machine</secondary>
933 <tertiary>HP-UX</tertiary>
937 <primary>AFS server partition</primary>
939 <secondary>configuring on first AFS machine</secondary>
941 <tertiary>HP-UX</tertiary>
945 <primary>first AFS machine</primary>
947 <secondary>AFS server partition</secondary>
949 <tertiary>on HP-UX</tertiary>
953 <primary>HP-UX</primary>
955 <secondary>AFS server partition</secondary>
957 <tertiary>on first AFS machine</tertiary>
962 <title>Configuring Server Partitions on HP-UX Systems</title>
964 <para>Every AFS file server machine must have at least one partition or logical volume dedicated to storing AFS volumes. Each
965 server partition is mounted at a directory named <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>, where
966 <replaceable>xx</replaceable> is one or two lowercase letters. The <emphasis
967 role="bold">/vicep</emphasis><replaceable>xx</replaceable> directories must reside in the file server machine's root
968 directory, not in one of its subdirectories (for example, <emphasis role="bold">/usr/vicepa</emphasis> is not an acceptable
969 directory location). For additional information, see <link linkend="HDRWQ20">Performing Platform-Specific Procedures</link>.
972 <para>Create a directory called <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable> for each AFS server
973 partition you are configuring (there must be at least one). Repeat the command for each partition. <programlisting>
974 # <emphasis role="bold">mkdir /vicep</emphasis><replaceable>xx</replaceable>
975 </programlisting></para>
979 <para>Use the <emphasis role="bold">SAM</emphasis> program to create a file system on each partition. For instructions,
980 consult the HP-UX documentation.</para>
984 <para>On some HP-UX systems that use logical volumes, the <emphasis role="bold">SAM</emphasis> program automatically
985 mounts the partitions. If it has not, mount each partition by issuing either the <emphasis role="bold">mount
986 -a</emphasis> command to mount all partitions at once or the <emphasis role="bold">mount</emphasis> command to mount
987 each partition in turn.</para>
989 </orderedlist></para>
992 <primary>replacing fsck program</primary>
994 <secondary>first AFS machine</secondary>
996 <tertiary>HP-UX</tertiary>
1000 <primary>fsck program</primary>
1002 <secondary>on first AFS machine</secondary>
1004 <tertiary>HP-UX</tertiary>
1008 <primary>first AFS machine</primary>
1010 <secondary>fsck program</secondary>
1012 <tertiary>on HP-UX</tertiary>
1016 <primary>HP-UX</primary>
1018 <secondary>fsck program</secondary>
1020 <tertiary>on first AFS machine</tertiary>
1024 <sect2 id="HDRWQ34">
1025 <title>Configuring the AFS-modified fsck Program on HP-UX Systems</title>
1027 <para>In this section, you make modifications to guarantee that the appropriate <emphasis role="bold">fsck</emphasis> program
1028 runs on AFS server partitions. The <emphasis role="bold">fsck</emphasis> program provided with the operating system must never
1029 run on AFS server partitions. Because it does not recognize the structures that the File Server uses to organize volume data,
1030 it removes all of the data. To repeat:</para>
1032 <para><emphasis role="bold">Never run the standard fsck program on AFS server partitions. It discards AFS
1033 volumes.</emphasis></para>
1035 <para>On HP-UX systems, there are several configuration files to install in addition to the AFS-modified <emphasis
1036 role="bold">fsck</emphasis> program (the <emphasis role="bold">vfsck</emphasis> binary). <orderedlist>
1038 <para>Create the command configuration file <emphasis role="bold">/sbin/lib/mfsconfig.d/afs</emphasis>. Use a text
1039 editor to place the indicated two lines in it: <programlisting>
1041 fsck 0 m,P,p,d,f,b:c:y,n,Y,N,q,
1042 </programlisting></para>
1046 <para>Create and change directory to an AFS-specific command directory called <emphasis
1047 role="bold">/sbin/fs/afs</emphasis>. <programlisting>
1048 # <emphasis role="bold">mkdir /sbin/fs/afs</emphasis>
1049 # <emphasis role="bold">cd /sbin/fs/afs</emphasis>
1050 </programlisting></para>
1054 <para>Copy the AFS-modified version of the <emphasis role="bold">fsck</emphasis> program (the <emphasis
1055 role="bold">vfsck</emphasis> binary) and related files from the distribution directory to the new AFS-specific command
1056 directory. <programlisting>
1057 # <emphasis role="bold">cp -p /tmp/afsdist/hp_ux110/root.server/etc/* .</emphasis>
1058 </programlisting></para>
1062 <para>Change the <emphasis role="bold">vfsck</emphasis> binary's name to <emphasis role="bold">fsck</emphasis> and set
1063 the mode bits appropriately on all of the files in the <emphasis role="bold">/sbin/fs/afs</emphasis> directory.
1065 # <emphasis role="bold">mv vfsck fsck</emphasis>
1066 # <emphasis role="bold">chmod 755 *</emphasis>
1067 </programlisting></para>
1071 <para>Edit the <emphasis role="bold">/etc/fstab</emphasis> file, changing the file system type for each AFS server
1072 partition from <computeroutput>hfs</computeroutput> to <computeroutput>afs</computeroutput>. This ensures that the
1073 AFS-modified <emphasis role="bold">fsck</emphasis> program runs on the appropriate partitions.</para>
1075 <para>The sixth line in the following example of an edited file shows an AFS server partition, <emphasis
1076 role="bold">/vicepa</emphasis>.</para>
1079 /dev/vg00/lvol1 / hfs defaults 0 1
1080 /dev/vg00/lvol4 /opt hfs defaults 0 2
1081 /dev/vg00/lvol5 /tmp hfs defaults 0 2
1082 /dev/vg00/lvol6 /usr hfs defaults 0 2
1083 /dev/vg00/lvol8 /var hfs defaults 0 2
1084 /dev/vg00/lvol9 /vicepa afs defaults 0 2
1085 /dev/vg00/lvol7 /usr/vice/cache hfs defaults 0 2
1090 <para>If you plan to retain client functionality on this machine after completing the installation, proceed to <link
1091 linkend="HDRWQ35">Enabling AFS Login on HP-UX Systems</link>. Otherwise, proceed to <link linkend="HDRWQ50">Starting the
1092 BOS Server</link>.</para>
1094 </orderedlist></para>
1097 <primary>enabling AFS login</primary>
1099 <secondary>file server machine</secondary>
1101 <tertiary>HP-UX</tertiary>
1105 <primary>AFS login</primary>
1107 <secondary>on file server machine</secondary>
1109 <tertiary>HP-UX</tertiary>
1113 <primary>first AFS machine</primary>
1115 <secondary>AFS login</secondary>
1117 <tertiary>on HP-UX</tertiary>
1121 <primary>HP-UX</primary>
1123 <secondary>AFS login</secondary>
1125 <tertiary>on file server machine</tertiary>
1129 <primary>PAM</primary>
1131 <secondary>on HP-UX</secondary>
1133 <tertiary>file server machine</tertiary>
1137 <primary>Pluggable Authentication Module</primary>
1143 <sect2 id="HDRWQ35">
1144 <title>Enabling AFS Login on HP-UX Systems</title>
1146 <note><para>If you plan to remove client functionality from this machine after completing the installation, skip this section and proceed to <link linkend="HDRWQ50">Starting the BOS Server</link>.</para></note>
1148 <para>At this point you incorporate AFS into the operating system's
1149 Pluggable Authentication Module (PAM) scheme. PAM integrates all
1150 authentication mechanisms on the machine, including login, to
1151 provide the security infrastructure for authenticated access to and
1152 from the machine.</para>
1154 <para>In modern AFS installations, you should be using Kerberos v5
1155 for user login, and obtaining AFS tokens subsequent to this
1156 authentication step. OpenAFS does not currently distribute a PAM
1157 module allowing AFS tokens to be automatically gained at
1158 login. Whilst there are a number of third party modules providing
1159 this functionality, it is not know if these have been tested with
1162 <para>Following login, users can obtain tokens by running the
1163 <emphasis role="bold">aklog</emphasis> command</para>
1165 <para>Sites which still require <emphasis
1166 role="bold">kaserver</emphasis> or external Kerberos v4
1167 authentication should consult <link linkend="KAS013">Enabling
1168 kaserver based AFS login on HP-UX systems</link> for details of how
1169 to enable HP-UX login.</para>
1171 <para>Proceed to <link linkend="HDRWQ50">Starting the BOS
1172 Server</link> (or if referring to these instructions while
1173 installing an additional file server machine, return to <link
1174 linkend="HDRWQ108">Starting Server Programs</link>).</para>
1178 <sect1 id="HDRWQ36">
1179 <title>Getting Started on IRIX Systems</title>
1182 <primary>incorporating AFS kernel extensions</primary>
1184 <secondary>first AFS machine</secondary>
1186 <tertiary>IRIX</tertiary>
1190 <primary>AFS kernel extensions</primary>
1192 <secondary>on first AFS machine</secondary>
1194 <tertiary>IRIX</tertiary>
1198 <primary>first AFS machine</primary>
1200 <secondary>AFS kernel extensions</secondary>
1202 <tertiary>on IRIX</tertiary>
1206 <primary>replacing fsck program</primary>
1208 <secondary>not necessary on IRIX</secondary>
1212 <primary>fsck program</primary>
1214 <secondary>on first AFS machine</secondary>
1216 <tertiary>IRIX</tertiary>
1220 <primary>first AFS machine</primary>
1222 <secondary>fsck program</secondary>
1224 <tertiary>on IRIX</tertiary>
1228 <primary>IRIX</primary>
1230 <secondary>fsck program replacement not necessary</secondary>
1233 <para>To incorporate AFS into the kernel on IRIX systems, choose one of two methods: <itemizedlist>
1235 <para>Run the AFS initialization script to invoke the <emphasis role="bold">ml</emphasis> program distributed by Silicon
1236 Graphics, Incorporated (SGI), which dynamically loads AFS modifications into the kernel</para>
1240 <para>Build a new static kernel</para>
1242 </itemizedlist></para>
1244 <para>Then create partitions for storing AFS volumes. You do not need to replace the IRIX <emphasis role="bold">fsck</emphasis>
1245 program because SGI has already modified it to handle AFS volumes properly. If the machine is to remain an AFS client machine,
1246 verify that the IRIX login utility installed on the machine grants an AFS token.</para>
1248 <para>In preparation for either dynamic loading or kernel building, perform the following procedures: <orderedlist>
1250 <para>Unpack the OpenAFS IRIX distribution tarball. The examples
1251 below assume that you have unpacked the files into the
1252 <emphasis role="bold">/tmp/afsdist</emphasis> directory. If you
1253 pick a different location, substitue this in all of the following
1254 examples. Once you have unpacked the distribution, change directory
1257 # <emphasis role="bold">cd /tmp/afsdist/sgi_65/root.client</emphasis>
1258 </programlisting></para>
1262 <para>Copy the AFS initialization script to the local directory for initialization files (by convention, <emphasis
1263 role="bold">/etc/init.d</emphasis> on IRIX machines). Note the removal of the <emphasis role="bold">.rc</emphasis>
1264 extension as you copy the script. <programlisting>
1265 # <emphasis role="bold">cp -p usr/vice/etc/afs.rc /etc/init.d/afs</emphasis>
1266 </programlisting></para>
1270 <para>Issue the <emphasis role="bold">uname -m</emphasis> command to determine the machine's CPU board type. The <emphasis
1271 role="bold">IP</emphasis><replaceable>xx</replaceable> value in the output must match one of the supported CPU board types
1272 listed in the <emphasis>OpenAFS Release Notes</emphasis> for the current version of AFS. <programlisting>
1273 # <emphasis role="bold">uname -m</emphasis>
1274 </programlisting></para>
1278 <para>Proceed to either <link linkend="HDRWQ37">Loading AFS into the IRIX Kernel</link> or <link
1279 linkend="HDRWQ38">Building AFS into the IRIX Kernel</link>.</para>
1281 </orderedlist></para>
1284 <primary>IRIX</primary>
1286 <secondary>AFS kernel extensions</secondary>
1288 <tertiary>on first AFS machine</tertiary>
1292 <primary>afsml variable (IRIX)</primary>
1294 <secondary>first AFS machine</secondary>
1298 <primary>variables</primary>
1300 <secondary>afsml (IRIX)</secondary>
1302 <tertiary>first AFS machine</tertiary>
1306 <primary>IRIX</primary>
1308 <secondary>afsml variable</secondary>
1310 <tertiary>first AFS machine</tertiary>
1314 <primary>afsxnfs variable (IRIX)</primary>
1316 <secondary>first AFS machine</secondary>
1320 <primary>variables</primary>
1322 <secondary>afsxnfs (IRIX)</secondary>
1324 <tertiary>first AFS machine</tertiary>
1328 <primary>IRIX</primary>
1330 <secondary>afsxnfs variable</secondary>
1332 <tertiary>first AFS machine</tertiary>
1335 <sect2 id="HDRWQ37">
1336 <title>Loading AFS into the IRIX Kernel</title>
1338 <para>The <emphasis role="bold">ml</emphasis> program is the dynamic kernel loader provided by SGI for IRIX systems. If you
1339 use it rather than building AFS modifications into a static kernel, then for AFS to function correctly the <emphasis
1340 role="bold">ml</emphasis> program must run each time the machine reboots. Therefore, the AFS initialization script (included
1341 on the AFS CD-ROM) invokes it automatically when the <emphasis role="bold">afsml</emphasis> configuration variable is
1342 activated. In this section you activate the variable and run the script.</para>
1344 <para>In later sections you verify that the script correctly initializes all AFS components, then create the links that
1345 incorporate AFS into the IRIX startup and shutdown sequence. <orderedlist>
1347 <para>Create the local <emphasis role="bold">/usr/vice/etc/sgiload</emphasis> directory to house the AFS kernel library
1348 file. <programlisting>
1349 # <emphasis role="bold">mkdir /usr/vice/etc/sgiload</emphasis>
1350 </programlisting></para>
1354 <para>Copy the appropriate AFS kernel library file to the <emphasis role="bold">/usr/vice/etc/sgiload</emphasis>
1355 directory. The <emphasis role="bold">IP</emphasis><replaceable>xx</replaceable> portion of the library file name must
1356 match the value previously returned by the <emphasis role="bold">uname -m</emphasis> command. Also choose the file
1357 appropriate to whether the machine's kernel supports NFS server functionality (NFS must be supported for the machine to
1358 act as an NFS/AFS Translator). Single- and multiprocessor machines use the same library file.</para>
1360 <para>(You can choose to copy all of the kernel library files into the <emphasis
1361 role="bold">/usr/vice/etc/sgiload</emphasis> directory, but they require a significant amount of space.)</para>
1363 <para>If the machine's kernel supports NFS server functionality:</para>
1366 # <emphasis role="bold">cp -p usr/vice/etc/sgiload/libafs.IP</emphasis><replaceable>xx</replaceable><emphasis role="bold">.o /usr/vice/etc/sgiload</emphasis>
1369 <para>If the machine's kernel does not support NFS server functionality:</para>
1372 # <emphasis role="bold">cp -p usr/vice/etc/sgiload/libafs.IP</emphasis><replaceable>xx</replaceable><emphasis role="bold">.nonfs.o</emphasis> \
1373 <emphasis role="bold">/usr/vice/etc/sgiload</emphasis>
1378 <para>Issue the <emphasis role="bold">chkconfig</emphasis> command to activate the <emphasis
1379 role="bold">afsml</emphasis> configuration variable. <programlisting>
1380 # <emphasis role="bold">/etc/chkconfig -f afsml on</emphasis>
1381 </programlisting></para>
1383 <para>If the machine is to function as an NFS/AFS Translator and the kernel supports NFS server functionality, activate
1384 the <emphasis role="bold">afsxnfs</emphasis> variable.</para>
1387 # <emphasis role="bold">/etc/chkconfig -f afsxnfs on</emphasis>
1392 <para>Run the <emphasis role="bold">/etc/init.d/afs</emphasis> script to load AFS extensions into the kernel. The script
1393 invokes the <emphasis role="bold">ml</emphasis> command, automatically determining which kernel library file to use
1394 based on this machine's CPU type and the activation state of the <emphasis role="bold">afsxnfs</emphasis>
1397 <para>You can ignore any error messages about the inability to start the BOS Server or the Cache Manager or AFS
1401 # <emphasis role="bold">/etc/init.d/afs start</emphasis>
1406 <para>Proceed to <link linkend="HDRWQ39">Configuring Server Partitions on IRIX Systems</link>.</para>
1408 </orderedlist></para>
1411 <primary>IRIX</primary>
1413 <secondary>AFS-modified kernel</secondary>
1415 <tertiary>on first AFS machine</tertiary>
1419 <sect2 id="HDRWQ38">
1420 <title>Building AFS into the IRIX Kernel</title>
1422 <para>Use the following instructions to build AFS modifications into the kernel on an IRIX system. <orderedlist>
1424 <para>Copy the kernel initialization file <emphasis role="bold">afs.sm</emphasis> to the local <emphasis
1425 role="bold">/var/sysgen/system</emphasis> directory, and the kernel master file <emphasis role="bold">afs</emphasis> to
1426 the local <emphasis role="bold">/var/sysgen/master.d</emphasis> directory. <programlisting>
1427 # <emphasis role="bold">cp -p bin/afs.sm /var/sysgen/system</emphasis>
1428 # <emphasis role="bold">cp -p bin/afs /var/sysgen/master.d</emphasis>
1429 </programlisting></para>
1433 <para>Copy the appropriate AFS kernel library file to the local file <emphasis
1434 role="bold">/var/sysgen/boot/afs.a</emphasis>; the <emphasis role="bold">IP</emphasis><replaceable>xx</replaceable>
1435 portion of the library file name must match the value previously returned by the <emphasis role="bold">uname
1436 -m</emphasis> command. Also choose the file appropriate to whether the machine's kernel supports NFS server
1437 functionality (NFS must be supported for the machine to act as an NFS/AFS Translator). Single- and multiprocessor
1438 machines use the same library file.</para>
1440 <para>If the machine's kernel supports NFS server functionality:</para>
1443 # <emphasis role="bold">cp -p bin/libafs.IP</emphasis><replaceable>xx</replaceable><emphasis role="bold">.a /var/sysgen/boot/afs.a</emphasis>
1446 <para>If the machine's kernel does not support NFS server functionality:</para>
1449 # <emphasis role="bold">cp -p bin/libafs.IP</emphasis><replaceable>xx</replaceable><emphasis role="bold">.nonfs.a /var/sysgen/boot/afs.a</emphasis>
1454 <para>Issue the <emphasis role="bold">chkconfig</emphasis> command to deactivate the <emphasis
1455 role="bold">afsml</emphasis> configuration variable. <programlisting>
1456 # <emphasis role="bold">/etc/chkconfig -f afsml off</emphasis>
1457 </programlisting></para>
1459 <para>If the machine is to function as an NFS/AFS Translator and the kernel supports NFS server functionality, activate
1460 the <emphasis role="bold">afsxnfs</emphasis> variable.</para>
1463 # <emphasis role="bold">/etc/chkconfig -f afsxnfs on</emphasis>
1468 <para>Copy the existing kernel file, <emphasis role="bold">/unix</emphasis>, to a safe location. Compile the new kernel,
1469 which is created in the file <emphasis role="bold">/unix.install</emphasis>. It overwrites the existing <emphasis
1470 role="bold">/unix</emphasis> file when the machine reboots in the next step. <programlisting>
1471 # <emphasis role="bold">cp /unix /unix_noafs</emphasis>
1472 # <emphasis role="bold">autoconfig</emphasis>
1473 </programlisting></para>
1477 <para>Reboot the machine to start using the new kernel, and login again as the superuser <emphasis
1478 role="bold">root</emphasis>. <programlisting>
1479 # <emphasis role="bold">cd /</emphasis>
1480 # <emphasis role="bold">shutdown -i6 -g0 -y</emphasis>
1481 login: <emphasis role="bold">root</emphasis>
1482 Password: <replaceable>root_password</replaceable>
1483 </programlisting></para>
1485 </orderedlist></para>
1488 <primary>configuring</primary>
1490 <secondary>AFS server partition on first AFS machine</secondary>
1492 <tertiary>IRIX</tertiary>
1496 <primary>AFS server partition</primary>
1498 <secondary>configuring on first AFS machine</secondary>
1500 <tertiary>IRIX</tertiary>
1504 <primary>first AFS machine</primary>
1506 <secondary>AFS server partition</secondary>
1508 <tertiary>on IRIX</tertiary>
1512 <primary>IRIX</primary>
1514 <secondary>AFS server partition</secondary>
1516 <tertiary>on first AFS machine</tertiary>
1520 <sect2 id="HDRWQ39">
1521 <title>Configuring Server Partitions on IRIX Systems</title>
1523 <para>Every AFS file server machine must have at least one partition or logical volume dedicated to storing AFS volumes. Each
1524 server partition is mounted at a directory named <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>, where
1525 <replaceable>xx</replaceable> is one or two lowercase letters. The <emphasis
1526 role="bold">/vicep</emphasis><replaceable>xx</replaceable> directories must reside in the file server machine's root
1527 directory, not in one of its subdirectories (for example, <emphasis role="bold">/usr/vicepa</emphasis> is not an acceptable
1528 directory location). For additional information, see <link linkend="HDRWQ20">Performing Platform-Specific
1529 Procedures</link>.</para>
1531 <para>AFS supports use of both EFS and XFS partitions for housing AFS volumes. SGI encourages use of XFS partitions.
1534 <para>Create a directory called <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable> for each AFS server
1535 partition you are configuring (there must be at least one). Repeat the command for each partition. <programlisting>
1536 # <emphasis role="bold">mkdir /vicep</emphasis><replaceable>xx</replaceable>
1537 </programlisting></para>
1541 <para>Add a line with the following format to the file systems registry file, <emphasis
1542 role="bold">/etc/fstab</emphasis>, for each partition (or logical volume created with the XLV volume manager) to be
1543 mounted on one of the directories created in the previous step.</para>
1545 <para>For an XFS partition or logical volume:</para>
1548 /dev/dsk/<replaceable>disk</replaceable> /vicep<replaceable>xx</replaceable> xfs rw,raw=/dev/rdsk/<replaceable>disk</replaceable> 0 0
1551 <para>For an EFS partition:</para>
1554 /dev/dsk/<replaceable>disk</replaceable> /vicep<replaceable>xx</replaceable> efs rw,raw=/dev/rdsk/<replaceable>disk</replaceable> 0 0
1557 <para>The following are examples of an entry for each file system type:</para>
1560 /dev/dsk/dks0d2s6 /vicepa xfs rw,raw=/dev/rdsk/dks0d2s6 0 0
1561 /dev/dsk/dks0d3s1 /vicepb efs rw,raw=/dev/rdsk/dks0d3s1 0 0
1566 <para>Create a file system on each partition that is to be mounted on a <emphasis
1567 role="bold">/vicep</emphasis><replaceable>xx</replaceable> directory. The following commands are probably appropriate,
1568 but consult the IRIX documentation for more information. In both cases, <replaceable>raw_device</replaceable> is a raw
1569 device name like <emphasis role="bold">/dev/rdsk/dks0d0s0</emphasis> for a single disk partition or <emphasis
1570 role="bold">/dev/rxlv/xlv0</emphasis> for a logical volume.</para>
1572 <para>For XFS file systems, include the indicated options to configure the partition or logical volume with inodes large
1573 enough to accommodate AFS-specific information:</para>
1576 # <emphasis role="bold">mkfs -t xfs -i size=512 -l size=4000b</emphasis> <replaceable>raw_device</replaceable>
1579 <para>For EFS file systems:</para>
1582 # <emphasis role="bold">mkfs -t efs</emphasis> <replaceable>raw_device</replaceable>
1587 <para>Mount each partition by issuing either the <emphasis role="bold">mount -a</emphasis> command to mount all
1588 partitions at once or the <emphasis role="bold">mount</emphasis> command to mount each partition in turn.</para>
1592 <para><emphasis role="bold">(Optional)</emphasis> If you have configured partitions or logical volumes to use XFS, issue
1593 the following command to verify that the inodes are configured properly (are large enough to accommodate AFS-specific
1594 information). If the configuration is correct, the command returns no output. Otherwise, it specifies the command to run
1595 in order to configure each partition or logical volume properly. <programlisting>
1596 # <emphasis role="bold">/usr/afs/bin/xfs_size_check</emphasis>
1597 </programlisting></para>
1601 <para>If you plan to retain client functionality on this machine after completing the installation, proceed to <link
1602 linkend="HDRWQ40">Enabling AFS Login on IRIX Systems</link>. Otherwise, proceed to <link linkend="HDRWQ50">Starting the
1603 BOS Server</link>.</para>
1605 </orderedlist></para>
1608 <primary>enabling AFS login</primary>
1610 <secondary>file server machine</secondary>
1612 <tertiary>IRIX</tertiary>
1616 <primary>AFS login</primary>
1618 <secondary>on file server machine</secondary>
1620 <tertiary>IRIX</tertiary>
1624 <primary>first AFS machine</primary>
1626 <secondary>AFS login</secondary>
1628 <tertiary>on IRIX</tertiary>
1632 <primary>IRIX</primary>
1634 <secondary>AFS login</secondary>
1638 <sect2 id="HDRWQ40">
1639 <title>Enabling AFS Login on IRIX Systems</title>
1642 <para>If you plan to remove client functionality from this machine after completing the installation, skip this section and
1643 proceed to <link linkend="HDRWQ50">Starting the BOS Server</link>.</para>
1646 <para>Whilst the standard IRIX command-line
1647 <emphasis role="bold">login</emphasis> program and the
1648 graphical <emphasis role="bold">xdm</emphasis> login program both have
1649 the ability to grant AFS tokens, this ability relies upon the deprecated
1650 kaserver authentication system.</para>
1652 <para>Users who have been successfully authenticated via Kerberos 5
1653 authentication may obtain AFS tokens following login by running the
1654 <emphasis role="bold">aklog</emphasis> command.</para>
1656 <para>Sites which still require <emphasis role="bold">kaserver</emphasis>
1657 or external Kerberos v4 authentication should consult
1658 <link linkend="KAS014">Enabling kaserver based AFS Login on IRIX Systems</link>
1659 for details of how to enable IRIX login.</para>
1661 <para>After taking any necessary action, proceed to
1662 <link linkend="HDRWQ50">Starting the BOS Server</link>.</para>
1666 <sect1 id="HDRWQ41">
1667 <title>Getting Started on Linux Systems</title>
1670 <primary>replacing fsck program</primary>
1672 <secondary>not necessary on Linux</secondary>
1676 <primary>fsck program</primary>
1678 <secondary>on first AFS machine</secondary>
1680 <tertiary>Linux</tertiary>
1684 <primary>first AFS machine</primary>
1686 <secondary>fsck program</secondary>
1688 <tertiary>on Linux</tertiary>
1692 <primary>Linux</primary>
1694 <secondary>fsck program replacement not necessary</secondary>
1697 <para>Since this guide was originally written, the procedure for starting
1698 OpenAFS has diverged significantly between different Linux distributions.
1699 The instructions that follow are appropriate for both the Fedora and
1700 RedHat Enterprise Linux packages distributed by OpenAFS. Additional
1701 instructions are provided for those building from source.</para>
1703 <para>Begin by running the AFS client startup scripts, which call the
1704 <emphasis role="bold">modprobe</emphasis> program to dynamically
1705 load the AFS modifications into the kernel. Then create partitions for
1706 storing AFS volumes. You do not need to replace the Linux <emphasis
1707 role="bold">fsck</emphasis> program. If the machine is to remain an
1708 AFS client machine, incorporate AFS into the machine's Pluggable
1709 Authentication Module (PAM) scheme. <indexterm>
1710 <primary>incorporating AFS kernel extensions</primary>
1712 <secondary>first AFS machine</secondary>
1714 <tertiary>Linux</tertiary>
1715 </indexterm> <indexterm>
1716 <primary>AFS kernel extensions</primary>
1718 <secondary>on first AFS machine</secondary>
1720 <tertiary>Linux</tertiary>
1721 </indexterm> <indexterm>
1722 <primary>first AFS machine</primary>
1724 <secondary>AFS kernel extensions</secondary>
1726 <tertiary>on Linux</tertiary>
1727 </indexterm> <indexterm>
1728 <primary>Linux</primary>
1730 <secondary>AFS kernel extensions</secondary>
1732 <tertiary>on first AFS machine</tertiary>
1735 <sect2 id="HDRWQ42">
1736 <title>Loading AFS into the Linux Kernel</title>
1738 <para>The <emphasis role="bold">modprobe</emphasis> program is the dynamic kernel loader for Linux. Linux does not support
1739 incorporation of AFS modifications during a kernel build.</para>
1741 <para>For AFS to function correctly, the <emphasis role="bold">modprobe</emphasis> program must run each time the machine
1742 reboots, so your distribution's AFS initialization script invokes it automatically. The script also includes
1743 commands that select the appropriate AFS library file automatically. In this section you run the script.</para>
1745 <para>In later sections you verify that the script correctly initializes all AFS components, then activate a configuration
1746 variable, which results in the script being incorporated into the Linux startup and shutdown sequence.</para>
1748 <para>The procedure for starting up OpenAFS depends upon your distribution</para>
1750 <title>Fedora and RedHat Enterprise Linux</title>
1751 <para>OpenAFS provides RPMS for all current Fedora and RedHat Enterprise Linux (RHEL) releases on the OpenAFS web site and the OpenAFS yum repository.
1755 http://dl.openafs.org/dl/openafs/<replaceable>VERSION</replaceable>,
1756 where VERSION is the latest stable release of
1757 OpenAFS. Download the
1758 openafs-repository-<replaceable>VERSION</replaceable>.noarch.rpm
1759 file for Fedora systems or the
1760 openafs-repository-rhel-<replaceable>VERSION</replaceable>.noarch.rpm
1761 file for RedHat-based systems.
1765 <para>Install the downloaded RPM file using the following command:
1767 # rpm -U openafs-repository*.rpm
1772 <para>Install the RPM set for your operating system using the yum command as follows:
1774 # yum -y install openafs-client openafs-server openafs-krb5 kmod-openafs
1778 <para>Alternatively, you may use dynamically-compiled kernel
1779 modules if you have the kernel headers, a compiler, and the
1781 <ulink url="http://fedoraproject.org/wiki/EPEL"><citetitle>EPEL</citetitle></ulink> installed.
1784 <para>To use dynamically-compiled kernel modules instead of statically compiled modules, use the following command instead of the kmod-openafs as shown above:
1786 # yum install openafs-client openafs-server openafs-krb5 dkms-openafs
1790 <!-- If you do this with current RHEL and Fedora releases you end up with
1791 a dynroot'd client running - this breaks setting up the root.afs volume
1792 as described later in this guide
1794 <para>Run the AFS initialization script to load AFS extensions into
1795 the kernel. You can ignore any error messages about the inability
1796 to start the BOS Server or the Cache Manager or AFS client.</para>
1798 # <emphasis role="bold">/etc/rc.d/init.d/openafs-client start</emphasis>
1806 <title>Systems packaged as tar files</title>
1807 <para>If you are running a system where the OpenAFS Binary Distribution
1808 is provided as a tar file, or where you have built the system from
1809 source yourself, you need to install the relevant components by hand
1814 <para>Unpack the distribution tarball. The examples below assume
1815 that you have unpacked the files into the
1816 <emphasis role="bold">/tmp/afsdist</emphasis> directory. If you
1817 pick a different location, substitute this in all of the following
1818 examples. Once you have unpacked the distribution,
1819 change directory as indicated.
1821 # <emphasis role="bold">cd /tmp/afsdist/linux/root.client/usr/vice/etc</emphasis>
1822 </programlisting></para>
1826 <para>Copy the AFS kernel library files to the local <emphasis role="bold">/usr/vice/etc/modload</emphasis> directory.
1827 The filenames for the libraries have the format <emphasis
1828 role="bold">libafs-</emphasis><replaceable>version</replaceable><emphasis role="bold">.o</emphasis>, where
1829 <replaceable>version</replaceable> indicates the kernel build level. The string <emphasis role="bold">.mp</emphasis> in
1830 the <replaceable>version</replaceable> indicates that the file is appropriate for machines running a multiprocessor
1831 kernel. <programlisting>
1832 # <emphasis role="bold">cp -rp modload /usr/vice/etc</emphasis>
1833 </programlisting></para>
1837 <para>Copy the AFS initialization script to the local directory for initialization files (by convention, <emphasis
1838 role="bold">/etc/rc.d/init.d</emphasis> on Linux machines). Note the removal of the <emphasis role="bold">.rc</emphasis>
1839 extension as you copy the script. <programlisting>
1840 # <emphasis role="bold">cp -p afs.rc /etc/rc.d/init.d/afs</emphasis>
1841 </programlisting></para>
1844 <!-- I don't think we need to do this for Linux, and it complicates things if
1845 dynroot is enabled ...
1847 <para>Run the AFS initialization script to load AFS extensions into the kernel. You can ignore any error messages about
1848 the inability to start the BOS Server or the Cache Manager or AFS client.</para>
1850 # <emphasis role="bold">/etc/rc.d/init.d/afs start</emphasis>
1857 <primary>configuring</primary>
1859 <secondary>AFS server partition on first AFS machine</secondary>
1861 <tertiary>Linux</tertiary>
1865 <primary>AFS server partition</primary>
1867 <secondary>configuring on first AFS machine</secondary>
1869 <tertiary>Linux</tertiary>
1873 <primary>first AFS machine</primary>
1875 <secondary>AFS server partition</secondary>
1877 <tertiary>on Linux</tertiary>
1881 <primary>Linux</primary>
1883 <secondary>AFS server partition</secondary>
1885 <tertiary>on first AFS machine</tertiary>
1890 <sect2 id="HDRWQ43">
1891 <title>Configuring Server Partitions on Linux Systems</title>
1893 <para>Every AFS file server machine must have at least one partition or logical volume dedicated to storing AFS volumes. Each
1894 server partition is mounted at a directory named <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>, where
1895 <replaceable>xx</replaceable> is one or two lowercase letters. The <emphasis
1896 role="bold">/vicep</emphasis><replaceable>xx</replaceable> directories must reside in the file server machine's root
1897 directory, not in one of its subdirectories (for example, <emphasis role="bold">/usr/vicepa</emphasis> is not an acceptable
1898 directory location). For additional information, see <link linkend="HDRWQ20">Performing Platform-Specific Procedures</link>.
1901 <para>Create a directory called <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable> for each AFS server
1902 partition you are configuring (there must be at least one). Repeat the command for each partition. <programlisting>
1903 # <emphasis role="bold">mkdir /vicep</emphasis><replaceable>xx</replaceable>
1904 </programlisting></para>
1908 <para>Add a line with the following format to the file systems registry file, <emphasis
1909 role="bold">/etc/fstab</emphasis>, for each directory just created. The entry maps the directory name to the disk
1910 partition to be mounted on it. <programlisting>
1911 /dev/<replaceable>disk</replaceable> /vicep<replaceable>xx</replaceable> ext2 defaults 0 2
1912 </programlisting></para>
1914 <para>The following is an example for the first partition being configured.</para>
1917 /dev/sda8 /vicepa ext2 defaults 0 2
1922 <para>Create a file system on each partition that is to be mounted at a <emphasis
1923 role="bold">/vicep</emphasis><replaceable>xx</replaceable> directory. The following command is probably appropriate, but
1924 consult the Linux documentation for more information. <programlisting>
1925 # <emphasis role="bold">mkfs -v /dev/</emphasis><replaceable>disk</replaceable>
1926 </programlisting></para>
1930 <para>Mount each partition by issuing either the <emphasis role="bold">mount -a</emphasis> command to mount all
1931 partitions at once or the <emphasis role="bold">mount</emphasis> command to mount each partition in turn.</para>
1935 <para>If you plan to retain client functionality on this machine after completing the installation, proceed to <link
1936 linkend="HDRWQ44">Enabling AFS Login on Linux Systems</link>. Otherwise, proceed to <link linkend="HDRWQ50">Starting the
1937 BOS Server</link>.</para>
1939 </orderedlist></para>
1942 <primary>enabling AFS login</primary>
1944 <secondary>file server machine</secondary>
1946 <tertiary>Linux</tertiary>
1950 <primary>AFS login</primary>
1952 <secondary>on file server machine</secondary>
1954 <tertiary>Linux</tertiary>
1958 <primary>first AFS machine</primary>
1960 <secondary>AFS login</secondary>
1962 <tertiary>on Linux</tertiary>
1966 <primary>Linux</primary>
1968 <secondary>AFS login</secondary>
1970 <tertiary>on file server machine</tertiary>
1974 <primary>PAM</primary>
1976 <secondary>on Linux</secondary>
1978 <tertiary>file server machine</tertiary>
1982 <sect2 id="HDRWQ44">
1983 <title>Enabling AFS Login on Linux Systems</title>
1986 <para>If you plan to remove client functionality from this machine
1987 after completing the installation, skip this section and proceed
1988 to <link linkend="HDRWQ50">Starting the BOS Server</link>.</para>
1991 <para>At this point you incorporate AFS into the operating system's
1992 Pluggable Authentication Module (PAM) scheme. PAM integrates all
1993 authentication mechanisms on the machine, including login, to provide
1994 the security infrastructure for authenticated access to and from the
1997 <para>You should first configure your system to obtain Kerberos v5
1998 tickets as part of the authentication process, and then run an AFS PAM
1999 module to obtain tokens from those tickets after authentication. Many
2000 Linux distributions come with a Kerberos v5 PAM module (usually called
2001 pam-krb5 or pam_krb5), or you can download and install <ulink
2002 url="http://www.eyrie.org/~eagle/software/pam-krb5">Russ Allbery's
2003 Kerberos v5 PAM module</ulink>, which is tested regularly with AFS.
2004 See the instructions of whatever PAM module you use for how to
2005 configure it.</para>
2007 <para>Some Kerberos v5 PAM modules do come with native AFS support
2008 (usually requiring the Heimdal Kerberos implementation rather than the
2009 MIT Kerberos implementation). If you are using one of those PAM
2010 modules, you can configure it to obtain AFS tokens. It's more common,
2011 however, to separate the AFS token acquisition into a separate PAM
2014 <para>The recommended AFS PAM module is <ulink
2015 url="http://www.eyrie.org/~eagle/software/pam-afs-session/">Russ
2016 Allbery's pam-afs-session module</ulink>. It should work with any of
2017 the Kerberos v5 PAM modules. To add it to the PAM configuration, you
2018 often only need to add configuration to the session group:</para>
2021 <title>Linux PAM session example</title>
2022 <literallayout>session required pam_afs_session.so</literallayout>
2025 <para>If you also want to obtain AFS tokens for <command>scp</command>
2026 and similar commands that don't open a session, you will also need to
2027 add the AFS PAM module to the auth group so that the PAM
2028 <function>setcred</function> call will obtain tokens. The
2029 <literal>pam_afs_session</literal> module will always return success
2030 for authentication so that it can be added to the auth group only for
2031 <function>setcred</function>, so make sure that it's not marked as
2032 <literal>sufficient</literal>.</para>
2035 <title>Linux PAM auth example</title>
2036 <literallayout>auth [success=ok default=1] pam_krb5.so
2037 auth [default=done] pam_afs_session.so
2038 auth required pam_unix.so try_first_pass</literallayout>
2041 <para>This example will work if you want to try Kerberos v5 first and
2042 then fall back to regular Unix authentication.
2043 <literal>success=ok</literal> for the Kerberos PAM module followed by
2044 <literal>default=done</literal> for the AFS PAM module will cause a
2045 successful Kerberos login to run the AFS PAM module and then skip the
2046 Unix authentication module. <literal>default=1</literal> on the
2047 Kerberos PAM module causes failure of that module to skip the next
2048 module (the AFS PAM module) and fall back to the Unix module. If you
2049 want to try Unix authentication first and rearrange the order, be sure
2050 to use <literal>default=die</literal> instead.</para>
2052 <para>The PAM configuration is stored in different places in different
2053 Linux distributions. On Red Hat, look in
2054 <filename>/etc/pam.d/system-auth</filename>. On Debian and
2055 derivatives, look in <filename>/etc/pam.d/common-session</filename>
2056 and <filename>/etc/pam.d/common-auth</filename>.</para>
2058 <para>For additional configuration examples and the configuration
2059 options of the AFS PAM module, see its documentation. For more
2060 details on the available options for the PAM configuration, see the
2061 Linux PAM documentation.</para>
2063 <para>Sites which still require <command>kaserver</command> or
2064 external Kerberos v4 authentication should consult <link
2065 linkend="KAS015">Enabling kaserver based AFS Login on Linux
2066 Systems</link> for details of how to enable AFS login on Linux.</para>
2068 <para>Proceed to <link linkend="HDRWQ50">Starting the BOS
2069 Server</link> (or if referring to these instructions while installing
2070 an additional file server machine, return to <link
2071 linkend="HDRWQ108">Starting Server Programs</link>).</para>
2075 <sect1 id="HDRWQ45">
2076 <title>Getting Started on Solaris Systems</title>
2078 <para>Begin by running the AFS initialization script to call the <emphasis role="bold">modload</emphasis> program distributed by
2079 Sun Microsystems, which dynamically loads AFS modifications into the kernel. Then create partitions for storing AFS volumes, and
2080 install and configure the AFS-modified <emphasis role="bold">fsck</emphasis> program to run on AFS server partitions. If the
2081 machine is to remain an AFS client machine, incorporate AFS into the machine's Pluggable Authentication Module (PAM) scheme.
2083 <primary>incorporating AFS kernel extensions</primary>
2085 <secondary>first AFS machine</secondary>
2087 <tertiary>Solaris</tertiary>
2088 </indexterm> <indexterm>
2089 <primary>AFS kernel extensions</primary>
2091 <secondary>on first AFS machine</secondary>
2093 <tertiary>Solaris</tertiary>
2094 </indexterm> <indexterm>
2095 <primary>first AFS machine</primary>
2097 <secondary>AFS kernel extensions</secondary>
2099 <tertiary>on Solaris</tertiary>
2100 </indexterm> <indexterm>
2101 <primary>Solaris</primary>
2103 <secondary>AFS kernel extensions</secondary>
2105 <tertiary>on first AFS machine</tertiary>
2108 <sect2 id="HDRWQ46">
2109 <title>Loading AFS into the Solaris Kernel</title>
2111 <para>The <emphasis role="bold">modload</emphasis> program is the dynamic kernel loader provided by Sun Microsystems for
2112 Solaris systems. Solaris does not support incorporation of AFS modifications during a kernel build.</para>
2114 <para>For AFS to function correctly, the <emphasis role="bold">modload</emphasis> program must run each time the machine
2115 reboots, so the AFS initialization script (included on the AFS CD-ROM) invokes it automatically. In this section you copy the
2116 appropriate AFS library file to the location where the <emphasis role="bold">modload</emphasis> program accesses it and then
2117 run the script.</para>
2119 <para>In later sections you verify that the script correctly initializes all AFS components, then create the links that
2120 incorporate AFS into the Solaris startup and shutdown sequence. <orderedlist>
2122 <para>Unpack the OpenAFS Solaris distribution tarball. The examples
2123 below assume that you have unpacked the files into the
2124 <emphasis role="bold">/tmp/afsdist</emphasis> directory. If you
2125 pick a diferent location, substitute this in all of the following
2126 exmaples. Once you have unpacked the distribution, change directory
2129 # <emphasis role="bold">cd /tmp/afsdist/sun4x_56/root.client/usr/vice/etc</emphasis>
2130 </programlisting></para>
2134 <para>Copy the AFS initialization script to the local directory for initialization files (by convention, <emphasis
2135 role="bold">/etc/init.d</emphasis> on Solaris machines). Note the removal of the <emphasis role="bold">.rc</emphasis>
2136 extension as you copy the script. <programlisting>
2137 # <emphasis role="bold">cp -p afs.rc /etc/init.d/afs</emphasis>
2138 </programlisting></para>
2142 <para>Copy the appropriate AFS kernel library file to the local file <emphasis
2143 role="bold">/kernel/fs/afs</emphasis>.</para>
2145 <para>If the machine is running Solaris 2.6 or the 32-bit version of Solaris 7, its kernel supports NFS server
2146 functionality, and the <emphasis role="bold">nfsd</emphasis> process is running:</para>
2149 # <emphasis role="bold">cp -p modload/libafs.o /kernel/fs/afs</emphasis>
2152 <para>If the machine is running Solaris 2.6 or the 32-bit version of Solaris 7, and its kernel does not support NFS
2153 server functionality or the <emphasis role="bold">nfsd</emphasis> process is not running:</para>
2156 # <emphasis role="bold">cp -p modload/libafs.nonfs.o /kernel/fs/afs</emphasis>
2159 <para>If the machine is running the 64-bit version of Solaris 7, its kernel supports NFS server functionality, and the
2160 <emphasis role="bold">nfsd</emphasis> process is running:</para>
2163 # <emphasis role="bold">cp -p modload/libafs64.o /kernel/fs/sparcv9/afs</emphasis>
2166 <para>If the machine is running the 64-bit version of Solaris 7, and its kernel does not support NFS server
2167 functionality or the <emphasis role="bold">nfsd</emphasis> process is not running:</para>
2170 # <emphasis role="bold">cp -p modload/libafs64.nonfs.o /kernel/fs/sparcv9/afs</emphasis>
2175 <para>Run the AFS initialization script to load AFS modifications into the kernel. You can ignore any error messages
2176 about the inability to start the BOS Server or the Cache Manager or AFS client. <programlisting>
2177 # <emphasis role="bold">/etc/init.d/afs start</emphasis>
2178 </programlisting></para>
2180 <para>When an entry called <computeroutput>afs</computeroutput> does not already exist in the local <emphasis
2181 role="bold">/etc/name_to_sysnum</emphasis> file, the script automatically creates it and reboots the machine to start
2182 using the new version of the file. If this happens, log in again as the superuser <emphasis role="bold">root</emphasis>
2183 after the reboot and run the initialization script again. This time the required entry exists in the <emphasis
2184 role="bold">/etc/name_to_sysnum</emphasis> file, and the <emphasis role="bold">modload</emphasis> program runs.</para>
2187 login: <emphasis role="bold">root</emphasis>
2188 Password: <replaceable>root_password</replaceable>
2189 # <emphasis role="bold">/etc/init.d/afs start</emphasis>
2192 </orderedlist></para>
2195 <primary>replacing fsck program</primary>
2197 <secondary>first AFS machine</secondary>
2199 <tertiary>Solaris</tertiary>
2203 <primary>fsck program</primary>
2205 <secondary>on first AFS machine</secondary>
2207 <tertiary>Solaris</tertiary>
2211 <primary>first AFS machine</primary>
2213 <secondary>fsck program</secondary>
2215 <tertiary>on Solaris</tertiary>
2219 <primary>Solaris</primary>
2221 <secondary>fsck program</secondary>
2223 <tertiary>on first AFS machine</tertiary>
2227 <sect2 id="HDRWQ47">
2228 <title>Configuring the AFS-modified fsck Program on Solaris Systems</title>
2230 <para>In this section, you make modifications to guarantee that the appropriate <emphasis role="bold">fsck</emphasis> program
2231 runs on AFS server partitions. The <emphasis role="bold">fsck</emphasis> program provided with the operating system must never
2232 run on AFS server partitions. Because it does not recognize the structures that the File Server uses to organize volume data,
2233 it removes all of the data. To repeat:</para>
2235 <para><emphasis role="bold">Never run the standard fsck program on AFS server partitions. It discards AFS volumes.</emphasis>
2238 <para>Create the <emphasis role="bold">/usr/lib/fs/afs</emphasis> directory to house the AFS-modified <emphasis
2239 role="bold">fsck</emphasis> program and related files. <programlisting>
2240 # <emphasis role="bold">mkdir /usr/lib/fs/afs</emphasis>
2241 # <emphasis role="bold">cd /usr/lib/fs/afs</emphasis>
2242 </programlisting></para>
2246 <para>Copy the <emphasis role="bold">vfsck</emphasis> binary to the newly created directory, changing the name as you do
2247 so. <programlisting>
2248 # <emphasis role="bold">cp /tmp/afsdist/sun4x_56/root.server/etc/vfsck fsck</emphasis>
2249 </programlisting></para>
2253 <para>Working in the <emphasis role="bold">/usr/lib/fs/afs</emphasis> directory, create the following links to Solaris
2254 libraries: <programlisting>
2255 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/clri</emphasis>
2256 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/df</emphasis>
2257 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/edquota</emphasis>
2258 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/ff</emphasis>
2259 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/fsdb</emphasis>
2260 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/fsirand</emphasis>
2261 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/fstyp</emphasis>
2262 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/labelit</emphasis>
2263 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/lockfs</emphasis>
2264 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/mkfs</emphasis>
2265 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/mount</emphasis>
2266 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/ncheck</emphasis>
2267 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/newfs</emphasis>
2268 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/quot</emphasis>
2269 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/quota</emphasis>
2270 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/quotaoff</emphasis>
2271 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/quotaon</emphasis>
2272 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/repquota</emphasis>
2273 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/tunefs</emphasis>
2274 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/ufsdump</emphasis>
2275 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/ufsrestore</emphasis>
2276 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/volcopy</emphasis>
2277 </programlisting></para>
2281 <para>Append the following line to the end of the file <emphasis role="bold">/etc/dfs/fstypes</emphasis>.
2284 </programlisting></para>
2288 <para>Edit the <emphasis role="bold">/sbin/mountall</emphasis> file, making two changes. <itemizedlist>
2290 <para>Add an entry for AFS to the <computeroutput>case</computeroutput> statement for option 2, so that it reads
2291 as follows: <programlisting>
2293 ufs) foptions="-o p"
2295 afs) foptions="-o p"
2297 s5) foptions="-y -t /var/tmp/tmp$$ -D"
2301 </programlisting></para>
2305 <para>Edit the file so that all AFS and UFS partitions are checked in parallel. Replace the following section of
2306 code: <programlisting>
2307 # For fsck purposes, we make a distinction between ufs and
2308 # other file systems
2310 if [ "$fstype" = "ufs" ]; then
2311 ufs_fscklist="$ufs_fscklist $fsckdev"
2312 saveentry $fstype "$OPTIONS" $special $mountp
2315 </programlisting></para>
2317 <para>with the following section of code:</para>
2320 # For fsck purposes, we make a distinction between ufs/afs
2321 # and other file systems.
2323 if [ "$fstype" = "ufs" -o "$fstype" = "afs" ]; then
2324 ufs_fscklist="$ufs_fscklist $fsckdev"
2325 saveentry $fstype "$OPTIONS" $special $mountp
2330 </itemizedlist></para>
2332 </orderedlist></para>
2335 <primary>configuring</primary>
2337 <secondary>AFS server partition on first AFS machine</secondary>
2339 <tertiary>Solaris</tertiary>
2343 <primary>AFS server partition</primary>
2345 <secondary>configuring on first AFS machine</secondary>
2347 <tertiary>Solaris</tertiary>
2351 <primary>first AFS machine</primary>
2353 <secondary>AFS server partition</secondary>
2355 <tertiary>on Solaris</tertiary>
2359 <primary>Solaris</primary>
2361 <secondary>AFS server partition</secondary>
2363 <tertiary>on first AFS machine</tertiary>
2367 <sect2 id="HDRWQ48">
2368 <title>Configuring Server Partitions on Solaris Systems</title>
2370 <para>Every AFS file server machine must have at least one partition or logical volume dedicated to storing AFS volumes. Each
2371 server partition is mounted at a directory named <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>, where
2372 <replaceable>xx</replaceable> is one or two lowercase letters. The <emphasis
2373 role="bold">/vicep</emphasis><replaceable>xx</replaceable> directories must reside in the file server machine's root
2374 directory, not in one of its subdirectories (for example, <emphasis role="bold">/usr/vicepa</emphasis> is not an acceptable
2375 directory location). For additional information, see <link linkend="HDRWQ20">Performing Platform-Specific Procedures</link>.
2378 <para>Create a directory called <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable> for each AFS server
2379 partition you are configuring (there must be at least one). Repeat the command for each partition. <programlisting>
2380 # <emphasis role="bold">mkdir /vicep</emphasis><replaceable>xx</replaceable>
2381 </programlisting></para>
2385 <para>Add a line with the following format to the file systems registry file, <emphasis
2386 role="bold">/etc/vfstab</emphasis>, for each partition to be mounted on a directory created in the previous step. Note
2387 the value <computeroutput>afs</computeroutput> in the fourth field, which tells Solaris to use the AFS-modified
2388 <emphasis role="bold">fsck</emphasis> program on this partition. <programlisting>
2389 /dev/dsk/<replaceable>disk</replaceable> /dev/rdsk/<replaceable>disk</replaceable> /vicep<replaceable>xx</replaceable> afs <replaceable>boot_order</replaceable> yes
2390 </programlisting></para>
2392 <para>The following is an example for the first partition being configured.</para>
2395 /dev/dsk/c0t6d0s1 /dev/rdsk/c0t6d0s1 /vicepa afs 3 yes
2400 <para>Create a file system on each partition that is to be mounted at a <emphasis
2401 role="bold">/vicep</emphasis><replaceable>xx</replaceable> directory. The following command is probably appropriate, but
2402 consult the Solaris documentation for more information. <programlisting>
2403 # <emphasis role="bold">newfs -v /dev/rdsk/</emphasis><replaceable>disk</replaceable>
2404 </programlisting></para>
2408 <para>Issue the <emphasis role="bold">mountall</emphasis> command to mount all partitions at once.</para>
2412 <para>If you plan to retain client functionality on this machine after completing the installation, proceed to <link
2413 linkend="HDRWQ49">Enabling AFS Login and Editing the File Systems Clean-up Script on Solaris Systems</link>. Otherwise,
2414 proceed to <link linkend="HDRWQ50">Starting the BOS Server</link>.</para>
2416 </orderedlist></para>
2419 <sect2 id="HDRWQ49">
2420 <title>Enabling AFS Login on Solaris Systems</title>
2422 <primary>enabling AFS login</primary>
2424 <secondary>file server machine</secondary>
2426 <tertiary>Solaris</tertiary>
2430 <primary>AFS login</primary>
2432 <secondary>on file server machine</secondary>
2434 <tertiary>Solaris</tertiary>
2438 <primary>first AFS machine</primary>
2440 <secondary>AFS login</secondary>
2442 <tertiary>on Solaris</tertiary>
2446 <primary>Solaris</primary>
2448 <secondary>AFS login</secondary>
2450 <tertiary>on file server machine</tertiary>
2454 <primary>PAM</primary>
2456 <secondary>on Solaris</secondary>
2458 <tertiary>file server machine</tertiary>
2462 <para>If you plan to remove client functionality from this machine after completing the installation, skip this section and
2463 proceed to <link linkend="HDRWQ50">Starting the BOS Server</link>.</para>
2466 <para>At this point you incorporate AFS into the operating system's
2467 Pluggable Authentication Module (PAM) scheme. PAM integrates all
2468 authentication mechanisms on the machine, including login, to provide
2469 the security infrastructure for authenticated access to and from the
2472 <para>Explaining PAM is beyond the scope of this document. It is
2473 assumed that you understand the syntax and meanings of settings in the
2474 PAM configuration file (for example, how the
2475 <computeroutput>other</computeroutput> entry works, the effect of
2476 marking an entry as <computeroutput>required</computeroutput>,
2477 <computeroutput>optional</computeroutput>, or
2478 <computeroutput>sufficient</computeroutput>, and so on).</para>
2480 <para>You should first configure your system to obtain Kerberos v5
2481 tickets as part of the authentication process, and then run an AFS PAM
2482 module to obtain tokens from those tickets after authentication.
2483 Current versions of Solaris come with a Kerberos v5 PAM module that
2484 will work, or you can download and install <ulink
2485 url="http://www.eyrie.org/~eagle/software/pam-krb5">Russ Allbery's
2486 Kerberos v5 PAM module</ulink>, which is tested regularly with AFS.
2487 See the instructions of whatever PAM module you use for how to
2488 configure it.</para>
2490 <para>Some Kerberos v5 PAM modules do come with native AFS support
2491 (usually requiring the Heimdal Kerberos implementation rather than the
2492 MIT Kerberos implementation). If you are using one of those PAM
2493 modules, you can configure it to obtain AFS tokens. It's more common,
2494 however, to separate the AFS token acquisition into a separate PAM
2497 <para>The recommended AFS PAM module is <ulink
2498 url="http://www.eyrie.org/~eagle/software/pam-afs-session/">Russ
2499 Allbery's pam-afs-session module</ulink>. It should work with any of
2500 the Kerberos v5 PAM modules. To add it to the PAM configuration, you
2501 often only need to add configuration to the session group in
2502 <filename>pam.conf</filename>:</para>
2505 <title>Solaris PAM session example</title>
2506 <literallayout>login session required pam_afs_session.so</literallayout>
2509 <para>This example enables PAM authentication only for console login.
2510 You may want to add a similar line for the ssh service and for any
2511 other login service that you use, including possibly the
2512 <literal>other</literal> service (which serves as a catch-all). You
2513 may also want to add options to the AFS PAM session module
2514 (particularly <literal>retain_after_close</literal>, which is
2515 necessary for some versions of Solaris.</para>
2517 <para>For additional configuration examples and the configuration
2518 options of the AFS PAM module, see its documentation. For more
2519 details on the available options for the PAM configuration, see the
2520 <filename>pam.conf</filename> manual page.</para>
2522 <para>Sites which still require <emphasis
2523 role="bold">kaserver</emphasis> or external Kerberos v4 authentication
2524 should consult <link linkend="KAS016">"Enabling kaserver based AFS
2525 Login on Solaris Systems"</link> for details of how to enable AFS
2526 login on Solaris.</para>
2528 <para>Proceed to <link linkend="HDRWQ49a">Editing the File Systems
2529 Clean-up Script on Solaris Systems</link></para>
2531 <sect2 id="HDRWQ49a">
2532 <title>Editing the File Systems Clean-up Script on Solaris Systems</title>
2534 <primary>Solaris</primary>
2536 <secondary>file systems clean-up script</secondary>
2538 <tertiary>on file server machine</tertiary>
2542 <primary>file systems clean-up script (Solaris)</primary>
2544 <secondary>file server machine</secondary>
2548 <primary>scripts</primary>
2550 <secondary>file systems clean-up (Solaris)</secondary>
2552 <tertiary>file server machine</tertiary>
2558 <para>Some Solaris distributions include a script that locates and removes unneeded files from various file systems. Its
2559 conventional location is <emphasis role="bold">/usr/lib/fs/nfs/nfsfind</emphasis>. The script generally uses an argument
2560 to the <emphasis role="bold">find</emphasis> command to define which file systems to search. In this step you modify the
2561 command to exclude the <emphasis role="bold">/afs</emphasis> directory. Otherwise, the command traverses the AFS
2562 filespace of every cell that is accessible from the machine, which can take many hours. The following alterations are
2563 possibilities, but you must verify that they are appropriate for your cell.</para>
2565 <para>The first possible alteration is to add the <emphasis role="bold">-local</emphasis> flag to the existing command,
2566 so that it looks like the following:</para>
2569 find $dir -local -name .nfs\* -mtime +7 -mount -exec rm -f {} \;
2572 <para>Another alternative is to exclude any directories whose names begin with the lowercase letter <emphasis
2573 role="bold">a</emphasis> or a non-alphabetic character.</para>
2576 find /[A-Zb-z]* <replaceable>remainder of existing command</replaceable>
2579 <para>Do not use the following command, which still searches under the <emphasis role="bold">/afs</emphasis> directory,
2580 looking for a subdirectory of type <emphasis role="bold">4.2</emphasis>.</para>
2583 find / -fstype 4.2 /* <replaceable>do not use</replaceable> */
2588 <para>Proceed to <link linkend="HDRWQ50">Starting the BOS Server</link> (or if referring to these instructions while
2589 installing an additional file server machine, return to <link linkend="HDRWQ108">Starting Server
2590 Programs</link>).</para>
2595 <primary>Basic OverSeer Server</primary>
2597 <see>BOS Server</see>
2601 <primary>BOS Server</primary>
2603 <secondary>starting</secondary>
2605 <tertiary>first AFS machine</tertiary>
2609 <primary>starting</primary>
2611 <secondary>BOS Server</secondary>
2613 <tertiary>first AFS machine</tertiary>
2617 <primary>first AFS machine</primary>
2619 <secondary>BOS Server</secondary>
2623 <primary>authorization checking (disabling)</primary>
2625 <secondary>first AFS machine</secondary>
2629 <primary>disabling authorization checking</primary>
2631 <secondary>first AFS machine</secondary>
2635 <primary>first AFS machine</primary>
2637 <secondary>authorization checking (disabling)</secondary>
2641 <sect1 id="HDRWQ50">
2642 <title>Starting the BOS Server</title>
2644 <para>You are now ready to start the AFS server processes on this machine.
2645 If you are not working from a packaged distribution, begin by copying the
2646 AFS server binaries from the distribution to the conventional local disk
2647 location, the <emphasis role="bold">/usr/afs/bin</emphasis> directory. The
2648 following instructions also create files in other subdirectories of the
2649 <emphasis role="bold">/usr/afs</emphasis> directory.</para>
2651 <para>Then issue the <emphasis role="bold">bosserver</emphasis> command to initialize the Basic OverSeer (BOS) Server, which
2652 monitors and controls other AFS server processes on its server machine. Include the <emphasis role="bold">-noauth</emphasis>
2653 flag to disable authorization checking. Because you have not yet configured your cell's AFS authentication and authorization
2654 mechanisms, the BOS Server cannot perform authorization checking as it does during normal operation. In no-authorization mode,
2655 it does not verify the identity or privilege of the issuer of a <emphasis role="bold">bos</emphasis> command, and so performs
2656 any operation for anyone.</para>
2658 <para>Disabling authorization checking gravely compromises cell security. You must complete all subsequent steps in one
2659 uninterrupted pass and must not leave the machine unattended until you restart the BOS Server with authorization checking
2660 enabled, in <link linkend="HDRWQ72">Verifying the AFS Initialization Script</link>.</para>
2662 <para>As it initializes for the first time, the BOS Server creates the following directories and files, setting the owner to the
2663 local superuser <emphasis role="bold">root</emphasis> and the mode bits to limit the ability to write (and in some cases, read)
2664 them. For a description of the contents and function of these directories and files, see the chapter in the <emphasis>OpenAFS
2665 Administration Guide</emphasis> about administering server machines. For further discussion of the mode bit settings, see <link
2666 linkend="HDRWQ96">Protecting Sensitive AFS Directories</link>. <indexterm>
2667 <primary>Binary Distribution</primary>
2669 <secondary>copying server files from</secondary>
2671 <tertiary>first AFS machine</tertiary>
2672 </indexterm> <indexterm>
2673 <primary>first AFS machine</primary>
2675 <secondary>subdirectories of /usr/afs</secondary>
2676 </indexterm> <indexterm>
2677 <primary>creating</primary>
2679 <secondary>/usr/afs/bin directory</secondary>
2681 <tertiary>first AFS machine</tertiary>
2682 </indexterm> <indexterm>
2683 <primary>creating</primary>
2685 <secondary>/usr/afs/etc directory</secondary>
2687 <tertiary>first AFS machine</tertiary>
2688 </indexterm> <indexterm>
2689 <primary>copying</primary>
2691 <secondary>server files to local disk</secondary>
2693 <tertiary>first AFS machine</tertiary>
2694 </indexterm> <indexterm>
2695 <primary>first AFS machine</primary>
2697 <secondary>copying</secondary>
2699 <tertiary>server files to local disk</tertiary>
2700 </indexterm> <indexterm>
2701 <primary>usr/afs/bin directory</primary>
2703 <secondary>first AFS machine</secondary>
2704 </indexterm> <indexterm>
2705 <primary>usr/afs/etc directory</primary>
2707 <secondary>first AFS machine</secondary>
2708 </indexterm> <indexterm>
2709 <primary>usr/afs/db directory</primary>
2710 </indexterm> <indexterm>
2711 <primary>usr/afs/local directory</primary>
2712 </indexterm> <indexterm>
2713 <primary>usr/afs/logs directory</primary>
2714 </indexterm> <itemizedlist>
2716 <para><emphasis role="bold">/usr/afs/db</emphasis></para>
2720 <para><emphasis role="bold">/usr/afs/etc/CellServDB</emphasis></para>
2724 <para><emphasis role="bold">/usr/afs/etc/ThisCell</emphasis></para>
2728 <para><emphasis role="bold">/usr/afs/local</emphasis></para>
2732 <para><emphasis role="bold">/usr/afs/logs</emphasis></para>
2734 </itemizedlist></para>
2736 <para>The BOS Server also creates symbolic links called <emphasis role="bold">/usr/vice/etc/ThisCell</emphasis> and <emphasis
2737 role="bold">/usr/vice/etc/CellServDB</emphasis> to the corresponding files in the <emphasis role="bold">/usr/afs/etc</emphasis>
2738 directory. The AFS command interpreters consult the <emphasis role="bold">CellServDB</emphasis> and <emphasis
2739 role="bold">ThisCell</emphasis> files in the <emphasis role="bold">/usr/vice/etc</emphasis> directory because they generally run
2740 on client machines. On machines that are AFS servers only (as this machine currently is), the files reside only in the <emphasis
2741 role="bold">/usr/afs/etc</emphasis> directory; the links enable the command interpreters to retrieve the information they need.
2742 Later instructions for installing the client functionality replace the links with actual files. <orderedlist>
2744 <para>If you are not working from a packaged distribution, you may need to copy files from the distribution media to the local <emphasis role="bold">/usr/afs</emphasis> directory.
2746 # <emphasis role="bold">cd /tmp/afsdist/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/root.server/usr/afs</emphasis>
2747 # <emphasis role="bold">cp -rp * /usr/afs</emphasis>
2748 </programlisting> <indexterm>
2749 <primary>commands</primary>
2751 <secondary>bosserver</secondary>
2752 </indexterm> <indexterm>
2753 <primary>bosserver command</primary>
2758 <para>Issue the <emphasis role="bold">bosserver</emphasis> command. Include the <emphasis role="bold">-noauth</emphasis>
2759 flag to disable authorization checking. <programlisting>
2760 # <emphasis role="bold">/usr/afs/bin/bosserver -noauth &</emphasis>
2761 </programlisting></para>
2765 <para>Verify that the BOS Server created <emphasis role="bold">/usr/vice/etc/ThisCell</emphasis> and <emphasis
2766 role="bold">/usr/vice/etc/CellServDB</emphasis> as symbolic links to the corresponding files in the <emphasis
2767 role="bold">/usr/afs/etc</emphasis> directory. <programlisting>
2768 # <emphasis role="bold">ls -l /usr/vice/etc</emphasis>
2769 </programlisting></para>
2771 <para>If either or both of <emphasis role="bold">/usr/vice/etc/ThisCell</emphasis> and <emphasis
2772 role="bold">/usr/vice/etc/CellServDB</emphasis> do not exist, or are not links, issue the following commands.</para>
2775 # <emphasis role="bold">cd /usr/vice/etc</emphasis>
2776 # <emphasis role="bold">ln -s /usr/afs/etc/ThisCell</emphasis>
2777 # <emphasis role="bold">ln -s /usr/afs/etc/CellServDB</emphasis>
2780 </orderedlist></para>
2783 <primary>cell name</primary>
2785 <secondary>defining during installation of first machine</secondary>
2789 <primary>defining</primary>
2791 <secondary>cell name during installation of first machine</secondary>
2795 <primary>cell name</primary>
2797 <secondary>setting in server ThisCell file</secondary>
2799 <tertiary>first AFS machine</tertiary>
2803 <primary>setting</primary>
2805 <secondary>cell name in server ThisCell file</secondary>
2807 <tertiary>first AFS machine</tertiary>
2811 <primary>first AFS machine</primary>
2813 <secondary>ThisCell file (server)</secondary>
2817 <primary>usr/afs/etc/ThisCell</primary>
2819 <see>ThisCell file (server)</see>
2823 <primary>ThisCell file (server)</primary>
2825 <secondary>first AFS machine</secondary>
2829 <primary>files</primary>
2831 <secondary>ThisCell (server)</secondary>
2835 <primary>database server machine</primary>
2837 <secondary>entry in server CellServDB file</secondary>
2839 <tertiary>on first AFS machine</tertiary>
2843 <primary>first AFS machine</primary>
2845 <secondary>cell membership, defining</secondary>
2847 <tertiary>for server processes</tertiary>
2851 <primary>usr/afs/etc/CellServDB file</primary>
2853 <see>CellServDB file (server)</see>
2857 <primary>CellServDB file (server)</primary>
2859 <secondary>creating</secondary>
2861 <tertiary>on first AFS machine</tertiary>
2865 <primary>creating</primary>
2867 <secondary>CellServDB file (server)</secondary>
2869 <tertiary>first AFS machine</tertiary>
2873 <primary>files</primary>
2875 <secondary>CellServDB (server)</secondary>
2879 <primary>first AFS machine</primary>
2881 <secondary>CellServDB file (server)</secondary>
2885 <primary>first AFS machine</primary>
2887 <secondary>defining</secondary>
2889 <tertiary>as database server</tertiary>
2893 <primary>defining</primary>
2895 <secondary>first AFS machine as database server</secondary>
2899 <sect1 id="HDRWQ51">
2900 <title>Defining Cell Name and Membership for Server Processes</title>
2902 <para>Now assign your cell's name. The chapter in the <emphasis>OpenAFS Administration Guide</emphasis> about cell configuration
2903 and administration issues discusses the important considerations, explains why changing the name is difficult, and outlines the
2904 restrictions on name format. Two of the most important restrictions are that the name cannot include uppercase letters or more
2905 than 64 characters.</para>
2907 <para>Use the <emphasis role="bold">bos setcellname</emphasis> command to assign the cell name. It creates two files:
2910 <para><emphasis role="bold">/usr/afs/etc/ThisCell</emphasis>, which defines this machine's cell membership</para>
2914 <para><emphasis role="bold">/usr/afs/etc/CellServDB</emphasis>, which lists the cell's database server machines; the
2915 machine named on the command line is placed on the list automatically</para>
2917 </itemizedlist> <note>
2918 <para>In the following and every instruction in this guide, for the <replaceable>machine name</replaceable> argument
2919 substitute the fully-qualified hostname (such as <emphasis role="bold">fs1.example.com</emphasis>) of the machine you are
2920 installing. For the <replaceable>cell name</replaceable> argument substitute your cell's complete name (such as <emphasis
2921 role="bold">example.com</emphasis>).</para>
2925 <primary>commands</primary>
2927 <secondary>bos setcellname</secondary>
2931 <primary>bos commands</primary>
2933 <secondary>setcellname</secondary>
2938 <para>If necessary, add the directory containing the <emphasis role="bold">bos</emphasis> command to your path.
2940 # <emphasis role="bold">export PATH=$PATH:/usr/afs/bin</emphasis>
2946 <para>Issue the <emphasis role="bold">bos setcellname</emphasis> command to set the cell name. <programlisting>
2947 # <emphasis role="bold">bos setcellname</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>cell name</replaceable>> <emphasis
2948 role="bold">-noauth</emphasis>
2949 </programlisting></para>
2951 <para>Because you are not authenticated and authorization checking is disabled, the <emphasis role="bold">bos</emphasis>
2952 command interpreter possibly produces error messages about being unable to obtain tickets and running unauthenticated. You
2953 can safely ignore the messages. <indexterm>
2954 <primary>commands</primary>
2956 <secondary>bos listhosts</secondary>
2957 </indexterm> <indexterm>
2958 <primary>bos commands</primary>
2960 <secondary>listhosts</secondary>
2961 </indexterm> <indexterm>
2962 <primary>CellServDB file (server)</primary>
2964 <secondary>displaying entries</secondary>
2965 </indexterm> <indexterm>
2966 <primary>displaying</primary>
2968 <secondary>CellServDB file (server) entries</secondary>
2973 <para>Issue the <emphasis role="bold">bos listhosts</emphasis> command to verify that the machine you are installing is now
2974 registered as the cell's first database server machine. <programlisting>
2975 # <emphasis role="bold">bos listhosts</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">-noauth</emphasis>
2976 Cell name is <replaceable>cell_name</replaceable>
2977 Host 1 is <replaceable>machine_name</replaceable>
2978 </programlisting></para>
2983 <primary>database server machine</primary>
2985 <secondary>installing</secondary>
2987 <tertiary>first</tertiary>
2991 <primary>instructions</primary>
2993 <secondary>database server machine, installing first</secondary>
2997 <primary>installing</primary>
2999 <secondary>database server machine</secondary>
3001 <tertiary>first</tertiary>
3005 <primary>Backup Server</primary>
3007 <secondary>starting</secondary>
3009 <tertiary>first AFS machine</tertiary>
3013 <primary>buserver process</primary>
3015 <see>Backup Server</see>
3019 <primary>starting</primary>
3021 <secondary>Backup Server</secondary>
3023 <tertiary>first AFS machine</tertiary>
3027 <primary>first AFS machine</primary>
3029 <secondary>Backup Server</secondary>
3033 <primary>Protection Server</primary>
3035 <secondary>starting</secondary>
3037 <tertiary>first AFS machine</tertiary>
3041 <primary>ptserver process</primary>
3043 <see>Protection Server</see>
3047 <primary>starting</primary>
3049 <secondary>Protection Server</secondary>
3051 <tertiary>first AFS machine</tertiary>
3055 <primary>first AFS machine</primary>
3057 <secondary>Protection Server</secondary>
3061 <primary>VL Server (vlserver process)</primary>
3063 <secondary>starting</secondary>
3065 <tertiary>first AFS machine</tertiary>
3069 <primary>Volume Location Server</primary>
3071 <see>VL Server</see>
3075 <primary>starting</primary>
3077 <secondary>VL Server</secondary>
3079 <tertiary>first AFS machine</tertiary>
3083 <primary>first AFS machine</primary>
3085 <secondary>VL Server</secondary>
3089 <primary>usr/afs/local/BosConfig</primary>
3091 <see>BosConfig file</see>
3095 <primary>BosConfig file</primary>
3097 <secondary>adding entries</secondary>
3099 <tertiary>first AFS machine</tertiary>
3103 <primary>adding</primary>
3105 <secondary>entries to BosConfig file</secondary>
3107 <tertiary>first AFS machine</tertiary>
3111 <primary>files</primary>
3113 <secondary>BosConfig</secondary>
3117 <primary>initializing</primary>
3119 <secondary>server process</secondary>
3125 <primary>server process</primary>
3127 <secondary>see also entry for each server's name</secondary>
3131 <sect1 id="HDRWQ52">
3132 <title>Starting the Database Server Processes</title>
3134 <para>Next use the <emphasis role="bold">bos create</emphasis> command to create entries for the three database server processes
3135 in the <emphasis role="bold">/usr/afs/local/BosConfig</emphasis> file and start them running. The three processes run on database
3136 server machines only: <itemizedlist>
3139 <para>The Backup Server (the <emphasis role="bold">buserver</emphasis> process) maintains the Backup Database</para>
3143 <para>The Protection Server (the <emphasis role="bold">ptserver</emphasis> process) maintains the Protection
3148 <para>The Volume Location (VL) Server (the <emphasis role="bold">vlserver</emphasis> process) maintains the Volume
3149 Location Database (VLDB)</para>
3151 </itemizedlist></para>
3154 <primary>Kerberos</primary>
3158 <para>AFS ships with an additional database server named 'kaserver', which
3159 was historically used to provide authentication services to AFS cells.
3160 kaserver was based on <emphasis>Kerberos v4</emphasis>, as such, it is
3161 not recommended for new cells. This guide assumes you have already
3162 configured a Kerberos v5 realm for your site, and details the procedures
3163 required to use AFS with this realm. If you do wish to use
3164 <emphasis role="bold">kaserver</emphasis>, please see the modifications
3165 to these instructions detailed in
3166 <link linkend="KAS006">Starting the kaserver Database Server Process</link>
3170 <para>The remaining instructions in this chapter include the <emphasis role="bold">-cell</emphasis> argument on all applicable
3171 commands. Provide the cell name you assigned in <link linkend="HDRWQ51">Defining Cell Name and Membership for Server
3172 Processes</link>. If a command appears on multiple lines, it is only for legibility. <indexterm>
3173 <primary>commands</primary>
3175 <secondary>bos create</secondary>
3176 </indexterm> <indexterm>
3177 <primary>bos commands</primary>
3179 <secondary>create</secondary>
3180 </indexterm> <orderedlist>
3182 <para>Issue the <emphasis role="bold">bos create</emphasis> command to start the Backup Server. <programlisting>
3183 # <emphasis role="bold">./bos create</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">buserver simple /usr/afs/bin/buserver</emphasis> <emphasis role="bold">-noauth</emphasis>
3184 </programlisting></para>
3188 <para>Issue the <emphasis role="bold">bos create</emphasis> command to start the Protection Server. <programlisting>
3189 # <emphasis role="bold">./bos create</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">ptserver simple /usr/afs/bin/ptserver</emphasis> <emphasis role="bold">-noauth</emphasis>
3190 </programlisting></para>
3194 <para>Issue the <emphasis role="bold">bos create</emphasis> command to start the VL Server. <programlisting>
3195 # <emphasis role="bold">./bos create</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">vlserver simple /usr/afs/bin/vlserver</emphasis> <emphasis role="bold">-noauth</emphasis>
3196 </programlisting></para>
3198 </orderedlist></para>
3201 <primary>admin account</primary>
3203 <secondary>creating</secondary>
3207 <primary>afs entry in Kerberos Database</primary>
3211 <primary>Kerberos Database</primary>
3215 <primary>creating</primary>
3217 <secondary>afs entry in Kerberos Database</secondary>
3221 <primary>creating</primary>
3223 <secondary>admin account in Kerberos Database</secondary>
3227 <primary>security</primary>
3229 <secondary>initializing cell-wide</secondary>
3233 <primary>cell</primary>
3235 <secondary>initializing security mechanisms</secondary>
3239 <primary>initializing</primary>
3241 <secondary>cell security mechanisms</secondary>
3245 <primary>usr/afs/etc/KeyFile</primary>
3247 <see>KeyFile file</see>
3251 <primary>KeyFile file</primary>
3253 <secondary>first AFS machine</secondary>
3257 <primary>files</primary>
3259 <secondary>KeyFile</secondary>
3263 <primary>key</primary>
3265 <see>server encryption key</see>
3269 <primary>encryption key</primary>
3271 <see>server encryption key</see>
3275 <sect1 id="HDRWQ53">
3276 <title>Initializing Cell Security </title>
3278 <para>If you are working with an existing cell which uses
3279 <emphasis role="bold">kaserver</emphasis> or Kerberos v4 for authentication,
3281 <link linkend="HDRWQ53">Initializing Cell Security with kaserver</link>
3282 for installation instructions which replace this section.</para>
3284 <para>Now initialize the cell's security mechanisms. Begin by creating the following two entires in your site's Kerberos database: <itemizedlist>
3286 <para>A generic administrative account, called <emphasis role="bold">admin</emphasis> by convention. If you choose to
3287 assign a different name, substitute it throughout the remainder of this document.</para>
3289 <para>After you complete the installation of the first machine, you can continue to have all administrators use the
3290 <emphasis role="bold">admin</emphasis> account, or you can create a separate administrative account for each of them. The
3291 latter scheme implies somewhat more overhead, but provides a more informative audit trail for administrative
3296 <para>The entry for AFS server processes, called either
3297 <emphasis role="bold">afs</emphasis> or
3298 <emphasis role="bold">afs/<replaceable>cell</replaceable></emphasis>.
3299 The latter form is preferred since it works regardless of whether
3300 your cell name matches your Kerberos realm name and allows multiple
3301 AFS cells to be served from a single Kerberos realm.
3302 No user logs in under this identity, but it is used to encrypt the
3303 server tickets that granted to AFS clients for presentation to
3304 server processes during mutual authentication. (The
3305 chapter in the <emphasis>OpenAFS Administration Guide</emphasis> about cell configuration and administration describes the
3306 role of server encryption keys in mutual authentication.)</para>
3308 <para>In Step <link linkend="LIWQ58">7</link>, you also place the initial AFS server encryption key into the <emphasis
3309 role="bold">/usr/afs/etc/KeyFile</emphasis> file. The AFS server processes refer to this file to learn the server
3310 encryption key when they need to decrypt server tickets.</para>
3312 </itemizedlist></para>
3314 <para>You also issue several commands that enable the new <emphasis role="bold">admin</emphasis> user to issue privileged
3315 commands in all of the AFS suites.</para>
3317 <para>The following instructions do not configure all of the security mechanisms related to the AFS Backup System. See the
3318 chapter in the <emphasis>OpenAFS Administration Guide</emphasis> about configuring the Backup System.</para>
3320 <para>The examples below assume you are using MIT Kerberos. Please refer
3321 to the documentation for your KDC's administrative interface if you are
3322 using a different vendor</para>
3326 <para>Enter <emphasis role="bold">kadmin</emphasis> interactive mode.
3328 # <emphasis role="bold">kadmin</emphasis>
3329 Authenticating as principal <replaceable>you</replaceable>/admin@<replaceable>YOUR REALM</replaceable> with password
3330 Password for <replaceable>you/admin@REALM</replaceable>: <replaceable>your_password</replaceable>
3331 </programlisting> <indexterm>
3332 <primary>server encryption key</primary>
3334 <secondary>in Kerberos Database</secondary>
3335 </indexterm> <indexterm>
3336 <primary>creating</primary>
3338 <secondary>server encryption key</secondary>
3340 <tertiary>Kerberos Database</tertiary>
3344 <listitem id="LIWQ54">
3346 <emphasis role="bold">add_principal</emphasis> command to create
3347 Kerberos Database entries called
3348 <emphasis role="bold">admin</emphasis> and
3349 <emphasis role="bold">afs/<<replaceable>cell name</replaceable>></emphasis>.</para>
3351 <para>You should make the <replaceable>admin_passwd</replaceable> as
3352 long and complex as possible, but keep in mind that administrators
3353 need to enter it often. It must be at least six characters long.</para>
3354 <para>Note that when creating the
3355 <emphasis role="bold">afs/<<replaceable>cell name</replaceable>></emphasis>
3356 entry, the encryption types should be restricted to des-cbc-crc:v4.
3357 For more details regarding encryption types, see the documentation
3358 for your Kerberos installation.
3361 kadmin: <emphasis role="bold">add_principal -randkey -e des-cbc-crc:v4 afs/</emphasis><<replaceable>cell name</replaceable>>
3362 Principal "afs/<replaceable>cell name</replaceable>@<replaceable>REALM</replaceable>" created.
3363 kadmin: <emphasis role="bold">add_principal admin</emphasis>
3364 Enter password for principal "admin@<replaceable>REALM</replaceable>": <emphasis role="bold"><replaceable>admin_password</replaceable></emphasis>
3365 Principal "admin@<replaceable>REALM</replaceable>" created.
3370 <primary>commands</primary>
3372 <secondary>kas examine</secondary>
3376 <primary>kas commands</primary>
3378 <secondary>examine</secondary>
3382 <primary>displaying</primary>
3384 <secondary>server encryption key</secondary>
3386 <tertiary>Authentication Database</tertiary>
3390 <listitem id="LIWQ55">
3391 <para>Issue the <emphasis role="bold">kadmin
3392 get_principal</emphasis> command to display the <emphasis
3393 role="bold">afs/</emphasis><<replaceable>cell name</replaceable>> entry.
3395 kadmin: <emphasis role="bold">get_principal afs/<<replaceable>cell name</replaceable>></emphasis>
3396 Principal: afs/<replaceable>cell</replaceable>
3398 Key: vno 2, DES cbc mode with CRC-32, no salt
3404 <para>Extract the newly created key for <emphasis role="bold">afs/<replaceable>cell</replaceable></emphasis> to a keytab on the local machine. We will use <emphasis role="bold">/etc/afs.keytab</emphasis> as the location for this keytab.</para>
3406 <para>The keytab contains the key material that ensures the security of your AFS cell. You should ensure that it is kept in a secure location at all times.</para>
3409 kadmin: <emphasis role="bold">ktadd -k /etc/afs.keytab -e des-cbc-crc:v4 afs/<<replaceable>cell name</replaceable>></emphasis>
3410 Entry for principal afs/<<replaceable>cell name</replaceable>> with kvno 3, encryption type DES cbc mode with CRC-32 added to keytab WRFILE:/etc/afs.keytab
3412 <para>Make a note of the key version number (kvno) given in the
3413 response, as you will need it to load the key into bos in a later
3416 <note><para>Note that each time you run
3417 <emphasis role="bold">ktadd</emphasis> a new key is generated
3418 for the item being extracted. This means that you cannot run ktadd
3419 multiple times and end up with the same key material each time.
3424 <para>Issue the <emphasis role="bold">quit</emphasis> command to leave <emphasis role="bold">kadmin</emphasis>
3425 interactive mode. <programlisting>
3426 kadmin: <emphasis role="bold">quit</emphasis>
3427 </programlisting> <indexterm>
3428 <primary>commands</primary>
3430 <secondary>bos adduser</secondary>
3431 </indexterm> <indexterm>
3432 <primary>bos commands</primary>
3434 <secondary>adduser</secondary>
3435 </indexterm> <indexterm>
3436 <primary>usr/afs/etc/UserList</primary>
3438 <see>UserList file</see>
3439 </indexterm> <indexterm>
3440 <primary>UserList file</primary>
3442 <secondary>first AFS machine</secondary>
3443 </indexterm> <indexterm>
3444 <primary>files</primary>
3446 <secondary>UserList</secondary>
3447 </indexterm> <indexterm>
3448 <primary>creating</primary>
3450 <secondary>UserList file entry</secondary>
3451 </indexterm> <indexterm>
3452 <primary>admin account</primary>
3454 <secondary>adding</secondary>
3456 <tertiary>to UserList file</tertiary>
3460 <listitem id="LIWQ57">
3461 <para>Issue the <emphasis role="bold">bos adduser</emphasis> command to add the <emphasis
3462 role="bold">admin</emphasis> user to the <emphasis role="bold">/usr/afs/etc/UserList</emphasis> file. This enables the
3463 <emphasis role="bold">admin</emphasis> user to issue privileged <emphasis role="bold">bos</emphasis> and <emphasis
3464 role="bold">vos</emphasis> commands. <programlisting>
3465 # <emphasis role="bold">./bos adduser</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">admin -noauth</emphasis>
3468 <primary>commands</primary>
3469 <secondary>asetkey</secondary>
3472 <primary>creating</primary>
3473 <secondary>server encryption key</secondary>
3474 <tertiary>KeyFile file</tertiary>
3477 <primary>server encryption key</primary>
3478 <secondary>in KeyFile file</secondary>
3482 <listitem id="LIWQ58">
3484 <emphasis role="bold">asetkey</emphasis> command to set the AFS
3485 server encryption key in the
3486 <emphasis role="bold">/usr/afs/etc/KeyFile</emphasis> file. This key
3487 is created from the <emphasis role="bold">/etc/afs.keytab</emphasis>
3488 file created earlier.</para>
3490 <para>asetkey requires the key version number (or kvno) of the
3491 <emphasis role="bold">afs/</emphasis><replaceable>cell</replaceable>
3492 key. You should have made note of the kvno when creating the key
3493 earlier. The key version number can also be found by running the
3494 <emphasis role="bold">kvno</emphasis> command</para>
3496 # <emphasis role="bold">kvno -k /etc/afs.keytab afs/</emphasis><<replaceable>cell name</replaceable>>
3499 <para>Once the kvno is known, the key can then be extracted using
3502 # <emphasis role="bold">asetkey add</emphasis> <<replaceable>kvno</replaceable>> <emphasis role="bold">/etc/afs.keytab afs/</emphasis><<replaceable>cell name</replaceable>>
3506 <primary>commands</primary>
3507 <secondary>bos listkeys</secondary>
3511 <primary>bos commands</primary>
3512 <secondary>listkeys</secondary>
3516 <primary>displaying</primary>
3517 <secondary>server encryption key</secondary>
3518 <tertiary>KeyFile file</tertiary>
3522 <listitem id="LIWQ59">
3524 <emphasis role="bold">bos listkeys</emphasis> command to verify that
3525 the key version number for the new key in the
3526 <emphasis role="bold">KeyFile</emphasis> file is the same as the key
3527 version number in the Authentication Database's
3528 <emphasis role="bold">afs/<replaceable>cell name</replaceable></emphasis>
3529 entry, which you displayed in Step <link linkend="LIWQ55">3</link>.
3531 # <emphasis role="bold">./bos listkeys</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">-noauth</emphasis>
3532 key 0 has cksum <replaceable>checksum</replaceable>
3533 </programlisting></para>
3535 <para>You can safely ignore any error messages indicating that <emphasis role="bold">bos</emphasis> failed to get tickets
3536 or that authentication failed.</para>
3540 <sect1 id="HDRWQ53a">
3541 <title>Initializing the Protection Database</title>
3543 <para>Now continue to configure your cell's security systems by
3544 populating the Protection Database with the newly created
3545 <emphasis role="bold">admin</emphasis> user, and permitting it
3546 to issue priviledged commands on the AFS filesystem.</para>
3551 <primary>commands</primary>
3552 <secondary>pts createuser</secondary>
3556 <primary>pts commands</primary>
3557 <secondary>createuser</secondary>
3561 <primary>Protection Database</primary>
3563 <para>Issue the <emphasis role="bold">pts createuser</emphasis> command to create a Protection Database entry for the
3564 <emphasis role="bold">admin</emphasis> user.</para>
3566 <para>By default, the Protection Server assigns AFS UID 1 (one) to the <emphasis role="bold">admin</emphasis> user,
3567 because it is the first user entry you are creating. If the local password file (<emphasis
3568 role="bold">/etc/passwd</emphasis> or equivalent) already has an entry for <emphasis role="bold">admin</emphasis> that
3569 assigns it a UNIX UID other than 1, it is best to use the <emphasis role="bold">-id</emphasis> argument to the <emphasis
3570 role="bold">pts createuser</emphasis> command to make the new AFS UID match the existing UNIX UID. Otherwise, it is best
3571 to accept the default.</para>
3574 # <emphasis role="bold">pts createuser -name admin</emphasis> [<emphasis
3575 role="bold">-id</emphasis> <<replaceable>AFS UID</replaceable>>] <emphasis role="bold">-noauth</emphasis>
3576 User admin has id <replaceable>AFS UID</replaceable>
3580 <primary>commands</primary>
3581 <secondary>pts adduser</secondary>
3585 <primary>pts commands</primary>
3586 <secondary>adduser</secondary>
3590 <primary>system:administrators group</primary>
3594 <primary>admin account</primary>
3595 <secondary>adding</secondary>
3596 <tertiary>to system:administrators group</tertiary>
3601 <para>Issue the <emphasis role="bold">pts adduser</emphasis> command to make the <emphasis role="bold">admin</emphasis>
3602 user a member of the <emphasis role="bold">system:administrators</emphasis> group, and the <emphasis role="bold">pts
3603 membership</emphasis> command to verify the new membership. Membership in the group enables the <emphasis
3604 role="bold">admin</emphasis> user to issue privileged <emphasis role="bold">pts</emphasis> commands and some privileged
3605 <emphasis role="bold">fs</emphasis> commands. <programlisting>
3606 # <emphasis role="bold">./pts adduser admin system:administrators</emphasis> <emphasis role="bold">-noauth</emphasis>
3607 # <emphasis role="bold">./pts membership admin</emphasis> <emphasis role="bold">-noauth</emphasis>
3608 Groups admin (id: 1) is a member of:
3609 system:administrators
3610 </programlisting> <indexterm>
3611 <primary>commands</primary>
3612 <secondary>bos restart</secondary>
3613 <tertiary>on first AFS machine</tertiary>
3614 </indexterm> <indexterm>
3615 <primary>bos commands</primary>
3616 <secondary>restart</secondary>
3617 <tertiary>on first AFS machine</tertiary>
3618 </indexterm> <indexterm>
3619 <primary>restarting server process</primary>
3620 <secondary>on first AFS machine</secondary>
3621 </indexterm> <indexterm>
3622 <primary>server process</primary>
3623 <secondary>restarting</secondary>
3624 <tertiary>on first AFS machine</tertiary>
3629 <para>Issue the <emphasis role="bold">bos restart</emphasis> command with the <emphasis role="bold">-all</emphasis> flag
3630 to restart the database server processes, so that they start using the new server encryption key. <programlisting>
3631 # <emphasis role="bold">./bos restart</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">-all</emphasis>
3632 <emphasis role="bold">-noauth</emphasis>
3633 </programlisting></para>
3638 <primary>File Server</primary>
3640 <secondary>first AFS machine</secondary>
3644 <primary>fileserver process</primary>
3646 <see>File Server</see>
3650 <primary>starting</primary>
3652 <secondary>File Server</secondary>
3654 <tertiary>first AFS machine</tertiary>
3658 <primary>first AFS machine</primary>
3660 <secondary>File Server, fs process</secondary>
3664 <primary>Volume Server</primary>
3666 <secondary>first AFS machine</secondary>
3670 <primary>volserver process</primary>
3672 <see>Volume Server</see>
3676 <primary>starting</primary>
3678 <secondary>Volume Server</secondary>
3680 <tertiary>first AFS machine</tertiary>
3684 <primary>first AFS machine</primary>
3686 <secondary>Volume Server</secondary>
3690 <primary>Salvager (salvager process)</primary>
3692 <secondary>first AFS machine</secondary>
3696 <primary>fs process</primary>
3698 <secondary>first AFS machine</secondary>
3702 <primary>starting</primary>
3704 <secondary>fs process</secondary>
3706 <tertiary>first AFS machine</tertiary>
3710 <primary>first AFS machine</primary>
3712 <secondary>Salvager</secondary>
3716 <sect1 id="HDRWQ60">
3717 <title>Starting the File Server processes</title>
3719 <para>Start either the <emphasis role="bold">fs</emphasis> process or, if you want to run the Demand-Attach File Server, the
3720 <emphasis role="bold">dafs</emphasis> process. The <emphasis role="bold">fs</emphasis> process consists of the File Server,
3721 Volume Server, and Salvager (<emphasis role="bold">fileserver</emphasis>, <emphasis role="bold">volserver</emphasis> and
3722 <emphasis role="bold">salvager</emphasis> processes). The <emphasis role="bold">dafs</emphasis> process consists of the
3723 Demand-Attach File Server, Volume Server, Salvage Server, and Salvager (<emphasis role="bold">dafileserver</emphasis>,
3724 <emphasis role="bold"> davolserver</emphasis>, <emphasis role="bold">salvageserver</emphasis>, and <emphasis
3725 role="bold">dasalvager</emphasis> processes). For information about the Demand-Attach File Server and to see whether or not
3726 you should run it, see <link linkend="DAFS">Appendix C, The Demand-Attach File Server</link>.
3729 <para>Issue the <emphasis role="bold">bos create</emphasis> command to start the <emphasis role="bold">fs</emphasis>
3730 process or the <emphasis role="bold">dafs</emphasis> process. The commands appear here on multiple lines only for legibility.
3734 <para>If you are not planning on running the Demand-Attach File Server, create the <emphasis role="bold">fs</emphasis>
3737 # <emphasis role="bold">./bos create</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">fs fs /usr/afs/bin/fileserver</emphasis> \
3738 <emphasis role="bold">/usr/afs/bin/volserver /usr/afs/bin/salvager</emphasis> \
3739 <emphasis role="bold">-noauth</emphasis>
3740 </programlisting></para>
3743 <para>If you are planning on running the Demand-Attach File Server, create the <emphasis
3744 role="bold">dafs</emphasis> process:
3746 # <emphasis role="bold">./bos create</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">dafs dafs /usr/afs/bin/dafileserver</emphasis> \
3747 <emphasis role="bold">/usr/afs/bin/davolserver /usr/afs/bin/salvageserver</emphasis> \
3748 <emphasis role="bold">/usr/afs/bin/dasalvager</emphasis> <emphasis role="bold">-noauth</emphasis>
3749 </programlisting></para>
3754 <para>Sometimes a message about Volume Location Database (VLDB) initialization appears, along with one or more instances
3755 of an error message similar to the following:</para>
3758 FSYNC_clientInit temporary failure (will retry)
3761 <para>This message appears when the <emphasis role="bold">volserver</emphasis> process tries to start before the <emphasis
3762 role="bold">fileserver</emphasis> process has completed its initialization. Wait a few minutes after the last such message
3763 before continuing, to guarantee that both processes have started successfully. <indexterm>
3764 <primary>commands</primary>
3766 <secondary>bos status</secondary>
3767 </indexterm> <indexterm>
3768 <primary>bos commands</primary>
3770 <secondary>status</secondary>
3773 <para>You can verify that the <emphasis role="bold">fs</emphasis> or <emphasis role="bold">dafs</emphasis> process has started
3774 successfully by issuing the <emphasis role="bold">bos status</emphasis> command. Its output mentions two <computeroutput>proc
3775 starts</computeroutput>.</para>
3779 <para>If you are not running the Demand-Attach File Server:
3782 # <emphasis role="bold">./bos status</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">fs -long -noauth</emphasis>
3783 </programlisting></para></listitem>
3786 <para>If you are running the Demand-Attach File Server:
3788 # <emphasis role="bold">./bos status</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">dafs -long -noauth</emphasis>
3789 </programlisting></para></listitem>
3795 <para>Your next action depends on whether you have ever run AFS file server machines in the cell: <itemizedlist>
3797 <primary>commands</primary>
3799 <secondary>vos create</secondary>
3801 <tertiary>root.afs volume</tertiary>
3805 <primary>vos commands</primary>
3807 <secondary>create</secondary>
3809 <tertiary>root.afs volume</tertiary>
3813 <primary>root.afs volume</primary>
3815 <secondary>creating</secondary>
3819 <primary>volume</primary>
3821 <secondary>creating</secondary>
3823 <tertiary>root.afs</tertiary>
3827 <primary>creating</primary>
3829 <secondary>root.afs volume</secondary>
3833 <para>If you are installing the first AFS server machine ever in the cell (that is, you are not upgrading the AFS
3834 software from a previous version), create the first AFS volume, <emphasis role="bold">root.afs</emphasis>.</para>
3836 <para>For the <replaceable>partition name</replaceable> argument, substitute the name of one of the machine's AFS
3837 server partitions (such as <emphasis role="bold">/vicepa</emphasis>).</para>
3840 # <emphasis role="bold">./vos create</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>partition name</replaceable>> <emphasis
3841 role="bold">root.afs</emphasis> \
3842 <emphasis role="bold">-noauth</emphasis>
3845 <para>The Volume Server produces a message confirming that it created the volume on the specified partition. You can
3846 ignore error messages indicating that tokens are missing, or that authentication failed. <indexterm>
3847 <primary>commands</primary>
3849 <secondary>vos syncvldb</secondary>
3850 </indexterm> <indexterm>
3851 <primary>vos commands</primary>
3853 <secondary>syncvldb</secondary>
3854 </indexterm> <indexterm>
3855 <primary>commands</primary>
3857 <secondary>vos syncserv</secondary>
3858 </indexterm> <indexterm>
3859 <primary>vos commands</primary>
3861 <secondary>syncserv</secondary>
3866 <para>If there are existing AFS file server machines and volumes in the cell, issue the <emphasis role="bold">vos
3867 syncvldb</emphasis> and <emphasis role="bold">vos syncserv</emphasis> commands to synchronize the VLDB with the
3868 actual state of volumes on the local machine. To follow the progress of the synchronization operation, which can
3869 take several minutes, use the <emphasis role="bold">-verbose</emphasis> flag. <programlisting>
3870 # <emphasis role="bold">./vos syncvldb</emphasis> <<replaceable>machine name</replaceable>> <emphasis
3871 role="bold">-verbose -noauth</emphasis>
3872 # <emphasis role="bold">./vos syncserv</emphasis> <<replaceable>machine name</replaceable>> <emphasis
3873 role="bold">-verbose -noauth</emphasis>
3874 </programlisting></para>
3876 <para>You can ignore error messages indicating that tokens are missing, or that authentication failed.</para>
3878 </itemizedlist></para>
3880 </orderedlist></para>
3883 <primary>Update Server</primary>
3885 <secondary>starting server portion</secondary>
3887 <tertiary>first AFS machine</tertiary>
3891 <primary>upserver process</primary>
3893 <see>Update Server</see>
3897 <primary>starting</primary>
3899 <secondary>Update Server server portion</secondary>
3901 <tertiary>first AFS machine</tertiary>
3905 <primary>first AFS machine</primary>
3907 <secondary>Update Server server portion</secondary>
3911 <primary>first AFS machine</primary>
3913 <secondary>defining</secondary>
3915 <tertiary>as binary distribution machine</tertiary>
3919 <primary>first AFS machine</primary>
3921 <secondary>defining</secondary>
3923 <tertiary>as system control machine</tertiary>
3927 <primary>system control machine</primary>
3931 <primary>binary distribution machine</primary>
3935 <sect1 id="HDRWQ61">
3936 <title>Starting the Server Portion of the Update Server</title>
3938 <para>Start the server portion of the Update Server (the <emphasis role="bold">upserver</emphasis> process), to distribute the
3939 contents of directories on this machine to other server machines in the cell. It becomes active when you configure the client
3940 portion of the Update Server on additional server machines.</para>
3942 <para>Distributing the contents of its <emphasis role="bold">/usr/afs/etc</emphasis> directory makes this machine the cell's
3943 <emphasis>system control machine</emphasis>. The other server machines in the cell run the <emphasis
3944 role="bold">upclientetc</emphasis> process (an instance of the client portion of the Update Server) to retrieve the
3945 configuration files. Use the <emphasis role="bold">-crypt</emphasis> argument to the <emphasis role="bold">upserver</emphasis>
3946 initialization command to specify that the Update Server distributes the contents of the <emphasis
3947 role="bold">/usr/afs/etc</emphasis> directory only in encrypted form, as shown in the following instruction. Several of the
3948 files in the directory, particularly the <emphasis role="bold">KeyFile</emphasis> file, are crucial to cell security and so must
3949 never cross the network unencrypted.</para>
3951 <para>(You can choose not to configure a system control machine, in which case you must update the configuration files in each
3952 server machine's <emphasis role="bold">/usr/afs/etc</emphasis> directory individually. The <emphasis role="bold">bos</emphasis>
3953 commands used for this purpose also encrypt data before sending it across the network.)</para>
3955 <para>Distributing the contents of its <emphasis role="bold">/usr/afs/bin</emphasis> directory to other server machines of its
3956 system type makes this machine a <emphasis>binary distribution machine</emphasis>. The other server machines of its system type
3957 run the <emphasis role="bold">upclientbin</emphasis> process (an instance of the client portion of the Update Server) to
3958 retrieve the binaries. If your platform has a package management system,
3959 such as 'rpm' or 'apt', running the Update Server to distribute binaries
3960 may interfere with this system.</para>
3962 <para>The binaries in the <emphasis role="bold">/usr/afs/bin</emphasis> directory are not sensitive, so it is not necessary to
3963 encrypt them before transfer across the network. Include the <emphasis role="bold">-clear</emphasis> argument to the <emphasis
3964 role="bold">upserver</emphasis> initialization command to specify that the Update Server distributes the contents of the
3965 <emphasis role="bold">/usr/afs/bin</emphasis> directory in unencrypted form unless an <emphasis
3966 role="bold">upclientbin</emphasis> process requests encrypted transfer.</para>
3968 <para>Note that the server and client portions of the Update Server always mutually authenticate with one another, regardless of
3969 whether you use the <emphasis role="bold">-clear</emphasis> or <emphasis role="bold">-crypt</emphasis> arguments. This protects
3970 their communications from eavesdropping to some degree.</para>
3972 <para>For more information on the <emphasis role="bold">upclient</emphasis> and <emphasis role="bold">upserver</emphasis>
3973 processes, see their reference pages in the <emphasis>OpenAFS Administration Reference</emphasis>. The commands appear on
3974 multiple lines here only for legibility. <orderedlist>
3976 <para>Issue the <emphasis role="bold">bos create</emphasis> command to start the <emphasis role="bold">upserver</emphasis>
3977 process. <programlisting>
3978 # <emphasis role="bold">./bos create</emphasis> <<replaceable>machine name></replaceable> <emphasis role="bold">upserver simple</emphasis> \
3979 <emphasis role="bold">"/usr/afs/bin/upserver -crypt /usr/afs/etc</emphasis> \
3980 <emphasis role="bold">-clear /usr/afs/bin"</emphasis> <emphasis role="bold">-noauth</emphasis>
3981 </programlisting></para>
3983 </orderedlist></para>
3986 <sect1 id="HDRWQ62">
3987 <title>Starting the Controller for NTPD</title>
3989 <para>Keeping the clocks on all server and client machines in your cell synchronized is crucial to several functions, and in
3990 particular to the correct operation of AFS's distributed database technology, Ubik. The chapter in the <emphasis>OpenAFS
3991 Administration Guide</emphasis> about administering server machines explains how time skew can disturb Ubik's performance and
3992 cause service outages in your cell.</para>
3994 <para>Historically, AFS used to distribute its own version of the Network
3995 Time Protocol Daemon. Whilst this is still provided for existing sites, we
3996 recommend that you configure and install your time service independently of
3997 AFS. A reliable timeservice will also be required by your Kerberos realm,
3998 and so may already be available at your site.</para>
4001 <primary>overview</primary>
4003 <secondary>installing client functionality on first machine</secondary>
4007 <primary>first AFS machine</primary>
4009 <secondary>client functionality</secondary>
4011 <tertiary>installing</tertiary>
4015 <primary>installing</primary>
4017 <secondary>client functionality</secondary>
4019 <tertiary>first AFS machine</tertiary>
4023 <sect1 id="HDRWQ63">
4024 <title>Overview: Installing Client Functionality</title>
4026 <para>The machine you are installing is now an AFS file server machine,
4027 database server machine, system control machine, and binary distribution
4028 machine. Now make it a client machine by completing the following tasks:
4031 <para>Define the machine's cell membership for client processes</para>
4035 <para>Create the client version of the <emphasis role="bold">CellServDB</emphasis> file</para>
4039 <para>Define cache location and size</para>
4043 <para>Create the <emphasis role="bold">/afs</emphasis> directory and start the Cache Manager</para>
4045 </orderedlist></para>
4048 <primary>Distribution</primary>
4050 <secondary>copying client files from</secondary>
4052 <tertiary>first AFS machine</tertiary>
4056 <primary>first AFS machine</primary>
4058 <secondary>copying</secondary>
4060 <tertiary>client files to local disk</tertiary>
4064 <primary>copying</primary>
4066 <secondary>client files to local disk</secondary>
4068 <tertiary>first AFS machine</tertiary>
4072 <sect1 id="HDRWQ64">
4073 <title>Copying Client Files to the Local Disk</title>
4075 <para>You need only undertake the steps in this section, if you are using
4076 a tar file distribution, or one built from scratch. Packaged distributions,
4077 such as RPMs or DEBs will already have installed the necessary files in
4078 the correct locations.</para>
4080 <para>Before installing and configuring the AFS client, copy the necessary files from the tarball to the local <emphasis
4081 role="bold">/usr/vice/etc</emphasis> directory. <orderedlist>
4083 <para>If you have not already done so, unpack the distribution
4084 tarball for this machine's system type into a suitable location on
4085 the filesystem, such as <emphasis role="bold">/tmp/afsdist</emphasis>.
4086 If you use a different location, substitue that in the examples that
4091 <para>Copy files to the local <emphasis role="bold">/usr/vice/etc</emphasis> directory.</para>
4093 <para>This step places a copy of the AFS initialization script (and related files, if applicable) into the <emphasis
4094 role="bold">/usr/vice/etc</emphasis> directory. In the preceding instructions for incorporating AFS into the kernel, you
4095 copied the script directly to the operating system's conventional location for initialization files. When you incorporate
4096 AFS into the machine's startup sequence in a later step, you can choose to link the two files.</para>
4098 <para>On some system types that use a dynamic kernel loader program, you previously copied AFS library files into a
4099 subdirectory of the <emphasis role="bold">/usr/vice/etc</emphasis> directory. On other system types, you copied the
4100 appropriate AFS library file directly to the directory where the operating system accesses it. The following commands do
4101 not copy or recopy the AFS library files into the <emphasis role="bold">/usr/vice/etc</emphasis> directory, because on
4102 some system types the library files consume a large amount of space. If you want to copy them, add the <emphasis
4103 role="bold">-r</emphasis> flag to the first <emphasis role="bold">cp</emphasis> command and skip the second <emphasis
4104 role="bold">cp</emphasis> command.</para>
4107 # <emphasis role="bold">cd /tmp/afsdist/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/root.client/usr/vice/etc</emphasis>
4108 # <emphasis role="bold">cp -p * /usr/vice/etc</emphasis>
4109 # <emphasis role="bold">cp -rp C /usr/vice/etc</emphasis>
4112 </orderedlist></para>
4115 <primary>cell name</primary>
4117 <secondary>setting in client ThisCell file</secondary>
4119 <tertiary>first AFS machine</tertiary>
4123 <primary>setting</primary>
4125 <secondary>cell name in client ThisCell file</secondary>
4127 <tertiary>first AFS machine</tertiary>
4131 <primary>first AFS machine</primary>
4133 <secondary>ThisCell file (client)</secondary>
4137 <primary>first AFS machine</primary>
4139 <secondary>cell membership, defining</secondary>
4141 <tertiary>for client processes</tertiary>
4145 <primary>usr/vice/etc/ThisCell</primary>
4147 <see>ThisCell file (client)</see>
4151 <primary>ThisCell file (client)</primary>
4153 <secondary>first AFS machine</secondary>
4157 <primary>files</primary>
4159 <secondary>ThisCell (client)</secondary>
4163 <sect1 id="HDRWQ65">
4164 <title>Defining Cell Membership for Client Processes</title>
4166 <para>Every AFS client machine has a copy of the <emphasis role="bold">/usr/vice/etc/ThisCell</emphasis> file on its local disk
4167 to define the machine's cell membership for the AFS client programs that run on it. The <emphasis
4168 role="bold">ThisCell</emphasis> file you created in the <emphasis role="bold">/usr/afs/etc</emphasis> directory (in <link
4169 linkend="HDRWQ51">Defining Cell Name and Membership for Server Processes</link>) is used only by server processes.</para>
4171 <para>Among other functions, the <emphasis role="bold">ThisCell</emphasis> file on a client machine determines the following:
4174 <para>The cell in which users gain tokens when they log onto the
4175 machine, assuming it is using an AFS-modified login utility</para>
4179 <para>The cell in which users gain tokens by default when they issue
4180 the <emphasis role="bold">aklog</emphasis> command</para>
4184 <para>The cell membership of the AFS server processes that the AFS
4185 command interpreters on this machine contact by default</para>
4190 <para>Change to the <emphasis role="bold">/usr/vice/etc</emphasis> directory and remove the symbolic link created in <link
4191 linkend="HDRWQ50">Starting the BOS Server</link>. <programlisting>
4192 # <emphasis role="bold">cd /usr/vice/etc</emphasis>
4193 # <emphasis role="bold">rm ThisCell</emphasis>
4194 </programlisting></para>
4198 <para>Create the <emphasis role="bold">ThisCell</emphasis> file as a copy of the <emphasis
4199 role="bold">/usr/afs/etc/ThisCell</emphasis> file. Defining the same local cell for both server and client processes leads
4200 to the most consistent AFS performance. <programlisting>
4201 # <emphasis role="bold">cp /usr/afs/etc/ThisCell ThisCell</emphasis>
4202 </programlisting></para>
4204 </orderedlist></para>
4207 <primary>database server machine</primary>
4209 <secondary>entry in client CellServDB file</secondary>
4211 <tertiary>on first AFS machine</tertiary>
4215 <primary>usr/vice/etc/CellServDB</primary>
4217 <see>CellServDB file (client)</see>
4221 <primary>CellServDB file (client)</primary>
4223 <secondary>creating</secondary>
4225 <tertiary>on first AFS machine</tertiary>
4229 <primary>creating</primary>
4231 <secondary>CellServDB file (client)</secondary>
4233 <tertiary>first AFS machine</tertiary>
4237 <primary>CellServDB file (client)</primary>
4239 <secondary>required format</secondary>
4243 <primary>requirements</primary>
4245 <secondary>CellServDB file format (client version)</secondary>
4249 <primary>files</primary>
4251 <secondary>CellServDB (client)</secondary>
4255 <primary>first AFS machine</primary>
4257 <secondary>CellServDB file (client)</secondary>
4261 <sect1 id="HDRWQ66">
4262 <title>Creating the Client CellServDB File</title>
4264 <para>The <emphasis role="bold">/usr/vice/etc/CellServDB</emphasis> file on a client machine's local disk lists the database
4265 server machines for each cell that the local Cache Manager can contact. If there is no entry in the file for a cell, or if the
4266 list of database server machines is wrong, then users working on this machine cannot access the cell. The chapter in the
4267 <emphasis>OpenAFS Administration Guide</emphasis> about administering client machines explains how to maintain the file after
4270 <para>As the <emphasis role="bold">afsd</emphasis> program initializes the Cache Manager, it copies the contents of the
4271 <emphasis role="bold">CellServDB</emphasis> file into kernel memory. The Cache Manager always consults the list in kernel memory
4272 rather than the <emphasis role="bold">CellServDB</emphasis> file itself. Between reboots of the machine, you can use the
4273 <emphasis role="bold">fs newcell</emphasis> command to update the list in kernel memory directly; see the chapter in the
4274 <emphasis>OpenAFS Administration Guide</emphasis> about administering client machines.</para>
4276 <para>The AFS distribution includes the file
4277 <emphasis role="bold">CellServDB.dist</emphasis>. It includes an entry for
4278 all AFS cells that agreed to share their database server machine
4279 information at the time the distribution was
4280 created. The definitive copy of this file is maintained at
4281 grand.central.org, and updates may be obtained from
4282 /afs/grand.central.org/service/CellServDB or
4283 <ulink url="http://grand.central.org/dl/cellservdb/CellServDB">
4284 http://grand.central.org/dl/cellservdb/CellServDB</ulink></para>
4286 <para>The <emphasis role="bold">CellServDB.dist</emphasis> file can be a
4287 good basis for the client <emphasis role="bold">CellServDB</emphasis> file,
4288 because all of the entries in it use the correct format. You can add or
4289 remove cell entries as you see fit. Depending on your cache manager
4290 configuration, additional steps (as detailed in
4291 <link linkend="HDRWQ91">Enabling Access to Foreign Cells</link>) may be
4292 required to enable the Cache Manager to actually reach the cells.</para>
4294 <para>In this section, you add an entry for the local cell to the local <emphasis role="bold">CellServDB</emphasis> file. The
4295 current working directory is still <emphasis role="bold">/usr/vice/etc</emphasis>. <orderedlist>
4297 <para>Remove the symbolic link created in <link linkend="HDRWQ50">Starting the BOS Server</link> and rename the <emphasis
4298 role="bold">CellServDB.sample</emphasis> file to <emphasis role="bold">CellServDB</emphasis>. <programlisting>
4299 # <emphasis role="bold">rm CellServDB</emphasis>
4300 # <emphasis role="bold">mv CellServDB.sample CellServDB</emphasis>
4301 </programlisting></para>
4305 <para>Add an entry for the local cell to the <emphasis role="bold">CellServDB</emphasis> file. One easy method is to use
4306 the <emphasis role="bold">cat</emphasis> command to append the contents of the server <emphasis
4307 role="bold">/usr/afs/etc/CellServDB</emphasis> file to the client version. <programlisting>
4308 # <emphasis role="bold">cat /usr/afs/etc/CellServDB >> CellServDB</emphasis>
4309 </programlisting></para>
4311 <para>Then open the file in a text editor to verify that there are no blank lines, and that all entries have the required
4312 format, which is described just following. The ordering of cells is not significant, but it can be convenient to have the
4313 client machine's home cell at the top; move it there now if you wish. <itemizedlist>
4315 <para>The first line of a cell's entry has the following format: <programlisting>
4316 ><replaceable>cell_name</replaceable> #<replaceable>organization</replaceable>
4317 </programlisting></para>
4319 <para>where <replaceable>cell_name</replaceable> is the cell's complete Internet domain name (for example, <emphasis
4320 role="bold">example.com</emphasis>) and <replaceable>organization</replaceable> is an optional field that follows any
4321 number of spaces and the number sign (<computeroutput>#</computeroutput>). By convention it names the organization
4322 to which the cell corresponds (for example, the Example Corporation).</para>
4326 <para>After the first line comes a separate line for each database server machine. Each line has the following
4327 format: <programlisting>
4328 <replaceable>IP_address</replaceable> #<replaceable>machine_name</replaceable>
4329 </programlisting></para>
4331 <para>where <replaceable>IP_address</replaceable> is the machine's IP address in dotted decimal format (for example,
4332 192.12.105.3). Following any number of spaces and the number sign (<computeroutput>#</computeroutput>) is
4333 <replaceable>machine_name</replaceable>, the machine's fully-qualified hostname (for example, <emphasis
4334 role="bold">db1.example.com</emphasis>). In this case, the number sign does not indicate a comment;
4335 <replaceable>machine_name</replaceable> is a required field.</para>
4337 </itemizedlist></para>
4341 <para>If the file includes cells that you do not wish users of this machine to access, remove their entries.</para>
4343 </orderedlist></para>
4345 <para>The following example shows entries for two cells, each of which has three database server machines:</para>
4348 >example.com #Example Corporation (home cell)
4349 192.12.105.3 #db1.example.com
4350 192.12.105.4 #db2.example.com
4351 192.12.105.55 #db3.example.com
4352 >stateu.edu #State University cell
4353 138.255.68.93 #serverA.stateu.edu
4354 138.255.68.72 #serverB.stateu.edu
4355 138.255.33.154 #serverC.stateu.edu
4359 <primary>cache</primary>
4361 <secondary>configuring</secondary>
4363 <tertiary>first AFS machine</tertiary>
4367 <primary>configuring</primary>
4369 <secondary>cache</secondary>
4371 <tertiary>first AFS machine</tertiary>
4375 <primary>setting</primary>
4377 <secondary>cache size and location</secondary>
4379 <tertiary>first AFS machine</tertiary>
4383 <primary>first AFS machine</primary>
4385 <secondary>cache size and location</secondary>
4389 <sect1 id="HDRWQ67">
4390 <title>Configuring the Cache</title>
4392 <para>The Cache Manager uses a cache on the local disk or in machine memory to store local copies of files fetched from file
4393 server machines. As the <emphasis role="bold">afsd</emphasis> program initializes the Cache Manager, it sets basic cache
4394 configuration parameters according to definitions in the local <emphasis role="bold">/usr/vice/etc/cacheinfo</emphasis> file.
4395 The file has three fields: <orderedlist>
4397 <para>The first field names the local directory on which to mount the AFS filespace. The conventional location is the
4398 <emphasis role="bold">/afs</emphasis> directory.</para>
4402 <para>The second field defines the local disk directory to use for the disk cache. The conventional location is the
4403 <emphasis role="bold">/usr/vice/cache</emphasis> directory, but you can specify an alternate directory if another
4404 partition has more space available. There must always be a value in this field, but the Cache Manager ignores it if the
4405 machine uses a memory cache.</para>
4409 <para>The third field specifies the number of kilobyte (1024 byte) blocks to allocate for the cache.</para>
4411 </orderedlist></para>
4413 <para>The values you define must meet the following requirements. <itemizedlist>
4415 <para>On a machine using a disk cache, the Cache Manager expects always to be able to use the amount of space specified in
4416 the third field. Failure to meet this requirement can cause serious problems, some of which can be repaired only by
4417 rebooting. You must prevent non-AFS processes from filling up the cache partition. The simplest way is to devote a
4418 partition to the cache exclusively.</para>
4422 <para>The amount of space available in memory or on the partition housing the disk cache directory imposes an absolute
4423 limit on cache size.</para>
4427 <para>The maximum supported cache size can vary in each AFS release; see the <emphasis>OpenAFS Release Notes</emphasis>
4428 for the current version.</para>
4432 <para>For a disk cache, you cannot specify a value in the third field that exceeds 95% of the space available on the
4433 partition mounted at the directory named in the second field. If you violate this restriction, the <emphasis
4434 role="bold">afsd</emphasis> program exits without starting the Cache Manager and prints an appropriate message on the
4435 standard output stream. A value of 90% is more appropriate on most machines. Some operating systems (such as AIX) do not
4436 automatically reserve some space to prevent the partition from filling completely; for them, a smaller value (say, 80% to
4437 85% of the space available) is more appropriate.</para>
4441 <para>For a memory cache, you must leave enough memory for other processes and applications to run. If you try to allocate
4442 more memory than is actually available, the <emphasis role="bold">afsd</emphasis> program exits without initializing the
4443 Cache Manager and produces the following message on the standard output stream. <programlisting>
4444 afsd: memCache allocation failure at <replaceable>number</replaceable> KB
4445 </programlisting></para>
4447 <para>The <replaceable>number</replaceable> value is how many kilobytes were allocated just before the failure, and so
4448 indicates the approximate amount of memory available.</para>
4450 </itemizedlist></para>
4452 <para>Within these hard limits, the factors that determine appropriate cache size include the number of users working on the
4453 machine, the size of the files with which they work, and (for a memory cache) the number of processes that run on the machine.
4454 The higher the demand from these factors, the larger the cache needs to be to maintain good performance.</para>
4456 <para>Disk caches smaller than 10 MB do not generally perform well. Machines serving multiple users usually perform better with
4457 a cache of at least 60 to 70 MB. The point at which enlarging the cache further does not really improve performance depends on
4458 the factors mentioned previously and is difficult to predict.</para>
4460 <para>Memory caches smaller than 1 MB are nonfunctional, and the performance of caches smaller than 5 MB is usually
4461 unsatisfactory. Suitable upper limits are similar to those for disk caches but are probably determined more by the demands on
4462 memory from other sources on the machine (number of users and processes). Machines running only a few processes possibly can use
4463 a smaller memory cache.</para>
4465 <sect2 id="HDRWQ68">
4466 <title>Configuring a Disk Cache</title>
4469 <para>Not all file system types that an operating system supports are necessarily supported for use as the cache partition.
4470 For possible restrictions, see the <emphasis>OpenAFS Release Notes</emphasis>.</para>
4473 <para>To configure the disk cache, perform the following procedures: <orderedlist>
4475 <para>Create the local directory to use for caching. The following instruction shows the conventional location,
4476 <emphasis role="bold">/usr/vice/cache</emphasis>. If you are devoting a partition exclusively to caching, as
4477 recommended, you must also configure it, make a file system on it, and mount it at the directory created in this step.
4479 # <emphasis role="bold">mkdir /usr/vice/cache</emphasis>
4480 </programlisting></para>
4484 <para>Create the <emphasis role="bold">cacheinfo</emphasis> file to define the configuration parameters discussed
4485 previously. The following instruction shows the standard mount location, <emphasis role="bold">/afs</emphasis>, and the
4486 standard cache location, <emphasis role="bold">/usr/vice/cache</emphasis>. <programlisting>
4487 # <emphasis role="bold">echo "/afs:/usr/vice/cache:</emphasis><replaceable>#blocks</replaceable><emphasis role="bold">" > /usr/vice/etc/cacheinfo</emphasis>
4488 </programlisting></para>
4490 <para>The following example defines the disk cache size as 50,000 KB:</para>
4493 # <emphasis role="bold">echo "/afs:/usr/vice/cache:50000" > /usr/vice/etc/cacheinfo</emphasis>
4496 </orderedlist></para>
4499 <sect2 id="HDRWQ69">
4500 <title>Configuring a Memory Cache</title>
4502 <para>To configure a memory cache, create the <emphasis role="bold">cacheinfo</emphasis> file to define the configuration
4503 parameters discussed previously. The following instruction shows the standard mount location, <emphasis
4504 role="bold">/afs</emphasis>, and the standard cache location, <emphasis role="bold">/usr/vice/cache</emphasis> (though the
4505 exact value of the latter is irrelevant for a memory cache).</para>
4508 # <emphasis role="bold">echo "/afs:/usr/vice/cache:</emphasis><replaceable>#blocks</replaceable><emphasis role="bold">" > /usr/vice/etc/cacheinfo</emphasis>
4511 <para>The following example allocates 25,000 KB of memory for the cache.</para>
4514 # <emphasis role="bold">echo "/afs:/usr/vice/cache:25000" > /usr/vice/etc/cacheinfo</emphasis>
4518 <primary>Cache Manager</primary>
4520 <secondary>first AFS machine</secondary>
4524 <primary>configuring</primary>
4526 <secondary>Cache Manager</secondary>
4528 <tertiary>first AFS machine</tertiary>
4532 <primary>first AFS machine</primary>
4534 <secondary>Cache Manager</secondary>
4538 <primary>afs (/afs) directory</primary>
4540 <secondary>creating</secondary>
4542 <tertiary>first AFS machine</tertiary>
4546 <primary>AFS initialization script</primary>
4548 <secondary>setting afsd parameters</secondary>
4550 <tertiary>first AFS machine</tertiary>
4554 <primary>first AFS machine</primary>
4556 <secondary>afsd command parameters</secondary>
4561 <sect1 id="HDRWQ70">
4562 <title>Configuring the Cache Manager</title>
4564 <para>By convention, the Cache Manager mounts the AFS filespace on the local <emphasis role="bold">/afs</emphasis> directory. In
4565 this section you create that directory.</para>
4567 <para>The <emphasis role="bold">afsd</emphasis> program sets several cache configuration parameters as it initializes the Cache
4568 Manager, and starts daemons that improve performance. You can use the <emphasis role="bold">afsd</emphasis> command's arguments
4569 to override the parameters' default values and to change the number of some of the daemons. Depending on the machine's cache
4570 size, its amount of RAM, and how many people work on it, you can sometimes improve Cache Manager performance by overriding the
4571 default values. For a discussion of all of the <emphasis role="bold">afsd</emphasis> command's arguments, see its reference page
4572 in the <emphasis>OpenAFS Administration Reference</emphasis>.</para>
4574 <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
4575 <computeroutput>OPTIONS</computeroutput> variable. You can use it to set nondefault values for the command's arguments, in one
4576 of the following ways: <itemizedlist>
4578 <para>You can create an <emphasis role="bold">afsd</emphasis> <emphasis>options file</emphasis> that sets values for
4579 arguments to the <emphasis role="bold">afsd</emphasis> command. If the file exists, its contents are automatically
4580 substituted for the <computeroutput>OPTIONS</computeroutput> variable in the AFS initialization script. The AFS
4581 distribution for some system types includes an options file; on other system types, you must create it.</para>
4583 <para>You use two variables in the AFS initialization script to specify the path to the options file:
4584 <computeroutput>CONFIG</computeroutput> and <computeroutput>AFSDOPT</computeroutput>. On system types that define a
4585 conventional directory for configuration files, the <computeroutput>CONFIG</computeroutput> variable indicates it by
4586 default; otherwise, the variable indicates an appropriate location.</para>
4588 <para>List the desired <emphasis role="bold">afsd</emphasis> options on a single line in the options file, separating each
4589 option with one or more spaces. The following example sets the <emphasis role="bold">-stat</emphasis> argument to 2500,
4590 the <emphasis role="bold">-daemons</emphasis> argument to 4, and the <emphasis role="bold">-volumes</emphasis> argument to
4594 -stat 2500 -daemons 4 -volumes 100
4599 <para>On a machine that uses a disk cache, you can set the <computeroutput>OPTIONS</computeroutput> variable in the AFS
4600 initialization script to one of <computeroutput>$SMALL</computeroutput>, <computeroutput>$MEDIUM</computeroutput>, or
4601 <computeroutput>$LARGE</computeroutput>. The AFS initialization script uses one of these settings if the <emphasis
4602 role="bold">afsd</emphasis> options file named by the <computeroutput>AFSDOPT</computeroutput> variable does not exist. In
4603 the script as distributed, the <computeroutput>OPTIONS</computeroutput> variable is set to the value
4604 <computeroutput>$MEDIUM</computeroutput>.</para>
4607 <para>Do not set the <computeroutput>OPTIONS</computeroutput> variable to <computeroutput>$SMALL</computeroutput>,
4608 <computeroutput>$MEDIUM</computeroutput>, or <computeroutput>$LARGE</computeroutput> on a machine that uses a memory
4609 cache. The arguments it sets are appropriate only on a machine that uses a disk cache.</para>
4612 <para>The script (or on some system types the <emphasis role="bold">afsd</emphasis> options file named by the
4613 <computeroutput>AFSDOPT</computeroutput> variable) defines a value for each of <computeroutput>SMALL</computeroutput>,
4614 <computeroutput>MEDIUM</computeroutput>, and <computeroutput>LARGE</computeroutput> that sets <emphasis
4615 role="bold">afsd</emphasis> command arguments appropriately for client machines of different sizes: <itemizedlist>
4617 <para><computeroutput>SMALL</computeroutput> is suitable for a small machine that serves one or two users and has
4618 approximately 8 MB of RAM and a 20-MB cache</para>
4622 <para><computeroutput>MEDIUM</computeroutput> is suitable for a medium-sized machine that serves two to six users
4623 and has 16 MB of RAM and a 40-MB cache</para>
4627 <para><computeroutput>LARGE</computeroutput> is suitable for a large machine that serves five to ten users and has
4628 32 MB of RAM and a 100-MB cache</para>
4630 </itemizedlist></para>
4634 <para>You can choose not to create an <emphasis role="bold">afsd</emphasis> options file and to set the
4635 <computeroutput>OPTIONS</computeroutput> variable in the initialization script to a null value rather than to the default
4636 <computeroutput>$MEDIUM</computeroutput> value. You can then either set arguments directly on the <emphasis
4637 role="bold">afsd</emphasis> command line in the script, or set no arguments (and so accept default values for all Cache
4638 Manager parameters).</para>
4643 <para>If you are running on a Fedora or RHEL based system, the
4644 openafs-client initialization script behaves differently from that
4645 described above. It sources /etc/sysconfig/openafs, in which the
4646 AFSD_ARGS variable may be set to contain any, or all, of the afsd options
4647 detailed. Note that this script does not support setting an OPTIONS
4648 variable, or the SMALL, MEDIUM and LARGE methods of defining cache size
4654 <para>Create the local directory on which to mount the AFS filespace, by convention <emphasis role="bold">/afs</emphasis>.
4655 If the directory already exists, verify that it is empty. <programlisting>
4656 # <emphasis role="bold">mkdir /afs</emphasis>
4657 </programlisting></para>
4661 <para>On AIX systems, add the following line to the <emphasis role="bold">/etc/vfs</emphasis> file. It enables AIX to
4662 unmount AFS correctly during shutdown. <programlisting>
4664 </programlisting></para>
4668 <para>On non-package based Linux systems, copy the <emphasis role="bold">afsd</emphasis> options file from the <emphasis
4669 role="bold">/usr/vice/etc</emphasis> directory to the <emphasis role="bold">/etc/sysconfig</emphasis> directory, removing
4670 the <emphasis role="bold">.conf</emphasis> extension as you do so. <programlisting>
4671 # <emphasis role="bold">cp /usr/vice/etc/afs.conf /etc/sysconfig/afs</emphasis>
4672 </programlisting></para>
4676 <para>Edit the machine's AFS initialization script or <emphasis role="bold">afsd</emphasis> options file to set
4677 appropriate values for <emphasis role="bold">afsd</emphasis> command parameters. The script resides in the indicated
4678 location on each system type: <itemizedlist>
4680 <para>On AIX systems, <emphasis role="bold">/etc/rc.afs</emphasis></para>
4684 <para>On HP-UX systems, <emphasis role="bold">/sbin/init.d/afs</emphasis></para>
4688 <para>On IRIX systems, <emphasis role="bold">/etc/init.d/afs</emphasis></para>
4692 <para>On Fedora and RHEL systems, <emphasis role="bold">/etc/sysconfg/openafs</emphasis></para>
4696 <para>On non-package based Linux systems, <emphasis role="bold">/etc/sysconfig/afs</emphasis> (the <emphasis
4697 role="bold">afsd</emphasis> options file)</para>
4701 <para>On Solaris systems, <emphasis role="bold">/etc/init.d/afs</emphasis></para>
4703 </itemizedlist></para>
4705 <para>Use one of the methods described in the introduction to this section to add the following flags to the <emphasis
4706 role="bold">afsd</emphasis> command line. If you intend for the machine to remain an AFS client, also set any
4707 performance-related arguments you wish. <itemizedlist>
4709 <para>Add the <emphasis role="bold">-memcache</emphasis> flag if the machine is to use a memory cache.</para>
4713 <para>Add the <emphasis role="bold">-verbose</emphasis> flag to display a trace of the Cache Manager's
4714 initialization on the standard output stream.</para>
4716 </itemizedlist></para>
4719 <note><para>In order to successfully complete the instructions in the
4720 remainder of this guide, it is important that the machine does not have
4721 a synthetic root (as discussed in <link linkend="HDRWQ91">Enabling Access
4722 to Foreign Cells</link>). As some distributions ship with this enabled, it
4723 may be necessary to remove any occurences of the
4724 <emphasis role="bold">-dynroot</emphasis> and
4725 <emphasis role="bold">-afsdb</emphasis> options from both the AFS
4726 initialisation script and options file. If this functionality is
4727 required it may be renabled as detailed in
4728 <link linkend="HDRWQ91">Enabling Access to Foreign Cells</link>.
4733 <primary>overview</primary>
4735 <secondary>completing installation of first machine</secondary>
4739 <primary>first AFS machine</primary>
4741 <secondary>completion of installation</secondary>
4745 <sect1 id="HDRWQ71">
4746 <title>Overview: Completing the Installation of the First AFS Machine</title>
4748 <para>The machine is now configured as an AFS file server and client machine. In this final phase of the installation, you
4749 initialize the Cache Manager and then create the upper levels of your AFS filespace, among other procedures. The procedures are:
4752 <para>Verify that the initialization script works correctly, and incorporate it into the operating system's startup and
4753 shutdown sequence</para>
4757 <para>Create and mount top-level volumes</para>
4761 <para>Create and mount volumes to store system binaries in AFS</para>
4765 <para>Enable access to foreign cells</para>
4769 <para>Institute additional security measures</para>
4773 <para>Remove client functionality if desired</para>
4775 </orderedlist></para>
4778 <primary>AFS initialization script</primary>
4780 <secondary>verifying on first AFS machine</secondary>
4784 <primary>AFS initialization script</primary>
4786 <secondary>running</secondary>
4788 <tertiary>first AFS machine</tertiary>
4792 <primary>first AFS machine</primary>
4794 <secondary>AFS initialization script</secondary>
4796 <tertiary>running/verifying</tertiary>
4800 <primary>running AFS init. script</primary>
4802 <secondary>first AFS machine</secondary>
4806 <primary>invoking AFS init. script</primary>
4812 <sect1 id="HDRWQ72">
4813 <title>Verifying the AFS Initialization Script</title>
4815 <para>At this point you run the AFS initialization script to verify that it correctly invokes all of the necessary programs and
4816 AFS processes, and that they start correctly. The following are the relevant commands: <itemizedlist>
4818 <para>The command that dynamically loads AFS modifications into the kernel, on some system types (not applicable if the
4819 kernel has AFS modifications built in)</para>
4823 <para>The <emphasis role="bold">bosserver</emphasis> command, which starts the BOS Server; it in turn starts the server
4824 processes for which you created entries in the <emphasis role="bold">/usr/afs/local/BosConfig</emphasis> file</para>
4828 <para>The <emphasis role="bold">afsd</emphasis> command, which initializes the Cache Manager</para>
4830 </itemizedlist></para>
4832 <para>On system types that use a dynamic loader program, you must reboot the machine before running the initialization script,
4833 so that it can freshly load AFS modifications into the kernel.</para>
4835 <para>If there are problems during the initialization, attempt to resolve them. The OpenAFS mailing lists can provide assistance if necessary.
4839 <primary>commands</primary>
4841 <secondary>bos shutdown</secondary>
4845 <primary>bos commands</primary>
4847 <secondary>shutdown</secondary>
4851 <para>Issue the <emphasis role="bold">bos shutdown</emphasis> command to shut down the AFS server processes other than the
4852 BOS Server. Include the <emphasis role="bold">-wait</emphasis> flag to delay return of the command shell prompt until all
4853 processes shut down completely. <programlisting>
4854 # <emphasis role="bold">/usr/afs/bin/bos shutdown</emphasis> <<replaceable>machine name</replaceable>> <emphasis
4855 role="bold">-wait</emphasis>
4856 </programlisting></para>
4860 <para>Issue the <emphasis role="bold">ps</emphasis> command to learn the <emphasis role="bold">bosserver</emphasis>
4861 process's process ID number (PID), and then the <emphasis role="bold">kill</emphasis> command to stop it. <programlisting>
4862 # <emphasis role="bold">ps</emphasis> <replaceable>appropriate_ps_options</replaceable> <emphasis role="bold">| grep bosserver</emphasis>
4863 # <emphasis role="bold">kill</emphasis> <replaceable>bosserver_PID</replaceable>
4864 </programlisting></para>
4868 <para>Issue the appropriate commands to run the AFS initialization script for this system type.</para>
4871 <primary>AIX</primary>
4873 <secondary>AFS initialization script</secondary>
4875 <tertiary>on first AFS machine</tertiary>
4878 <para><emphasis role="bold">On AIX systems:</emphasis> <orderedlist>
4880 <para>Reboot the machine and log in again as the local superuser <emphasis role="bold">root</emphasis>.
4882 # <emphasis role="bold">cd /</emphasis>
4883 # <emphasis role="bold">shutdown -r now</emphasis>
4884 login: <emphasis role="bold">root</emphasis>
4885 Password: <replaceable>root_password</replaceable>
4886 </programlisting></para>
4890 <para>Run the AFS initialization script. <programlisting>
4891 # <emphasis role="bold">/etc/rc.afs</emphasis>
4892 </programlisting></para>
4894 </orderedlist></para>
4897 <primary>HP-UX</primary>
4899 <secondary>AFS initialization script</secondary>
4901 <tertiary>on first AFS machine</tertiary>
4904 <para><emphasis role="bold">On HP-UX systems:</emphasis> <orderedlist>
4906 <para>Run the AFS initialization script. <programlisting>
4907 # <emphasis role="bold">/sbin/init.d/afs start</emphasis>
4908 </programlisting></para>
4910 </orderedlist></para>
4913 <primary>IRIX</primary>
4915 <secondary>AFS initialization script</secondary>
4917 <tertiary>on first AFS machine</tertiary>
4921 <primary>afsclient variable (IRIX)</primary>
4923 <secondary>first AFS machine</secondary>
4927 <primary>variables</primary>
4929 <secondary>afsclient (IRIX)</secondary>
4931 <tertiary>first AFS machine</tertiary>
4935 <primary>IRIX</primary>
4937 <secondary>afsclient variable</secondary>
4939 <tertiary>first AFS machine</tertiary>
4943 <primary>afsserver variable (IRIX)</primary>
4945 <secondary>first AFS machine</secondary>
4949 <primary>variables</primary>
4951 <secondary>afsserver (IRIX)</secondary>
4953 <tertiary>first AFS machine</tertiary>
4957 <primary>IRIX</primary>
4959 <secondary>afsserver variable</secondary>
4961 <tertiary>first AFS machine</tertiary>
4964 <para><emphasis role="bold">On IRIX systems:</emphasis> <orderedlist>
4966 <para>If you have configured the machine to use the <emphasis role="bold">ml</emphasis> dynamic loader program,
4967 reboot the machine and log in again as the local superuser <emphasis role="bold">root</emphasis>. <programlisting>
4968 # <emphasis role="bold">cd /</emphasis>
4969 # <emphasis role="bold">shutdown -i6 -g0 -y</emphasis>
4970 login: <emphasis role="bold">root</emphasis>
4971 Password: <replaceable>root_password</replaceable>
4972 </programlisting></para>
4976 <para>Issue the <emphasis role="bold">chkconfig</emphasis> command to activate the <emphasis
4977 role="bold">afsserver</emphasis> and <emphasis role="bold">afsclient</emphasis> configuration variables.
4979 # <emphasis role="bold">/etc/chkconfig -f afsserver on</emphasis>
4980 # <emphasis role="bold">/etc/chkconfig -f afsclient on</emphasis>
4981 </programlisting></para>
4985 <para>Run the AFS initialization script. <programlisting>
4986 # <emphasis role="bold">/etc/init.d/afs start</emphasis>
4987 </programlisting></para>
4989 </orderedlist></para>
4992 <primary>Linux</primary>
4994 <secondary>AFS initialization script</secondary>
4996 <tertiary>on first AFS machine</tertiary>
4999 <para><emphasis role="bold">On Linux systems:</emphasis> <orderedlist>
5001 <para>Reboot the machine and log in again as the local superuser <emphasis role="bold">root</emphasis>.
5003 # <emphasis role="bold">cd /</emphasis>
5004 # <emphasis role="bold">shutdown -r now</emphasis>
5005 login: <emphasis role="bold">root</emphasis>
5006 Password: <replaceable>root_password</replaceable>
5007 </programlisting></para>
5011 <para>Run the AFS initialization scripts.
5013 # <emphasis role="bold">/etc/rc.d/init.d/openafs-client start</emphasis>
5014 # <emphasis role="bold">/etc/rc.d/init.d/openafs-server start</emphasis>
5015 </programlisting></para>
5017 </orderedlist></para>
5020 <primary>Solaris</primary>
5022 <secondary>AFS initialization script</secondary>
5024 <tertiary>on first AFS machine</tertiary>
5027 <para><emphasis role="bold">On Solaris systems:</emphasis> <orderedlist>
5029 <para>Reboot the machine and log in again as the local superuser <emphasis role="bold">root</emphasis>.
5031 # <emphasis role="bold">cd /</emphasis>
5032 # <emphasis role="bold">shutdown -i6 -g0 -y</emphasis>
5033 login: <emphasis role="bold">root</emphasis>
5034 Password: <replaceable>root_password</replaceable>
5035 </programlisting></para>
5039 <para>Run the AFS initialization script. <programlisting>
5040 # <emphasis role="bold">/etc/init.d/afs start</emphasis>
5041 </programlisting></para>
5043 </orderedlist></para>
5047 <para>Wait for the message that confirms that Cache Manager initialization is complete.</para>
5049 <para>On machines that use a disk cache, it can take a while to initialize the Cache Manager for the first time, because
5050 the <emphasis role="bold">afsd</emphasis> program must create all of the <emphasis
5051 role="bold">V</emphasis><replaceable>n</replaceable> files in the cache directory. Subsequent Cache Manager
5052 initializations do not take nearly as long, because the <emphasis role="bold">V</emphasis><replaceable>n</replaceable>
5053 files already exist.</para>
5058 <primary>commands</primary>
5059 <secondary>aklog</secondary>
5063 <primary>aklog command</primary>
5066 <para>If you are working with an existing cell which uses
5067 <emphasis role="bold">kaserver</emphasis> for authentication,
5068 please recall the note in
5069 <link linkend="KAS003">Using this Appendix</link> detailing the
5070 substitution of <emphasis role="bold">kinit</emphasis> and
5071 <emphasis role="bold">aklog</emphasis> with
5072 <emphasis role="bold">klog</emphasis>.</para>
5074 <para>As a basic test of correct AFS functioning, issue the
5075 <emphasis role="bold">kinit</emphasis> and
5076 <emphasis role="bold">aklog</emphasis> commands to authenticate
5077 as the <emphasis role="bold">admin</emphasis> user.
5078 Provide the password (<replaceable>admin_passwd</replaceable>) you
5079 defined in <link linkend="HDRWQ53">Initializing Cell Security</link>.</para>
5082 # <emphasis role="bold">kinit admin</emphasis>
5083 Password: <replaceable>admin_passwd</replaceable>
5084 # <emphasis role="bold">aklog</emphasis>
5088 <primary>commands</primary>
5090 <secondary>tokens</secondary>
5094 <primary>tokens command</primary>
5099 <para>Issue the <emphasis role="bold">tokens</emphasis> command to
5100 verify that the <emphasis role="bold">aklog</emphasis>
5101 command worked correctly. If it did, the output looks similar to the following example for the <emphasis
5102 role="bold">example.com</emphasis> cell, where <emphasis role="bold">admin</emphasis>'s AFS UID is 1. If the output does not
5103 seem correct, resolve the problem. Changes to the AFS initialization script are possibly necessary. The OpenAFS mailing lists can provide assistance as necessary. <programlisting>
5104 # <emphasis role="bold">tokens</emphasis>
5105 Tokens held by the Cache Manager:
5106 User's (AFS ID 1) tokens for afs@example.com [Expires May 22 11:52]
5108 </programlisting></para>
5112 <para>Issue the <emphasis role="bold">bos status</emphasis> command to verify that the output for each process reads
5113 <computeroutput>Currently running normally</computeroutput>. <programlisting>
5114 # <emphasis role="bold">/usr/afs/bin/bos status</emphasis> <<replaceable>machine name</replaceable>>
5115 </programlisting> <indexterm>
5116 <primary>fs commands</primary>
5118 <secondary>checkvolumes</secondary>
5119 </indexterm> <indexterm>
5120 <primary>commands</primary>
5122 <secondary>fs checkvolumes</secondary>
5127 <para>Change directory to the local file system root (<emphasis role="bold">/</emphasis>) and issue the <emphasis
5128 role="bold">fs checkvolumes</emphasis> command. <programlisting>
5129 # <emphasis role="bold">cd /</emphasis>
5130 # <emphasis role="bold">/usr/afs/bin/fs checkvolumes</emphasis>
5131 </programlisting></para>
5133 </orderedlist></para>
5136 <primary>AFS initialization script</primary>
5138 <secondary>adding to machine startup sequence</secondary>
5140 <tertiary>first AFS machine</tertiary>
5144 <primary>installing</primary>
5146 <secondary>AFS initialization script</secondary>
5148 <tertiary>first AFS machine</tertiary>
5152 <primary>first AFS machine</primary>
5154 <secondary>AFS initialization script</secondary>
5156 <tertiary>activating</tertiary>
5160 <primary>activating AFS init. script</primary>
5162 <see>installing</see>
5166 <sect1 id="HDRWQ73">
5167 <title>Activating the AFS Initialization Script</title>
5169 <para>Now that you have confirmed that the AFS initialization script works correctly, take the action necessary to have it run
5170 automatically at each reboot. Proceed to the instructions for your system type: <itemizedlist>
5172 <para><link linkend="HDRWQ74">Activating the Script on AIX Systems</link></para>
5176 <para><link linkend="HDRWQ76">Activating the Script on HP-UX Systems</link></para>
5180 <para><link linkend="HDRWQ77">Activating the Script on IRIX Systems</link></para>
5184 <para><link linkend="HDRWQ78">Activating the Script on Linux Systems</link></para>
5188 <para><link linkend="HDRWQ79">Activating the Script on Solaris Systems</link></para>
5190 </itemizedlist></para>
5193 <primary>AIX</primary>
5195 <secondary>AFS initialization script</secondary>
5197 <tertiary>on first AFS machine</tertiary>
5200 <sect2 id="HDRWQ74">
5201 <title>Activating the Script on AIX Systems</title>
5205 <para>Edit the AIX initialization file, <emphasis role="bold">/etc/inittab</emphasis>, adding the following line to invoke
5206 the AFS initialization script. Place it just after the line that starts NFS daemons. <programlisting>
5207 rcafs:2:wait:/etc/rc.afs > /dev/console 2>&1 # Start AFS services
5208 </programlisting></para>
5212 <para><emphasis role="bold">(Optional)</emphasis> There are now copies of the AFS initialization file in both the
5213 <emphasis role="bold">/usr/vice/etc</emphasis> and <emphasis role="bold">/etc</emphasis> directories. If you want to avoid
5214 potential confusion by guaranteeing that they are always the same, create a link between them. You can always retrieve the
5215 original script from the AFS CD-ROM if necessary. <programlisting>
5216 # <emphasis role="bold">cd /usr/vice/etc</emphasis>
5217 # <emphasis role="bold">rm rc.afs</emphasis>
5218 # <emphasis role="bold">ln -s /etc/rc.afs</emphasis>
5219 </programlisting></para>
5223 <para>Proceed to <link linkend="HDRWQ80">Configuring the Top Levels of the AFS Filespace</link>.</para>
5228 <primary>HP-UX</primary>
5230 <secondary>AFS initialization script</secondary>
5232 <tertiary>on first AFS machine</tertiary>
5236 <sect2 id="HDRWQ76">
5237 <title>Activating the Script on HP-UX Systems</title>
5241 <para>Change to the <emphasis role="bold">/sbin/init.d</emphasis> directory and issue the <emphasis role="bold">ln
5242 -s</emphasis> command to create symbolic links that incorporate the AFS initialization script into the HP-UX startup and
5243 shutdown sequence. <programlisting>
5244 # <emphasis role="bold">cd /sbin/init.d</emphasis>
5245 # <emphasis role="bold">ln -s ../init.d/afs /sbin/rc2.d/S460afs</emphasis>
5246 # <emphasis role="bold">ln -s ../init.d/afs /sbin/rc2.d/K800afs</emphasis>
5247 </programlisting></para>
5251 <para><emphasis role="bold">(Optional)</emphasis> There are now copies of the AFS initialization file in both the
5252 <emphasis role="bold">/usr/vice/etc</emphasis> and <emphasis role="bold">/sbin/init.d</emphasis> directories. If you want
5253 to avoid potential confusion by guaranteeing that they are always the same, create a link between them. You can always
5254 retrieve the original script from the AFS CD-ROM if necessary. <programlisting>
5255 # <emphasis role="bold">cd /usr/vice/etc</emphasis>
5256 # <emphasis role="bold">rm afs.rc</emphasis>
5257 # <emphasis role="bold">ln -s /sbin/init.d/afs afs.rc</emphasis>
5258 </programlisting></para>
5262 <para>Proceed to <link linkend="HDRWQ80">Configuring the Top Levels of the AFS Filespace</link>.</para>
5267 <primary>IRIX</primary>
5269 <secondary>AFS initialization script</secondary>
5271 <tertiary>on first AFS machine</tertiary>
5275 <sect2 id="HDRWQ77">
5276 <title>Activating the Script on IRIX Systems</title>
5280 <para>Change to the <emphasis role="bold">/etc/init.d</emphasis> directory and issue the <emphasis role="bold">ln
5281 -s</emphasis> command to create symbolic links that incorporate the AFS initialization script into the IRIX startup and
5282 shutdown sequence. <programlisting>
5283 # <emphasis role="bold">cd /etc/init.d</emphasis>
5284 # <emphasis role="bold">ln -s ../init.d/afs /etc/rc2.d/S35afs</emphasis>
5285 # <emphasis role="bold">ln -s ../init.d/afs /etc/rc0.d/K35afs</emphasis>
5286 </programlisting></para>
5290 <para><emphasis role="bold">(Optional)</emphasis> There are now copies of the AFS initialization file in both the
5291 <emphasis role="bold">/usr/vice/etc</emphasis> and <emphasis role="bold">/etc/init.d</emphasis> directories. If you want
5292 to avoid potential confusion by guaranteeing that they are always the same, create a link between them. You can always
5293 retrieve the original script from the AFS CD-ROM if necessary. <programlisting>
5294 # <emphasis role="bold">cd /usr/vice/etc</emphasis>
5295 # <emphasis role="bold">rm afs.rc</emphasis>
5296 # <emphasis role="bold">ln -s /etc/init.d/afs afs.rc</emphasis>
5297 </programlisting></para>
5301 <para>Proceed to <link linkend="HDRWQ80">Configuring the Top Levels of the AFS Filespace</link>.</para>
5306 <primary>Linux</primary>
5308 <secondary>AFS initialization script</secondary>
5310 <tertiary>on first AFS machine</tertiary>
5314 <sect2 id="HDRWQ78">
5315 <title>Activating the Script on Linux Systems</title>
5319 <para>Issue the <emphasis role="bold">chkconfig</emphasis> command to activate the <emphasis role="bold">openafs-client</emphasis> and <emphasis role="bold">openafs-server</emphasis>
5320 configuration variables. Based on the instruction in the AFS initialization file that begins with the string
5321 <computeroutput>#chkconfig</computeroutput>, the command automatically creates the symbolic links that incorporate the
5322 script into the Linux startup and shutdown sequence. <programlisting>
5323 # <emphasis role="bold">/sbin/chkconfig --add openafs-client</emphasis>
5324 # <emphasis role="bold">/sbin/chkconfig --add openafs-server</emphasis>
5325 </programlisting></para>
5329 <para><emphasis role="bold">(Optional)</emphasis> There are now copies of the AFS initialization file in both the
5330 <emphasis role="bold">/usr/vice/etc</emphasis> and <emphasis role="bold">/etc/rc.d/init.d</emphasis> directories, and
5331 copies of the <emphasis role="bold">afsd</emphasis> options file in both the <emphasis
5332 role="bold">/usr/vice/etc</emphasis> and <emphasis role="bold">/etc/sysconfig</emphasis> directories. If you want to avoid
5333 potential confusion by guaranteeing that the two copies of each file are always the same, create a link between them. You
5334 can always retrieve the original script or options file from the AFS CD-ROM if necessary. <programlisting>
5335 # <emphasis role="bold">cd /usr/vice/etc</emphasis>
5336 # <emphasis role="bold">rm afs.rc afs.conf</emphasis>
5337 # <emphasis role="bold">ln -s /etc/rc.d/init.d/afs afs.rc</emphasis>
5338 # <emphasis role="bold">ln -s /etc/sysconfig/afs afs.conf</emphasis>
5339 </programlisting></para>
5343 <para>Proceed to <link linkend="HDRWQ80">Configuring the Top Levels of the AFS Filespace</link>.</para>
5348 <primary>Solaris</primary>
5350 <secondary>AFS initialization script</secondary>
5352 <tertiary>on first AFS machine</tertiary>
5356 <sect2 id="HDRWQ79">
5357 <title>Activating the Script on Solaris Systems</title>
5361 <para>Change to the <emphasis role="bold">/etc/init.d</emphasis> directory and issue the <emphasis role="bold">ln
5362 -s</emphasis> command to create symbolic links that incorporate the AFS initialization script into the Solaris startup and
5363 shutdown sequence. <programlisting>
5364 # <emphasis role="bold">cd /etc/init.d</emphasis>
5365 # <emphasis role="bold">ln -s ../init.d/afs /etc/rc3.d/S99afs</emphasis>
5366 # <emphasis role="bold">ln -s ../init.d/afs /etc/rc0.d/K66afs</emphasis>
5367 </programlisting></para>
5371 <para><emphasis role="bold">(Optional)</emphasis> There are now copies of the AFS initialization file in both the
5372 <emphasis role="bold">/usr/vice/etc</emphasis> and <emphasis role="bold">/etc/init.d</emphasis> directories. If you want
5373 to avoid potential confusion by guaranteeing that they are always the same, create a link between them. You can always
5374 retrieve the original script from the AFS CD-ROM if necessary. <programlisting>
5375 # <emphasis role="bold">cd /usr/vice/etc</emphasis>
5376 # <emphasis role="bold">rm afs.rc</emphasis>
5377 # <emphasis role="bold">ln -s /etc/init.d/afs afs.rc</emphasis>
5378 </programlisting></para>
5383 <primary>AFS filespace</primary>
5385 <secondary>configuring top levels</secondary>
5389 <primary>configuring</primary>
5391 <secondary>AFS filespace (top levels)</secondary>
5396 <sect1 id="HDRWQ80">
5397 <title>Configuring the Top Levels of the AFS Filespace</title>
5399 <para>If you have not previously run AFS in your cell, you now configure the top levels of your cell's AFS filespace. If you
5400 have run a previous version of AFS, the filespace is already configured. Proceed to <link linkend="HDRWQ83">Storing AFS Binaries
5401 in AFS</link>. <indexterm>
5402 <primary>root.cell volume</primary>
5404 <secondary>creating and replicating</secondary>
5405 </indexterm> <indexterm>
5406 <primary>volume</primary>
5408 <secondary>creating</secondary>
5410 <tertiary>root.cell</tertiary>
5411 </indexterm> <indexterm>
5412 <primary>creating</primary>
5414 <secondary>root.cell volume</secondary>
5417 <para>You created the <emphasis role="bold">root.afs</emphasis> volume in <link linkend="HDRWQ60">Starting the File Server,
5418 Volume Server, and Salvager</link>, and the Cache Manager mounted it automatically on the local <emphasis
5419 role="bold">/afs</emphasis> directory when you ran the AFS initialization script in <link linkend="HDRWQ72">Verifying the AFS
5420 Initialization Script</link>. You now set the access control list (ACL) on the <emphasis role="bold">/afs</emphasis> directory;
5421 creating, mounting, and setting the ACL are the three steps required when creating any volume.</para>
5423 <para>After setting the ACL on the <emphasis role="bold">root.afs</emphasis> volume, you create your cell's <emphasis
5424 role="bold">root.cell</emphasis> volume, mount it as a subdirectory of the <emphasis role="bold">/afs</emphasis> directory, and
5425 set the ACL. Create both a read/write and a regular mount point for the <emphasis role="bold">root.cell</emphasis> volume. The
5426 read/write mount point enables you to access the read/write version of replicated volumes when necessary. Creating both mount
5427 points essentially creates separate read-only and read-write copies of your filespace, and enables the Cache Manager to traverse
5428 the filespace on a read-only path or read/write path as appropriate. For further discussion of these concepts, see the chapter
5429 in the <emphasis>OpenAFS Administration Guide</emphasis> about administering volumes. <indexterm>
5430 <primary>root.afs volume</primary>
5432 <secondary>replicating</secondary>
5433 </indexterm> <indexterm>
5434 <primary>volume</primary>
5436 <secondary>replicating root.afs and root.cell</secondary>
5437 </indexterm> <indexterm>
5438 <primary>replicating volumes</primary>
5441 <para>Then replicate both the <emphasis role="bold">root.afs</emphasis> and <emphasis role="bold">root.cell</emphasis> volumes.
5442 This is required if you want to replicate any other volumes in your cell, because all volumes mounted above a replicated volume
5443 must themselves be replicated in order for the Cache Manager to access the replica.</para>
5445 <para>When the <emphasis role="bold">root.afs</emphasis> volume is replicated, the Cache Manager is programmed to access its
5446 read-only version (<emphasis role="bold">root.afs.readonly</emphasis>) whenever possible. To make changes to the contents of the
5447 <emphasis role="bold">root.afs</emphasis> volume (when, for example, you mount another cell's <emphasis
5448 role="bold">root.cell</emphasis> volume at the second level in your filespace), you must mount the <emphasis
5449 role="bold">root.afs</emphasis> volume temporarily, make the changes, release the volume and remove the temporary mount point.
5450 For instructions, see <link linkend="HDRWQ91">Enabling Access to Foreign Cells</link>. <indexterm>
5451 <primary>fs commands</primary>
5453 <secondary>setacl</secondary>
5454 </indexterm> <indexterm>
5455 <primary>commands</primary>
5457 <secondary>fs setacl</secondary>
5458 </indexterm> <indexterm>
5459 <primary>access control list (ACL), setting</primary>
5460 </indexterm> <indexterm>
5461 <primary>setting</primary>
5463 <secondary>ACL</secondary>
5464 </indexterm> <orderedlist>
5466 <para>Issue the <emphasis role="bold">fs setacl</emphasis> command to edit the ACL on the <emphasis
5467 role="bold">/afs</emphasis> directory. Add an entry that grants the <emphasis role="bold">l</emphasis> (<emphasis
5468 role="bold">lookup</emphasis>) and <emphasis role="bold">r</emphasis> (<emphasis role="bold">read</emphasis>) permissions
5469 to the <emphasis role="bold">system:anyuser</emphasis> group, to enable all AFS users who can reach your cell to traverse
5470 through the directory. If you prefer to enable access only to locally authenticated users, substitute the <emphasis
5471 role="bold">system:authuser</emphasis> group.</para>
5473 <para>Note that there is already an ACL entry that grants all seven access rights to the <emphasis
5474 role="bold">system:administrators</emphasis> group. It is a default entry that AFS places on every new volume's root
5477 <para>The top-level AFS directory, typically /afs, is a special case:
5478 when the client is configured to run in dynroot mode (e.g.
5479 <emphasis role="bold">afsd -dynroot</emphasis>, attempts to set
5480 the ACL on this directory will return <emphasis role="bold">
5481 Connection timed out</emphasis>. This is because the dynamically-
5482 generated root directory is not a part of the global AFS space,
5483 and cannot have an access control list set on it.</para>
5486 # <emphasis role="bold">/usr/afs/bin/fs setacl /afs system:anyuser rl</emphasis>
5490 <primary>commands</primary>
5492 <secondary>vos create</secondary>
5494 <tertiary>root.cell volume</tertiary>
5498 <primary>vos commands</primary>
5500 <secondary>create</secondary>
5502 <tertiary>root.cell volume</tertiary>
5506 <primary>fs commands</primary>
5508 <secondary>mkmount</secondary>
5512 <primary>commands</primary>
5514 <secondary>fs mkmount</secondary>
5518 <primary>mount point</primary>
5522 <primary>creating</primary>
5524 <secondary>mount point</secondary>
5528 <primary>volume</primary>
5530 <secondary>mounting</secondary>
5534 <listitem id="LIWQ81">
5535 <para>Issue the <emphasis role="bold">vos create</emphasis> command to create the <emphasis
5536 role="bold">root.cell</emphasis> volume. Then issue the <emphasis role="bold">fs mkmount</emphasis> command to mount it as
5537 a subdirectory of the <emphasis role="bold">/afs</emphasis> directory, where it serves as the root of your cell's local
5538 AFS filespace. Finally, issue the <emphasis role="bold">fs setacl</emphasis> command to create an ACL entry for the
5539 <emphasis role="bold">system:anyuser</emphasis> group (or <emphasis role="bold">system:authuser</emphasis> group).</para>
5541 <para>For the <replaceable>partition name</replaceable> argument, substitute the name of one of the machine's AFS server
5542 partitions (such as <emphasis role="bold">/vicepa</emphasis>). For the <replaceable>cellname</replaceable> argument,
5543 substitute your cell's fully-qualified Internet domain name (such as <emphasis role="bold">abc.com</emphasis>).</para>
5546 # <emphasis role="bold">/usr/afs/bin/vos create</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>partition name</replaceable>> <emphasis
5547 role="bold">root.cell</emphasis>
5548 # <emphasis role="bold">/usr/afs/bin/fs mkmount /afs/</emphasis><replaceable>cellname</replaceable> <emphasis role="bold">root.cell</emphasis>
5549 # <emphasis role="bold">/usr/afs/bin/fs setacl /afs/</emphasis><replaceable>cellname</replaceable> <emphasis role="bold">system:anyuser rl</emphasis>
5553 <primary>creating</primary>
5555 <secondary>symbolic link</secondary>
5557 <tertiary>for abbreviated cell name</tertiary>
5561 <primary>symbolic link</primary>
5563 <secondary>for abbreviated cell name</secondary>
5567 <primary>cell name</primary>
5569 <secondary>symbolic link for abbreviated</secondary>
5574 <para><emphasis role="bold">(Optional)</emphasis> Create a symbolic link to a shortened cell name, to reduce the length of
5575 pathnames for users in the local cell. For example, in the <emphasis role="bold">abc.com</emphasis> cell, <emphasis
5576 role="bold">/afs/abc</emphasis> is a link to <emphasis role="bold">/afs/abc.com</emphasis>. <programlisting>
5577 # <emphasis role="bold">cd /afs</emphasis>
5578 # <emphasis role="bold">ln -s</emphasis> <replaceable>full_cellname</replaceable> <replaceable>short_cellname</replaceable>
5579 </programlisting> <indexterm>
5580 <primary>read/write mount point for root.afs volume</primary>
5581 </indexterm> <indexterm>
5582 <primary>root.afs volume</primary>
5584 <secondary>read/write mount point</secondary>
5585 </indexterm> <indexterm>
5586 <primary>creating</primary>
5588 <secondary>read/write mount point</secondary>
5593 <para>Issue the <emphasis role="bold">fs mkmount</emphasis> command to create a read/write mount point for the <emphasis
5594 role="bold">root.cell</emphasis> volume (you created a regular mount point in Step <link
5595 linkend="LIWQ81">2</link>).</para>
5597 <para>By convention, the name of a read/write mount point begins with a period, both to distinguish it from the regular
5598 mount point and to make it visible only when the <emphasis role="bold">-a</emphasis> flag is used on the <emphasis
5599 role="bold">ls</emphasis> command.</para>
5601 <para>Change directory to <emphasis role="bold">/usr/afs/bin</emphasis> to make it easier to access the command
5605 # <emphasis role="bold">cd /usr/afs/bin</emphasis>
5606 # <emphasis role="bold">./fs mkmount /afs/.</emphasis><replaceable>cellname</replaceable> <emphasis role="bold">root.cell -rw</emphasis>
5610 <primary>commands</primary>
5612 <secondary>vos addsite</secondary>
5616 <primary>vos commands</primary>
5618 <secondary>addsite</secondary>
5622 <primary>volume</primary>
5624 <secondary>defining replication site</secondary>
5628 <primary>defining</primary>
5630 <secondary>replication site for volume</secondary>
5634 <listitem id="LIWQ82">
5635 <para>Issue the <emphasis role="bold">vos addsite</emphasis> command to define a replication site
5636 for both the <emphasis role="bold">root.afs</emphasis> and <emphasis role="bold">root.cell</emphasis> volumes. In each
5637 case, substitute for the <replaceable>partition name</replaceable> argument the partition where the volume's read/write
5638 version resides. When you install additional file server machines, it is a good idea to create replication sites on them
5639 as well. <programlisting>
5640 # <emphasis role="bold">./vos addsite</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>partition name</replaceable>> <emphasis
5641 role="bold">root.afs</emphasis>
5642 # <emphasis role="bold">./vos addsite</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>partition name</replaceable>> <emphasis
5643 role="bold">root.cell</emphasis>
5644 </programlisting> <indexterm>
5645 <primary>fs commands</primary>
5647 <secondary>examine</secondary>
5648 </indexterm> <indexterm>
5649 <primary>commands</primary>
5651 <secondary>fs examine</secondary>
5656 <para>Issue the <emphasis role="bold">fs examine</emphasis> command to verify that the Cache Manager can access both the
5657 <emphasis role="bold">root.afs</emphasis> and <emphasis role="bold">root.cell</emphasis> volumes, before you attempt to
5658 replicate them. The output lists each volume's name, volumeID number, quota, size, and the size of the partition that
5659 houses them. If you get an error message instead, do not continue before taking corrective action. <programlisting>
5660 # <emphasis role="bold">./fs examine /afs</emphasis>
5661 # <emphasis role="bold">./fs examine /afs/</emphasis><replaceable>cellname</replaceable>
5662 </programlisting> <indexterm>
5663 <primary>commands</primary>
5665 <secondary>vos release</secondary>
5666 </indexterm> <indexterm>
5667 <primary>vos commands</primary>
5669 <secondary>release</secondary>
5670 </indexterm> <indexterm>
5671 <primary>volume</primary>
5673 <secondary>releasing replicated</secondary>
5674 </indexterm> <indexterm>
5675 <primary>releasing replicated volume</primary>
5680 <para>Issue the <emphasis role="bold">vos release</emphasis> command to release a replica of the <emphasis
5681 role="bold">root.afs</emphasis> and <emphasis role="bold">root.cell</emphasis> volumes to the sites you defined in Step
5682 <link linkend="LIWQ82">5</link>. <programlisting>
5683 # <emphasis role="bold">./vos release root.afs</emphasis>
5684 # <emphasis role="bold">./vos release root.cell</emphasis>
5685 </programlisting> <indexterm>
5686 <primary>fs commands</primary>
5688 <secondary>checkvolumes</secondary>
5689 </indexterm> <indexterm>
5690 <primary>commands</primary>
5692 <secondary>fs checkvolumes</secondary>
5697 <para>Issue the <emphasis role="bold">fs checkvolumes</emphasis> to force the Cache Manager to notice that you have
5698 released read-only versions of the volumes, then issue the <emphasis role="bold">fs examine</emphasis> command again. This
5699 time its output mentions the read-only version of the volumes (<emphasis role="bold">root.afs.readonly</emphasis> and
5700 <emphasis role="bold">root.cell.readonly</emphasis>) instead of the read/write versions, because of the Cache Manager's
5701 bias to access the read-only version of the <emphasis role="bold">root.afs</emphasis> volume if it exists.
5703 # <emphasis role="bold">./fs checkvolumes</emphasis>
5704 # <emphasis role="bold">./fs examine /afs</emphasis>
5705 # <emphasis role="bold">./fs examine /afs/</emphasis><replaceable>cellname</replaceable>
5706 </programlisting></para>
5708 </orderedlist></para>
5711 <primary>storing</primary>
5713 <secondary>AFS binaries in volumes</secondary>
5717 <primary>creating</primary>
5719 <secondary>volume</secondary>
5721 <tertiary>for AFS binaries</tertiary>
5725 <primary>volume</primary>
5727 <secondary>for AFS binaries</secondary>
5731 <primary>binaries</primary>
5733 <secondary>storing AFS in volume</secondary>
5737 <primary>usr/afsws directory</primary>
5741 <primary>directories</primary>
5743 <secondary>/usr/afsws</secondary>
5747 <sect1 id="HDRWQ83">
5748 <title>Storing AFS Binaries in AFS</title>
5750 <note><para>Sites with existing binary distribution mechanisms, including
5751 those which use packaging systems such as RPM, may wish to skip this step,
5752 and use tools native to their operating system to manage AFS configuration
5753 information.</para></note>
5755 <para>In the conventional configuration, you make AFS client binaries and configuration files available in the subdirectories of
5756 the <emphasis role="bold">/usr/afsws</emphasis> directory on client machines (<emphasis role="bold">afsws</emphasis> is an
5757 acronym for <emphasis role="bold">AFS w</emphasis><emphasis>ork</emphasis><emphasis
5758 role="bold">s</emphasis><emphasis>tation</emphasis>). You can conserve local disk space by creating <emphasis
5759 role="bold">/usr/afsws</emphasis> as a link to an AFS volume that houses the AFS client binaries and configuration files for
5760 this system type.</para>
5762 <para>In this section you create the necessary volumes. The conventional location to which to link <emphasis
5763 role="bold">/usr/afsws</emphasis> is <emphasis role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
5764 role="bold">/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/usr/afsws</emphasis>, where
5765 <replaceable>sysname</replaceable> is the appropriate system type name as specified in the <emphasis>OpenAFS Release
5766 Notes</emphasis>. The instructions in <link linkend="HDRWQ133">Installing Additional Client Machines</link> assume that you have
5767 followed the instructions in this section.</para>
5769 <para>If you have previously run AFS in the cell, the volumes possibly already exist. If so, you need to perform Step <link
5770 linkend="LIWQ86">8</link> only.</para>
5772 <para>The current working directory is still <emphasis role="bold">/usr/afs/bin</emphasis>, which houses the <emphasis
5773 role="bold">fs</emphasis> and <emphasis role="bold">vos</emphasis> command suite binaries. In the following commands, it is
5774 possible you still need to specify the pathname to the commands, depending on how your PATH environment variable is set.
5777 <primary>commands</primary>
5779 <secondary>vos create</secondary>
5781 <tertiary>volume for AFS binaries</tertiary>
5785 <primary>vos commands</primary>
5787 <secondary>create</secondary>
5789 <tertiary>volume for AFS binaries</tertiary>
5792 <listitem id="LIWQ84">
5793 <para>Issue the <emphasis role="bold">vos create</emphasis> command to create volumes for storing
5794 the AFS client binaries for this system type. The following example instruction creates volumes called
5795 <replaceable>sysname</replaceable>, <replaceable>sysname</replaceable>.<emphasis role="bold">usr</emphasis>, and
5796 <replaceable>sysname</replaceable>.<emphasis role="bold">usr.afsws</emphasis>. Refer to the <emphasis>OpenAFS Release
5797 Notes</emphasis> to learn the proper value of <replaceable>sysname</replaceable> for this system type. <programlisting>
5798 # <emphasis role="bold">vos create</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>partition name</replaceable>> <replaceable>sysname</replaceable>
5799 # <emphasis role="bold">vos create</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>partition name</replaceable>> <replaceable>sysname</replaceable><emphasis
5800 role="bold">.usr</emphasis>
5801 # <emphasis role="bold">vos create</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>partition name</replaceable>> <replaceable>sysname</replaceable><emphasis
5802 role="bold">.usr.afsws</emphasis>
5803 </programlisting></para>
5807 <para>Issue the <emphasis role="bold">fs mkmount</emphasis> command to mount the newly created volumes. Because the
5808 <emphasis role="bold">root.cell</emphasis> volume is replicated, you must precede the <emphasis>cellname</emphasis> part
5809 of the pathname with a period to specify the read/write mount point, as shown. Then issue the <emphasis role="bold">vos
5810 release</emphasis> command to release a new replica of the <emphasis role="bold">root.cell</emphasis> volume, and the
5811 <emphasis role="bold">fs checkvolumes</emphasis> command to force the local Cache Manager to access them. <programlisting>
5812 # <emphasis role="bold">fs mkmount -dir /afs/.</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/</emphasis><replaceable>sysname</replaceable> <emphasis
5813 role="bold">-vol</emphasis> <replaceable>sysname</replaceable>
5814 # <emphasis role="bold">fs mkmount -dir /afs/.</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/</emphasis><replaceable>sysname</replaceable><emphasis
5815 role="bold">/usr</emphasis> <emphasis role="bold">-vol</emphasis> <replaceable>sysname</replaceable><emphasis
5816 role="bold">.usr</emphasis>
5817 # <emphasis role="bold">fs mkmount -dir /afs/.</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/</emphasis><replaceable>sysname</replaceable><emphasis
5818 role="bold">/usr/afsws</emphasis> <emphasis role="bold">-vol</emphasis> <replaceable>sysname</replaceable><emphasis
5819 role="bold">.usr.afsws</emphasis>
5820 # <emphasis role="bold">vos release root.cell</emphasis>
5821 # <emphasis role="bold">fs checkvolumes</emphasis>
5822 </programlisting></para>
5826 <para>Issue the <emphasis role="bold">fs setacl</emphasis> command to grant the <emphasis role="bold">l</emphasis>
5827 (<emphasis role="bold">lookup</emphasis>) and <emphasis role="bold">r</emphasis> (<emphasis role="bold">read</emphasis>)
5828 permissions to the <emphasis role="bold">system:anyuser</emphasis> group on each new directory's ACL. <programlisting>
5829 # <emphasis role="bold">cd /afs/.</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/</emphasis><replaceable>sysname</replaceable>
5830 # <emphasis role="bold">fs setacl -dir . usr usr/afsws -acl system:anyuser rl</emphasis>
5831 </programlisting> <indexterm>
5832 <primary>commands</primary>
5834 <secondary>fs setquota</secondary>
5835 </indexterm> <indexterm>
5836 <primary>fs commands</primary>
5838 <secondary>setquota</secondary>
5839 </indexterm> <indexterm>
5840 <primary>quota for volume</primary>
5841 </indexterm> <indexterm>
5842 <primary>volume</primary>
5844 <secondary>setting quota</secondary>
5845 </indexterm> <indexterm>
5846 <primary>setting</primary>
5848 <secondary>volume quota</secondary>
5852 <listitem id="LIWQ85">
5853 <para>Issue the <emphasis role="bold">fs setquota</emphasis> command to set an unlimited quota on
5854 the volume mounted at the <emphasis role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
5855 role="bold">/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/usr/afsws</emphasis> directory. This
5856 enables you to copy all of the appropriate files from the CD-ROM into the volume without exceeding the volume's
5859 <para>If you wish, you can set the volume's quota to a finite value after you complete the copying operation. At that
5860 point, use the <emphasis role="bold">vos examine</emphasis> command to determine how much space the volume is occupying.
5861 Then issue the <emphasis role="bold">fs setquota</emphasis> command to set a quota that is slightly larger.</para>
5864 # <emphasis role="bold">fs setquota /afs/.</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/</emphasis><replaceable>sysname</replaceable><emphasis
5865 role="bold">/usr/afsws 0</emphasis>
5870 <para>Unpack the distribution tarball into the <emphasis role="bold">/tmp/afsdist</emphasis> directory,
5871 if it is not already. <indexterm>
5872 <primary>copying</primary>
5874 <secondary>AFS binaries into volume</secondary>
5875 </indexterm> <indexterm>
5876 <primary>CD-ROM</primary>
5878 <secondary>copying AFS binaries into volume</secondary>
5879 </indexterm> <indexterm>
5880 <primary>first AFS machine</primary>
5882 <secondary>copying</secondary>
5884 <tertiary>AFS binaries into volume</tertiary>
5889 <para>Copy the contents of the indicated directories from the
5890 distribution into the <emphasis
5891 role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
5892 role="bold">/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/usr/afsws</emphasis> directory.
5894 # <emphasis role="bold">cd /afs/.</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/</emphasis><replaceable>sysname</replaceable><emphasis
5895 role="bold">/usr/afsws</emphasis>
5896 # <emphasis role="bold">cp -rp /tmp/afsdist/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/bin .</emphasis>
5897 # <emphasis role="bold">cp -rp /tmp/afsdist/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/etc .</emphasis>
5898 # <emphasis role="bold">cp -rp /tmp/afsdist/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/include .</emphasis>
5899 # <emphasis role="bold">cp -rp /tmp/afsdist/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/lib .</emphasis>
5902 <primary>creating</primary>
5904 <secondary>symbolic link</secondary>
5906 <tertiary>to AFS binaries</tertiary>
5907 </indexterm> <indexterm>
5908 <primary>symbolic link</primary>
5910 <secondary>to AFS binaries from local disk</secondary>
5914 <listitem id="LIWQ86">
5915 <para>Create <emphasis role="bold">/usr/afsws</emphasis> on the local disk as a symbolic link to the
5916 directory <emphasis role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
5917 role="bold">/@sys/usr/afsws</emphasis>. You can specify the actual system name instead of <emphasis
5918 role="bold">@sys</emphasis> if you wish, but the advantage of using <emphasis role="bold">@sys</emphasis> is that it
5919 remains valid if you upgrade this machine to a different system type. <programlisting>
5920 # <emphasis role="bold">ln -s /afs/</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/@sys/usr/afsws /usr/afsws</emphasis>
5921 </programlisting> <indexterm>
5922 <primary>PATH environment variable for users</primary>
5923 </indexterm> <indexterm>
5924 <primary>variables</primary>
5926 <secondary>PATH, setting for users</secondary>
5931 <para><emphasis role="bold">(Optional)</emphasis> To enable users to issue commands from the AFS suites (such as <emphasis
5932 role="bold">fs</emphasis>) without having to specify a pathname to their binaries, include the <emphasis
5933 role="bold">/usr/afsws/bin</emphasis> and <emphasis role="bold">/usr/afsws/etc</emphasis> directories in the PATH
5934 environment variable you define in each user's shell initialization file (such as <emphasis
5935 role="bold">.cshrc</emphasis>).</para>
5937 </orderedlist></para>
5940 <primary>storing</primary>
5942 <secondary>AFS documentation in volumes</secondary>
5946 <primary>creating</primary>
5948 <secondary>volume</secondary>
5950 <tertiary>for AFS documentation</tertiary>
5954 <primary>volume</primary>
5956 <secondary>for AFS documentation</secondary>
5960 <primary>documentation, creating volume for AFS</primary>
5964 <primary>usr/afsdoc directory</primary>
5968 <primary>directories</primary>
5970 <secondary>/usr/afsdoc</secondary>
5974 <sect1 id="HDRWQ87">
5975 <title>Storing AFS Documents in AFS</title>
5977 <para>The AFS distribution includes the following documents: <itemizedlist>
5979 <para><emphasis>OpenAFS Release Notes</emphasis></para>
5983 <para><emphasis>OpenAFS Quick Beginnings</emphasis></para>
5987 <para><emphasis>OpenAFS User Guide</emphasis></para>
5991 <para><emphasis>OpenAFS Administration Reference</emphasis></para>
5995 <para><emphasis>OpenAFS Administration Guide</emphasis></para>
5997 </itemizedlist></para>
5999 <note><para>OpenAFS Documentation is not currently provided with all
6000 distributions, but may be downloaded separately from the OpenAFS
6001 website</para></note>
6003 <para>The OpenAFS Documentation Distribution has a directory for each
6004 document format provided. The different formats are suitable for online
6005 viewing, printing, or both.</para>
6007 <para>This section explains how to create and mount a volume to house the documents, making them available to your users. The
6008 recommended mount point for the volume is <emphasis role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
6009 role="bold">/afsdoc</emphasis>. If you wish, you can create a link to the mount point on each client machine's local disk,
6010 called <emphasis role="bold">/usr/afsdoc</emphasis>. Alternatively, you can create a link to the mount point in each user's home
6011 directory. You can also choose to permit users to access only certain documents (most probably, the <emphasis>OpenAFS User
6012 Guide</emphasis>) by creating different mount points or setting different ACLs on different document directories.</para>
6014 <para>The current working directory is still <emphasis role="bold">/usr/afs/bin</emphasis>, which houses the <emphasis
6015 role="bold">fs</emphasis> and <emphasis role="bold">vos</emphasis> command suite binaries you use to create and mount volumes.
6016 In the following commands, it is possible you still need to specify the pathname to the commands, depending on how your PATH
6017 environment variable is set. <orderedlist>
6019 <primary>commands</primary>
6021 <secondary>vos create</secondary>
6023 <tertiary>volume for AFS documentation</tertiary>
6027 <primary>vos commands</primary>
6029 <secondary>create</secondary>
6031 <tertiary>volume for AFS documentation</tertiary>
6035 <para>Issue the <emphasis role="bold">vos create</emphasis> command to create a volume for storing the AFS documentation.
6036 Include the <emphasis role="bold">-maxquota</emphasis> argument to set an unlimited quota on the volume. This enables you
6037 to copy all of the appropriate files from the CD-ROM into the volume without exceeding the volume's quota.</para>
6039 <para>If you wish, you can set the volume's quota to a finite value after you complete the copying operations. At that
6040 point, use the <emphasis role="bold">vos examine</emphasis> command to determine how much space the volume is occupying.
6041 Then issue the <emphasis role="bold">fs setquota</emphasis> command to set a quota that is slightly larger.</para>
6044 # <emphasis role="bold">vos create</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>partition name</replaceable>> <emphasis
6045 role="bold">afsdoc -maxquota 0</emphasis>
6050 <para>Issue the <emphasis role="bold">fs mkmount</emphasis> command to mount the new volume. Because the <emphasis
6051 role="bold">root.cell</emphasis> volume is replicated, you must precede the <emphasis>cellname</emphasis> with a period to
6052 specify the read/write mount point, as shown. Then issue the <emphasis role="bold">vos release</emphasis> command to
6053 release a new replica of the <emphasis role="bold">root.cell</emphasis> volume, and the <emphasis role="bold">fs
6054 checkvolumes</emphasis> command to force the local Cache Manager to access them. <programlisting>
6055 # <emphasis role="bold">fs mkmount -dir /afs/.</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/afsdoc</emphasis> <emphasis
6056 role="bold">-vol</emphasis> <emphasis role="bold">afsdoc</emphasis>
6057 # <emphasis role="bold">vos release root.cell</emphasis>
6058 # <emphasis role="bold">fs checkvolumes</emphasis>
6059 </programlisting></para>
6063 <para>Issue the <emphasis role="bold">fs setacl</emphasis> command to grant the <emphasis role="bold">rl</emphasis>
6064 permissions to the <emphasis role="bold">system:anyuser</emphasis> group on the new directory's ACL. <programlisting>
6065 # <emphasis role="bold">cd /afs/.</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/afsdoc</emphasis>
6066 # <emphasis role="bold">fs setacl . system:anyuser rl</emphasis>
6067 </programlisting></para>
6071 <para>Unpack the OpenAFS documentation distribution into the
6072 <emphasis role="bold">/tmp/afsdocs</emphasis> directory. You may use
6073 a different directory, in which case the location you use should be
6074 subsituted in the following examples. For instructions on unpacking
6075 the distribution, consult the documentation for your operating
6076 system's <emphasis role="bold">tar</emphasis> command.
6078 <primary>copying</primary>
6080 <secondary>AFS documentation from distribution</secondary>
6081 </indexterm> <indexterm>
6082 <primary>OpenAFS Distribution</primary>
6084 <secondary>copying AFS documentation from</secondary>
6085 </indexterm> <indexterm>
6086 <primary>first AFS machine</primary>
6088 <secondary>copying</secondary>
6090 <tertiary>AFS documentation from OpenAFS distribution</tertiary>
6091 </indexterm> <indexterm>
6092 <primary>index.htm file</primary>
6093 </indexterm> <indexterm>
6094 <primary>files</primary>
6096 <secondary>index.htm</secondary>
6101 <para>Copy the AFS documents in one or more formats from the unpacked distribution into subdirectories of the <emphasis
6102 role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/afsdoc</emphasis> directory. Repeat
6103 the commands for each format. <programlisting>
6104 # <emphasis role="bold">mkdir</emphasis> <replaceable>format_name</replaceable>
6105 # <emphasis role="bold">cd</emphasis> <replaceable>format_name</replaceable>
6106 # <emphasis role="bold">cp -rp /tmp/afsdocs/</emphasis><replaceable>format</replaceable> <emphasis role="bold">.</emphasis>
6107 </programlisting></para>
6109 <para>If you choose to store the HTML version of the documents in AFS, note that in addition to a subdirectory for each
6110 document there are several files with a <emphasis role="bold">.gif</emphasis> extension, which enable readers to move
6111 easily between sections of a document. The file called <emphasis role="bold">index.htm</emphasis> is an introductory HTML
6112 page that contains a hyperlink to each of the documents. For online viewing to work properly, these files must remain in
6113 the top-level HTML directory (the one named, for example, <emphasis
6114 role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/afsdoc/html</emphasis>).</para>
6118 <para><emphasis role="bold">(Optional)</emphasis> If you believe it is helpful to your users to access the AFS documents
6119 in a certain format via a local disk directory, create <emphasis role="bold">/usr/afsdoc</emphasis> on the local disk as a
6120 symbolic link to the documentation directory in AFS (<emphasis
6121 role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
6122 role="bold">/afsdoc/</emphasis><replaceable>format_name</replaceable>). <programlisting>
6123 # <emphasis role="bold">ln -s /afs/</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/afsdoc/</emphasis><replaceable>format_name</replaceable> <emphasis
6124 role="bold">/usr/afsdoc</emphasis>
6125 </programlisting></para>
6127 <para>An alternative is to create a link in each user's home directory to the <emphasis
6128 role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
6129 role="bold">/afsdoc/</emphasis><replaceable>format_name</replaceable> directory.</para>
6131 </orderedlist></para>
6134 <primary>storing</primary>
6136 <secondary>system binaries in volumes</secondary>
6140 <primary>creating</primary>
6142 <secondary>volume</secondary>
6144 <tertiary>for system binaries</tertiary>
6148 <primary>volume</primary>
6150 <secondary>for system binaries</secondary>
6154 <primary>binaries</primary>
6156 <secondary>storing system in volumes</secondary>
6160 <sect1 id="HDRWQ88">
6161 <title>Storing System Binaries in AFS</title>
6163 <para>You can also choose to store other system binaries in AFS volumes, such as the standard UNIX programs conventionally
6164 located in local disk directories such as <emphasis role="bold">/etc</emphasis>, <emphasis role="bold">/bin</emphasis>, and
6165 <emphasis role="bold">/lib</emphasis>. Storing such binaries in an AFS volume not only frees local disk space, but makes it
6166 easier to update binaries on all client machines.</para>
6168 <para>The following is a suggested scheme for storing system binaries in AFS. It does not include instructions, but you can use
6169 the instructions in <link linkend="HDRWQ83">Storing AFS Binaries in AFS</link> (which are for AFS-specific binaries) as a
6172 <para>Some files must remain on the local disk for use when AFS is inaccessible (during bootup and file server or network
6173 outages). The required binaries include the following: <itemizedlist>
6175 <para>A text editor, network commands, and so on</para>
6179 <para>Files used during the boot sequence before the <emphasis role="bold">afsd</emphasis> program runs, such as
6180 initialization and configuration files, and binaries for commands that mount file systems</para>
6184 <para>Files used by dynamic kernel loader programs</para>
6186 </itemizedlist></para>
6188 <para>In most cases, it is more secure to enable only locally authenticated users to access system binaries, by granting the
6189 <emphasis role="bold">l</emphasis> (<emphasis role="bold">lookup</emphasis>) and <emphasis role="bold">r</emphasis> (<emphasis
6190 role="bold">read</emphasis>) permissions to the <emphasis role="bold">system:authuser</emphasis> group on the ACLs of
6191 directories that contain the binaries. If users need to access a binary while unauthenticated, however, the ACL on its directory
6192 must grant those permissions to the <emphasis role="bold">system:anyuser</emphasis> group.</para>
6194 <para>The following chart summarizes the suggested volume and mount point names for storing system binaries. It uses a separate
6195 volume for each directory. You already created a volume called <replaceable>sysname</replaceable> for this machine's system type
6196 when you followed the instructions in <link linkend="HDRWQ83">Storing AFS Binaries in AFS</link>.</para>
6198 <para>You can name volumes in any way you wish, and mount them at other locations than those suggested here. However, this
6199 scheme has several advantages: <itemizedlist>
6201 <para>Volume names clearly identify volume contents</para>
6205 <para>Using the <replaceable>sysname</replaceable> prefix on every volume makes it is easy to back up all of the volumes
6206 together, because the AFS Backup System enables you to define sets of volumes based on a string included in all of their
6211 <para>It makes it easy to track related volumes, keeping them together on the same file server machine if desired</para>
6215 <para>There is a clear relationship between volume name and mount point name</para>
6217 </itemizedlist></para>
6219 <informaltable frame="none">
6221 <colspec colwidth="50*" />
6223 <colspec colwidth="50*" />
6227 <entry><emphasis role="bold">Volume Name</emphasis></entry>
6229 <entry><emphasis role="bold">Mount Point</emphasis></entry>
6235 <entry><replaceable>sysname</replaceable></entry>
6238 role="bold">/afs/</emphasis><replaceable>cellname</replaceable>/<replaceable>sysname</replaceable></entry>
6242 <entry><replaceable>sysname</replaceable>.<emphasis role="bold">bin</emphasis></entry>
6245 role="bold">/afs/</emphasis><replaceable>cellname</replaceable>/<replaceable>sysname</replaceable><emphasis
6246 role="bold">/bin</emphasis></entry>
6250 <entry><replaceable>sysname</replaceable>.<emphasis role="bold">etc</emphasis></entry>
6253 role="bold">/afs/</emphasis><replaceable>cellname</replaceable>/<replaceable>sysname</replaceable><emphasis
6254 role="bold">/etc</emphasis></entry>
6258 <entry><replaceable>sysname</replaceable>.<emphasis role="bold">usr</emphasis></entry>
6261 role="bold">/afs/</emphasis><replaceable>cellname</replaceable>/<replaceable>sysname</replaceable><emphasis
6262 role="bold">/usr</emphasis></entry>
6266 <entry><replaceable>sysname</replaceable>.<emphasis role="bold">usr.afsws</emphasis></entry>
6269 role="bold">/afs/</emphasis><replaceable>cellname</replaceable>/<replaceable>sysname</replaceable><emphasis
6270 role="bold">/usr/afsws</emphasis></entry>
6274 <entry><replaceable>sysname</replaceable>.<emphasis role="bold">usr.bin</emphasis></entry>
6277 role="bold">/afs/</emphasis><replaceable>cellname</replaceable>/<replaceable>sysname</replaceable><emphasis
6278 role="bold">/usr/bin</emphasis></entry>
6282 <entry><replaceable>sysname</replaceable>.<emphasis role="bold">usr.etc</emphasis></entry>
6285 role="bold">/afs/</emphasis><replaceable>cellname</replaceable>/<replaceable>sysname</replaceable><emphasis
6286 role="bold">/usr/etc</emphasis></entry>
6290 <entry><replaceable>sysname</replaceable>.<emphasis role="bold">usr.inc</emphasis></entry>
6293 role="bold">/afs/</emphasis><replaceable>cellname</replaceable>/<replaceable>sysname</replaceable><emphasis
6294 role="bold">/usr/include</emphasis></entry>
6298 <entry><replaceable>sysname</replaceable>.<emphasis role="bold">usr.lib</emphasis></entry>
6301 role="bold">/afs/</emphasis><replaceable>cellname</replaceable>/<replaceable>sysname</replaceable><emphasis
6302 role="bold">/usr/lib</emphasis></entry>
6306 <entry><replaceable>sysname</replaceable>.<emphasis role="bold">usr.loc</emphasis></entry>
6309 role="bold">/afs/</emphasis><replaceable>cellname</replaceable>/<replaceable>sysname</replaceable><emphasis
6310 role="bold">/usr/local</emphasis></entry>
6314 <entry><replaceable>sysname</replaceable>.<emphasis role="bold">usr.man</emphasis></entry>
6317 role="bold">/afs/</emphasis><replaceable>cellname</replaceable>/<replaceable>sysname</replaceable><emphasis
6318 role="bold">/usr/man</emphasis></entry>
6322 <entry><replaceable>sysname</replaceable>.<emphasis role="bold">usr.sys</emphasis></entry>
6325 role="bold">/afs/</emphasis><replaceable>cellname</replaceable>/<replaceable>sysname</replaceable><emphasis
6326 role="bold">/usr/sys</emphasis></entry>
6333 <primary>foreign cell, enabling access</primary>
6337 <primary>cell</primary>
6339 <secondary>enabling access to foreign</secondary>
6343 <primary>access</primary>
6345 <secondary>to local and foreign cells</secondary>
6349 <primary>AFS filespace</primary>
6351 <secondary>enabling access to foreign cells</secondary>
6355 <primary>root.cell volume</primary>
6357 <secondary>mounting for foreign cells in local filespace</secondary>
6361 <primary>database server machine</primary>
6363 <secondary>entry in client CellServDB file</secondary>
6365 <tertiary>for foreign cell</tertiary>
6369 <primary>CellServDB file (client)</primary>
6371 <secondary>adding entry</secondary>
6373 <tertiary>for foreign cell</tertiary>
6377 <sect1 id="HDRWQ91">
6378 <title>Enabling Access to Foreign Cells</title>
6380 <para>With current OpenAFS releases, there exist a number of mechanisms for
6381 providing access to foreign cells. You may add mount points in your AFS
6382 filespace for each foreign cell you wish users to access, or you can
6383 enable a 'synthetic' AFS root, which contains mountpoints for either all
6384 AFS cells defined in the client machine's local
6385 <emphasis role="bold">/usr/vice/etc/CellServDB</emphasis>, or for all cells
6386 providing location information in the DNS.
6390 <title>Enabling a Synthetic AFS root</title>
6392 <para>When a synthetic root is enabled, the client cache machine creates its
6393 own root.afs volume, rather than using the one provided with your cell. This
6394 allows clients to access all cells in the
6395 <emphasis role="bold">CellServDB</emphasis> file and, optionally, all cells
6396 registered in the DNS, without requiring system administrator action to
6397 enable this access. Using a synthetic root has the additional advantage that
6398 it allows a client to start its AFS service without a network available, as
6399 it is no longer necessary to contact a fileserver to obtain the root volume.
6402 <para>OpenAFS supports two complimentary mechanisms for creating the
6403 synthetic root. Starting the cache manager with the
6404 <emphasis role="bold">-dynroot</emphasis> option adds all cells listed
6405 in <emphasis role="bold">/usr/vice/etc/CellServDB</emphasis> to the client's
6406 AFS root. Adding the <emphasis role="bold">-afsdb</emphasis> option in
6407 addition to this enables DNS lookups for any cells that are not found in
6408 the client's CellServDB file. Both of these options are added to the AFS
6409 initialisation script, or options file, as detailed in
6410 <link linkend="HDRWQ70">Configuring the Cache Manager</link>.</para>
6413 <title>Adding foreign cells to a conventional root volume</title>
6415 <para>In this section you create a mount point in your AFS filespace for the <emphasis role="bold">root.cell</emphasis> volume
6416 of each foreign cell that you want to enable your users to access. For users working on a client machine to access the cell,
6417 there must in addition be an entry for it in the client machine's local <emphasis
6418 role="bold">/usr/vice/etc/CellServDB</emphasis> file. (The instructions in <link linkend="HDRWQ66">Creating the Client
6419 CellServDB File</link> suggest that you use the <emphasis role="bold">CellServDB.sample</emphasis> file included in the AFS
6420 distribution as the basis for your cell's client <emphasis role="bold">CellServDB</emphasis> file. The sample file lists all of
6421 the cells that had agreed to participate in the AFS global namespace at the time your AFS CD-ROM was created. As mentioned in
6422 that section, the AFS Product Support group also maintains a copy of the file, updating it as necessary.)</para>
6424 <para>The chapter in the <emphasis>OpenAFS Administration Guide</emphasis> about cell administration and configuration issues
6425 discusses the implications of participating in the global AFS namespace. The chapter about administering client machines
6426 explains how to maintain knowledge of foreign cells on client machines, and includes suggestions for maintaining a central
6427 version of the file in AFS. <orderedlist>
6429 <para>Issue the <emphasis role="bold">fs mkmount</emphasis> command to mount each foreign cell's <emphasis
6430 role="bold">root.cell</emphasis> volume on a directory called <emphasis
6431 role="bold">/afs/</emphasis><replaceable>foreign_cell</replaceable>. Because the <emphasis role="bold">root.afs</emphasis>
6432 volume is replicated, you must create a temporary mount point for its read/write version in a directory to which you have
6433 write access (such as your cell's <emphasis role="bold">/afs/.</emphasis><replaceable>cellname</replaceable> directory).
6434 Create the mount points, issue the <emphasis role="bold">vos release</emphasis> command to release new replicas to the
6435 read-only sites for the <emphasis role="bold">root.afs</emphasis> volume, and issue the <emphasis role="bold">fs
6436 checkvolumes</emphasis> command to force the local Cache Manager to access the new replica.</para>
6439 <para>You need to issue the <emphasis role="bold">fs mkmount</emphasis> command only once for each foreign cell's
6440 <emphasis role="bold">root.cell</emphasis> volume. You do not need to repeat the command on each client machine.</para>
6443 <para>Substitute your cell's name for <replaceable>cellname</replaceable>.</para>
6446 # <emphasis role="bold">cd /afs/.</emphasis><replaceable>cellname</replaceable>
6447 # <emphasis role="bold">/usr/afs/bin/fs mkmount temp root.afs</emphasis>
6450 <para>Repeat the <emphasis role="bold">fs mkmount</emphasis> command for each foreign cell you wish to mount at this
6454 # <emphasis role="bold">/usr/afs/bin/fs mkmount temp/</emphasis><replaceable>foreign_cell</replaceable> <emphasis role="bold">root.cell -c</emphasis> <replaceable>foreign_cell</replaceable>
6457 <para>Issue the following commands only once.</para>
6460 # <emphasis role="bold">/usr/afs/bin/fs rmmount temp</emphasis>
6461 # <emphasis role="bold">/usr/afs/bin/vos release root.afs</emphasis>
6462 # <emphasis role="bold">/usr/afs/bin/fs checkvolumes</emphasis>
6466 <primary>fs commands</primary>
6468 <secondary>newcell</secondary>
6472 <primary>commands</primary>
6474 <secondary>fs newcell</secondary>
6478 <listitem id="LIWQ92">
6479 <para>If this machine is going to remain an AFS client after you complete the installation, verify
6480 that the local <emphasis role="bold">/usr/vice/etc/CellServDB</emphasis> file includes an entry for each foreign
6483 <para>For each cell that does not already have an entry, complete the following instructions: <orderedlist>
6485 <para>Create an entry in the <emphasis role="bold">CellServDB</emphasis> file. Be sure to comply with the formatting
6486 instructions in <link linkend="HDRWQ66">Creating the Client CellServDB File</link>.</para>
6490 <para>Issue the <emphasis role="bold">fs newcell</emphasis> command to add an entry for the cell directly to the
6491 list that the Cache Manager maintains in kernel memory. Provide each database server machine's fully qualified
6492 hostname. <programlisting>
6493 # <emphasis role="bold">/usr/afs/bin/fs newcell</emphasis> <<replaceable>foreign_cell</replaceable>> <<replaceable>dbserver1></replaceable> \
6494 [<<replaceable>dbserver2></replaceable>] [<<replaceable>dbserver3></replaceable>]
6495 </programlisting></para>
6499 <para>If you plan to maintain a central version of the <emphasis role="bold">CellServDB</emphasis> file (the
6500 conventional location is <emphasis role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
6501 role="bold">/common/etc/CellServDB</emphasis>), create it now as a copy of the local <emphasis
6502 role="bold">/usr/vice/etc/CellServDB</emphasis> file. Verify that it includes an entry for each foreign cell you
6503 want your users to be able to access. <programlisting>
6504 # <emphasis role="bold">mkdir common</emphasis>
6505 # <emphasis role="bold">mkdir common/etc</emphasis>
6506 # <emphasis role="bold">cp /usr/vice/etc/CellServDB common/etc</emphasis>
6507 # <emphasis role="bold">/usr/afs/bin/vos release root.cell</emphasis>
6508 </programlisting></para>
6510 </orderedlist></para>
6514 <para>Issue the <emphasis role="bold">ls</emphasis> command to verify that the new cell's mount point is visible in your
6515 filespace. The output lists the directories at the top level of the new cell's AFS filespace. <programlisting>
6516 # <emphasis role="bold">ls /afs/</emphasis><replaceable>foreign_cell</replaceable>
6517 </programlisting></para>
6521 <para>If you wish to participate in the global AFS namespace, and only
6522 intend running one database server, please
6523 register your cell with grand.central.org at this time.
6524 To do so, email the <emphasis role="bold">CellServDB</emphasis> fragment
6525 describing your cell, together with a contact name and email address
6526 for any queries, to cellservdb@grand.central.org. If you intend
6527 on deploying multiple database servers, please wait until you have
6528 installed all of them before registering your cell.</para>
6531 <para>If you wish to allow your cell to be located through DNS lookups,
6532 at this time you should also add the necessary configuration to your
6535 <para>AFS database servers may be located by creating AFSDB records
6536 in the DNS for the domain name corresponding to the name of your cell.
6537 It's outside the scope of this guide to give an indepth description of
6538 managing, or configuring, your site's DNS. You should consult the
6539 documentation for your DNS server for further details on AFSDB
6542 </orderedlist></para>
6546 <sect1 id="HDRWQ93">
6547 <title>Improving Cell Security</title>
6550 <primary>cell</primary>
6552 <secondary>improving security</secondary>
6556 <primary>security</primary>
6558 <secondary>improving</secondary>
6562 <primary>root superuser</primary>
6564 <secondary>controlling access</secondary>
6568 <primary>access</primary>
6570 <secondary>to root and admin accounts</secondary>
6574 <primary>admin account</primary>
6576 <secondary>controlling access to</secondary>
6580 <primary>AFS filespace</primary>
6582 <secondary>controlling access by root superuser</secondary>
6585 <para>This section discusses ways to improve the security of AFS data
6586 in your cell. Also see the chapter in the <emphasis>OpenAFS
6587 Administration Guide</emphasis> about configuration and administration
6590 <sect2 id="HDRWQ94">
6591 <title>Controlling root Access</title>
6593 <para>As on any machine, it is important to prevent unauthorized users from logging onto an AFS server or client machine as
6594 the local superuser <emphasis role="bold">root</emphasis>. Take care to keep the <emphasis role="bold">root</emphasis>
6595 password secret.</para>
6597 <para>The local <emphasis role="bold">root</emphasis> superuser does not have special access to AFS data through the Cache
6598 Manager (as members of the <emphasis role="bold">system:administrators</emphasis> group do), but it does have the following
6599 privileges: <itemizedlist>
6601 <para>On client machines, the ability to issue commands from the <emphasis role="bold">fs</emphasis> suite that affect
6602 AFS performance</para>
6606 <para>On server machines, the ability to disable authorization checking, or to install rogue process binaries</para>
6608 </itemizedlist></para>
6611 <sect2 id="HDRWQ95">
6612 <title>Controlling System Administrator Access</title>
6614 <para>Following are suggestions for managing AFS administrative privilege: <itemizedlist>
6616 <para>Create an administrative account for each administrator named
6618 <replaceable>username</replaceable><emphasis role="bold">.admin</emphasis>.
6619 Administrators authenticate under these identities only when
6620 performing administrative tasks, and destroy the administrative
6621 tokens immediately after finishing the task (either by issuing the
6622 <emphasis role="bold">unlog</emphasis> command, or the
6623 <emphasis role="bold">kinit</emphasis> and
6624 <emphasis role="bold">aklog</emphasis> commands to adopt their
6625 regular identity).</para>
6629 <para>Set a short ticket lifetime for administrator accounts (for example, 20 minutes) by using the
6630 facilities of your KDC. For instance, with a MIT Kerberos KDC, this
6631 can be performed using the
6632 <emphasis role="bold">--max-ticket-life</emphasis> argument to
6633 the <emphasis role="bold">kadmin modify_principal</emphasis>
6634 command. Do not however, use a short lifetime for users
6635 who issue long-running <emphasis role="bold">backup</emphasis> commands.</para>
6639 <para>Limit the number of system administrators in your cell, especially those who belong to the <emphasis
6640 role="bold">system:administrators</emphasis> group. By default they have all ACL rights on all directories in the local
6641 AFS filespace, and therefore must be trusted not to examine private files.</para>
6645 <para>Limit the use of system administrator accounts on machines in public areas. It is especially important not to
6646 leave such machines unattended without first destroying the administrative tokens.</para>
6650 <para>Limit the use by administrators of standard UNIX commands that make connections to remote machines (such as the
6651 <emphasis role="bold">telnet</emphasis> utility). Many of these programs send passwords across the network without
6652 encrypting them.</para>
6654 </itemizedlist></para>
6657 <primary>BOS Server</primary>
6659 <secondary>checking mode bits on AFS directories</secondary>
6663 <primary>mode bits on local AFS directories</primary>
6667 <primary>UNIX mode bits on local AFS directories</primary>
6671 <sect2 id="HDRWQ96">
6672 <title>Protecting Sensitive AFS Directories</title>
6674 <para>Some subdirectories of the <emphasis role="bold">/usr/afs</emphasis> directory contain files crucial to cell security.
6675 Unauthorized users must not read or write to these files because of the potential for misuse of the information they
6678 <para>As the BOS Server initializes for the first time on a server machine, it creates several files and directories (as
6679 mentioned in <link linkend="HDRWQ50">Starting the BOS Server</link>). It sets their owner to the local superuser <emphasis
6680 role="bold">root</emphasis> and sets their mode bits to enable writing by the owner only; in some cases, it also restricts
6683 <para>At each subsequent restart, the BOS Server checks that the owner and mode bits on these files are still set
6684 appropriately. If they are not, it write the following message to the <emphasis role="bold">/usr/afs/logs/BosLog</emphasis>
6688 Bosserver reports inappropriate access on server directories
6691 <para>The BOS Server does not reset the mode bits, which enables you to set alternate values if you wish.</para>
6693 <para>The following charts lists the expected mode bit settings. A question mark indicates that the BOS Server does not check
6694 that mode bit.</para>
6696 <informaltable frame="none">
6698 <colspec colwidth="30*" />
6700 <colspec colwidth="70*" />
6704 <entry><emphasis role="bold">/usr/afs</emphasis></entry>
6706 <entry><computeroutput>drwxr</computeroutput>?<computeroutput>xr-x</computeroutput></entry>
6710 <entry><emphasis role="bold">/usr/afs/backup</emphasis></entry>
6712 <entry><computeroutput>drwx</computeroutput>???<computeroutput>---</computeroutput></entry>
6716 <entry><emphasis role="bold">/usr/afs/bin</emphasis></entry>
6718 <entry><computeroutput>drwxr</computeroutput>?<computeroutput>xr-x</computeroutput></entry>
6722 <entry><emphasis role="bold">/usr/afs/db</emphasis></entry>
6724 <entry><computeroutput>drwx</computeroutput>???<computeroutput>---</computeroutput></entry>
6728 <entry><emphasis role="bold">/usr/afs/etc</emphasis></entry>
6730 <entry><computeroutput>drwxr</computeroutput>?<computeroutput>xr-x</computeroutput></entry>
6734 <entry><emphasis role="bold">/usr/afs/etc/KeyFile</emphasis></entry>
6736 <entry><computeroutput>-rw</computeroutput>????<computeroutput>---</computeroutput></entry>
6740 <entry><emphasis role="bold">/usr/afs/etc/UserList</emphasis></entry>
6742 <entry><computeroutput>-rw</computeroutput>?????<computeroutput>--</computeroutput></entry>
6746 <entry><emphasis role="bold">/usr/afs/local</emphasis></entry>
6748 <entry><computeroutput>drwx</computeroutput>???<computeroutput>---</computeroutput></entry>
6752 <entry><emphasis role="bold">/usr/afs/logs</emphasis></entry>
6754 <entry><computeroutput>drwxr</computeroutput>?<computeroutput>xr-x</computeroutput></entry>
6761 <primary>first AFS machine</primary>
6763 <secondary>client functionality</secondary>
6765 <tertiary>removing</tertiary>
6769 <primary>removing</primary>
6771 <secondary>client functionality from first AFS machine</secondary>
6776 <sect1 id="HDRWQ98">
6777 <title>Removing Client Functionality</title>
6779 <para>Follow the instructions in this section only if you do not wish this machine to remain an AFS client. Removing client
6780 functionality means that you cannot use this machine to access AFS files. <orderedlist>
6782 <para>Remove the files from the <emphasis role="bold">/usr/vice/etc</emphasis> directory. The command does not remove the
6783 directory for files used by the dynamic kernel loader program, if it exists on this system type. Those files are still
6784 needed on a server-only machine. <programlisting>
6785 # <emphasis role="bold">cd /usr/vice/etc</emphasis>
6786 # <emphasis role="bold">rm *</emphasis>
6787 # <emphasis role="bold">rm -rf C</emphasis>
6788 </programlisting></para>
6792 <para>Create symbolic links to the <emphasis role="bold">ThisCell</emphasis> and <emphasis
6793 role="bold">CellServDB</emphasis> files in the <emphasis role="bold">/usr/afs/etc</emphasis> directory. This makes it
6794 possible to issue commands from the AFS command suites (such as <emphasis role="bold">bos</emphasis> and <emphasis
6795 role="bold">fs</emphasis>) on this machine. <programlisting>
6796 # <emphasis role="bold">ln -s /usr/afs/etc/ThisCell ThisCell</emphasis>
6797 # <emphasis role="bold">ln -s /usr/afs/etc/CellServDB CellServDB</emphasis>
6798 </programlisting></para>
6802 <para>On IRIX systems, issue the <emphasis role="bold">chkconfig</emphasis> command to deactivate the <emphasis
6803 role="bold">afsclient</emphasis> configuration variable. <programlisting>
6804 # <emphasis role="bold">/etc/chkconfig -f afsclient off</emphasis>
6805 </programlisting></para>
6809 <para>Reboot the machine. Most system types use the <emphasis role="bold">shutdown</emphasis> command, but the appropriate
6810 options vary. <programlisting>
6811 # <emphasis role="bold">cd /</emphasis>
6812 # <emphasis role="bold">shutdown</emphasis> <replaceable>appropriate_options</replaceable>
6813 </programlisting></para>
6815 </orderedlist></para>