1 <?xml version="1.0" encoding="UTF-8"?>
3 <title>Installing the First AFS Machine</title>
6 <primary>file server machine</primary>
8 <seealso>first AFS machine</seealso>
10 <seealso>file server machine, additional</seealso>
14 <primary>instructions</primary>
16 <secondary>first AFS machine</secondary>
20 <primary>installing</primary>
22 <secondary>first AFS machine</secondary>
25 <para>This chapter describes how to install the first AFS machine in your cell, configuring it as both a file server machine and a
26 client machine. After completing all procedures in this chapter, you can remove the client functionality if you wish, as described
27 in <link linkend="HDRWQ98">Removing Client Functionality</link>.</para>
29 <para>To install additional file server machines after completing this chapter, see <link linkend="HDRWQ99">Installing Additional
30 Server Machines</link>.</para>
32 <para>To install additional client machines after completing this chapter, see <link linkend="HDRWQ133">Installing Additional
33 Client Machines</link>. <indexterm>
34 <primary>requirements</primary>
36 <secondary>first AFS machine</secondary>
39 <sect1 id="Header_29">
40 <title>Requirements and Configuration Decisions</title>
42 <para>The instructions in this chapter assume that you meet the following requirements.
45 <para>You are logged onto the machine's console as the local superuser <emphasis role="bold">root</emphasis></para>
49 <para>A standard version of one of the operating systems supported by the current version of AFS is running on the
54 <para>You have either installed the provided OpenAFS packages for
55 your system, have access to a binary distribution tarball, or have
56 successfully built OpenAFS from source</para>
60 <para>You have a Kerberos v5 realm running for your site. If you are
61 working with an existing cell which uses
62 <emphasis role="bold">kaserver</emphasis> or Kerberos v4 for
63 authentication, please see
64 <link linkend="KAS001">kaserver and Legacy Kerberos v4 Authentication</link>
65 for the modifications required to this installation procedure.</para>
69 <para>You have a NTP, or similar, time service deployed to ensure
70 rough clock syncronistation between your clients and servers. If you
71 wish to use AFS's built in timeservice (which is deprecated) please
72 see Appendix B for the necessary modifications to this installation
75 </itemizedlist></para>
77 <para>You must make the following configuration decisions while installing the first AFS machine. To speed the installation
78 itself, it is best to make the decisions before beginning. See the chapter in the <emphasis>OpenAFS Administration
79 Guide</emphasis> about issues in cell administration and configuration for detailed guidelines. <indexterm>
80 <primary>cell name</primary>
82 <secondary>choosing</secondary>
83 </indexterm> <indexterm>
84 <primary>AFS filespace</primary>
86 <secondary>deciding how to configure</secondary>
87 </indexterm> <indexterm>
88 <primary>filespace</primary>
90 <see>AFS filespace</see>
91 </indexterm> <itemizedlist>
93 <para>Select the first AFS machine</para>
97 <para>Select the cell name</para>
101 <para>Decide which partitions or logical volumes to configure as AFS server partitions, and choose the directory names on
102 which to mount them</para>
106 <para>Decide how big to make the client cache</para>
110 <para>Decide how to configure the top levels of your cell's AFS filespace</para>
112 </itemizedlist></para>
114 <para>This chapter is divided into three large sections corresponding to the three parts of installing the first AFS machine.
115 Perform all of the steps in the order they appear. Each functional section begins with a summary of the procedures to perform.
116 The sections are as follows: <itemizedlist>
118 <para>Installing server functionality (begins in <link linkend="HDRWQ18">Overview: Installing Server
119 Functionality</link>)</para>
123 <para>Installing client functionality (begins in <link linkend="HDRWQ63">Overview: Installing Client
124 Functionality</link>)</para>
128 <para>Configuring your cell's filespace, establishing further security mechanisms, and enabling access to foreign cells
129 (begins in <link linkend="HDRWQ71">Overview: Completing the Installation of the First AFS Machine</link>)</para>
131 </itemizedlist></para>
134 <primary>overview</primary>
136 <secondary>installing server functionality on first AFS machine</secondary>
140 <primary>first AFS machine</primary>
142 <secondary>server functionality</secondary>
146 <primary>installing</primary>
148 <secondary>server functionality</secondary>
150 <tertiary>first AFS machine</tertiary>
155 <title>Overview: Installing Server Functionality</title>
157 <para>In the first phase of installing your cell's first AFS machine, you install file server and database server functionality
158 by performing the following procedures:
161 <para>Choose which machine to install as the first AFS machine</para>
165 <para>Create AFS-related directories on the local disk</para>
169 <para>Incorporate AFS modifications into the machine's kernel</para>
173 <para>Configure partitions or logical volumes for storing AFS volumes</para>
177 <para>On some system types, install and configure an AFS-modified version of the <emphasis role="bold">fsck</emphasis>
182 <para>If the machine is to remain a client machine, incorporate AFS into its authentication system</para>
186 <para>Start the Basic OverSeer (BOS) Server</para>
190 <para>Define the cell name and the machine's cell membership</para>
194 <para>Start the database server processes: Backup Server, Protection Server, and Volume Location
199 <para>Configure initial security mechanisms</para>
203 <para>Start the <emphasis role="bold">fs</emphasis> process, which incorporates three component processes: the File
204 Server, Volume Server, and Salvager</para>
208 <para>Start the server portion of the Update Server</para>
211 </orderedlist></para>
215 <title>Choosing the First AFS Machine</title>
217 <para>The first AFS machine you install must have sufficient disk space to store AFS volumes. To take best advantage of AFS's
218 capabilities, store client-side binaries as well as user files in volumes. When you later install additional file server
219 machines in your cell, you can distribute these volumes among the different machines as you see fit.</para>
221 <para>These instructions configure the first AFS machine as a <emphasis>database server machine</emphasis>, the <emphasis>binary
222 distribution machine</emphasis> for its system type, and the cell's <emphasis>system control machine</emphasis>. For a
223 description of these roles, see the <emphasis>OpenAFS Administration Guide</emphasis>.</para>
225 <para>Installation of additional machines is simplest if the first machine has the lowest IP address of any database server
226 machine you currently plan to install. If you later install database server functionality on a machine with a lower IP address,
227 you must first update the <emphasis role="bold">/usr/vice/etc/CellServDB</emphasis> file on all of your cell's client machines.
228 For more details, see <link linkend="HDRWQ114">Installing Database Server Functionality</link>.</para>
231 <sect1 id="Header_32">
232 <title>Creating AFS Directories</title>
235 <primary>usr/afs directory</primary>
237 <secondary>first AFS machine</secondary>
241 <primary>first AFS machine</primary>
243 <secondary>/usr/afs directory</secondary>
247 <primary>creating</primary>
249 <secondary>/usr/afs directory</secondary>
251 <tertiary>first AFS machine</tertiary>
255 <primary>usr/vice/etc directory</primary>
257 <secondary>first AFS machine</secondary>
261 <primary>first AFS machine</primary>
263 <secondary>/usr/vice/etc directory</secondary>
267 <primary>creating</primary>
269 <secondary>/usr/vice/etc directory</secondary>
271 <tertiary>first AFS machine</tertiary>
275 <primary>/ as start to file and directory names</primary>
277 <secondary>see alphabetized entries without initial slash</secondary>
280 <para>If you are installing from packages (such as Debian .deb or
281 Fedora/SuSe .rpm files), you should now install all of the available
282 OpenAFS packages for your system type. Typically, these will include
283 packages for client and server functionality, and a seperate package
284 containing a suitable kernel module for your running kernel. Consult
285 the package lists on the OpenAFS website to determine the packages
286 appropriate for your system.</para>
288 <para>If you are installing from a tarfile, or from a locally compiled
289 source tree you should create the <emphasis role="bold">/usr/afs</emphasis>
290 and <emphasis role="bold">/usr/vice/etc</emphasis> directories on the
291 local disk, to house server and client files respectively. Subsequent
292 instructions copy files from the distribution tarfile into them. </para>
294 # <emphasis role="bold">mkdir /usr/afs</emphasis>
295 # <emphasis role="bold">mkdir /usr/vice</emphasis>
296 # <emphasis role="bold">mkdir /usr/vice/etc</emphasis>
301 <title>Performing Platform-Specific Procedures</title>
303 <para>Several of the initial procedures for installing a file server machine differ for each system type. For convenience, the
304 following sections group them together for each system type: <itemizedlist>
306 <primary>kernel extensions</primary>
308 <see>AFS kernel extensions</see>
312 <primary>loading AFS kernel extensions</primary>
314 <see>incorporating</see>
318 <primary>building</primary>
320 <secondary>AFS extensions into kernel</secondary>
322 <see>incorporating AFS kernel extensions</see>
326 <para>Incorporate AFS modifications into the kernel.</para>
328 <para>The kernel on every AFS client machine and, on some systems,
329 the AFS fileservers, must incorporate AFS extensions. On machines
330 that use a dynamic kernel module loader, it is conventional to
331 alter the machine's initialization script to load the AFS extensions
332 at each reboot. <indexterm>
333 <primary>AFS server partition</primary>
335 <secondary>mounted on /vicep directory</secondary>
336 </indexterm> <indexterm>
337 <primary>partition</primary>
339 <see>AFS server partition</see>
340 </indexterm> <indexterm>
341 <primary>logical volume</primary>
343 <see>AFS server partition</see>
344 </indexterm> <indexterm>
345 <primary>requirements</primary>
347 <secondary>AFS server partition name and location</secondary>
348 </indexterm> <indexterm>
349 <primary>naming conventions for AFS server partition</primary>
350 </indexterm> <indexterm>
351 <primary>vicep<emphasis>xx</emphasis> directory</primary>
353 <see>AFS server partition</see>
354 </indexterm> <indexterm>
355 <primary>directories</primary>
357 <secondary>/vicep<emphasis>xx</emphasis></secondary>
359 <see>AFS server partition</see>
364 <para>Configure server partitions or logical volumes to house AFS volumes.</para>
366 <para>Every AFS file server machine must have at least one partition or logical volume dedicated to storing AFS volumes
367 (for convenience, the documentation hereafter refers to partitions only). Each server partition is mounted at a directory
368 named <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>, where <replaceable>xx</replaceable> is one or
369 two lowercase letters. By convention, the first 26 partitions are mounted on the directories called <emphasis
370 role="bold">/vicepa</emphasis> through <emphasis role="bold">/vicepz</emphasis>, the 27th one is mounted on the <emphasis
371 role="bold">/vicepaa</emphasis> directory, and so on through <emphasis role="bold">/vicepaz</emphasis> and <emphasis
372 role="bold">/vicepba</emphasis>, continuing up to the index corresponding to the maximum number of server partitions
373 supported in the current version of AFS (which is specified in the <emphasis>OpenAFS Release Notes</emphasis>).</para>
375 <para>The <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable> directories must reside in the file server
376 machine's root directory, not in one of its subdirectories (for example, <emphasis role="bold">/usr/vicepa</emphasis> is
377 not an acceptable directory location).</para>
379 <para>You can also add or remove server partitions on an existing file server machine. For instructions, see the chapter
380 in the <emphasis>OpenAFS Administration Guide</emphasis> about maintaining server machines.</para>
383 <para>Not all file system types supported by an operating system are necessarily supported as AFS server partitions. For
384 possible restrictions, see the <emphasis>OpenAFS Release Notes</emphasis>.</para>
389 <para>On some system types, install and configure a modified <emphasis role="bold">fsck</emphasis> program which
390 recognizes the structures that the File Server uses to organize volume data on AFS server partitions. The <emphasis
391 role="bold">fsck</emphasis> program provided with the operating system does not understand the AFS data structures, and so
392 removes them to the <emphasis role="bold">lost+found</emphasis> directory.</para>
396 <para>If the machine is to remain an AFS client machine, modify the machine's authentication system so that users obtain
397 an AFS token as they log into the local file system. Using AFS is simpler and more convenient for your users if you make
398 the modifications on all client machines. Otherwise, users must perform a two or three step login procedure (login to the local
399 system, then obtain Kerberos credentials, and then issue the <emphasis role="bold">aklog</emphasis> command). For further discussion of AFS
400 authentication, see the chapter in the <emphasis>OpenAFS Administration Guide</emphasis> about cell configuration and
401 administration issues.</para>
403 </itemizedlist></para>
405 <para>To continue, proceed to the appropriate section: <itemizedlist>
407 <para><link linkend="HDRWQ21">Getting Started on AIX Systems</link></para>
411 <para><link linkend="HDRWQ31">Getting Started on HP-UX Systems</link></para>
415 <para><link linkend="HDRWQ36">Getting Started on IRIX Systems</link></para>
419 <para><link linkend="HDRWQ41">Getting Started on Linux Systems</link></para>
423 <para><link linkend="HDRWQ45">Getting Started on Solaris Systems</link></para>
425 </itemizedlist></para>
429 <title>Getting Started on AIX Systems</title>
431 <para>Begin by running the AFS initialization script to call the AIX kernel extension facility, which dynamically loads AFS
432 modifications into the kernel. Then use the <emphasis role="bold">SMIT</emphasis> program to configure partitions for storing
433 AFS volumes, and replace the AIX <emphasis role="bold">fsck</emphasis> program helper with a version that correctly handles AFS
434 volumes. If the machine is to remain an AFS client machine, incorporate AFS into the AIX secondary authentication system.
436 <primary>incorporating AFS kernel extensions</primary>
438 <secondary>first AFS machine</secondary>
440 <tertiary>AIX</tertiary>
441 </indexterm> <indexterm>
442 <primary>AFS kernel extensions</primary>
444 <secondary>on first AFS machine</secondary>
446 <tertiary>AIX</tertiary>
447 </indexterm> <indexterm>
448 <primary>first AFS machine</primary>
450 <secondary>AFS kernel extensions</secondary>
452 <tertiary>on AIX</tertiary>
453 </indexterm> <indexterm>
454 <primary>AIX</primary>
456 <secondary>AFS kernel extensions</secondary>
458 <tertiary>on first AFS machine</tertiary>
462 <title>Loading AFS into the AIX Kernel</title>
464 <para>The AIX kernel extension facility is the dynamic kernel loader
465 provided by IBM Corporation. AIX does not support incorporation of
466 AFS modifications during a kernel build.</para>
468 <para>For AFS to function correctly, the kernel extension facility must run each time the machine reboots, so the AFS
469 initialization script (included in the AFS distribution) invokes it automatically. In this section you copy the script to the
470 conventional location and edit it to select the appropriate options depending on whether NFS is also to run.</para>
472 <para>After editing the script, you run it to incorporate AFS into the kernel. In later sections you verify that the script
473 correctly initializes all AFS components, then configure the AIX <emphasis role="bold">inittab</emphasis> file so that the
474 script runs automatically at reboot. <orderedlist>
476 <para>Unpack the distribution tarball. The examples below assume
477 that you have unpacked the files into the
478 <emphasis role="bold">/tmp/afsdist</emphasis> directory. If you
479 pick a different location, substitute this in all of the following
480 examples. Once you have unpacked the distribution,
481 change directory as indicated.
483 # <emphasis role="bold">cd /tmp/afsdist/rs_aix42/root.client/usr/vice/etc</emphasis>
484 </programlisting></para>
488 <para>Copy the AFS kernel library files to the local <emphasis role="bold">/usr/vice/etc/dkload</emphasis> directory,
489 and the AFS initialization script to the <emphasis role="bold">/etc</emphasis> directory. <programlisting>
490 # <emphasis role="bold">cp -rp dkload /usr/vice/etc</emphasis>
491 # <emphasis role="bold">cp -p rc.afs /etc/rc.afs</emphasis>
492 </programlisting></para>
496 <para>Edit the <emphasis role="bold">/etc/rc.afs</emphasis> script, setting the <computeroutput>NFS</computeroutput>
497 variable as indicated.</para>
499 <para>If the machine is not to function as an NFS/AFS Translator, set the <computeroutput>NFS</computeroutput> variable
506 <para>If the machine is to function as an NFS/AFS Translator and is running AIX 4.2.1 or higher, set the
507 <computeroutput>NFS</computeroutput> variable as follows. Note that NFS must already be loaded into the kernel, which
508 happens automatically on systems running AIX 4.1.1 and later, as long as the file <emphasis
509 role="bold">/etc/exports</emphasis> exists.</para>
517 <para>Invoke the <emphasis role="bold">/etc/rc.afs</emphasis> script to load AFS modifications into the kernel. You can
518 ignore any error messages about the inability to start the BOS Server or the Cache Manager or AFS client.
520 # <emphasis role="bold">/etc/rc.afs</emphasis>
521 </programlisting></para>
523 </orderedlist></para>
526 <primary>configuring</primary>
528 <secondary>AFS server partition on first AFS machine</secondary>
530 <tertiary>AIX</tertiary>
534 <primary>AFS server partition</primary>
536 <secondary>configuring on first AFS machine</secondary>
538 <tertiary>AIX</tertiary>
542 <primary>first AFS machine</primary>
544 <secondary>AFS server partition</secondary>
546 <tertiary>on AIX</tertiary>
550 <primary>AIX</primary>
552 <secondary>AFS server partition</secondary>
554 <tertiary>on first AFS machine</tertiary>
559 <title>Configuring Server Partitions on AIX Systems</title>
561 <para>Every AFS file server machine must have at least one partition or logical volume dedicated to storing AFS volumes. Each
562 server partition is mounted at a directory named <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>, where
563 <replaceable>xx</replaceable> is one or two lowercase letters. The <emphasis
564 role="bold">/vicep</emphasis><replaceable>xx</replaceable> directories must reside in the file server machine's root
565 directory, not in one of its subdirectories (for example, <emphasis role="bold">/usr/vicepa</emphasis> is not an acceptable
566 directory location). For additional information, see <link linkend="HDRWQ20">Performing Platform-Specific
567 Procedures</link>.</para>
569 <para>To configure server partitions on an AIX system, perform the following procedures: <orderedlist>
571 <para>Create a directory called <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable> for each AFS server
572 partition you are configuring (there must be at least one). Repeat the command for each partition. <programlisting>
573 # <emphasis role="bold">mkdir /vicep</emphasis><replaceable>xx</replaceable>
574 </programlisting></para>
578 <para>Use the <emphasis role="bold">SMIT</emphasis> program to create a journaling file system on each partition to be
579 configured as an AFS server partition.</para>
583 <para>Mount each partition at one of the <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>
584 directories. Choose one of the following three methods: <itemizedlist>
586 <para>Use the <emphasis role="bold">SMIT</emphasis> program</para>
590 <para>Use the <emphasis role="bold">mount -a</emphasis> command to mount all partitions at once</para>
594 <para>Use the <emphasis role="bold">mount</emphasis> command on each partition in turn</para>
596 </itemizedlist></para>
598 <para>Also configure the partitions so that they are mounted automatically at each reboot. For more information, refer
599 to the AIX documentation.</para>
601 </orderedlist></para>
604 <primary>replacing fsck program</primary>
606 <secondary>first AFS machine</secondary>
608 <tertiary>AIX</tertiary>
612 <primary>fsck program</primary>
614 <secondary>on first AFS machine</secondary>
616 <tertiary>AIX</tertiary>
620 <primary>first AFS machine</primary>
622 <secondary>fsck program</secondary>
624 <tertiary>on AIX</tertiary>
628 <primary>AIX</primary>
630 <secondary>fsck program</secondary>
632 <tertiary>on first AFS machine</tertiary>
637 <title>Replacing the fsck Program Helper on AIX Systems</title>
639 <note><para>The AFS modified fsck program is not required on AIX 5.1
640 systems, and the <emphasis role="bold">v3fshelper</emphasis> program
641 refered to below is not shipped for these systems.</para></note>
643 <para>In this section, you make modifications to guarantee that the appropriate <emphasis role="bold">fsck</emphasis> program
644 runs on AFS server partitions. The <emphasis role="bold">fsck</emphasis> program provided with the operating system must never
645 run on AFS server partitions. Because it does not recognize the structures that the File Server uses to organize volume data,
646 it removes all of the data. To repeat:</para>
648 <para><emphasis role="bold">Never run the standard fsck program on AFS server partitions. It discards AFS
649 volumes.</emphasis></para>
651 <para>On AIX systems, you do not replace the <emphasis role="bold">fsck</emphasis> binary itself, but rather the
652 <emphasis>program helper</emphasis> file included in the AIX distribution as <emphasis
653 role="bold">/sbin/helpers/v3fshelper</emphasis>. <orderedlist>
655 <para>Move the AIX <emphasis role="bold">fsck</emphasis> program helper to a safe location and install the version from
656 the AFS distribution in its place.
658 # <emphasis role="bold">cd /sbin/helpers</emphasis>
659 # <emphasis role="bold">mv v3fshelper v3fshelper.noafs</emphasis>
660 # <emphasis role="bold">cp -p /tmp/afsdist/rs_aix42/root.server/etc/v3fshelper v3fshelper</emphasis>
661 </programlisting></para>
665 <para>If you plan to retain client functionality on this machine after completing the installation, proceed to <link
666 linkend="HDRWQ25">Enabling AFS Login on AIX Systems</link>. Otherwise, proceed to <link linkend="HDRWQ50">Starting the
667 BOS Server</link>.</para>
669 </orderedlist></para>
672 <primary>enabling AFS login</primary>
674 <secondary>file server machine</secondary>
676 <tertiary>AIX</tertiary>
680 <primary>AFS login</primary>
682 <secondary>on file server machine</secondary>
684 <tertiary>AIX</tertiary>
688 <primary>first AFS machine</primary>
690 <secondary>AFS login</secondary>
692 <tertiary>on AIX</tertiary>
696 <primary>AIX</primary>
698 <secondary>AFS login</secondary>
700 <tertiary>on file server machine</tertiary>
704 <primary>secondary authentication system (AIX)</primary>
706 <secondary>server machine</secondary>
711 <title>Enabling AFS Login on AIX Systems</title>
714 <para>If you plan to remove client functionality from this machine after completing the installation, skip this section and
715 proceed to <link linkend="HDRWQ50">Starting the BOS Server</link>.</para>
718 <para>In modern AFS installations, you should be using Kerberos v5
719 for user login, and obtaining AFS tokens following this authentication
722 <para>There are currently no instructions available on configuring AIX to
723 automatically obtain AFS tokens at login. Following login, users can
724 obtain tokens by running the <emphasis role="bold">aklog</emphasis>
727 <para>Sites which still require <emphasis role="bold">kaserver</emphasis>
728 or external Kerberos v4 authentication should consult
729 <link linkend="KAS012">Enabling kaserver based AFS login on AIX systems</link>
730 for details of how to enable AIX login.</para>
732 <para>Proceed to <link linkend="HDRWQ50">Starting the BOS Server</link>
733 (or if referring to these instructions while installing an additional
734 file server machine, return to <link linkend="HDRWQ108">Starting Server
735 Programs</link>).</para>
740 <title>Getting Started on HP-UX Systems</title>
742 <para>Begin by building AFS modifications into a new kernel; HP-UX does not support dynamic loading. Then create partitions for
743 storing AFS volumes, and install and configure the AFS-modified <emphasis role="bold">fsck</emphasis> program to run on AFS
744 server partitions. If the machine is to remain an AFS client machine, incorporate AFS into the machine's Pluggable
745 Authentication Module (PAM) scheme. <indexterm>
746 <primary>incorporating AFS kernel extensions</primary>
748 <secondary>first AFS machine</secondary>
750 <tertiary>HP-UX</tertiary>
751 </indexterm> <indexterm>
752 <primary>AFS kernel extensions</primary>
754 <secondary>on first AFS machine</secondary>
756 <tertiary>HP-UX</tertiary>
757 </indexterm> <indexterm>
758 <primary>first AFS machine</primary>
760 <secondary>AFS kernel extensions</secondary>
762 <tertiary>on HP-UX</tertiary>
763 </indexterm> <indexterm>
764 <primary>HP-UX</primary>
766 <secondary>AFS-modified kernel</secondary>
768 <tertiary>on first AFS machine</tertiary>
772 <title>Building AFS into the HP-UX Kernel</title>
774 <para>Use the following instructions to build AFS modifications into the kernel on an HP-UX system. <orderedlist>
776 <para>Move the existing kernel-related files to a safe location. <programlisting>
777 # <emphasis role="bold">cp /stand/vmunix /stand/vmunix.noafs</emphasis>
778 # <emphasis role="bold">cp /stand/system /stand/system.noafs</emphasis>
779 </programlisting></para>
783 <para>Unpack the OpenAFS HP-UX distribution tarball. The examples
784 below assume that you have unpacked the files into the
785 <emphasis role="bold">/tmp/afsdist</emphasis> directory. If you
786 pick a different location, substitute this in all of the following
787 examples. Once you have unpacked the distribution, change directory
790 # <emphasis role="bold">cd /tmp/afsdist/hp_ux110/root.client</emphasis>
791 </programlisting></para>
795 <para>Copy the AFS initialization file to the local directory for initialization files (by convention, <emphasis
796 role="bold">/sbin/init.d</emphasis> on HP-UX machines). Note the removal of the <emphasis role="bold">.rc</emphasis>
797 extension as you copy the file. <programlisting>
798 # <emphasis role="bold">cp usr/vice/etc/afs.rc /sbin/init.d/afs</emphasis>
799 </programlisting></para>
803 <para>Copy the file <emphasis role="bold">afs.driver</emphasis> to the local <emphasis
804 role="bold">/usr/conf/master.d</emphasis> directory, changing its name to <emphasis role="bold">afs</emphasis> as you
806 # <emphasis role="bold">cp usr/vice/etc/afs.driver /usr/conf/master.d/afs</emphasis>
807 </programlisting></para>
811 <para>Copy the AFS kernel module to the local <emphasis role="bold">/usr/conf/lib</emphasis> directory.</para>
813 <para>If the machine's kernel supports NFS server functionality:</para>
816 # <emphasis role="bold">cp bin/libafs.a /usr/conf/lib</emphasis>
819 <para>If the machine's kernel does not support NFS server functionality, change the file's name as you copy it:</para>
822 # <emphasis role="bold">cp bin/libafs.nonfs.a /usr/conf/lib/libafs.a</emphasis>
827 <para>Incorporate the AFS driver into the kernel, either using the <emphasis role="bold">SAM</emphasis> program or a
828 series of individual commands. <itemizedlist>
830 <para>To use the <emphasis role="bold">SAM</emphasis> program: <orderedlist>
832 <para>Invoke the <emphasis role="bold">SAM</emphasis> program, specifying the hostname of the local machine
833 as <replaceable>local_hostname</replaceable>. The <emphasis role="bold">SAM</emphasis> graphical user
834 interface pops up. <programlisting>
835 # <emphasis role="bold">sam -display</emphasis> <replaceable>local_hostname</replaceable><emphasis role="bold">:0</emphasis>
836 </programlisting></para>
840 <para>Choose the <emphasis role="bold">Kernel Configuration</emphasis> icon, then the <emphasis
841 role="bold">Drivers</emphasis> icon. From the list of drivers, select <emphasis
842 role="bold">afs</emphasis>.</para>
846 <para>Open the pull-down <emphasis role="bold">Actions</emphasis> menu and choose the <emphasis
847 role="bold">Add Driver to Kernel</emphasis> option.</para>
851 <para>Open the <emphasis role="bold">Actions</emphasis> menu again and choose the <emphasis
852 role="bold">Create a New Kernel</emphasis> option.</para>
856 <para>Confirm your choices by choosing <emphasis role="bold">Yes</emphasis> and <emphasis
857 role="bold">OK</emphasis> when prompted by subsequent pop-up windows. The <emphasis
858 role="bold">SAM</emphasis> program builds the kernel and reboots the system.</para>
862 <para>Login again as the superuser <emphasis role="bold">root</emphasis>. <programlisting>
863 login: <emphasis role="bold">root</emphasis>
864 Password: <replaceable>root_password</replaceable>
865 </programlisting></para>
867 </orderedlist></para>
871 <para>To use individual commands: <orderedlist>
873 <para>Edit the file <emphasis role="bold">/stand/system</emphasis>, adding an entry for <emphasis
874 role="bold">afs</emphasis> to the <computeroutput>Subsystems</computeroutput> section.</para>
878 <para>Change to the <emphasis role="bold">/stand/build</emphasis> directory and issue the <emphasis
879 role="bold">mk_kernel</emphasis> command to build the kernel. <programlisting>
880 # <emphasis role="bold">cd /stand/build</emphasis>
881 # <emphasis role="bold">mk_kernel</emphasis>
882 </programlisting></para>
886 <para>Move the new kernel to the standard location (<emphasis role="bold">/stand/vmunix</emphasis>), reboot
887 the machine to start using it, and login again as the superuser <emphasis role="bold">root</emphasis>.
889 # <emphasis role="bold">mv /stand/build/vmunix_test /stand/vmunix</emphasis>
890 # <emphasis role="bold">cd /</emphasis>
891 # <emphasis role="bold">shutdown -r now</emphasis>
892 login: <emphasis role="bold">root</emphasis>
893 Password: <replaceable>root_password</replaceable>
894 </programlisting></para>
896 </orderedlist></para>
898 </itemizedlist></para>
900 </orderedlist></para>
903 <primary>configuring</primary>
905 <secondary>AFS server partition on first AFS machine</secondary>
907 <tertiary>HP-UX</tertiary>
911 <primary>AFS server partition</primary>
913 <secondary>configuring on first AFS machine</secondary>
915 <tertiary>HP-UX</tertiary>
919 <primary>first AFS machine</primary>
921 <secondary>AFS server partition</secondary>
923 <tertiary>on HP-UX</tertiary>
927 <primary>HP-UX</primary>
929 <secondary>AFS server partition</secondary>
931 <tertiary>on first AFS machine</tertiary>
936 <title>Configuring Server Partitions on HP-UX Systems</title>
938 <para>Every AFS file server machine must have at least one partition or logical volume dedicated to storing AFS volumes. Each
939 server partition is mounted at a directory named <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>, where
940 <replaceable>xx</replaceable> is one or two lowercase letters. The <emphasis
941 role="bold">/vicep</emphasis><replaceable>xx</replaceable> directories must reside in the file server machine's root
942 directory, not in one of its subdirectories (for example, <emphasis role="bold">/usr/vicepa</emphasis> is not an acceptable
943 directory location). For additional information, see <link linkend="HDRWQ20">Performing Platform-Specific Procedures</link>.
946 <para>Create a directory called <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable> for each AFS server
947 partition you are configuring (there must be at least one). Repeat the command for each partition. <programlisting>
948 # <emphasis role="bold">mkdir /vicep</emphasis><replaceable>xx</replaceable>
949 </programlisting></para>
953 <para>Use the <emphasis role="bold">SAM</emphasis> program to create a file system on each partition. For instructions,
954 consult the HP-UX documentation.</para>
958 <para>On some HP-UX systems that use logical volumes, the <emphasis role="bold">SAM</emphasis> program automatically
959 mounts the partitions. If it has not, mount each partition by issuing either the <emphasis role="bold">mount
960 -a</emphasis> command to mount all partitions at once or the <emphasis role="bold">mount</emphasis> command to mount
961 each partition in turn.</para>
963 </orderedlist></para>
966 <primary>replacing fsck program</primary>
968 <secondary>first AFS machine</secondary>
970 <tertiary>HP-UX</tertiary>
974 <primary>fsck program</primary>
976 <secondary>on first AFS machine</secondary>
978 <tertiary>HP-UX</tertiary>
982 <primary>first AFS machine</primary>
984 <secondary>fsck program</secondary>
986 <tertiary>on HP-UX</tertiary>
990 <primary>HP-UX</primary>
992 <secondary>fsck program</secondary>
994 <tertiary>on first AFS machine</tertiary>
999 <title>Configuring the AFS-modified fsck Program on HP-UX Systems</title>
1001 <para>In this section, you make modifications to guarantee that the appropriate <emphasis role="bold">fsck</emphasis> program
1002 runs on AFS server partitions. The <emphasis role="bold">fsck</emphasis> program provided with the operating system must never
1003 run on AFS server partitions. Because it does not recognize the structures that the File Server uses to organize volume data,
1004 it removes all of the data. To repeat:</para>
1006 <para><emphasis role="bold">Never run the standard fsck program on AFS server partitions. It discards AFS
1007 volumes.</emphasis></para>
1009 <para>On HP-UX systems, there are several configuration files to install in addition to the AFS-modified <emphasis
1010 role="bold">fsck</emphasis> program (the <emphasis role="bold">vfsck</emphasis> binary). <orderedlist>
1012 <para>Create the command configuration file <emphasis role="bold">/sbin/lib/mfsconfig.d/afs</emphasis>. Use a text
1013 editor to place the indicated two lines in it: <programlisting>
1015 fsck 0 m,P,p,d,f,b:c:y,n,Y,N,q,
1016 </programlisting></para>
1020 <para>Create and change directory to an AFS-specific command directory called <emphasis
1021 role="bold">/sbin/fs/afs</emphasis>. <programlisting>
1022 # <emphasis role="bold">mkdir /sbin/fs/afs</emphasis>
1023 # <emphasis role="bold">cd /sbin/fs/afs</emphasis>
1024 </programlisting></para>
1028 <para>Copy the AFS-modified version of the <emphasis role="bold">fsck</emphasis> program (the <emphasis
1029 role="bold">vfsck</emphasis> binary) and related files from the distribution directory to the new AFS-specific command
1030 directory. <programlisting>
1031 # <emphasis role="bold">cp -p /tmp/afsdist/hp_ux110/root.server/etc/* .</emphasis>
1032 </programlisting></para>
1036 <para>Change the <emphasis role="bold">vfsck</emphasis> binary's name to <emphasis role="bold">fsck</emphasis> and set
1037 the mode bits appropriately on all of the files in the <emphasis role="bold">/sbin/fs/afs</emphasis> directory.
1039 # <emphasis role="bold">mv vfsck fsck</emphasis>
1040 # <emphasis role="bold">chmod 755 *</emphasis>
1041 </programlisting></para>
1045 <para>Edit the <emphasis role="bold">/etc/fstab</emphasis> file, changing the file system type for each AFS server
1046 partition from <computeroutput>hfs</computeroutput> to <computeroutput>afs</computeroutput>. This ensures that the
1047 AFS-modified <emphasis role="bold">fsck</emphasis> program runs on the appropriate partitions.</para>
1049 <para>The sixth line in the following example of an edited file shows an AFS server partition, <emphasis
1050 role="bold">/vicepa</emphasis>.</para>
1053 /dev/vg00/lvol1 / hfs defaults 0 1
1054 /dev/vg00/lvol4 /opt hfs defaults 0 2
1055 /dev/vg00/lvol5 /tmp hfs defaults 0 2
1056 /dev/vg00/lvol6 /usr hfs defaults 0 2
1057 /dev/vg00/lvol8 /var hfs defaults 0 2
1058 /dev/vg00/lvol9 /vicepa afs defaults 0 2
1059 /dev/vg00/lvol7 /usr/vice/cache hfs defaults 0 2
1064 <para>If you plan to retain client functionality on this machine after completing the installation, proceed to <link
1065 linkend="HDRWQ35">Enabling AFS Login on HP-UX Systems</link>. Otherwise, proceed to <link linkend="HDRWQ50">Starting the
1066 BOS Server</link>.</para>
1068 </orderedlist></para>
1071 <primary>enabling AFS login</primary>
1073 <secondary>file server machine</secondary>
1075 <tertiary>HP-UX</tertiary>
1079 <primary>AFS login</primary>
1081 <secondary>on file server machine</secondary>
1083 <tertiary>HP-UX</tertiary>
1087 <primary>first AFS machine</primary>
1089 <secondary>AFS login</secondary>
1091 <tertiary>on HP-UX</tertiary>
1095 <primary>HP-UX</primary>
1097 <secondary>AFS login</secondary>
1099 <tertiary>on file server machine</tertiary>
1103 <primary>PAM</primary>
1105 <secondary>on HP-UX</secondary>
1107 <tertiary>file server machine</tertiary>
1111 <primary>Pluggable Authentication Module</primary>
1117 <sect2 id="HDRWQ35">
1118 <title>Enabling AFS Login on HP-UX Systems</title>
1120 <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>
1122 <para>At this point you incorporate AFS into the operating system's Pluggable Authentication Module (PAM) scheme. PAM
1123 integrates all authentication mechanisms on the machine, including login, to provide the security infrastructure for
1124 authenticated access to and from the machine.</para>
1126 <para>In modern AFS installations, you should be using Kerberos v5
1127 for user login, and obtaining AFS tokens subsequent to this authentication
1128 step. OpenAFS does not currently distribute a PAM module allowing AFS
1129 tokens to be automatically gained at login. Whilst there are a number of
1130 third party modules providing this functionality, it is not know if these
1131 have been tested with HP/UX.</para>
1133 <para>Following login, users can
1134 obtain tokens by running the <emphasis role="bold">aklog</emphasis>
1137 <para>Sites which still require <emphasis role="bold">kaserver</emphasis>
1138 or external Kerberos v4 authentication should consult
1139 <link linkend="KAS013">Enabling kaserver based AFS login on HP-UX systems</link>
1140 for details of how to enable HP-UX login.</para>
1142 <para>Proceed to <link linkend="HDRWQ50">Starting the BOS Server</link>
1143 (or if referring to these instructions while installing an additional
1144 file server machine, return to <link linkend="HDRWQ108">Starting Server
1145 Programs</link>).</para>
1149 <sect1 id="HDRWQ36">
1150 <title>Getting Started on IRIX Systems</title>
1153 <primary>incorporating AFS kernel extensions</primary>
1155 <secondary>first AFS machine</secondary>
1157 <tertiary>IRIX</tertiary>
1161 <primary>AFS kernel extensions</primary>
1163 <secondary>on first AFS machine</secondary>
1165 <tertiary>IRIX</tertiary>
1169 <primary>first AFS machine</primary>
1171 <secondary>AFS kernel extensions</secondary>
1173 <tertiary>on IRIX</tertiary>
1177 <primary>replacing fsck program</primary>
1179 <secondary>not necessary on IRIX</secondary>
1183 <primary>fsck program</primary>
1185 <secondary>on first AFS machine</secondary>
1187 <tertiary>IRIX</tertiary>
1191 <primary>first AFS machine</primary>
1193 <secondary>fsck program</secondary>
1195 <tertiary>on IRIX</tertiary>
1199 <primary>IRIX</primary>
1201 <secondary>fsck program replacement not necessary</secondary>
1204 <para>To incorporate AFS into the kernel on IRIX systems, choose one of two methods: <itemizedlist>
1206 <para>Run the AFS initialization script to invoke the <emphasis role="bold">ml</emphasis> program distributed by Silicon
1207 Graphics, Incorporated (SGI), which dynamically loads AFS modifications into the kernel</para>
1211 <para>Build a new static kernel</para>
1213 </itemizedlist></para>
1215 <para>Then create partitions for storing AFS volumes. You do not need to replace the IRIX <emphasis role="bold">fsck</emphasis>
1216 program because SGI has already modified it to handle AFS volumes properly. If the machine is to remain an AFS client machine,
1217 verify that the IRIX login utility installed on the machine grants an AFS token.</para>
1219 <para>In preparation for either dynamic loading or kernel building, perform the following procedures: <orderedlist>
1221 <para>Unpack the OpenAFS IRIX distribution tarball. The examples
1222 below assume that you have unpacked the files into the
1223 <emphasis role="bold">/tmp/afsdist</emphasis> directory. If you
1224 pick a different location, substitue this in all of the following
1225 examples. Once you have unpacked the distribution, change directory
1228 # <emphasis role="bold">cd /tmp/afsdist/sgi_65/root.client</emphasis>
1229 </programlisting></para>
1233 <para>Copy the AFS initialization script to the local directory for initialization files (by convention, <emphasis
1234 role="bold">/etc/init.d</emphasis> on IRIX machines). Note the removal of the <emphasis role="bold">.rc</emphasis>
1235 extension as you copy the script. <programlisting>
1236 # <emphasis role="bold">cp -p usr/vice/etc/afs.rc /etc/init.d/afs</emphasis>
1237 </programlisting></para>
1241 <para>Issue the <emphasis role="bold">uname -m</emphasis> command to determine the machine's CPU board type. The <emphasis
1242 role="bold">IP</emphasis><replaceable>xx</replaceable> value in the output must match one of the supported CPU board types
1243 listed in the <emphasis>OpenAFS Release Notes</emphasis> for the current version of AFS. <programlisting>
1244 # <emphasis role="bold">uname -m</emphasis>
1245 </programlisting></para>
1249 <para>Proceed to either <link linkend="HDRWQ37">Loading AFS into the IRIX Kernel</link> or <link
1250 linkend="HDRWQ38">Building AFS into the IRIX Kernel</link>.</para>
1252 </orderedlist></para>
1255 <primary>IRIX</primary>
1257 <secondary>AFS kernel extensions</secondary>
1259 <tertiary>on first AFS machine</tertiary>
1263 <primary>afsml variable (IRIX)</primary>
1265 <secondary>first AFS machine</secondary>
1269 <primary>variables</primary>
1271 <secondary>afsml (IRIX)</secondary>
1273 <tertiary>first AFS machine</tertiary>
1277 <primary>IRIX</primary>
1279 <secondary>afsml variable</secondary>
1281 <tertiary>first AFS machine</tertiary>
1285 <primary>afsxnfs variable (IRIX)</primary>
1287 <secondary>first AFS machine</secondary>
1291 <primary>variables</primary>
1293 <secondary>afsxnfs (IRIX)</secondary>
1295 <tertiary>first AFS machine</tertiary>
1299 <primary>IRIX</primary>
1301 <secondary>afsxnfs variable</secondary>
1303 <tertiary>first AFS machine</tertiary>
1306 <sect2 id="HDRWQ37">
1307 <title>Loading AFS into the IRIX Kernel</title>
1309 <para>The <emphasis role="bold">ml</emphasis> program is the dynamic kernel loader provided by SGI for IRIX systems. If you
1310 use it rather than building AFS modifications into a static kernel, then for AFS to function correctly the <emphasis
1311 role="bold">ml</emphasis> program must run each time the machine reboots. Therefore, the AFS initialization script (included
1312 on the AFS CD-ROM) invokes it automatically when the <emphasis role="bold">afsml</emphasis> configuration variable is
1313 activated. In this section you activate the variable and run the script.</para>
1315 <para>In later sections you verify that the script correctly initializes all AFS components, then create the links that
1316 incorporate AFS into the IRIX startup and shutdown sequence. <orderedlist>
1318 <para>Create the local <emphasis role="bold">/usr/vice/etc/sgiload</emphasis> directory to house the AFS kernel library
1319 file. <programlisting>
1320 # <emphasis role="bold">mkdir /usr/vice/etc/sgiload</emphasis>
1321 </programlisting></para>
1325 <para>Copy the appropriate AFS kernel library file to the <emphasis role="bold">/usr/vice/etc/sgiload</emphasis>
1326 directory. The <emphasis role="bold">IP</emphasis><replaceable>xx</replaceable> portion of the library file name must
1327 match the value previously returned by the <emphasis role="bold">uname -m</emphasis> command. Also choose the file
1328 appropriate to whether the machine's kernel supports NFS server functionality (NFS must be supported for the machine to
1329 act as an NFS/AFS Translator). Single- and multiprocessor machines use the same library file.</para>
1331 <para>(You can choose to copy all of the kernel library files into the <emphasis
1332 role="bold">/usr/vice/etc/sgiload</emphasis> directory, but they require a significant amount of space.)</para>
1334 <para>If the machine's kernel supports NFS server functionality:</para>
1337 # <emphasis role="bold">cp -p usr/vice/etc/sgiload/libafs.IP</emphasis><replaceable>xx</replaceable><emphasis role="bold">.o /usr/vice/etc/sgiload</emphasis>
1340 <para>If the machine's kernel does not support NFS server functionality:</para>
1343 # <emphasis role="bold">cp -p usr/vice/etc/sgiload/libafs.IP</emphasis><replaceable>xx</replaceable><emphasis role="bold">.nonfs.o</emphasis> \
1344 <emphasis role="bold">/usr/vice/etc/sgiload</emphasis>
1349 <para>Issue the <emphasis role="bold">chkconfig</emphasis> command to activate the <emphasis
1350 role="bold">afsml</emphasis> configuration variable. <programlisting>
1351 # <emphasis role="bold">/etc/chkconfig -f afsml on</emphasis>
1352 </programlisting></para>
1354 <para>If the machine is to function as an NFS/AFS Translator and the kernel supports NFS server functionality, activate
1355 the <emphasis role="bold">afsxnfs</emphasis> variable.</para>
1358 # <emphasis role="bold">/etc/chkconfig -f afsxnfs on</emphasis>
1363 <para>Run the <emphasis role="bold">/etc/init.d/afs</emphasis> script to load AFS extensions into the kernel. The script
1364 invokes the <emphasis role="bold">ml</emphasis> command, automatically determining which kernel library file to use
1365 based on this machine's CPU type and the activation state of the <emphasis role="bold">afsxnfs</emphasis>
1368 <para>You can ignore any error messages about the inability to start the BOS Server or the Cache Manager or AFS
1372 # <emphasis role="bold">/etc/init.d/afs start</emphasis>
1377 <para>Proceed to <link linkend="HDRWQ39">Configuring Server Partitions on IRIX Systems</link>.</para>
1379 </orderedlist></para>
1382 <primary>IRIX</primary>
1384 <secondary>AFS-modified kernel</secondary>
1386 <tertiary>on first AFS machine</tertiary>
1390 <sect2 id="HDRWQ38">
1391 <title>Building AFS into the IRIX Kernel</title>
1393 <para>Use the following instructions to build AFS modifications into the kernel on an IRIX system. <orderedlist>
1395 <para>Copy the kernel initialization file <emphasis role="bold">afs.sm</emphasis> to the local <emphasis
1396 role="bold">/var/sysgen/system</emphasis> directory, and the kernel master file <emphasis role="bold">afs</emphasis> to
1397 the local <emphasis role="bold">/var/sysgen/master.d</emphasis> directory. <programlisting>
1398 # <emphasis role="bold">cp -p bin/afs.sm /var/sysgen/system</emphasis>
1399 # <emphasis role="bold">cp -p bin/afs /var/sysgen/master.d</emphasis>
1400 </programlisting></para>
1404 <para>Copy the appropriate AFS kernel library file to the local file <emphasis
1405 role="bold">/var/sysgen/boot/afs.a</emphasis>; the <emphasis role="bold">IP</emphasis><replaceable>xx</replaceable>
1406 portion of the library file name must match the value previously returned by the <emphasis role="bold">uname
1407 -m</emphasis> command. Also choose the file appropriate to whether the machine's kernel supports NFS server
1408 functionality (NFS must be supported for the machine to act as an NFS/AFS Translator). Single- and multiprocessor
1409 machines use the same library file.</para>
1411 <para>If the machine's kernel supports NFS server functionality:</para>
1414 # <emphasis role="bold">cp -p bin/libafs.IP</emphasis><replaceable>xx</replaceable><emphasis role="bold">.a /var/sysgen/boot/afs.a</emphasis>
1417 <para>If the machine's kernel does not support NFS server functionality:</para>
1420 # <emphasis role="bold">cp -p bin/libafs.IP</emphasis><replaceable>xx</replaceable><emphasis role="bold">.nonfs.a /var/sysgen/boot/afs.a</emphasis>
1425 <para>Issue the <emphasis role="bold">chkconfig</emphasis> command to deactivate the <emphasis
1426 role="bold">afsml</emphasis> configuration variable. <programlisting>
1427 # <emphasis role="bold">/etc/chkconfig -f afsml off</emphasis>
1428 </programlisting></para>
1430 <para>If the machine is to function as an NFS/AFS Translator and the kernel supports NFS server functionality, activate
1431 the <emphasis role="bold">afsxnfs</emphasis> variable.</para>
1434 # <emphasis role="bold">/etc/chkconfig -f afsxnfs on</emphasis>
1439 <para>Copy the existing kernel file, <emphasis role="bold">/unix</emphasis>, to a safe location. Compile the new kernel,
1440 which is created in the file <emphasis role="bold">/unix.install</emphasis>. It overwrites the existing <emphasis
1441 role="bold">/unix</emphasis> file when the machine reboots in the next step. <programlisting>
1442 # <emphasis role="bold">cp /unix /unix_noafs</emphasis>
1443 # <emphasis role="bold">autoconfig</emphasis>
1444 </programlisting></para>
1448 <para>Reboot the machine to start using the new kernel, and login again as the superuser <emphasis
1449 role="bold">root</emphasis>. <programlisting>
1450 # <emphasis role="bold">cd /</emphasis>
1451 # <emphasis role="bold">shutdown -i6 -g0 -y</emphasis>
1452 login: <emphasis role="bold">root</emphasis>
1453 Password: <replaceable>root_password</replaceable>
1454 </programlisting></para>
1456 </orderedlist></para>
1459 <primary>configuring</primary>
1461 <secondary>AFS server partition on first AFS machine</secondary>
1463 <tertiary>IRIX</tertiary>
1467 <primary>AFS server partition</primary>
1469 <secondary>configuring on first AFS machine</secondary>
1471 <tertiary>IRIX</tertiary>
1475 <primary>first AFS machine</primary>
1477 <secondary>AFS server partition</secondary>
1479 <tertiary>on IRIX</tertiary>
1483 <primary>IRIX</primary>
1485 <secondary>AFS server partition</secondary>
1487 <tertiary>on first AFS machine</tertiary>
1491 <sect2 id="HDRWQ39">
1492 <title>Configuring Server Partitions on IRIX Systems</title>
1494 <para>Every AFS file server machine must have at least one partition or logical volume dedicated to storing AFS volumes. Each
1495 server partition is mounted at a directory named <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>, where
1496 <replaceable>xx</replaceable> is one or two lowercase letters. The <emphasis
1497 role="bold">/vicep</emphasis><replaceable>xx</replaceable> directories must reside in the file server machine's root
1498 directory, not in one of its subdirectories (for example, <emphasis role="bold">/usr/vicepa</emphasis> is not an acceptable
1499 directory location). For additional information, see <link linkend="HDRWQ20">Performing Platform-Specific
1500 Procedures</link>.</para>
1502 <para>AFS supports use of both EFS and XFS partitions for housing AFS volumes. SGI encourages use of XFS partitions.
1505 <para>Create a directory called <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable> for each AFS server
1506 partition you are configuring (there must be at least one). Repeat the command for each partition. <programlisting>
1507 # <emphasis role="bold">mkdir /vicep</emphasis><replaceable>xx</replaceable>
1508 </programlisting></para>
1512 <para>Add a line with the following format to the file systems registry file, <emphasis
1513 role="bold">/etc/fstab</emphasis>, for each partition (or logical volume created with the XLV volume manager) to be
1514 mounted on one of the directories created in the previous step.</para>
1516 <para>For an XFS partition or logical volume:</para>
1519 /dev/dsk/<replaceable>disk</replaceable> /vicep<replaceable>xx</replaceable> xfs rw,raw=/dev/rdsk/<replaceable>disk</replaceable> 0 0
1522 <para>For an EFS partition:</para>
1525 /dev/dsk/<replaceable>disk</replaceable> /vicep<replaceable>xx</replaceable> efs rw,raw=/dev/rdsk/<replaceable>disk</replaceable> 0 0
1528 <para>The following are examples of an entry for each file system type:</para>
1531 /dev/dsk/dks0d2s6 /vicepa xfs rw,raw=/dev/rdsk/dks0d2s6 0 0
1532 /dev/dsk/dks0d3s1 /vicepb efs rw,raw=/dev/rdsk/dks0d3s1 0 0
1537 <para>Create a file system on each partition that is to be mounted on a <emphasis
1538 role="bold">/vicep</emphasis><replaceable>xx</replaceable> directory. The following commands are probably appropriate,
1539 but consult the IRIX documentation for more information. In both cases, <replaceable>raw_device</replaceable> is a raw
1540 device name like <emphasis role="bold">/dev/rdsk/dks0d0s0</emphasis> for a single disk partition or <emphasis
1541 role="bold">/dev/rxlv/xlv0</emphasis> for a logical volume.</para>
1543 <para>For XFS file systems, include the indicated options to configure the partition or logical volume with inodes large
1544 enough to accommodate AFS-specific information:</para>
1547 # <emphasis role="bold">mkfs -t xfs -i size=512 -l size=4000b</emphasis> <replaceable>raw_device</replaceable>
1550 <para>For EFS file systems:</para>
1553 # <emphasis role="bold">mkfs -t efs</emphasis> <replaceable>raw_device</replaceable>
1558 <para>Mount each partition by issuing either the <emphasis role="bold">mount -a</emphasis> command to mount all
1559 partitions at once or the <emphasis role="bold">mount</emphasis> command to mount each partition in turn.</para>
1563 <para><emphasis role="bold">(Optional)</emphasis> If you have configured partitions or logical volumes to use XFS, issue
1564 the following command to verify that the inodes are configured properly (are large enough to accommodate AFS-specific
1565 information). If the configuration is correct, the command returns no output. Otherwise, it specifies the command to run
1566 in order to configure each partition or logical volume properly. <programlisting>
1567 # <emphasis role="bold">/usr/afs/bin/xfs_size_check</emphasis>
1568 </programlisting></para>
1572 <para>If you plan to retain client functionality on this machine after completing the installation, proceed to <link
1573 linkend="HDRWQ40">Enabling AFS Login on IRIX Systems</link>. Otherwise, proceed to <link linkend="HDRWQ50">Starting the
1574 BOS Server</link>.</para>
1576 </orderedlist></para>
1579 <primary>enabling AFS login</primary>
1581 <secondary>file server machine</secondary>
1583 <tertiary>IRIX</tertiary>
1587 <primary>AFS login</primary>
1589 <secondary>on file server machine</secondary>
1591 <tertiary>IRIX</tertiary>
1595 <primary>first AFS machine</primary>
1597 <secondary>AFS login</secondary>
1599 <tertiary>on IRIX</tertiary>
1603 <primary>IRIX</primary>
1605 <secondary>AFS login</secondary>
1609 <sect2 id="HDRWQ40">
1610 <title>Enabling AFS Login on IRIX Systems</title>
1613 <para>If you plan to remove client functionality from this machine after completing the installation, skip this section and
1614 proceed to <link linkend="HDRWQ50">Starting the BOS Server</link>.</para>
1617 <para>Whilst the standard IRIX command-line
1618 <emphasis role="bold">login</emphasis> program and the
1619 graphical <emphasis role="bold">xdm</emphasis> login program both have
1620 the ability to grant AFS tokens, this ability relies upon the deprecated
1621 kaserver authentication system.</para>
1623 <para>Users who have been successfully authenticated via Kerberos 5
1624 authentication may obtain AFS tokens following login by running the
1625 <emphasis role="bold">aklog</emphasis> command.</para>
1627 <para>Sites which still require <emphasis role="bold">kaserver</emphasis>
1628 or external Kerberos v4 authentication should consult
1629 <link linkend="KAS014">Enabling kaserver based AFS Login on IRIX Systems</link>
1630 for details of how to enable IRIX login.</para>
1632 <para>After taking any necessary action, proceed to
1633 <link linkend="HDRWQ50">Starting the BOS Server</link>.</para>
1637 <sect1 id="HDRWQ41">
1638 <title>Getting Started on Linux Systems</title>
1641 <primary>replacing fsck program</primary>
1643 <secondary>not necessary on Linux</secondary>
1647 <primary>fsck program</primary>
1649 <secondary>on first AFS machine</secondary>
1651 <tertiary>Linux</tertiary>
1655 <primary>first AFS machine</primary>
1657 <secondary>fsck program</secondary>
1659 <tertiary>on Linux</tertiary>
1663 <primary>Linux</primary>
1665 <secondary>fsck program replacement not necessary</secondary>
1668 <para>Since this guide was originally written, the procedure for starting
1669 OpenAFS has diverged significantly between different Linux distributions.
1670 The instructions that follow are appropriate for both the Fedora and
1671 RedHat Enterprise Linux packages distributed by OpenAFS. Additional
1672 instructions are provided for those building from source.</para>
1674 <para>Begin by running the AFS client startup scripts, which call the <emphasis role="bold">modprobe</emphasis> program, which
1675 dynamically loads AFS modifications into the kernel. Then create partitions for storing AFS volumes. You do not need to replace
1676 the Linux <emphasis role="bold">fsck</emphasis> program. If the machine is to remain an AFS client machine, incorporate AFS into
1677 the machine's Pluggable Authentication Module (PAM) scheme. <indexterm>
1678 <primary>incorporating AFS kernel extensions</primary>
1680 <secondary>first AFS machine</secondary>
1682 <tertiary>Linux</tertiary>
1683 </indexterm> <indexterm>
1684 <primary>AFS kernel extensions</primary>
1686 <secondary>on first AFS machine</secondary>
1688 <tertiary>Linux</tertiary>
1689 </indexterm> <indexterm>
1690 <primary>first AFS machine</primary>
1692 <secondary>AFS kernel extensions</secondary>
1694 <tertiary>on Linux</tertiary>
1695 </indexterm> <indexterm>
1696 <primary>Linux</primary>
1698 <secondary>AFS kernel extensions</secondary>
1700 <tertiary>on first AFS machine</tertiary>
1703 <sect2 id="HDRWQ42">
1704 <title>Loading AFS into the Linux Kernel</title>
1706 <para>The <emphasis role="bold">modprobe</emphasis> program is the dynamic kernel loader for Linux. Linux does not support
1707 incorporation of AFS modifications during a kernel build.</para>
1709 <para>For AFS to function correctly, the <emphasis role="bold">modprobe</emphasis> program must run each time the machine
1710 reboots, so your distribution's AFS initialization script invokes it automatically. The script also includes
1711 commands that select the appropriate AFS library file automatically. In this section you run the script.</para>
1713 <para>In later sections you verify that the script correctly initializes all AFS components, then activate a configuration
1714 variable, which results in the script being incorporated into the Linux startup and shutdown sequence.</para>
1716 <para>The procedure for starting up OpenAFS depends upon your distribution</para>
1718 <title>Fedora and RedHat Enterprise Linux</title>
1719 <para>OpenAFS ship RPMS for all current Fedora and RHEL releases.
1722 <para>Download and install the RPM set for your operating system.
1723 RPMs are available from the OpenAFS web site. You will need the
1724 <emphasis role="bold">openafs</emphasis>
1725 <emphasis role="bold">openafs-client></emphasis>
1726 <emphasis role="bold">openafs-server</emphasis> packages, along with
1727 an <emphasis role="bold">openafs-kernel</emphasis> package matching
1728 your current, running, kernel.</para>
1729 <para>You can find the version of your current kernel by running
1732 <replaceable>2.6.20-1.2933.fc6</replaceable>
1733 </programlisting></para>
1734 <para>Once downloaded, the packages may be installed with the
1735 <emphasis role="bold">rpm</emphasis> command
1737 # rpm -U openafs-* openafs-client-* openafs-server-* openafs-kernel-*
1738 </programlisting></para>
1740 <!-- If you do this with current RHEL and Fedora releases you end up with
1741 a dynroot'd client running - this breaks setting up the root.afs volume
1742 as described later in this guide
1744 <para>Run the AFS initialization script to load AFS extensions into
1745 the kernel. You can ignore any error messages about the inability
1746 to start the BOS Server or the Cache Manager or AFS client.</para>
1748 # <emphasis role="bold">/etc/rc.d/init.d/openafs-client start</emphasis>
1756 <title>Systems packaged as tar files</title>
1757 <para>If you are running a system where the OpenAFS Binary Distribution
1758 is provided as a tar file, or where you have built the system from
1759 source yourself, you need to install the relevant components by hand
1764 <para>Unpack the distribution tarball. The examples below assume
1765 that you have unpacked the files into the
1766 <emphasis role="bold">/tmp/afsdist</emphasis>directory. If you
1767 pick a different location, substitute this in all of the following
1768 examples. Once you have unpacked the distribution,
1769 change directory as indicated.
1771 # <emphasis role="bold">cd /tmp/afsdist/linux/root.client/usr/vice/etc</emphasis>
1772 </programlisting></para>
1776 <para>Copy the AFS kernel library files to the local <emphasis role="bold">/usr/vice/etc/modload</emphasis> directory.
1777 The filenames for the libraries have the format <emphasis
1778 role="bold">libafs-</emphasis><replaceable>version</replaceable><emphasis role="bold">.o</emphasis>, where
1779 <replaceable>version</replaceable> indicates the kernel build level. The string <emphasis role="bold">.mp</emphasis> in
1780 the <replaceable>version</replaceable> indicates that the file is appropriate for machines running a multiprocessor
1781 kernel. <programlisting>
1782 # <emphasis role="bold">cp -rp modload /usr/vice/etc</emphasis>
1783 </programlisting></para>
1787 <para>Copy the AFS initialization script to the local directory for initialization files (by convention, <emphasis
1788 role="bold">/etc/rc.d/init.d</emphasis> on Linux machines). Note the removal of the <emphasis role="bold">.rc</emphasis>
1789 extension as you copy the script. <programlisting>
1790 # <emphasis role="bold">cp -p afs.rc /etc/rc.d/init.d/afs</emphasis>
1791 </programlisting></para>
1794 <!-- I don't think we need to do this for Linux, and it complicates things if
1795 dynroot is enabled ...
1797 <para>Run the AFS initialization script to load AFS extensions into the kernel. You can ignore any error messages about
1798 the inability to start the BOS Server or the Cache Manager or AFS client.</para>
1800 # <emphasis role="bold">/etc/rc.d/init.d/afs start</emphasis>
1807 <primary>configuring</primary>
1809 <secondary>AFS server partition on first AFS machine</secondary>
1811 <tertiary>Linux</tertiary>
1815 <primary>AFS server partition</primary>
1817 <secondary>configuring on first AFS machine</secondary>
1819 <tertiary>Linux</tertiary>
1823 <primary>first AFS machine</primary>
1825 <secondary>AFS server partition</secondary>
1827 <tertiary>on Linux</tertiary>
1831 <primary>Linux</primary>
1833 <secondary>AFS server partition</secondary>
1835 <tertiary>on first AFS machine</tertiary>
1840 <sect2 id="HDRWQ43">
1841 <title>Configuring Server Partitions on Linux Systems</title>
1843 <para>Every AFS file server machine must have at least one partition or logical volume dedicated to storing AFS volumes. Each
1844 server partition is mounted at a directory named <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>, where
1845 <replaceable>xx</replaceable> is one or two lowercase letters. The <emphasis
1846 role="bold">/vicep</emphasis><replaceable>xx</replaceable> directories must reside in the file server machine's root
1847 directory, not in one of its subdirectories (for example, <emphasis role="bold">/usr/vicepa</emphasis> is not an acceptable
1848 directory location). For additional information, see <link linkend="HDRWQ20">Performing Platform-Specific Procedures</link>.
1851 <para>Create a directory called <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable> for each AFS server
1852 partition you are configuring (there must be at least one). Repeat the command for each partition. <programlisting>
1853 # <emphasis role="bold">mkdir /vicep</emphasis><replaceable>xx</replaceable>
1854 </programlisting></para>
1858 <para>Add a line with the following format to the file systems registry file, <emphasis
1859 role="bold">/etc/fstab</emphasis>, for each directory just created. The entry maps the directory name to the disk
1860 partition to be mounted on it. <programlisting>
1861 /dev/<replaceable>disk</replaceable> /vicep<replaceable>xx</replaceable> ext2 defaults 0 2
1862 </programlisting></para>
1864 <para>The following is an example for the first partition being configured.</para>
1867 /dev/sda8 /vicepa ext2 defaults 0 2
1872 <para>Create a file system on each partition that is to be mounted at a <emphasis
1873 role="bold">/vicep</emphasis><replaceable>xx</replaceable> directory. The following command is probably appropriate, but
1874 consult the Linux documentation for more information. <programlisting>
1875 # <emphasis role="bold">mkfs -v /dev/</emphasis><replaceable>disk</replaceable>
1876 </programlisting></para>
1880 <para>Mount each partition by issuing either the <emphasis role="bold">mount -a</emphasis> command to mount all
1881 partitions at once or the <emphasis role="bold">mount</emphasis> command to mount each partition in turn.</para>
1885 <para>If you plan to retain client functionality on this machine after completing the installation, proceed to <link
1886 linkend="HDRWQ44">Enabling AFS Login on Linux Systems</link>. Otherwise, proceed to <link linkend="HDRWQ50">Starting the
1887 BOS Server</link>.</para>
1889 </orderedlist></para>
1892 <primary>enabling AFS login</primary>
1894 <secondary>file server machine</secondary>
1896 <tertiary>Linux</tertiary>
1900 <primary>AFS login</primary>
1902 <secondary>on file server machine</secondary>
1904 <tertiary>Linux</tertiary>
1908 <primary>first AFS machine</primary>
1910 <secondary>AFS login</secondary>
1912 <tertiary>on Linux</tertiary>
1916 <primary>Linux</primary>
1918 <secondary>AFS login</secondary>
1920 <tertiary>on file server machine</tertiary>
1924 <primary>PAM</primary>
1926 <secondary>on Linux</secondary>
1928 <tertiary>file server machine</tertiary>
1932 <sect2 id="HDRWQ44">
1933 <title>Enabling AFS Login on Linux Systems</title>
1936 <para>If you plan to remove client functionality from this machine after completing the installation, skip this section and
1937 proceed to <link linkend="HDRWQ50">Starting the BOS Server</link>.</para>
1940 <para>At this point you incorporate AFS into the operating system's Pluggable Authentication Module (PAM) scheme. PAM
1941 integrates all authentication mechanisms on the machine, including login, to provide the security infrastructure for
1942 authenticated access to and from the machine.</para>
1944 <para>At this time, we recommend that new sites requiring AFS credentials
1945 to be gained as part of PAM authentication use Russ Alberry's
1946 pam_afs_session, rather than utilising the bundled pam_afs2 module.
1947 A typical PAM stack should authenticate the user using an external
1948 Kerberos V service, and then use the AFS PAM module to obtain AFS
1949 credentials in the <computeroutput>session</computeroutput> section</para>
1951 <para>Sites which still require <emphasis role="bold">kaserver</emphasis>
1952 or external Kerberos v4 authentication should consult
1953 <link linkend="KAS015">Enabling kaserver based AFS Login on Linux Systems</link>
1954 for details of how to enable AFS login on Linux.</para>
1956 <para>Proceed to <link linkend="HDRWQ50">Starting the BOS Server</link>
1957 (or if referring to these instructions while installing an additional
1958 file server machine, return to <link linkend="HDRWQ108">Starting Server
1959 Programs</link>).</para>
1963 <sect1 id="HDRWQ45">
1964 <title>Getting Started on Solaris Systems</title>
1966 <para>Begin by running the AFS initialization script to call the <emphasis role="bold">modload</emphasis> program distributed by
1967 Sun Microsystems, which dynamically loads AFS modifications into the kernel. Then create partitions for storing AFS volumes, and
1968 install and configure the AFS-modified <emphasis role="bold">fsck</emphasis> program to run on AFS server partitions. If the
1969 machine is to remain an AFS client machine, incorporate AFS into the machine's Pluggable Authentication Module (PAM) scheme.
1971 <primary>incorporating AFS kernel extensions</primary>
1973 <secondary>first AFS machine</secondary>
1975 <tertiary>Solaris</tertiary>
1976 </indexterm> <indexterm>
1977 <primary>AFS kernel extensions</primary>
1979 <secondary>on first AFS machine</secondary>
1981 <tertiary>Solaris</tertiary>
1982 </indexterm> <indexterm>
1983 <primary>first AFS machine</primary>
1985 <secondary>AFS kernel extensions</secondary>
1987 <tertiary>on Solaris</tertiary>
1988 </indexterm> <indexterm>
1989 <primary>Solaris</primary>
1991 <secondary>AFS kernel extensions</secondary>
1993 <tertiary>on first AFS machine</tertiary>
1996 <sect2 id="HDRWQ46">
1997 <title>Loading AFS into the Solaris Kernel</title>
1999 <para>The <emphasis role="bold">modload</emphasis> program is the dynamic kernel loader provided by Sun Microsystems for
2000 Solaris systems. Solaris does not support incorporation of AFS modifications during a kernel build.</para>
2002 <para>For AFS to function correctly, the <emphasis role="bold">modload</emphasis> program must run each time the machine
2003 reboots, so the AFS initialization script (included on the AFS CD-ROM) invokes it automatically. In this section you copy the
2004 appropriate AFS library file to the location where the <emphasis role="bold">modload</emphasis> program accesses it and then
2005 run the script.</para>
2007 <para>In later sections you verify that the script correctly initializes all AFS components, then create the links that
2008 incorporate AFS into the Solaris startup and shutdown sequence. <orderedlist>
2010 <para>Unpack the OpenAFS Solaris distribution tarball. The examples
2011 below assume that you have unpacked the files into the
2012 <emphasis role="bold">/tmp/afsdist</emphasis> directory. If you
2013 pick a diferent location, substitute this in all of the following
2014 exmaples. Once you have unpacked the distribution, change directory
2017 # <emphasis role="bold">cd /tmp/afsdist/sun4x_56/root.client/usr/vice/etc</emphasis>
2018 </programlisting></para>
2022 <para>Copy the AFS initialization script to the local directory for initialization files (by convention, <emphasis
2023 role="bold">/etc/init.d</emphasis> on Solaris machines). Note the removal of the <emphasis role="bold">.rc</emphasis>
2024 extension as you copy the script. <programlisting>
2025 # <emphasis role="bold">cp -p afs.rc /etc/init.d/afs</emphasis>
2026 </programlisting></para>
2030 <para>Copy the appropriate AFS kernel library file to the local file <emphasis
2031 role="bold">/kernel/fs/afs</emphasis>.</para>
2033 <para>If the machine is running Solaris 2.6 or the 32-bit version of Solaris 7, its kernel supports NFS server
2034 functionality, and the <emphasis role="bold">nfsd</emphasis> process is running:</para>
2037 # <emphasis role="bold">cp -p modload/libafs.o /kernel/fs/afs</emphasis>
2040 <para>If the machine is running Solaris 2.6 or the 32-bit version of Solaris 7, and its kernel does not support NFS
2041 server functionality or the <emphasis role="bold">nfsd</emphasis> process is not running:</para>
2044 # <emphasis role="bold">cp -p modload/libafs.nonfs.o /kernel/fs/afs</emphasis>
2047 <para>If the machine is running the 64-bit version of Solaris 7, its kernel supports NFS server functionality, and the
2048 <emphasis role="bold">nfsd</emphasis> process is running:</para>
2051 # <emphasis role="bold">cp -p modload/libafs64.o /kernel/fs/sparcv9/afs</emphasis>
2054 <para>If the machine is running the 64-bit version of Solaris 7, and its kernel does not support NFS server
2055 functionality or the <emphasis role="bold">nfsd</emphasis> process is not running:</para>
2058 # <emphasis role="bold">cp -p modload/libafs64.nonfs.o /kernel/fs/sparcv9/afs</emphasis>
2063 <para>Run the AFS initialization script to load AFS modifications into the kernel. You can ignore any error messages
2064 about the inability to start the BOS Server or the Cache Manager or AFS client. <programlisting>
2065 # <emphasis role="bold">/etc/init.d/afs start</emphasis>
2066 </programlisting></para>
2068 <para>When an entry called <computeroutput>afs</computeroutput> does not already exist in the local <emphasis
2069 role="bold">/etc/name_to_sysnum</emphasis> file, the script automatically creates it and reboots the machine to start
2070 using the new version of the file. If this happens, log in again as the superuser <emphasis role="bold">root</emphasis>
2071 after the reboot and run the initialization script again. This time the required entry exists in the <emphasis
2072 role="bold">/etc/name_to_sysnum</emphasis> file, and the <emphasis role="bold">modload</emphasis> program runs.</para>
2075 login: <emphasis role="bold">root</emphasis>
2076 Password: <replaceable>root_password</replaceable>
2077 # <emphasis role="bold">/etc/init.d/afs start</emphasis>
2080 </orderedlist></para>
2083 <primary>replacing fsck program</primary>
2085 <secondary>first AFS machine</secondary>
2087 <tertiary>Solaris</tertiary>
2091 <primary>fsck program</primary>
2093 <secondary>on first AFS machine</secondary>
2095 <tertiary>Solaris</tertiary>
2099 <primary>first AFS machine</primary>
2101 <secondary>fsck program</secondary>
2103 <tertiary>on Solaris</tertiary>
2107 <primary>Solaris</primary>
2109 <secondary>fsck program</secondary>
2111 <tertiary>on first AFS machine</tertiary>
2115 <sect2 id="HDRWQ47">
2116 <title>Configuring the AFS-modified fsck Program on Solaris Systems</title>
2118 <para>In this section, you make modifications to guarantee that the appropriate <emphasis role="bold">fsck</emphasis> program
2119 runs on AFS server partitions. The <emphasis role="bold">fsck</emphasis> program provided with the operating system must never
2120 run on AFS server partitions. Because it does not recognize the structures that the File Server uses to organize volume data,
2121 it removes all of the data. To repeat:</para>
2123 <para><emphasis role="bold">Never run the standard fsck program on AFS server partitions. It discards AFS volumes.</emphasis>
2126 <para>Create the <emphasis role="bold">/usr/lib/fs/afs</emphasis> directory to house the AFS-modified <emphasis
2127 role="bold">fsck</emphasis> program and related files. <programlisting>
2128 # <emphasis role="bold">mkdir /usr/lib/fs/afs</emphasis>
2129 # <emphasis role="bold">cd /usr/lib/fs/afs</emphasis>
2130 </programlisting></para>
2134 <para>Copy the <emphasis role="bold">vfsck</emphasis> binary to the newly created directory, changing the name as you do
2135 so. <programlisting>
2136 # <emphasis role="bold">cp /tmp/afsdist/sun4x_56/root.server/etc/vfsck fsck</emphasis>
2137 </programlisting></para>
2141 <para>Working in the <emphasis role="bold">/usr/lib/fs/afs</emphasis> directory, create the following links to Solaris
2142 libraries: <programlisting>
2143 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/clri</emphasis>
2144 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/df</emphasis>
2145 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/edquota</emphasis>
2146 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/ff</emphasis>
2147 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/fsdb</emphasis>
2148 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/fsirand</emphasis>
2149 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/fstyp</emphasis>
2150 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/labelit</emphasis>
2151 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/lockfs</emphasis>
2152 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/mkfs</emphasis>
2153 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/mount</emphasis>
2154 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/ncheck</emphasis>
2155 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/newfs</emphasis>
2156 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/quot</emphasis>
2157 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/quota</emphasis>
2158 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/quotaoff</emphasis>
2159 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/quotaon</emphasis>
2160 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/repquota</emphasis>
2161 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/tunefs</emphasis>
2162 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/ufsdump</emphasis>
2163 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/ufsrestore</emphasis>
2164 # <emphasis role="bold">ln -s /usr/lib/fs/ufs/volcopy</emphasis>
2165 </programlisting></para>
2169 <para>Append the following line to the end of the file <emphasis role="bold">/etc/dfs/fstypes</emphasis>.
2172 </programlisting></para>
2176 <para>Edit the <emphasis role="bold">/sbin/mountall</emphasis> file, making two changes. <itemizedlist>
2178 <para>Add an entry for AFS to the <computeroutput>case</computeroutput> statement for option 2, so that it reads
2179 as follows: <programlisting>
2181 ufs) foptions="-o p"
2183 afs) foptions="-o p"
2185 s5) foptions="-y -t /var/tmp/tmp$$ -D"
2189 </programlisting></para>
2193 <para>Edit the file so that all AFS and UFS partitions are checked in parallel. Replace the following section of
2194 code: <programlisting>
2195 # For fsck purposes, we make a distinction between ufs and
2196 # other file systems
2198 if [ "$fstype" = "ufs" ]; then
2199 ufs_fscklist="$ufs_fscklist $fsckdev"
2200 saveentry $fstype "$OPTIONS" $special $mountp
2203 </programlisting></para>
2205 <para>with the following section of code:</para>
2208 # For fsck purposes, we make a distinction between ufs/afs
2209 # and other file systems.
2211 if [ "$fstype" = "ufs" -o "$fstype" = "afs" ]; then
2212 ufs_fscklist="$ufs_fscklist $fsckdev"
2213 saveentry $fstype "$OPTIONS" $special $mountp
2218 </itemizedlist></para>
2220 </orderedlist></para>
2223 <primary>configuring</primary>
2225 <secondary>AFS server partition on first AFS machine</secondary>
2227 <tertiary>Solaris</tertiary>
2231 <primary>AFS server partition</primary>
2233 <secondary>configuring on first AFS machine</secondary>
2235 <tertiary>Solaris</tertiary>
2239 <primary>first AFS machine</primary>
2241 <secondary>AFS server partition</secondary>
2243 <tertiary>on Solaris</tertiary>
2247 <primary>Solaris</primary>
2249 <secondary>AFS server partition</secondary>
2251 <tertiary>on first AFS machine</tertiary>
2255 <sect2 id="HDRWQ48">
2256 <title>Configuring Server Partitions on Solaris Systems</title>
2258 <para>Every AFS file server machine must have at least one partition or logical volume dedicated to storing AFS volumes. Each
2259 server partition is mounted at a directory named <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable>, where
2260 <replaceable>xx</replaceable> is one or two lowercase letters. The <emphasis
2261 role="bold">/vicep</emphasis><replaceable>xx</replaceable> directories must reside in the file server machine's root
2262 directory, not in one of its subdirectories (for example, <emphasis role="bold">/usr/vicepa</emphasis> is not an acceptable
2263 directory location). For additional information, see <link linkend="HDRWQ20">Performing Platform-Specific Procedures</link>.
2266 <para>Create a directory called <emphasis role="bold">/vicep</emphasis><replaceable>xx</replaceable> for each AFS server
2267 partition you are configuring (there must be at least one). Repeat the command for each partition. <programlisting>
2268 # <emphasis role="bold">mkdir /vicep</emphasis><replaceable>xx</replaceable>
2269 </programlisting></para>
2273 <para>Add a line with the following format to the file systems registry file, <emphasis
2274 role="bold">/etc/vfstab</emphasis>, for each partition to be mounted on a directory created in the previous step. Note
2275 the value <computeroutput>afs</computeroutput> in the fourth field, which tells Solaris to use the AFS-modified
2276 <emphasis role="bold">fsck</emphasis> program on this partition. <programlisting>
2277 /dev/dsk/<replaceable>disk</replaceable> /dev/rdsk/<replaceable>disk</replaceable> /vicep<replaceable>xx</replaceable> afs <replaceable>boot_order</replaceable> yes
2278 </programlisting></para>
2280 <para>The following is an example for the first partition being configured.</para>
2283 /dev/dsk/c0t6d0s1 /dev/rdsk/c0t6d0s1 /vicepa afs 3 yes
2288 <para>Create a file system on each partition that is to be mounted at a <emphasis
2289 role="bold">/vicep</emphasis><replaceable>xx</replaceable> directory. The following command is probably appropriate, but
2290 consult the Solaris documentation for more information. <programlisting>
2291 # <emphasis role="bold">newfs -v /dev/rdsk/</emphasis><replaceable>disk</replaceable>
2292 </programlisting></para>
2296 <para>Issue the <emphasis role="bold">mountall</emphasis> command to mount all partitions at once.</para>
2300 <para>If you plan to retain client functionality on this machine after completing the installation, proceed to <link
2301 linkend="HDRWQ49">Enabling AFS Login and Editing the File Systems Clean-up Script on Solaris Systems</link>. Otherwise,
2302 proceed to <link linkend="HDRWQ50">Starting the BOS Server</link>.</para>
2304 </orderedlist></para>
2307 <sect2 id="HDRWQ49">
2308 <title>Enabling AFS Login on Solaris Systems</title>
2310 <primary>enabling AFS login</primary>
2312 <secondary>file server machine</secondary>
2314 <tertiary>Solaris</tertiary>
2318 <primary>AFS login</primary>
2320 <secondary>on file server machine</secondary>
2322 <tertiary>Solaris</tertiary>
2326 <primary>first AFS machine</primary>
2328 <secondary>AFS login</secondary>
2330 <tertiary>on Solaris</tertiary>
2334 <primary>Solaris</primary>
2336 <secondary>AFS login</secondary>
2338 <tertiary>on file server machine</tertiary>
2342 <primary>PAM</primary>
2344 <secondary>on Solaris</secondary>
2346 <tertiary>file server machine</tertiary>
2350 <para>If you plan to remove client functionality from this machine after completing the installation, skip this section and
2351 proceed to <link linkend="HDRWQ50">Starting the BOS Server</link>.</para>
2354 <para>At this point you incorporate AFS into the operating system's Pluggable Authentication Module (PAM) scheme. PAM
2355 integrates all authentication mechanisms on the machine, including login, to provide the security infrastructure for
2356 authenticated access to and from the machine.</para>
2358 <para>Explaining PAM is beyond the scope of this document. It is assumed that you understand the syntax and meanings of
2359 settings in the PAM configuration file (for example, how the <computeroutput>other</computeroutput> entry works, the effect of
2360 marking an entry as <computeroutput>required</computeroutput>, <computeroutput>optional</computeroutput>, or
2361 <computeroutput>sufficient</computeroutput>, and so on).</para>
2363 <para>In modern AFS installations, you should be using Kerberos v5
2364 for user login, and obtaining AFS tokens subsequent to this authentication
2365 step. OpenAFS does not currently distribute a PAM module allowing AFS
2366 tokens to be automatically gained at login. Whilst there are a number of
2367 third party modules providing this functionality, it is not know if these
2368 have been tested with HP/UX.</para>
2370 <para>Following login, users can
2371 obtain tokens by running the <emphasis role="bold">aklog</emphasis>
2374 <para>Sites which still require <emphasis role="bold">kaserver</emphasis>
2375 or external Kerberos v4 authentication should consult
2376 <link linkend="KAS016">Enabling kaserver based AFS Login on Solaris Systems"</link>
2377 for details of how to enable AIX login.</para>
2379 <para>Proceed to <link linkend="HDRWQ49a">Editing the File Systems
2380 Clean-up Script on Solaris Systems</link></para>
2382 <sect2 id="HDRWQ49a">
2383 <title>Editing the File Systems Clean-up Script on Solaris Systems</title>
2385 <primary>Solaris</primary>
2387 <secondary>file systems clean-up script</secondary>
2389 <tertiary>on file server machine</tertiary>
2393 <primary>file systems clean-up script (Solaris)</primary>
2395 <secondary>file server machine</secondary>
2399 <primary>scripts</primary>
2401 <secondary>file systems clean-up (Solaris)</secondary>
2403 <tertiary>file server machine</tertiary>
2409 <para>Some Solaris distributions include a script that locates and removes unneeded files from various file systems. Its
2410 conventional location is <emphasis role="bold">/usr/lib/fs/nfs/nfsfind</emphasis>. The script generally uses an argument
2411 to the <emphasis role="bold">find</emphasis> command to define which file systems to search. In this step you modify the
2412 command to exclude the <emphasis role="bold">/afs</emphasis> directory. Otherwise, the command traverses the AFS
2413 filespace of every cell that is accessible from the machine, which can take many hours. The following alterations are
2414 possibilities, but you must verify that they are appropriate for your cell.</para>
2416 <para>The first possible alteration is to add the <emphasis role="bold">-local</emphasis> flag to the existing command,
2417 so that it looks like the following:</para>
2420 find $dir -local -name .nfs\* -mtime +7 -mount -exec rm -f {} \;
2423 <para>Another alternative is to exclude any directories whose names begin with the lowercase letter <emphasis
2424 role="bold">a</emphasis> or a non-alphabetic character.</para>
2427 find /[A-Zb-z]* <replaceable>remainder of existing command</replaceable>
2430 <para>Do not use the following command, which still searches under the <emphasis role="bold">/afs</emphasis> directory,
2431 looking for a subdirectory of type <emphasis role="bold">4.2</emphasis>.</para>
2434 find / -fstype 4.2 /* <replaceable>do not use</replaceable> */
2439 <para>Proceed to <link linkend="HDRWQ50">Starting the BOS Server</link> (or if referring to these instructions while
2440 installing an additional file server machine, return to <link linkend="HDRWQ108">Starting Server
2441 Programs</link>).</para>
2446 <primary>Basic OverSeer Server</primary>
2448 <see>BOS Server</see>
2452 <primary>BOS Server</primary>
2454 <secondary>starting</secondary>
2456 <tertiary>first AFS machine</tertiary>
2460 <primary>starting</primary>
2462 <secondary>BOS Server</secondary>
2464 <tertiary>first AFS machine</tertiary>
2468 <primary>first AFS machine</primary>
2470 <secondary>BOS Server</secondary>
2474 <primary>authorization checking (disabling)</primary>
2476 <secondary>first AFS machine</secondary>
2480 <primary>disabling authorization checking</primary>
2482 <secondary>first AFS machine</secondary>
2486 <primary>first AFS machine</primary>
2488 <secondary>authorization checking (disabling)</secondary>
2492 <sect1 id="HDRWQ50">
2493 <title>Starting the BOS Server</title>
2495 <para>You are now ready to start the AFS server processes on this machine.
2496 If you are not working from a packaged distribution, begin by copying the
2497 AFS server binaries from the distribution to the conventional local disk
2498 location, the <emphasis role="bold">/usr/afs/bin</emphasis> directory. The
2499 following instructions also create files in other subdirectories of the
2500 <emphasis role="bold">/usr/afs</emphasis> directory.</para>
2502 <para>Then issue the <emphasis role="bold">bosserver</emphasis> command to initialize the Basic OverSeer (BOS) Server, which
2503 monitors and controls other AFS server processes on its server machine. Include the <emphasis role="bold">-noauth</emphasis>
2504 flag to disable authorization checking. Because you have not yet configured your cell's AFS authentication and authorization
2505 mechanisms, the BOS Server cannot perform authorization checking as it does during normal operation. In no-authorization mode,
2506 it does not verify the identity or privilege of the issuer of a <emphasis role="bold">bos</emphasis> command, and so performs
2507 any operation for anyone.</para>
2509 <para>Disabling authorization checking gravely compromises cell security. You must complete all subsequent steps in one
2510 uninterrupted pass and must not leave the machine unattended until you restart the BOS Server with authorization checking
2511 enabled, in <link linkend="HDRWQ72">Verifying the AFS Initialization Script</link>.</para>
2513 <para>As it initializes for the first time, the BOS Server creates the following directories and files, setting the owner to the
2514 local superuser <emphasis role="bold">root</emphasis> and the mode bits to limit the ability to write (and in some cases, read)
2515 them. For a description of the contents and function of these directories and files, see the chapter in the <emphasis>OpenAFS
2516 Administration Guide</emphasis> about administering server machines. For further discussion of the mode bit settings, see <link
2517 linkend="HDRWQ96">Protecting Sensitive AFS Directories</link>. <indexterm>
2518 <primary>Binary Distribution</primary>
2520 <secondary>copying server files from</secondary>
2522 <tertiary>first AFS machine</tertiary>
2523 </indexterm> <indexterm>
2524 <primary>first AFS machine</primary>
2526 <secondary>subdirectories of /usr/afs</secondary>
2527 </indexterm> <indexterm>
2528 <primary>creating</primary>
2530 <secondary>/usr/afs/bin directory</secondary>
2532 <tertiary>first AFS machine</tertiary>
2533 </indexterm> <indexterm>
2534 <primary>creating</primary>
2536 <secondary>/usr/afs/etc directory</secondary>
2538 <tertiary>first AFS machine</tertiary>
2539 </indexterm> <indexterm>
2540 <primary>copying</primary>
2542 <secondary>server files to local disk</secondary>
2544 <tertiary>first AFS machine</tertiary>
2545 </indexterm> <indexterm>
2546 <primary>first AFS machine</primary>
2548 <secondary>copying</secondary>
2550 <tertiary>server files to local disk</tertiary>
2551 </indexterm> <indexterm>
2552 <primary>usr/afs/bin directory</primary>
2554 <secondary>first AFS machine</secondary>
2555 </indexterm> <indexterm>
2556 <primary>usr/afs/etc directory</primary>
2558 <secondary>first AFS machine</secondary>
2559 </indexterm> <indexterm>
2560 <primary>usr/afs/db directory</primary>
2561 </indexterm> <indexterm>
2562 <primary>usr/afs/local directory</primary>
2563 </indexterm> <indexterm>
2564 <primary>usr/afs/logs directory</primary>
2565 </indexterm> <itemizedlist>
2567 <para><emphasis role="bold">/usr/afs/db</emphasis></para>
2571 <para><emphasis role="bold">/usr/afs/etc/CellServDB</emphasis></para>
2575 <para><emphasis role="bold">/usr/afs/etc/ThisCell</emphasis></para>
2579 <para><emphasis role="bold">/usr/afs/local</emphasis></para>
2583 <para><emphasis role="bold">/usr/afs/logs</emphasis></para>
2585 </itemizedlist></para>
2587 <para>The BOS Server also creates symbolic links called <emphasis role="bold">/usr/vice/etc/ThisCell</emphasis> and <emphasis
2588 role="bold">/usr/vice/etc/CellServDB</emphasis> to the corresponding files in the <emphasis role="bold">/usr/afs/etc</emphasis>
2589 directory. The AFS command interpreters consult the <emphasis role="bold">CellServDB</emphasis> and <emphasis
2590 role="bold">ThisCell</emphasis> files in the <emphasis role="bold">/usr/vice/etc</emphasis> directory because they generally run
2591 on client machines. On machines that are AFS servers only (as this machine currently is), the files reside only in the <emphasis
2592 role="bold">/usr/afs/etc</emphasis> directory; the links enable the command interpreters to retrieve the information they need.
2593 Later instructions for installing the client functionality replace the links with actual files. <orderedlist>
2595 <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.
2597 # <emphasis role="bold">cd /tmp/afsdist/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/root.server/usr/afs</emphasis>
2598 # <emphasis role="bold">cp -rp * /usr/afs</emphasis>
2599 </programlisting> <indexterm>
2600 <primary>commands</primary>
2602 <secondary>bosserver</secondary>
2603 </indexterm> <indexterm>
2604 <primary>bosserver command</primary>
2609 <para>Issue the <emphasis role="bold">bosserver</emphasis> command. Include the <emphasis role="bold">-noauth</emphasis>
2610 flag to disable authorization checking. <programlisting>
2611 # <emphasis role="bold">/usr/afs/bin/bosserver -noauth &</emphasis>
2612 </programlisting></para>
2616 <para>Verify that the BOS Server created <emphasis role="bold">/usr/vice/etc/ThisCell</emphasis> and <emphasis
2617 role="bold">/usr/vice/etc/CellServDB</emphasis> as symbolic links to the corresponding files in the <emphasis
2618 role="bold">/usr/afs/etc</emphasis> directory. <programlisting>
2619 # <emphasis role="bold">ls -l /usr/vice/etc</emphasis>
2620 </programlisting></para>
2622 <para>If either or both of <emphasis role="bold">/usr/vice/etc/ThisCell</emphasis> and <emphasis
2623 role="bold">/usr/vice/etc/CellServDB</emphasis> do not exist, or are not links, issue the following commands.</para>
2626 # <emphasis role="bold">cd /usr/vice/etc</emphasis>
2627 # <emphasis role="bold">ln -s /usr/afs/etc/ThisCell</emphasis>
2628 # <emphasis role="bold">ln -s /usr/afs/etc/CellServDB</emphasis>
2631 </orderedlist></para>
2634 <primary>cell name</primary>
2636 <secondary>defining during installation of first machine</secondary>
2640 <primary>defining</primary>
2642 <secondary>cell name during installation of first machine</secondary>
2646 <primary>cell name</primary>
2648 <secondary>setting in server ThisCell file</secondary>
2650 <tertiary>first AFS machine</tertiary>
2654 <primary>setting</primary>
2656 <secondary>cell name in server ThisCell file</secondary>
2658 <tertiary>first AFS machine</tertiary>
2662 <primary>first AFS machine</primary>
2664 <secondary>ThisCell file (server)</secondary>
2668 <primary>usr/afs/etc/ThisCell</primary>
2670 <see>ThisCell file (server)</see>
2674 <primary>ThisCell file (server)</primary>
2676 <secondary>first AFS machine</secondary>
2680 <primary>files</primary>
2682 <secondary>ThisCell (server)</secondary>
2686 <primary>database server machine</primary>
2688 <secondary>entry in server CellServDB file</secondary>
2690 <tertiary>on first AFS machine</tertiary>
2694 <primary>first AFS machine</primary>
2696 <secondary>cell membership, defining</secondary>
2698 <tertiary>for server processes</tertiary>
2702 <primary>usr/afs/etc/CellServDB file</primary>
2704 <see>CellServDB file (server)</see>
2708 <primary>CellServDB file (server)</primary>
2710 <secondary>creating</secondary>
2712 <tertiary>on first AFS machine</tertiary>
2716 <primary>creating</primary>
2718 <secondary>CellServDB file (server)</secondary>
2720 <tertiary>first AFS machine</tertiary>
2724 <primary>files</primary>
2726 <secondary>CellServDB (server)</secondary>
2730 <primary>first AFS machine</primary>
2732 <secondary>CellServDB file (server)</secondary>
2736 <primary>first AFS machine</primary>
2738 <secondary>defining</secondary>
2740 <tertiary>as database server</tertiary>
2744 <primary>defining</primary>
2746 <secondary>first AFS machine as database server</secondary>
2750 <sect1 id="HDRWQ51">
2751 <title>Defining Cell Name and Membership for Server Processes</title>
2753 <para>Now assign your cell's name. The chapter in the <emphasis>OpenAFS Administration Guide</emphasis> about cell configuration
2754 and administration issues discusses the important considerations, explains why changing the name is difficult, and outlines the
2755 restrictions on name format. Two of the most important restrictions are that the name cannot include uppercase letters or more
2756 than 64 characters.</para>
2758 <para>Use the <emphasis role="bold">bos setcellname</emphasis> command to assign the cell name. It creates two files:
2761 <para><emphasis role="bold">/usr/afs/etc/ThisCell</emphasis>, which defines this machine's cell membership</para>
2765 <para><emphasis role="bold">/usr/afs/etc/CellServDB</emphasis>, which lists the cell's database server machines; the
2766 machine named on the command line is placed on the list automatically</para>
2768 </itemizedlist> <note>
2769 <para>In the following and every instruction in this guide, for the <replaceable>machine name</replaceable> argument
2770 substitute the fully-qualified hostname (such as <emphasis role="bold">fs1.example.com</emphasis>) of the machine you are
2771 installing. For the <replaceable>cell name</replaceable> argument substitute your cell's complete name (such as <emphasis
2772 role="bold">example.com</emphasis>).</para>
2776 <primary>commands</primary>
2778 <secondary>bos setcellname</secondary>
2782 <primary>bos commands</primary>
2784 <secondary>setcellname</secondary>
2789 <para>If necessary, add the directory containing the <emphasis role="bold">bos</emphasis> command to your path.
2791 # <emphasis role="bold">export PATH=$PATH:/usr/afs/bin</emphasis>
2797 <para>Issue the <emphasis role="bold">bos setcellname</emphasis> command to set the cell name. <programlisting>
2798 # <emphasis role="bold">bos setcellname</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>cell name</replaceable>> <emphasis
2799 role="bold">-noauth</emphasis>
2800 </programlisting></para>
2802 <para>Because you are not authenticated and authorization checking is disabled, the <emphasis role="bold">bos</emphasis>
2803 command interpreter possibly produces error messages about being unable to obtain tickets and running unauthenticated. You
2804 can safely ignore the messages. <indexterm>
2805 <primary>commands</primary>
2807 <secondary>bos listhosts</secondary>
2808 </indexterm> <indexterm>
2809 <primary>bos commands</primary>
2811 <secondary>listhosts</secondary>
2812 </indexterm> <indexterm>
2813 <primary>CellServDB file (server)</primary>
2815 <secondary>displaying entries</secondary>
2816 </indexterm> <indexterm>
2817 <primary>displaying</primary>
2819 <secondary>CellServDB file (server) entries</secondary>
2824 <para>Issue the <emphasis role="bold">bos listhosts</emphasis> command to verify that the machine you are installing is now
2825 registered as the cell's first database server machine. <programlisting>
2826 # <emphasis role="bold">bos listhosts</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">-noauth</emphasis>
2827 Cell name is <replaceable>cell_name</replaceable>
2828 Host 1 is <replaceable>machine_name</replaceable>
2829 </programlisting></para>
2834 <primary>database server machine</primary>
2836 <secondary>installing</secondary>
2838 <tertiary>first</tertiary>
2842 <primary>instructions</primary>
2844 <secondary>database server machine, installing first</secondary>
2848 <primary>installing</primary>
2850 <secondary>database server machine</secondary>
2852 <tertiary>first</tertiary>
2856 <primary>Backup Server</primary>
2858 <secondary>starting</secondary>
2860 <tertiary>first AFS machine</tertiary>
2864 <primary>buserver process</primary>
2866 <see>Backup Server</see>
2870 <primary>starting</primary>
2872 <secondary>Backup Server</secondary>
2874 <tertiary>first AFS machine</tertiary>
2878 <primary>first AFS machine</primary>
2880 <secondary>Backup Server</secondary>
2884 <primary>Protection Server</primary>
2886 <secondary>starting</secondary>
2888 <tertiary>first AFS machine</tertiary>
2892 <primary>ptserver process</primary>
2894 <see>Protection Server</see>
2898 <primary>starting</primary>
2900 <secondary>Protection Server</secondary>
2902 <tertiary>first AFS machine</tertiary>
2906 <primary>first AFS machine</primary>
2908 <secondary>Protection Server</secondary>
2912 <primary>VL Server (vlserver process)</primary>
2914 <secondary>starting</secondary>
2916 <tertiary>first AFS machine</tertiary>
2920 <primary>Volume Location Server</primary>
2922 <see>VL Server</see>
2926 <primary>starting</primary>
2928 <secondary>VL Server</secondary>
2930 <tertiary>first AFS machine</tertiary>
2934 <primary>first AFS machine</primary>
2936 <secondary>VL Server</secondary>
2940 <primary>usr/afs/local/BosConfig</primary>
2942 <see>BosConfig file</see>
2946 <primary>BosConfig file</primary>
2948 <secondary>adding entries</secondary>
2950 <tertiary>first AFS machine</tertiary>
2954 <primary>adding</primary>
2956 <secondary>entries to BosConfig file</secondary>
2958 <tertiary>first AFS machine</tertiary>
2962 <primary>files</primary>
2964 <secondary>BosConfig</secondary>
2968 <primary>initializing</primary>
2970 <secondary>server process</secondary>
2976 <primary>server process</primary>
2978 <secondary>see also entry for each server's name</secondary>
2982 <sect1 id="HDRWQ52">
2983 <title>Starting the Database Server Processes</title>
2985 <para>Next use the <emphasis role="bold">bos create</emphasis> command to create entries for the three database server processes
2986 in the <emphasis role="bold">/usr/afs/local/BosConfig</emphasis> file and start them running. The three processes run on database
2987 server machines only: <itemizedlist>
2990 <para>The Backup Server (the <emphasis role="bold">buserver</emphasis> process) maintains the Backup Database</para>
2994 <para>The Protection Server (the <emphasis role="bold">ptserver</emphasis> process) maintains the Protection
2999 <para>The Volume Location (VL) Server (the <emphasis role="bold">vlserver</emphasis> process) maintains the Volume
3000 Location Database (VLDB)</para>
3002 </itemizedlist></para>
3005 <primary>Kerberos</primary>
3009 <para>AFS ships with an additional database server named 'kaserver', which
3010 was historically used to provide authentication services to AFS cells.
3011 kaserver was based on <emphasis>Kerberos v4</emphasis>, as such, it is
3012 not recommended for new cells. This guide assumes you have already
3013 configured a Kerberos v5 realm for your site, and details the procedures
3014 required to use AFS with this realm. If you do wish to use
3015 <emphasis role="bold">kaserver</emphasis>, please see the modifications
3016 to these instructions detailed in
3017 <link linkend="KAS006">Starting the kaserver Database Server Process</link>
3021 <para>The remaining instructions in this chapter include the <emphasis role="bold">-cell</emphasis> argument on all applicable
3022 commands. Provide the cell name you assigned in <link linkend="HDRWQ51">Defining Cell Name and Membership for Server
3023 Processes</link>. If a command appears on multiple lines, it is only for legibility. <indexterm>
3024 <primary>commands</primary>
3026 <secondary>bos create</secondary>
3027 </indexterm> <indexterm>
3028 <primary>bos commands</primary>
3030 <secondary>create</secondary>
3031 </indexterm> <orderedlist>
3033 <para>Issue the <emphasis role="bold">bos create</emphasis> command to start the Backup Server. <programlisting>
3034 # <emphasis role="bold">./bos create</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">buserver simple /usr/afs/bin/buserver</emphasis> \
3035 <emphasis role="bold"> -cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis role="bold">-noauth</emphasis>
3036 </programlisting></para>
3040 <para>Issue the <emphasis role="bold">bos create</emphasis> command to start the Protection Server. <programlisting>
3041 # <emphasis role="bold">./bos create</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">ptserver simple /usr/afs/bin/ptserver</emphasis> \
3042 <emphasis role="bold"> -cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis role="bold">-noauth</emphasis>
3043 </programlisting></para>
3047 <para>Issue the <emphasis role="bold">bos create</emphasis> command to start the VL Server. <programlisting>
3048 # <emphasis role="bold">./bos create</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">vlserver simple /usr/afs/bin/vlserver</emphasis> \
3049 <emphasis role="bold"> -cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis role="bold">-noauth</emphasis>
3050 </programlisting></para>
3052 </orderedlist></para>
3055 <primary>admin account</primary>
3057 <secondary>creating</secondary>
3061 <primary>afs entry in Kerberos Database</primary>
3065 <primary>Kerberos Database</primary>
3069 <primary>creating</primary>
3071 <secondary>afs entry in Kerberos Database</secondary>
3075 <primary>creating</primary>
3077 <secondary>admin account in Kerberos Database</secondary>
3081 <primary>security</primary>
3083 <secondary>initializing cell-wide</secondary>
3087 <primary>cell</primary>
3089 <secondary>initializing security mechanisms</secondary>
3093 <primary>initializing</primary>
3095 <secondary>cell security mechanisms</secondary>
3099 <primary>usr/afs/etc/KeyFile</primary>
3101 <see>KeyFile file</see>
3105 <primary>KeyFile file</primary>
3107 <secondary>first AFS machine</secondary>
3111 <primary>files</primary>
3113 <secondary>KeyFile</secondary>
3117 <primary>key</primary>
3119 <see>server encryption key</see>
3123 <primary>encryption key</primary>
3125 <see>server encryption key</see>
3129 <sect1 id="HDRWQ53">
3130 <title>Initializing Cell Security </title>
3132 <para>If you are working with an existing cell which uses
3133 <emphasis role="bold">kaserver</emphasis> or Kerberos v4 for authentication,
3135 <link linkend="HDRWQ53">Initializing Cell Security with kaserver</link>
3136 for installation instructions which replace this section.</para>
3138 <para>Now initialize the cell's security mechanisms. Begin by creating the following two entires in your site's Kerberos database: <itemizedlist>
3140 <para>A generic administrative account, called <emphasis role="bold">admin</emphasis> by convention. If you choose to
3141 assign a different name, substitute it throughout the remainder of this document.</para>
3143 <para>After you complete the installation of the first machine, you can continue to have all administrators use the
3144 <emphasis role="bold">admin</emphasis> account, or you can create a separate administrative account for each of them. The
3145 latter scheme implies somewhat more overhead, but provides a more informative audit trail for administrative
3150 <para>The entry for AFS server processes, called either
3151 <emphasis role="bold">afs</emphasis> or
3152 <emphasis role="bold">afs/<replaceable>cell</replaceable></emphasis>.
3153 No user logs in under this identity, but it is used to encrypt the
3154 server tickets that granted to AFS clients for presentation to
3155 server processes during mutual authentication. (The
3156 chapter in the <emphasis>OpenAFS Administration Guide</emphasis> about cell configuration and administration describes the
3157 role of server encryption keys in mutual authentication.)</para>
3159 <para>In Step <link linkend="LIWQ58">7</link>, you also place the initial AFS server encryption key into the <emphasis
3160 role="bold">/usr/afs/etc/KeyFile</emphasis> file. The AFS server processes refer to this file to learn the server
3161 encryption key when they need to decrypt server tickets.</para>
3163 </itemizedlist></para>
3165 <para>You also issue several commands that enable the new <emphasis role="bold">admin</emphasis> user to issue privileged
3166 commands in all of the AFS suites.</para>
3168 <para>The following instructions do not configure all of the security mechanisms related to the AFS Backup System. See the
3169 chapter in the <emphasis>OpenAFS Administration Guide</emphasis> about configuring the Backup System.</para>
3171 <para>The examples below assume you are using MIT Kerberos. Please refer
3172 to the documentation for your KDC's administrative interface if you are
3173 using a different vendor</para>
3177 <para>Enter <emphasis role="bold">kadmin</emphasis> interactive mode.
3179 # <emphasis role="bold">kadmin</emphasis>
3180 Authenticating as principal <replaceable>you</replaceable>/admin@<replaceable>YOUR REALM</replaceable> with password
3181 Password for <replaceable>you/admin@REALM</replaceable>: <replaceable>your_password</replaceable>
3182 </programlisting> <indexterm>
3183 <primary>server encryption key</primary>
3185 <secondary>in Kerberos Database</secondary>
3186 </indexterm> <indexterm>
3187 <primary>creating</primary>
3189 <secondary>server encryption key</secondary>
3191 <tertiary>Kerberos Database</tertiary>
3196 <para><anchor id="LIWQ54" />Issue the
3197 <emphasis role="bold">add_principal</emphasis> command to create
3198 Kerberos Database entries called
3199 <emphasis role="bold">admin</emphasis> and
3200 <emphasis role="bold">afs/<<replaceable>cell name</replaceable>></emphasis>.</para>
3202 <para>You should make the <replaceable>admin_passwd</replaceable> as
3203 long and complex as possible, but keep in mind that administrators
3204 need to enter it often. It must be at least six characters long.</para>
3205 <para>Note that when creating the
3206 <emphasis role="bold">afs/<<replaceable>cell name</replaceable>></emphasis>
3207 entry, the encryption types should be restricted to des-cbc-crc:v4.
3208 For more details regarding encryption types, see the documentation
3209 for your Kerberos installation.
3212 kadmin: <emphasis role="bold">add_principal -randkey -e des-cbc-crc:v4 afs/</emphasis><<replaceable>cell name</replaceable>>
3213 Principal "afs/<replaceable>cell name</replaceable>@<replaceable>REALM</replaceable>" created.
3214 kadmin: <emphasis role="bold">add_principal admin</emphasis>
3215 Enter password for principal "admin@<replaceable>REALM</replaceable>": <emphasis role="bold"><replaceable>admin_password</replaceable></emphasis>
3216 Principal "admin@<replaceable>REALM</replaceable>" created.
3221 <primary>commands</primary>
3223 <secondary>kas examine</secondary>
3227 <primary>kas commands</primary>
3229 <secondary>examine</secondary>
3233 <primary>displaying</primary>
3235 <secondary>server encryption key</secondary>
3237 <tertiary>Authentication Database</tertiary>
3242 <para><anchor id="LIWQ55" />Issue the <emphasis role="bold">kadmin
3243 get_principal</emphasis> command to display the <emphasis
3244 role="bold">afs/</emphasis><<replaceable>cell name</replaceable>> entry.
3246 kadmin: <emphasis role="bold">get_principal afs/<<replaceable>cell name</replaceable>></emphasis>
3247 Principal: afs/<replaceable>cell</replaceable>
3249 Key: vno 2, DES cbc mode with CRC-32, no salt
3255 <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>
3257 <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>
3260 kadmin: <emphasis role="bold">ktadd -k /etc/afs.keytab -e des-cbc-crc:v4 afs/<<replaceable>cell name</replaceable>></emphasis>
3261 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
3263 <para>Make a note of the key version number (kvno) given in the
3264 response, as you will need it to load the key into bos in a later
3267 <note><para>Note that each time you run
3268 <emphasis role="bold">ktadd</emphasis> a new key is generated
3269 for the item being extracted. This means that you cannot run ktadd
3270 multiple times and end up with the same key material each time.
3275 <para>Issue the <emphasis role="bold">kadmin quit</emphasis> command to leave <emphasis role="bold">kadmin</emphasis>
3276 interactive mode. <programlisting>
3277 kadmin: <emphasis role="bold">quit</emphasis>
3278 </programlisting> <indexterm>
3279 <primary>commands</primary>
3281 <secondary>bos adduser</secondary>
3282 </indexterm> <indexterm>
3283 <primary>bos commands</primary>
3285 <secondary>adduser</secondary>
3286 </indexterm> <indexterm>
3287 <primary>usr/afs/etc/UserList</primary>
3289 <see>UserList file</see>
3290 </indexterm> <indexterm>
3291 <primary>UserList file</primary>
3293 <secondary>first AFS machine</secondary>
3294 </indexterm> <indexterm>
3295 <primary>files</primary>
3297 <secondary>UserList</secondary>
3298 </indexterm> <indexterm>
3299 <primary>creating</primary>
3301 <secondary>UserList file entry</secondary>
3302 </indexterm> <indexterm>
3303 <primary>admin account</primary>
3305 <secondary>adding</secondary>
3307 <tertiary>to UserList file</tertiary>
3312 <para><anchor id="LIWQ57" />Issue the <emphasis role="bold">bos adduser</emphasis> command to add the <emphasis
3313 role="bold">admin</emphasis> user to the <emphasis role="bold">/usr/afs/etc/UserList</emphasis> file. This enables the
3314 <emphasis role="bold">admin</emphasis> user to issue privileged <emphasis role="bold">bos</emphasis> and <emphasis
3315 role="bold">vos</emphasis> commands. <programlisting>
3316 # <emphasis role="bold">./bos adduser</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">admin -cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis
3317 role="bold">-noauth</emphasis>
3320 <primary>commands</primary>
3321 <secondary>asetkey</secondary>
3324 <primary>creating</primary>
3325 <secondary>server encryption key</secondary>
3326 <tertiary>KeyFile file</tertiary>
3329 <primary>server encryption key</primary>
3330 <secondary>in KeyFile file</secondary>
3335 <para><anchor id="LIWQ58" />Issue the
3336 <emphasis role="bold">asetkey</emphasis> command to set the AFS
3337 server encryption key in the
3338 <emphasis role="bold">/usr/afs/etc/KeyFile</emphasis> file. This key
3339 is created from the <emphasis role="bold">/etc/afs.keytab</emphasis>
3340 file created earlier.</para>
3342 <para>asetkey requires the key version number (or kvno) of the
3343 <emphasis role="bold">afs/</emphasis><replaceable>cell</replaceable>
3344 key. You should have noted this down when creating the key earlier.
3345 The key version number can also be found by running the
3346 <emphasis role="bold">kvno</emphasis> command</para>
3348 # <emphasis role="bold">kvno afs/</emphasis><<replaceable>cell name</replaceable>>
3351 <para>Once the kvno is known, the key can then be extracted using
3354 # <emphasis role="bold">asetkey</emphasis> <<replaceable>kvno</replaceable>> <emphasis role="bold">/etc/afs.keytab afs/</emphasis><<replaceable>cell name</replaceable>>
3358 <primary>commands</primary>
3359 <secondary>bos listkeys</secondary>
3363 <primary>bos commands</primary>
3364 <secondary>listkeys</secondary>
3368 <primary>displaying</primary>
3369 <secondary>server encryption key</secondary>
3370 <tertiary>KeyFile file</tertiary>
3375 <para><anchor id="LIWQ59" />Issue the
3376 <emphasis role="bold">bos listkeys</emphasis> command to verify that
3377 the key version number for the new key in the
3378 <emphasis role="bold">KeyFile</emphasis> file is the same as the key
3379 version number in the Authentication Database's
3380 <emphasis role="bold">afs/<replaceable>cell name</replaceable></emphasis>
3381 entry, which you displayed in Step <link linkend="LIWQ55">3</link>.
3383 # <emphasis role="bold">./bos listkeys</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">-cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis
3384 role="bold">-noauth</emphasis>
3385 key 0 has cksum <replaceable>checksum</replaceable>
3386 </programlisting></para>
3388 <para>You can safely ignore any error messages indicating that <emphasis role="bold">bos</emphasis> failed to get tickets
3389 or that authentication failed.</para>
3393 <sect1 id="HDRWQ53a">
3394 <title>Initializing the Protection Database</title>
3396 <para>Now continue to configure your cell's security systems by
3397 populating the Protection Database with the newly created
3398 <emphasis role="bold">admin</emphasis> user, and permitting it
3399 to issue priviledged commands on the AFS filesystem.</para>
3404 <primary>commands</primary>
3405 <secondary>pts createuser</secondary>
3409 <primary>pts commands</primary>
3410 <secondary>createuser</secondary>
3414 <primary>Protection Database</primary>
3416 <para>Issue the <emphasis role="bold">pts createuser</emphasis> command to create a Protection Database entry for the
3417 <emphasis role="bold">admin</emphasis> user.</para>
3419 <para>By default, the Protection Server assigns AFS UID 1 (one) to the <emphasis role="bold">admin</emphasis> user,
3420 because it is the first user entry you are creating. If the local password file (<emphasis
3421 role="bold">/etc/passwd</emphasis> or equivalent) already has an entry for <emphasis role="bold">admin</emphasis> that
3422 assigns it a UNIX UID other than 1, it is best to use the <emphasis role="bold">-id</emphasis> argument to the <emphasis
3423 role="bold">pts createuser</emphasis> command to make the new AFS UID match the existing UNIX UID. Otherwise, it is best
3424 to accept the default.</para>
3427 # <emphasis role="bold">pts createuser -name admin -cell</emphasis> <<replaceable>cell name</replaceable>> [<emphasis
3428 role="bold">-id</emphasis> <<replaceable>AFS UID</replaceable>>] <emphasis role="bold">-noauth</emphasis>
3429 User admin has id <replaceable>AFS UID</replaceable>
3433 <primary>commands</primary>
3434 <secondary>pts adduser</secondary>
3438 <primary>pts commands</primary>
3439 <secondary>adduser</secondary>
3443 <primary>system:administrators group</primary>
3447 <primary>admin account</primary>
3448 <secondary>adding</secondary>
3449 <tertiary>to system:administrators group</tertiary>
3454 <para>Issue the <emphasis role="bold">pts adduser</emphasis> command to make the <emphasis role="bold">admin</emphasis>
3455 user a member of the <emphasis role="bold">system:administrators</emphasis> group, and the <emphasis role="bold">pts
3456 membership</emphasis> command to verify the new membership. Membership in the group enables the <emphasis
3457 role="bold">admin</emphasis> user to issue privileged <emphasis role="bold">pts</emphasis> commands and some privileged
3458 <emphasis role="bold">fs</emphasis> commands. <programlisting>
3459 # <emphasis role="bold">./pts adduser admin system:administrators -cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis
3460 role="bold">-noauth</emphasis>
3461 # <emphasis role="bold">./pts membership admin -cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis
3462 role="bold">-noauth</emphasis>
3463 Groups admin (id: 1) is a member of:
3464 system:administrators
3465 </programlisting> <indexterm>
3466 <primary>commands</primary>
3467 <secondary>bos restart</secondary>
3468 <tertiary>on first AFS machine</tertiary>
3469 </indexterm> <indexterm>
3470 <primary>bos commands</primary>
3471 <secondary>restart</secondary>
3472 <tertiary>on first AFS machine</tertiary>
3473 </indexterm> <indexterm>
3474 <primary>restarting server process</primary>
3475 <secondary>on first AFS machine</secondary>
3476 </indexterm> <indexterm>
3477 <primary>server process</primary>
3478 <secondary>restarting</secondary>
3479 <tertiary>on first AFS machine</tertiary>
3484 <para>Issue the <emphasis role="bold">bos restart</emphasis> command with the <emphasis role="bold">-all</emphasis> flag
3485 to restart the database server processes, so that they start using the new server encryption key. <programlisting>
3486 # <emphasis role="bold">./bos restart</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">-all -cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis
3487 role="bold">-noauth</emphasis>
3488 </programlisting></para>
3493 <primary>File Server</primary>
3495 <secondary>first AFS machine</secondary>
3499 <primary>fileserver process</primary>
3501 <see>File Server</see>
3505 <primary>starting</primary>
3507 <secondary>File Server</secondary>
3509 <tertiary>first AFS machine</tertiary>
3513 <primary>first AFS machine</primary>
3515 <secondary>File Server, fs process</secondary>
3519 <primary>Volume Server</primary>
3521 <secondary>first AFS machine</secondary>
3525 <primary>volserver process</primary>
3527 <see>Volume Server</see>
3531 <primary>starting</primary>
3533 <secondary>Volume Server</secondary>
3535 <tertiary>first AFS machine</tertiary>
3539 <primary>first AFS machine</primary>
3541 <secondary>Volume Server</secondary>
3545 <primary>Salvager (salvager process)</primary>
3547 <secondary>first AFS machine</secondary>
3551 <primary>fs process</primary>
3553 <secondary>first AFS machine</secondary>
3557 <primary>starting</primary>
3559 <secondary>fs process</secondary>
3561 <tertiary>first AFS machine</tertiary>
3565 <primary>first AFS machine</primary>
3567 <secondary>Salvager</secondary>
3571 <sect1 id="HDRWQ60">
3572 <title>Starting the File Server, Volume Server, and Salvager</title>
3574 <para>Start the <emphasis role="bold">fs</emphasis> process, which consists of the File Server, Volume Server, and Salvager
3575 (<emphasis role="bold">fileserver</emphasis>, <emphasis role="bold">volserver</emphasis> and <emphasis
3576 role="bold">salvager</emphasis> processes). <orderedlist>
3578 <para>Issue the <emphasis role="bold">bos create</emphasis> command to start the <emphasis role="bold">fs</emphasis>
3579 process. The command appears here on multiple lines only for legibility. <programlisting>
3580 # <emphasis role="bold">./bos create</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">fs fs /usr/afs/bin/fileserver</emphasis> \
3581 <emphasis role="bold">/usr/afs/bin/volserver /usr/afs/bin/salvager</emphasis> \
3582 <emphasis role="bold">-cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis role="bold">-noauth</emphasis>
3583 </programlisting></para>
3585 <para>Sometimes a message about Volume Location Database (VLDB) initialization appears, along with one or more instances
3586 of an error message similar to the following:</para>
3589 FSYNC_clientInit temporary failure (will retry)
3592 <para>This message appears when the <emphasis role="bold">volserver</emphasis> process tries to start before the <emphasis
3593 role="bold">fileserver</emphasis> process has completed its initialization. Wait a few minutes after the last such message
3594 before continuing, to guarantee that both processes have started successfully. <indexterm>
3595 <primary>commands</primary>
3597 <secondary>bos status</secondary>
3598 </indexterm> <indexterm>
3599 <primary>bos commands</primary>
3601 <secondary>status</secondary>
3604 <para>You can verify that the <emphasis role="bold">fs</emphasis> process has started successfully by issuing the
3605 <emphasis role="bold">bos status</emphasis> command. Its output mentions two <computeroutput>proc
3606 starts</computeroutput>.</para>
3609 # <emphasis role="bold">./bos status</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">fs -long -noauth</emphasis>
3614 <para>Your next action depends on whether you have ever run AFS file server machines in the cell: <itemizedlist>
3616 <primary>commands</primary>
3618 <secondary>vos create</secondary>
3620 <tertiary>root.afs volume</tertiary>
3624 <primary>vos commands</primary>
3626 <secondary>create</secondary>
3628 <tertiary>root.afs volume</tertiary>
3632 <primary>root.afs volume</primary>
3634 <secondary>creating</secondary>
3638 <primary>volume</primary>
3640 <secondary>creating</secondary>
3642 <tertiary>root.afs</tertiary>
3646 <primary>creating</primary>
3648 <secondary>root.afs volume</secondary>
3652 <para>If you are installing the first AFS server machine ever in the cell (that is, you are not upgrading the AFS
3653 software from a previous version), create the first AFS volume, <emphasis role="bold">root.afs</emphasis>.</para>
3655 <para>For the <replaceable>partition name</replaceable> argument, substitute the name of one of the machine's AFS
3656 server partitions (such as <emphasis role="bold">/vicepa</emphasis>).</para>
3659 # <emphasis role="bold">./vos create</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>partition name</replaceable>> <emphasis
3660 role="bold">root.afs</emphasis> \
3661 <emphasis role="bold">-cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis role="bold">-noauth</emphasis>
3664 <para>The Volume Server produces a message confirming that it created the volume on the specified partition. You can
3665 ignore error messages indicating that tokens are missing, or that authentication failed. <indexterm>
3666 <primary>commands</primary>
3668 <secondary>vos syncvldb</secondary>
3669 </indexterm> <indexterm>
3670 <primary>vos commands</primary>
3672 <secondary>syncvldb</secondary>
3673 </indexterm> <indexterm>
3674 <primary>commands</primary>
3676 <secondary>vos syncserv</secondary>
3677 </indexterm> <indexterm>
3678 <primary>vos commands</primary>
3680 <secondary>syncserv</secondary>
3685 <para>If there are existing AFS file server machines and volumes in the cell, issue the <emphasis role="bold">vos
3686 syncvldb</emphasis> and <emphasis role="bold">vos syncserv</emphasis> commands to synchronize the VLDB with the
3687 actual state of volumes on the local machine. To follow the progress of the synchronization operation, which can
3688 take several minutes, use the <emphasis role="bold">-verbose</emphasis> flag. <programlisting>
3689 # <emphasis role="bold">./vos syncvldb</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">-cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis
3690 role="bold">-verbose -noauth</emphasis>
3691 # <emphasis role="bold">./vos syncserv</emphasis> <<replaceable>machine name</replaceable>> <emphasis role="bold">-cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis
3692 role="bold">-verbose -noauth</emphasis>
3693 </programlisting></para>
3695 <para>You can ignore error messages indicating that tokens are missing, or that authentication failed.</para>
3697 </itemizedlist></para>
3699 </orderedlist></para>
3702 <primary>Update Server</primary>
3704 <secondary>starting server portion</secondary>
3706 <tertiary>first AFS machine</tertiary>
3710 <primary>upserver process</primary>
3712 <see>Update Server</see>
3716 <primary>starting</primary>
3718 <secondary>Update Server server portion</secondary>
3720 <tertiary>first AFS machine</tertiary>
3724 <primary>first AFS machine</primary>
3726 <secondary>Update Server server portion</secondary>
3730 <primary>first AFS machine</primary>
3732 <secondary>defining</secondary>
3734 <tertiary>as binary distribution machine</tertiary>
3738 <primary>first AFS machine</primary>
3740 <secondary>defining</secondary>
3742 <tertiary>as system control machine</tertiary>
3746 <primary>system control machine</primary>
3750 <primary>binary distribution machine</primary>
3754 <sect1 id="HDRWQ61">
3755 <title>Starting the Server Portion of the Update Server</title>
3757 <para>Start the server portion of the Update Server (the <emphasis role="bold">upserver</emphasis> process), to distribute the
3758 contents of directories on this machine to other server machines in the cell. It becomes active when you configure the client
3759 portion of the Update Server on additional server machines.</para>
3761 <para>Distributing the contents of its <emphasis role="bold">/usr/afs/etc</emphasis> directory makes this machine the cell's
3762 <emphasis>system control machine</emphasis>. The other server machines in the cell run the <emphasis
3763 role="bold">upclientetc</emphasis> process (an instance of the client portion of the Update Server) to retrieve the
3764 configuration files. Use the <emphasis role="bold">-crypt</emphasis> argument to the <emphasis role="bold">upserver</emphasis>
3765 initialization command to specify that the Update Server distributes the contents of the <emphasis
3766 role="bold">/usr/afs/etc</emphasis> directory only in encrypted form, as shown in the following instruction. Several of the
3767 files in the directory, particularly the <emphasis role="bold">KeyFile</emphasis> file, are crucial to cell security and so must
3768 never cross the network unencrypted.</para>
3770 <para>(You can choose not to configure a system control machine, in which case you must update the configuration files in each
3771 server machine's <emphasis role="bold">/usr/afs/etc</emphasis> directory individually. The <emphasis role="bold">bos</emphasis>
3772 commands used for this purpose also encrypt data before sending it across the network.)</para>
3774 <para>Distributing the contents of its <emphasis role="bold">/usr/afs/bin</emphasis> directory to other server machines of its
3775 system type makes this machine a <emphasis>binary distribution machine</emphasis>. The other server machines of its system type
3776 run the <emphasis role="bold">upclientbin</emphasis> process (an instance of the client portion of the Update Server) to
3777 retrieve the binaries. If your platform has a package management system,
3778 such as 'rpm' or 'apt', running the Update Server to distribute binaries
3779 may interfere with this system.</para>
3781 <para>The binaries in the <emphasis role="bold">/usr/afs/bin</emphasis> directory are not sensitive, so it is not necessary to
3782 encrypt them before transfer across the network. Include the <emphasis role="bold">-clear</emphasis> argument to the <emphasis
3783 role="bold">upserver</emphasis> initialization command to specify that the Update Server distributes the contents of the
3784 <emphasis role="bold">/usr/afs/bin</emphasis> directory in unencrypted form unless an <emphasis
3785 role="bold">upclientbin</emphasis> process requests encrypted transfer.</para>
3787 <para>Note that the server and client portions of the Update Server always mutually authenticate with one another, regardless of
3788 whether you use the <emphasis role="bold">-clear</emphasis> or <emphasis role="bold">-crypt</emphasis> arguments. This protects
3789 their communications from eavesdropping to some degree.</para>
3791 <para>For more information on the <emphasis role="bold">upclient</emphasis> and <emphasis role="bold">upserver</emphasis>
3792 processes, see their reference pages in the <emphasis>OpenAFS Administration Reference</emphasis>. The commands appear on
3793 multiple lines here only for legibility. <orderedlist>
3795 <para>Issue the <emphasis role="bold">bos create</emphasis> command to start the <emphasis role="bold">upserver</emphasis>
3796 process. <programlisting>
3797 # <emphasis role="bold">./bos create</emphasis> <<replaceable>machine name></replaceable> <emphasis role="bold">upserver simple</emphasis> \
3798 <emphasis role="bold">"/usr/afs/bin/upserver -crypt /usr/afs/etc</emphasis> \
3799 <emphasis role="bold">-clear /usr/afs/bin" -cell</emphasis> <<replaceable>cell name</replaceable>> <emphasis
3800 role="bold">-noauth</emphasis>
3801 </programlisting></para>
3803 </orderedlist></para>
3806 <sect1 id="HDRWQ62">
3807 <title>Starting the Controller for NTPD</title>
3809 <para>Keeping the clocks on all server and client machines in your cell synchronized is crucial to several functions, and in
3810 particular to the correct operation of AFS's distributed database technology, Ubik. The chapter in the <emphasis>OpenAFS
3811 Administration Guide</emphasis> about administering server machines explains how time skew can disturb Ubik's performance and
3812 cause service outages in your cell.</para>
3814 <para>Historically, AFS used to distribute its own version of the Network
3815 Time Protocol Daemon. Whilst this is still provided for existing sites, we
3816 recommend that you configure and install your time service independently of
3817 AFS. A reliable timeservice will also be required by your Kerberos realm,
3818 and so may already be available at your site.</para>
3821 <primary>overview</primary>
3823 <secondary>installing client functionality on first machine</secondary>
3827 <primary>first AFS machine</primary>
3829 <secondary>client functionality</secondary>
3831 <tertiary>installing</tertiary>
3835 <primary>installing</primary>
3837 <secondary>client functionality</secondary>
3839 <tertiary>first AFS machine</tertiary>
3843 <sect1 id="HDRWQ63">
3844 <title>Overview: Installing Client Functionality</title>
3846 <para>The machine you are installing is now an AFS file server machine,
3847 database server machine, system control machine, and binary distribution
3848 machine. Now make it a client machine by completing the following tasks:
3851 <para>Define the machine's cell membership for client processes</para>
3855 <para>Create the client version of the <emphasis role="bold">CellServDB</emphasis> file</para>
3859 <para>Define cache location and size</para>
3863 <para>Create the <emphasis role="bold">/afs</emphasis> directory and start the Cache Manager</para>
3865 </orderedlist></para>
3868 <primary>Distribution</primary>
3870 <secondary>copying client files from</secondary>
3872 <tertiary>first AFS machine</tertiary>
3876 <primary>first AFS machine</primary>
3878 <secondary>copying</secondary>
3880 <tertiary>client files to local disk</tertiary>
3884 <primary>copying</primary>
3886 <secondary>client files to local disk</secondary>
3888 <tertiary>first AFS machine</tertiary>
3892 <sect1 id="HDRWQ64">
3893 <title>Copying Client Files to the Local Disk</title>
3895 <para>You need only undertake the steps in this section, if you are using
3896 a tar file distribution, or one built from scratch. Packaged distributions,
3897 such as RPMs or DEBs will already have installed the necessary files in
3898 the correct locations.</para>
3900 <para>Before installing and configuring the AFS client, copy the necessary files from the tarball to the local <emphasis
3901 role="bold">/usr/vice/etc</emphasis> directory. <orderedlist>
3903 <para>If you have not already done so, unpack the distribution
3904 tarball for this machine's system type into a suitable location on
3905 the filesystem, such as <emphasis role="bold">/tmp/afsdist</emphasis>.
3906 If you use a different location, substitue that in the examples that
3911 <para>Copy files to the local <emphasis role="bold">/usr/vice/etc</emphasis> directory.</para>
3913 <para>This step places a copy of the AFS initialization script (and related files, if applicable) into the <emphasis
3914 role="bold">/usr/vice/etc</emphasis> directory. In the preceding instructions for incorporating AFS into the kernel, you
3915 copied the script directly to the operating system's conventional location for initialization files. When you incorporate
3916 AFS into the machine's startup sequence in a later step, you can choose to link the two files.</para>
3918 <para>On some system types that use a dynamic kernel loader program, you previously copied AFS library files into a
3919 subdirectory of the <emphasis role="bold">/usr/vice/etc</emphasis> directory. On other system types, you copied the
3920 appropriate AFS library file directly to the directory where the operating system accesses it. The following commands do
3921 not copy or recopy the AFS library files into the <emphasis role="bold">/usr/vice/etc</emphasis> directory, because on
3922 some system types the library files consume a large amount of space. If you want to copy them, add the <emphasis
3923 role="bold">-r</emphasis> flag to the first <emphasis role="bold">cp</emphasis> command and skip the second <emphasis
3924 role="bold">cp</emphasis> command.</para>
3927 # <emphasis role="bold">cd /tmp/afsdist/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/root.client/usr/vice/etc</emphasis>
3928 # <emphasis role="bold">cp -p * /usr/vice/etc</emphasis>
3929 # <emphasis role="bold">cp -rp C /usr/vice/etc</emphasis>
3932 </orderedlist></para>
3935 <primary>cell name</primary>
3937 <secondary>setting in client ThisCell file</secondary>
3939 <tertiary>first AFS machine</tertiary>
3943 <primary>setting</primary>
3945 <secondary>cell name in client ThisCell file</secondary>
3947 <tertiary>first AFS machine</tertiary>
3951 <primary>first AFS machine</primary>
3953 <secondary>ThisCell file (client)</secondary>
3957 <primary>first AFS machine</primary>
3959 <secondary>cell membership, defining</secondary>
3961 <tertiary>for client processes</tertiary>
3965 <primary>usr/vice/etc/ThisCell</primary>
3967 <see>ThisCell file (client)</see>
3971 <primary>ThisCell file (client)</primary>
3973 <secondary>first AFS machine</secondary>
3977 <primary>files</primary>
3979 <secondary>ThisCell (client)</secondary>
3983 <sect1 id="HDRWQ65">
3984 <title>Defining Cell Membership for Client Processes</title>
3986 <para>Every AFS client machine has a copy of the <emphasis role="bold">/usr/vice/etc/ThisCell</emphasis> file on its local disk
3987 to define the machine's cell membership for the AFS client programs that run on it. The <emphasis
3988 role="bold">ThisCell</emphasis> file you created in the <emphasis role="bold">/usr/afs/etc</emphasis> directory (in <link
3989 linkend="HDRWQ51">Defining Cell Name and Membership for Server Processes</link>) is used only by server processes.</para>
3991 <para>Among other functions, the <emphasis role="bold">ThisCell</emphasis> file on a client machine determines the following:
3994 <para>The cell in which users gain tokens when they log onto the
3995 machine, assuming it is using an AFS-modified login utility</para>
3999 <para>The cell in which users gain tokens by default when they issue
4000 the <emphasis role="bold">aklog</emphasis> command</para>
4004 <para>The cell membership of the AFS server processes that the AFS
4005 command interpreters on this machine contact by default</para>
4010 <para>Change to the <emphasis role="bold">/usr/vice/etc</emphasis> directory and remove the symbolic link created in <link
4011 linkend="HDRWQ50">Starting the BOS Server</link>. <programlisting>
4012 # <emphasis role="bold">cd /usr/vice/etc</emphasis>
4013 # <emphasis role="bold">rm ThisCell</emphasis>
4014 </programlisting></para>
4018 <para>Create the <emphasis role="bold">ThisCell</emphasis> file as a copy of the <emphasis
4019 role="bold">/usr/afs/etc/ThisCell</emphasis> file. Defining the same local cell for both server and client processes leads
4020 to the most consistent AFS performance. <programlisting>
4021 # <emphasis role="bold">cp /usr/afs/etc/ThisCell ThisCell</emphasis>
4022 </programlisting></para>
4024 </orderedlist></para>
4027 <primary>database server machine</primary>
4029 <secondary>entry in client CellServDB file</secondary>
4031 <tertiary>on first AFS machine</tertiary>
4035 <primary>usr/vice/etc/CellServDB</primary>
4037 <see>CellServDB file (client)</see>
4041 <primary>CellServDB file (client)</primary>
4043 <secondary>creating</secondary>
4045 <tertiary>on first AFS machine</tertiary>
4049 <primary>creating</primary>
4051 <secondary>CellServDB file (client)</secondary>
4053 <tertiary>first AFS machine</tertiary>
4057 <primary>CellServDB file (client)</primary>
4059 <secondary>required format</secondary>
4063 <primary>requirements</primary>
4065 <secondary>CellServDB file format (client version)</secondary>
4069 <primary>files</primary>
4071 <secondary>CellServDB (client)</secondary>
4075 <primary>first AFS machine</primary>
4077 <secondary>CellServDB file (client)</secondary>
4081 <sect1 id="HDRWQ66">
4082 <title>Creating the Client CellServDB File</title>
4084 <para>The <emphasis role="bold">/usr/vice/etc/CellServDB</emphasis> file on a client machine's local disk lists the database
4085 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
4086 list of database server machines is wrong, then users working on this machine cannot access the cell. The chapter in the
4087 <emphasis>OpenAFS Administration Guide</emphasis> about administering client machines explains how to maintain the file after
4090 <para>As the <emphasis role="bold">afsd</emphasis> program initializes the Cache Manager, it copies the contents of the
4091 <emphasis role="bold">CellServDB</emphasis> file into kernel memory. The Cache Manager always consults the list in kernel memory
4092 rather than the <emphasis role="bold">CellServDB</emphasis> file itself. Between reboots of the machine, you can use the
4093 <emphasis role="bold">fs newcell</emphasis> command to update the list in kernel memory directly; see the chapter in the
4094 <emphasis>OpenAFS Administration Guide</emphasis> about administering client machines.</para>
4096 <para>The AFS distribution includes the file
4097 <emphasis role="bold">CellServDB.dist</emphasis>. It includes an entry for
4098 all AFS cells that agreed to share their database server machine
4099 information at the time the distribution was
4100 created. The definitive copy of this file is maintained at
4101 grand.central.org, and updates may be obtained from
4102 /afs/grand.central.org/service/CellServDB or
4103 <ulink url="http://grand.central.org/dl/cellservdb/CellServDB">
4104 http://grand.central.org/dl/cellservdb/CellServDB</ulink></para>
4106 <para>The <emphasis role="bold">CellServDB.dist</emphasis> file can be a
4107 good basis for the client <emphasis role="bold">CellServDB</emphasis> file,
4108 because all of the entries in it use the correct format. You can add or
4109 remove cell entries as you see fit. Depending on your cache manager
4110 configuration, additional steps (as detailed in
4111 <link linkend="HDRWQ91">Enabling Access to Foreign Cells</link>) may be
4112 required to enable the Cache Manager to actually reach the cells.</para>
4114 <para>In this section, you add an entry for the local cell to the local <emphasis role="bold">CellServDB</emphasis> file. The
4115 current working directory is still <emphasis role="bold">/usr/vice/etc</emphasis>. <orderedlist>
4117 <para>Remove the symbolic link created in <link linkend="HDRWQ50">Starting the BOS Server</link> and rename the <emphasis
4118 role="bold">CellServDB.sample</emphasis> file to <emphasis role="bold">CellServDB</emphasis>. <programlisting>
4119 # <emphasis role="bold">rm CellServDB</emphasis>
4120 # <emphasis role="bold">mv CellServDB.sample CellServDB</emphasis>
4121 </programlisting></para>
4125 <para>Add an entry for the local cell to the <emphasis role="bold">CellServDB</emphasis> file. One easy method is to use
4126 the <emphasis role="bold">cat</emphasis> command to append the contents of the server <emphasis
4127 role="bold">/usr/afs/etc/CellServDB</emphasis> file to the client version. <programlisting>
4128 # <emphasis role="bold">cat /usr/afs/etc/CellServDB >> CellServDB</emphasis>
4129 </programlisting></para>
4131 <para>Then open the file in a text editor to verify that there are no blank lines, and that all entries have the required
4132 format, which is described just following. The ordering of cells is not significant, but it can be convenient to have the
4133 client machine's home cell at the top; move it there now if you wish. <itemizedlist>
4135 <para>The first line of a cell's entry has the following format: <programlisting>
4136 ><replaceable>cell_name</replaceable> #<replaceable>organization</replaceable>
4137 </programlisting></para>
4139 <para>where <replaceable>cell_name</replaceable> is the cell's complete Internet domain name (for example, <emphasis
4140 role="bold">example.com</emphasis>) and <replaceable>organization</replaceable> is an optional field that follows any
4141 number of spaces and the number sign (<computeroutput>#</computeroutput>). By convention it names the organization
4142 to which the cell corresponds (for example, the Example Corporation).</para>
4146 <para>After the first line comes a separate line for each database server machine. Each line has the following
4147 format: <programlisting>
4148 <replaceable>IP_address</replaceable> #<replaceable>machine_name</replaceable>
4149 </programlisting></para>
4151 <para>where <replaceable>IP_address</replaceable> is the machine's IP address in dotted decimal format (for example,
4152 192.12.105.3). Following any number of spaces and the number sign (<computeroutput>#</computeroutput>) is
4153 <replaceable>machine_name</replaceable>, the machine's fully-qualified hostname (for example, <emphasis
4154 role="bold">db1.example.com</emphasis>). In this case, the number sign does not indicate a comment;
4155 <replaceable>machine_name</replaceable> is a required field.</para>
4157 </itemizedlist></para>
4161 <para>If the file includes cells that you do not wish users of this machine to access, remove their entries.</para>
4163 </orderedlist></para>
4165 <para>The following example shows entries for two cells, each of which has three database server machines:</para>
4168 >example.com #Example Corporation (home cell)
4169 192.12.105.3 #db1.example.com
4170 192.12.105.4 #db2.example.com
4171 192.12.105.55 #db3.example.com
4172 >stateu.edu #State University cell
4173 138.255.68.93 #serverA.stateu.edu
4174 138.255.68.72 #serverB.stateu.edu
4175 138.255.33.154 #serverC.stateu.edu
4179 <primary>cache</primary>
4181 <secondary>configuring</secondary>
4183 <tertiary>first AFS machine</tertiary>
4187 <primary>configuring</primary>
4189 <secondary>cache</secondary>
4191 <tertiary>first AFS machine</tertiary>
4195 <primary>setting</primary>
4197 <secondary>cache size and location</secondary>
4199 <tertiary>first AFS machine</tertiary>
4203 <primary>first AFS machine</primary>
4205 <secondary>cache size and location</secondary>
4209 <sect1 id="HDRWQ67">
4210 <title>Configuring the Cache</title>
4212 <para>The Cache Manager uses a cache on the local disk or in machine memory to store local copies of files fetched from file
4213 server machines. As the <emphasis role="bold">afsd</emphasis> program initializes the Cache Manager, it sets basic cache
4214 configuration parameters according to definitions in the local <emphasis role="bold">/usr/vice/etc/cacheinfo</emphasis> file.
4215 The file has three fields: <orderedlist>
4217 <para>The first field names the local directory on which to mount the AFS filespace. The conventional location is the
4218 <emphasis role="bold">/afs</emphasis> directory.</para>
4222 <para>The second field defines the local disk directory to use for the disk cache. The conventional location is the
4223 <emphasis role="bold">/usr/vice/cache</emphasis> directory, but you can specify an alternate directory if another
4224 partition has more space available. There must always be a value in this field, but the Cache Manager ignores it if the
4225 machine uses a memory cache.</para>
4229 <para>The third field specifies the number of kilobyte (1024 byte) blocks to allocate for the cache.</para>
4231 </orderedlist></para>
4233 <para>The values you define must meet the following requirements. <itemizedlist>
4235 <para>On a machine using a disk cache, the Cache Manager expects always to be able to use the amount of space specified in
4236 the third field. Failure to meet this requirement can cause serious problems, some of which can be repaired only by
4237 rebooting. You must prevent non-AFS processes from filling up the cache partition. The simplest way is to devote a
4238 partition to the cache exclusively.</para>
4242 <para>The amount of space available in memory or on the partition housing the disk cache directory imposes an absolute
4243 limit on cache size.</para>
4247 <para>The maximum supported cache size can vary in each AFS release; see the <emphasis>OpenAFS Release Notes</emphasis>
4248 for the current version.</para>
4252 <para>For a disk cache, you cannot specify a value in the third field that exceeds 95% of the space available on the
4253 partition mounted at the directory named in the second field. If you violate this restriction, the <emphasis
4254 role="bold">afsd</emphasis> program exits without starting the Cache Manager and prints an appropriate message on the
4255 standard output stream. A value of 90% is more appropriate on most machines. Some operating systems (such as AIX) do not
4256 automatically reserve some space to prevent the partition from filling completely; for them, a smaller value (say, 80% to
4257 85% of the space available) is more appropriate.</para>
4261 <para>For a memory cache, you must leave enough memory for other processes and applications to run. If you try to allocate
4262 more memory than is actually available, the <emphasis role="bold">afsd</emphasis> program exits without initializing the
4263 Cache Manager and produces the following message on the standard output stream. <programlisting>
4264 afsd: memCache allocation failure at <replaceable>number</replaceable> KB
4265 </programlisting></para>
4267 <para>The <replaceable>number</replaceable> value is how many kilobytes were allocated just before the failure, and so
4268 indicates the approximate amount of memory available.</para>
4270 </itemizedlist></para>
4272 <para>Within these hard limits, the factors that determine appropriate cache size include the number of users working on the
4273 machine, the size of the files with which they work, and (for a memory cache) the number of processes that run on the machine.
4274 The higher the demand from these factors, the larger the cache needs to be to maintain good performance.</para>
4276 <para>Disk caches smaller than 10 MB do not generally perform well. Machines serving multiple users usually perform better with
4277 a cache of at least 60 to 70 MB. The point at which enlarging the cache further does not really improve performance depends on
4278 the factors mentioned previously and is difficult to predict.</para>
4280 <para>Memory caches smaller than 1 MB are nonfunctional, and the performance of caches smaller than 5 MB is usually
4281 unsatisfactory. Suitable upper limits are similar to those for disk caches but are probably determined more by the demands on
4282 memory from other sources on the machine (number of users and processes). Machines running only a few processes possibly can use
4283 a smaller memory cache.</para>
4285 <sect2 id="HDRWQ68">
4286 <title>Configuring a Disk Cache</title>
4289 <para>Not all file system types that an operating system supports are necessarily supported for use as the cache partition.
4290 For possible restrictions, see the <emphasis>OpenAFS Release Notes</emphasis>.</para>
4293 <para>To configure the disk cache, perform the following procedures: <orderedlist>
4295 <para>Create the local directory to use for caching. The following instruction shows the conventional location,
4296 <emphasis role="bold">/usr/vice/cache</emphasis>. If you are devoting a partition exclusively to caching, as
4297 recommended, you must also configure it, make a file system on it, and mount it at the directory created in this step.
4299 # <emphasis role="bold">mkdir /usr/vice/cache</emphasis>
4300 </programlisting></para>
4304 <para>Create the <emphasis role="bold">cacheinfo</emphasis> file to define the configuration parameters discussed
4305 previously. The following instruction shows the standard mount location, <emphasis role="bold">/afs</emphasis>, and the
4306 standard cache location, <emphasis role="bold">/usr/vice/cache</emphasis>. <programlisting>
4307 # <emphasis role="bold">echo "/afs:/usr/vice/cache:</emphasis><replaceable>#blocks</replaceable><emphasis role="bold">" > /usr/vice/etc/cacheinfo</emphasis>
4308 </programlisting></para>
4310 <para>The following example defines the disk cache size as 50,000 KB:</para>
4313 # <emphasis role="bold">echo "/afs:/usr/vice/cache:50000" > /usr/vice/etc/cacheinfo</emphasis>
4316 </orderedlist></para>
4319 <sect2 id="HDRWQ69">
4320 <title>Configuring a Memory Cache</title>
4322 <para>To configure a memory cache, create the <emphasis role="bold">cacheinfo</emphasis> file to define the configuration
4323 parameters discussed previously. The following instruction shows the standard mount location, <emphasis
4324 role="bold">/afs</emphasis>, and the standard cache location, <emphasis role="bold">/usr/vice/cache</emphasis> (though the
4325 exact value of the latter is irrelevant for a memory cache).</para>
4328 # <emphasis role="bold">echo "/afs:/usr/vice/cache:</emphasis><replaceable>#blocks</replaceable><emphasis role="bold">" > /usr/vice/etc/cacheinfo</emphasis>
4331 <para>The following example allocates 25,000 KB of memory for the cache.</para>
4334 # <emphasis role="bold">echo "/afs:/usr/vice/cache:25000" > /usr/vice/etc/cacheinfo</emphasis>
4338 <primary>Cache Manager</primary>
4340 <secondary>first AFS machine</secondary>
4344 <primary>configuring</primary>
4346 <secondary>Cache Manager</secondary>
4348 <tertiary>first AFS machine</tertiary>
4352 <primary>first AFS machine</primary>
4354 <secondary>Cache Manager</secondary>
4358 <primary>afs (/afs) directory</primary>
4360 <secondary>creating</secondary>
4362 <tertiary>first AFS machine</tertiary>
4366 <primary>AFS initialization script</primary>
4368 <secondary>setting afsd parameters</secondary>
4370 <tertiary>first AFS machine</tertiary>
4374 <primary>first AFS machine</primary>
4376 <secondary>afsd command parameters</secondary>
4381 <sect1 id="HDRWQ70">
4382 <title>Configuring the Cache Manager</title>
4384 <para>By convention, the Cache Manager mounts the AFS filespace on the local <emphasis role="bold">/afs</emphasis> directory. In
4385 this section you create that directory.</para>
4387 <para>The <emphasis role="bold">afsd</emphasis> program sets several cache configuration parameters as it initializes the Cache
4388 Manager, and starts daemons that improve performance. You can use the <emphasis role="bold">afsd</emphasis> command's arguments
4389 to override the parameters' default values and to change the number of some of the daemons. Depending on the machine's cache
4390 size, its amount of RAM, and how many people work on it, you can sometimes improve Cache Manager performance by overriding the
4391 default values. For a discussion of all of the <emphasis role="bold">afsd</emphasis> command's arguments, see its reference page
4392 in the <emphasis>OpenAFS Administration Reference</emphasis>.</para>
4394 <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
4395 <computeroutput>OPTIONS</computeroutput> variable. You can use it to set nondefault values for the command's arguments, in one
4396 of the following ways: <itemizedlist>
4398 <para>You can create an <emphasis role="bold">afsd</emphasis> <emphasis>options file</emphasis> that sets values for
4399 arguments to the <emphasis role="bold">afsd</emphasis> command. If the file exists, its contents are automatically
4400 substituted for the <computeroutput>OPTIONS</computeroutput> variable in the AFS initialization script. The AFS
4401 distribution for some system types includes an options file; on other system types, you must create it.</para>
4403 <para>You use two variables in the AFS initialization script to specify the path to the options file:
4404 <computeroutput>CONFIG</computeroutput> and <computeroutput>AFSDOPT</computeroutput>. On system types that define a
4405 conventional directory for configuration files, the <computeroutput>CONFIG</computeroutput> variable indicates it by
4406 default; otherwise, the variable indicates an appropriate location.</para>
4408 <para>List the desired <emphasis role="bold">afsd</emphasis> options on a single line in the options file, separating each
4409 option with one or more spaces. The following example sets the <emphasis role="bold">-stat</emphasis> argument to 2500,
4410 the <emphasis role="bold">-daemons</emphasis> argument to 4, and the <emphasis role="bold">-volumes</emphasis> argument to
4414 -stat 2500 -daemons 4 -volumes 100
4419 <para>On a machine that uses a disk cache, you can set the <computeroutput>OPTIONS</computeroutput> variable in the AFS
4420 initialization script to one of <computeroutput>$SMALL</computeroutput>, <computeroutput>$MEDIUM</computeroutput>, or
4421 <computeroutput>$LARGE</computeroutput>. The AFS initialization script uses one of these settings if the <emphasis
4422 role="bold">afsd</emphasis> options file named by the <computeroutput>AFSDOPT</computeroutput> variable does not exist. In
4423 the script as distributed, the <computeroutput>OPTIONS</computeroutput> variable is set to the value
4424 <computeroutput>$MEDIUM</computeroutput>.</para>
4427 <para>Do not set the <computeroutput>OPTIONS</computeroutput> variable to <computeroutput>$SMALL</computeroutput>,
4428 <computeroutput>$MEDIUM</computeroutput>, or <computeroutput>$LARGE</computeroutput> on a machine that uses a memory
4429 cache. The arguments it sets are appropriate only on a machine that uses a disk cache.</para>
4432 <para>The script (or on some system types the <emphasis role="bold">afsd</emphasis> options file named by the
4433 <computeroutput>AFSDOPT</computeroutput> variable) defines a value for each of <computeroutput>SMALL</computeroutput>,
4434 <computeroutput>MEDIUM</computeroutput>, and <computeroutput>LARGE</computeroutput> that sets <emphasis
4435 role="bold">afsd</emphasis> command arguments appropriately for client machines of different sizes: <itemizedlist>
4437 <para><computeroutput>SMALL</computeroutput> is suitable for a small machine that serves one or two users and has
4438 approximately 8 MB of RAM and a 20-MB cache</para>
4442 <para><computeroutput>MEDIUM</computeroutput> is suitable for a medium-sized machine that serves two to six users
4443 and has 16 MB of RAM and a 40-MB cache</para>
4447 <para><computeroutput>LARGE</computeroutput> is suitable for a large machine that serves five to ten users and has
4448 32 MB of RAM and a 100-MB cache</para>
4450 </itemizedlist></para>
4454 <para>You can choose not to create an <emphasis role="bold">afsd</emphasis> options file and to set the
4455 <computeroutput>OPTIONS</computeroutput> variable in the initialization script to a null value rather than to the default
4456 <computeroutput>$MEDIUM</computeroutput> value. You can then either set arguments directly on the <emphasis
4457 role="bold">afsd</emphasis> command line in the script, or set no arguments (and so accept default values for all Cache
4458 Manager parameters).</para>
4463 <para>If you are running on a Fedora or RHEL based system, the
4464 openafs-client initialization script behaves differently from that
4465 described above. It sources /etc/sysconfig/openafs, in which the
4466 AFSD_ARGS variable may be set to contain any, or all, of the afsd options
4467 detailed. Note that this script does not support setting an OPTIONS
4468 variable, or the SMALL, MEDIUM and LARGE methods of defining cache size
4474 <para>Create the local directory on which to mount the AFS filespace, by convention <emphasis role="bold">/afs</emphasis>.
4475 If the directory already exists, verify that it is empty. <programlisting>
4476 # <emphasis role="bold">mkdir /afs</emphasis>
4477 </programlisting></para>
4481 <para>On AIX systems, add the following line to the <emphasis role="bold">/etc/vfs</emphasis> file. It enables AIX to
4482 unmount AFS correctly during shutdown. <programlisting>
4484 </programlisting></para>
4488 <para>On non-package based Linux systems, copy the <emphasis role="bold">afsd</emphasis> options file from the <emphasis
4489 role="bold">/usr/vice/etc</emphasis> directory to the <emphasis role="bold">/etc/sysconfig</emphasis> directory, removing
4490 the <emphasis role="bold">.conf</emphasis> extension as you do so. <programlisting>
4491 # <emphasis role="bold">cp /usr/vice/etc/afs.conf /etc/sysconfig/afs</emphasis>
4492 </programlisting></para>
4496 <para>Edit the machine's AFS initialization script or <emphasis role="bold">afsd</emphasis> options file to set
4497 appropriate values for <emphasis role="bold">afsd</emphasis> command parameters. The script resides in the indicated
4498 location on each system type: <itemizedlist>
4500 <para>On AIX systems, <emphasis role="bold">/etc/rc.afs</emphasis></para>
4504 <para>On HP-UX systems, <emphasis role="bold">/sbin/init.d/afs</emphasis></para>
4508 <para>On IRIX systems, <emphasis role="bold">/etc/init.d/afs</emphasis></para>
4512 <para>On Fedora and RHEL systems, <emphasis role="bold">/etc/sysconfg/openafs</emphasis></para>
4516 <para>On non-package based Linux systems, <emphasis role="bold">/etc/sysconfig/afs</emphasis> (the <emphasis
4517 role="bold">afsd</emphasis> options file)</para>
4521 <para>On Solaris systems, <emphasis role="bold">/etc/init.d/afs</emphasis></para>
4523 </itemizedlist></para>
4525 <para>Use one of the methods described in the introduction to this section to add the following flags to the <emphasis
4526 role="bold">afsd</emphasis> command line. If you intend for the machine to remain an AFS client, also set any
4527 performance-related arguments you wish. <itemizedlist>
4529 <para>Add the <emphasis role="bold">-memcache</emphasis> flag if the machine is to use a memory cache.</para>
4533 <para>Add the <emphasis role="bold">-verbose</emphasis> flag to display a trace of the Cache Manager's
4534 initialization on the standard output stream.</para>
4536 </itemizedlist></para>
4539 <note><para>In order to successfully complete the instructions in the
4540 remainder of this guide, it is important that the machine does not have
4541 a synthetic root (as discussed in <link linkend="HDRWQ91">Enabling Access
4542 to Foreign Cells</link>). As some distributions ship with this enabled, it
4543 may be necessary to remove any occurences of the
4544 <emphasis role="bold">-dynroot</emphasis> and
4545 <emphasis role="bold">-afsdb</emphasis> options from both the AFS
4546 initialisation script and options file. If this functionality is
4547 required it may be renabled as detailed in
4548 <link linkend="HDRWQ91">Enabling Access to Foreign Cells</link>.
4553 <primary>overview</primary>
4555 <secondary>completing installation of first machine</secondary>
4559 <primary>first AFS machine</primary>
4561 <secondary>completion of installation</secondary>
4565 <sect1 id="HDRWQ71">
4566 <title>Overview: Completing the Installation of the First AFS Machine</title>
4568 <para>The machine is now configured as an AFS file server and client machine. In this final phase of the installation, you
4569 initialize the Cache Manager and then create the upper levels of your AFS filespace, among other procedures. The procedures are:
4572 <para>Verify that the initialization script works correctly, and incorporate it into the operating system's startup and
4573 shutdown sequence</para>
4577 <para>Create and mount top-level volumes</para>
4581 <para>Create and mount volumes to store system binaries in AFS</para>
4585 <para>Enable access to foreign cells</para>
4589 <para>Institute additional security measures</para>
4593 <para>Remove client functionality if desired</para>
4595 </orderedlist></para>
4598 <primary>AFS initialization script</primary>
4600 <secondary>verifying on first AFS machine</secondary>
4604 <primary>AFS initialization script</primary>
4606 <secondary>running</secondary>
4608 <tertiary>first AFS machine</tertiary>
4612 <primary>first AFS machine</primary>
4614 <secondary>AFS initialization script</secondary>
4616 <tertiary>running/verifying</tertiary>
4620 <primary>running AFS init. script</primary>
4622 <secondary>first AFS machine</secondary>
4626 <primary>invoking AFS init. script</primary>
4632 <sect1 id="HDRWQ72">
4633 <title>Verifying the AFS Initialization Script</title>
4635 <para>At this point you run the AFS initialization script to verify that it correctly invokes all of the necessary programs and
4636 AFS processes, and that they start correctly. The following are the relevant commands: <itemizedlist>
4638 <para>The command that dynamically loads AFS modifications into the kernel, on some system types (not applicable if the
4639 kernel has AFS modifications built in)</para>
4643 <para>The <emphasis role="bold">bosserver</emphasis> command, which starts the BOS Server; it in turn starts the server
4644 processes for which you created entries in the <emphasis role="bold">/usr/afs/local/BosConfig</emphasis> file</para>
4648 <para>The <emphasis role="bold">afsd</emphasis> command, which initializes the Cache Manager</para>
4650 </itemizedlist></para>
4652 <para>On system types that use a dynamic loader program, you must reboot the machine before running the initialization script,
4653 so that it can freshly load AFS modifications into the kernel.</para>
4655 <para>If there are problems during the initialization, attempt to resolve them. The OpenAFS mailing lists can provide assistance if necessary.
4659 <primary>commands</primary>
4661 <secondary>bos shutdown</secondary>
4665 <primary>bos commands</primary>
4667 <secondary>shutdown</secondary>
4671 <para>Issue the <emphasis role="bold">bos shutdown</emphasis> command to shut down the AFS server processes other than the
4672 BOS Server. Include the <emphasis role="bold">-wait</emphasis> flag to delay return of the command shell prompt until all
4673 processes shut down completely. <programlisting>
4674 # <emphasis role="bold">/usr/afs/bin/bos shutdown</emphasis> <<replaceable>machine name</replaceable>> <emphasis
4675 role="bold">-wait</emphasis>
4676 </programlisting></para>
4680 <para>Issue the <emphasis role="bold">ps</emphasis> command to learn the <emphasis role="bold">bosserver</emphasis>
4681 process's process ID number (PID), and then the <emphasis role="bold">kill</emphasis> command to stop it. <programlisting>
4682 # <emphasis role="bold">ps</emphasis> <replaceable>appropriate_ps_options</replaceable> <emphasis role="bold">| grep bosserver</emphasis>
4683 # <emphasis role="bold">kill</emphasis> <replaceable>bosserver_PID</replaceable>
4684 </programlisting></para>
4688 <para>Issue the appropriate commands to run the AFS initialization script for this system type.</para>
4691 <primary>AIX</primary>
4693 <secondary>AFS initialization script</secondary>
4695 <tertiary>on first AFS machine</tertiary>
4698 <para><emphasis role="bold">On AIX systems:</emphasis> <orderedlist>
4700 <para>Reboot the machine and log in again as the local superuser <emphasis role="bold">root</emphasis>.
4702 # <emphasis role="bold">cd /</emphasis>
4703 # <emphasis role="bold">shutdown -r now</emphasis>
4704 login: <emphasis role="bold">root</emphasis>
4705 Password: <replaceable>root_password</replaceable>
4706 </programlisting></para>
4710 <para>Run the AFS initialization script. <programlisting>
4711 # <emphasis role="bold">/etc/rc.afs</emphasis>
4712 </programlisting></para>
4714 </orderedlist></para>
4717 <primary>HP-UX</primary>
4719 <secondary>AFS initialization script</secondary>
4721 <tertiary>on first AFS machine</tertiary>
4724 <para><emphasis role="bold">On HP-UX systems:</emphasis> <orderedlist>
4726 <para>Run the AFS initialization script. <programlisting>
4727 # <emphasis role="bold">/sbin/init.d/afs start</emphasis>
4728 </programlisting></para>
4730 </orderedlist></para>
4733 <primary>IRIX</primary>
4735 <secondary>AFS initialization script</secondary>
4737 <tertiary>on first AFS machine</tertiary>
4741 <primary>afsclient variable (IRIX)</primary>
4743 <secondary>first AFS machine</secondary>
4747 <primary>variables</primary>
4749 <secondary>afsclient (IRIX)</secondary>
4751 <tertiary>first AFS machine</tertiary>
4755 <primary>IRIX</primary>
4757 <secondary>afsclient variable</secondary>
4759 <tertiary>first AFS machine</tertiary>
4763 <primary>afsserver variable (IRIX)</primary>
4765 <secondary>first AFS machine</secondary>
4769 <primary>variables</primary>
4771 <secondary>afsserver (IRIX)</secondary>
4773 <tertiary>first AFS machine</tertiary>
4777 <primary>IRIX</primary>
4779 <secondary>afsserver variable</secondary>
4781 <tertiary>first AFS machine</tertiary>
4784 <para><emphasis role="bold">On IRIX systems:</emphasis> <orderedlist>
4786 <para>If you have configured the machine to use the <emphasis role="bold">ml</emphasis> dynamic loader program,
4787 reboot the machine and log in again as the local superuser <emphasis role="bold">root</emphasis>. <programlisting>
4788 # <emphasis role="bold">cd /</emphasis>
4789 # <emphasis role="bold">shutdown -i6 -g0 -y</emphasis>
4790 login: <emphasis role="bold">root</emphasis>
4791 Password: <replaceable>root_password</replaceable>
4792 </programlisting></para>
4796 <para>Issue the <emphasis role="bold">chkconfig</emphasis> command to activate the <emphasis
4797 role="bold">afsserver</emphasis> and <emphasis role="bold">afsclient</emphasis> configuration variables.
4799 # <emphasis role="bold">/etc/chkconfig -f afsserver on</emphasis>
4800 # <emphasis role="bold">/etc/chkconfig -f afsclient on</emphasis>
4801 </programlisting></para>
4805 <para>Run the AFS initialization script. <programlisting>
4806 # <emphasis role="bold">/etc/init.d/afs start</emphasis>
4807 </programlisting></para>
4809 </orderedlist></para>
4812 <primary>Linux</primary>
4814 <secondary>AFS initialization script</secondary>
4816 <tertiary>on first AFS machine</tertiary>
4819 <para><emphasis role="bold">On Linux systems:</emphasis> <orderedlist>
4821 <para>Reboot the machine and log in again as the local superuser <emphasis role="bold">root</emphasis>.
4823 # <emphasis role="bold">cd /</emphasis>
4824 # <emphasis role="bold">shutdown -r now</emphasis>
4825 login: <emphasis role="bold">root</emphasis>
4826 Password: <replaceable>root_password</replaceable>
4827 </programlisting></para>
4831 <para>Run the AFS initialization scripts.
4833 # <emphasis role="bold">/etc/rc.d/init.d/openafs-client start</emphasis>
4834 # <emphasis role="bold">/etc/rc.d/init.d/openafs-server start</emphasis>
4835 </programlisting></para>
4837 </orderedlist></para>
4840 <primary>Solaris</primary>
4842 <secondary>AFS initialization script</secondary>
4844 <tertiary>on first AFS machine</tertiary>
4847 <para><emphasis role="bold">On Solaris systems:</emphasis> <orderedlist>
4849 <para>Reboot the machine and log in again as the local superuser <emphasis role="bold">root</emphasis>.
4851 # <emphasis role="bold">cd /</emphasis>
4852 # <emphasis role="bold">shutdown -i6 -g0 -y</emphasis>
4853 login: <emphasis role="bold">root</emphasis>
4854 Password: <replaceable>root_password</replaceable>
4855 </programlisting></para>
4859 <para>Run the AFS initialization script. <programlisting>
4860 # <emphasis role="bold">/etc/init.d/afs start</emphasis>
4861 </programlisting></para>
4863 </orderedlist></para>
4867 <para>Wait for the message that confirms that Cache Manager initialization is complete.</para>
4869 <para>On machines that use a disk cache, it can take a while to initialize the Cache Manager for the first time, because
4870 the <emphasis role="bold">afsd</emphasis> program must create all of the <emphasis
4871 role="bold">V</emphasis><replaceable>n</replaceable> files in the cache directory. Subsequent Cache Manager
4872 initializations do not take nearly as long, because the <emphasis role="bold">V</emphasis><replaceable>n</replaceable>
4873 files already exist.</para>
4878 <primary>commands</primary>
4879 <secondary>aklog</secondary>
4883 <primary>aklog command</primary>
4886 <para>If you are working with an existing cell which uses
4887 <emphasis role="bold">kaserver</emphasis> for authentication,
4888 please recall the note in
4889 <link linkend="KAS003">Using this Appendix</link> detailing the
4890 substitution of <emphasis role="bold">kinit</emphasis> and
4891 <emphasis role="bold">aklog</emphasis> with
4892 <emphasis role="bold">klog</emphasis>.</para>
4894 <para>As a basic test of correct AFS functioning, issue the
4895 <emphasis role="bold">kinit</emphasis> and
4896 <emphasis role="bold">aklog</emphasis> commands to authenticate
4897 as the <emphasis role="bold">admin</emphasis> user.
4898 Provide the password (<replaceable>admin_passwd</replaceable>) you
4899 defined in <link linkend="HDRWQ53">Initializing Cell Security</link>.</para>
4902 # <emphasis role="bold">kinit admin</emphasis>
4903 Password: <replaceable>admin_passwd</replaceable>
4904 # <emphasis role="bold">aklog</emphasis>
4908 <primary>commands</primary>
4910 <secondary>tokens</secondary>
4914 <primary>tokens command</primary>
4919 <para>Issue the <emphasis role="bold">tokens</emphasis> command to
4920 verify that the <emphasis role="bold">aklog</emphasis>
4921 command worked correctly. If it did, the output looks similar to the following example for the <emphasis
4922 role="bold">example.com</emphasis> cell, where <emphasis role="bold">admin</emphasis>'s AFS UID is 1. If the output does not
4923 seem correct, resolve the problem. Changes to the AFS initialization script are possibly necessary. The OpenAFS mailing lists can provide assistance as necessary. <programlisting>
4924 # <emphasis role="bold">tokens</emphasis>
4925 Tokens held by the Cache Manager:
4926 User's (AFS ID 1) tokens for afs@example.com [Expires May 22 11:52]
4928 </programlisting></para>
4932 <para>Issue the <emphasis role="bold">bos status</emphasis> command to verify that the output for each process reads
4933 <computeroutput>Currently running normally</computeroutput>. <programlisting>
4934 # <emphasis role="bold">/usr/afs/bin/bos status</emphasis> <<replaceable>machine name</replaceable>>
4935 </programlisting> <indexterm>
4936 <primary>fs commands</primary>
4938 <secondary>checkvolumes</secondary>
4939 </indexterm> <indexterm>
4940 <primary>commands</primary>
4942 <secondary>fs checkvolumes</secondary>
4947 <para>Change directory to the local file system root (<emphasis role="bold">/</emphasis>) and issue the <emphasis
4948 role="bold">fs checkvolumes</emphasis> command. <programlisting>
4949 # <emphasis role="bold">cd /</emphasis>
4950 # <emphasis role="bold">/usr/afs/bin/fs checkvolumes</emphasis>
4951 </programlisting></para>
4953 </orderedlist></para>
4956 <primary>AFS initialization script</primary>
4958 <secondary>adding to machine startup sequence</secondary>
4960 <tertiary>first AFS machine</tertiary>
4964 <primary>installing</primary>
4966 <secondary>AFS initialization script</secondary>
4968 <tertiary>first AFS machine</tertiary>
4972 <primary>first AFS machine</primary>
4974 <secondary>AFS initialization script</secondary>
4976 <tertiary>activating</tertiary>
4980 <primary>activating AFS init. script</primary>
4982 <see>installing</see>
4986 <sect1 id="HDRWQ73">
4987 <title>Activating the AFS Initialization Script</title>
4989 <para>Now that you have confirmed that the AFS initialization script works correctly, take the action necessary to have it run
4990 automatically at each reboot. Proceed to the instructions for your system type: <itemizedlist>
4992 <para><link linkend="HDRWQ74">Activating the Script on AIX Systems</link></para>
4996 <para><link linkend="HDRWQ76">Activating the Script on HP-UX Systems</link></para>
5000 <para><link linkend="HDRWQ77">Activating the Script on IRIX Systems</link></para>
5004 <para><link linkend="HDRWQ78">Activating the Script on Linux Systems</link></para>
5008 <para><link linkend="HDRWQ79">Activating the Script on Solaris Systems</link></para>
5010 </itemizedlist></para>
5013 <primary>AIX</primary>
5015 <secondary>AFS initialization script</secondary>
5017 <tertiary>on first AFS machine</tertiary>
5020 <sect2 id="HDRWQ74">
5021 <title>Activating the Script on AIX Systems</title>
5025 <para>Edit the AIX initialization file, <emphasis role="bold">/etc/inittab</emphasis>, adding the following line to invoke
5026 the AFS initialization script. Place it just after the line that starts NFS daemons. <programlisting>
5027 rcafs:2:wait:/etc/rc.afs > /dev/console 2>&1 # Start AFS services
5028 </programlisting></para>
5032 <para><emphasis role="bold">(Optional)</emphasis> There are now copies of the AFS initialization file in both the
5033 <emphasis role="bold">/usr/vice/etc</emphasis> and <emphasis role="bold">/etc</emphasis> directories. If you want to avoid
5034 potential confusion by guaranteeing that they are always the same, create a link between them. You can always retrieve the
5035 original script from the AFS CD-ROM if necessary. <programlisting>
5036 # <emphasis role="bold">cd /usr/vice/etc</emphasis>
5037 # <emphasis role="bold">rm rc.afs</emphasis>
5038 # <emphasis role="bold">ln -s /etc/rc.afs</emphasis>
5039 </programlisting></para>
5043 <para>Proceed to <link linkend="HDRWQ80">Configuring the Top Levels of the AFS Filespace</link>.</para>
5048 <primary>HP-UX</primary>
5050 <secondary>AFS initialization script</secondary>
5052 <tertiary>on first AFS machine</tertiary>
5056 <sect2 id="HDRWQ76">
5057 <title>Activating the Script on HP-UX Systems</title>
5061 <para>Change to the <emphasis role="bold">/sbin/init.d</emphasis> directory and issue the <emphasis role="bold">ln
5062 -s</emphasis> command to create symbolic links that incorporate the AFS initialization script into the HP-UX startup and
5063 shutdown sequence. <programlisting>
5064 # <emphasis role="bold">cd /sbin/init.d</emphasis>
5065 # <emphasis role="bold">ln -s ../init.d/afs /sbin/rc2.d/S460afs</emphasis>
5066 # <emphasis role="bold">ln -s ../init.d/afs /sbin/rc2.d/K800afs</emphasis>
5067 </programlisting></para>
5071 <para><emphasis role="bold">(Optional)</emphasis> There are now copies of the AFS initialization file in both the
5072 <emphasis role="bold">/usr/vice/etc</emphasis> and <emphasis role="bold">/sbin/init.d</emphasis> directories. If you want
5073 to avoid potential confusion by guaranteeing that they are always the same, create a link between them. You can always
5074 retrieve the original script from the AFS CD-ROM if necessary. <programlisting>
5075 # <emphasis role="bold">cd /usr/vice/etc</emphasis>
5076 # <emphasis role="bold">rm afs.rc</emphasis>
5077 # <emphasis role="bold">ln -s /sbin/init.d/afs afs.rc</emphasis>
5078 </programlisting></para>
5082 <para>Proceed to <link linkend="HDRWQ80">Configuring the Top Levels of the AFS Filespace</link>.</para>
5087 <primary>IRIX</primary>
5089 <secondary>AFS initialization script</secondary>
5091 <tertiary>on first AFS machine</tertiary>
5095 <sect2 id="HDRWQ77">
5096 <title>Activating the Script on IRIX Systems</title>
5100 <para>Change to the <emphasis role="bold">/etc/init.d</emphasis> directory and issue the <emphasis role="bold">ln
5101 -s</emphasis> command to create symbolic links that incorporate the AFS initialization script into the IRIX startup and
5102 shutdown sequence. <programlisting>
5103 # <emphasis role="bold">cd /etc/init.d</emphasis>
5104 # <emphasis role="bold">ln -s ../init.d/afs /etc/rc2.d/S35afs</emphasis>
5105 # <emphasis role="bold">ln -s ../init.d/afs /etc/rc0.d/K35afs</emphasis>
5106 </programlisting></para>
5110 <para><emphasis role="bold">(Optional)</emphasis> There are now copies of the AFS initialization file in both the
5111 <emphasis role="bold">/usr/vice/etc</emphasis> and <emphasis role="bold">/etc/init.d</emphasis> directories. If you want
5112 to avoid potential confusion by guaranteeing that they are always the same, create a link between them. You can always
5113 retrieve the original script from the AFS CD-ROM if necessary. <programlisting>
5114 # <emphasis role="bold">cd /usr/vice/etc</emphasis>
5115 # <emphasis role="bold">rm afs.rc</emphasis>
5116 # <emphasis role="bold">ln -s /etc/init.d/afs afs.rc</emphasis>
5117 </programlisting></para>
5121 <para>Proceed to <link linkend="HDRWQ80">Configuring the Top Levels of the AFS Filespace</link>.</para>
5126 <primary>Linux</primary>
5128 <secondary>AFS initialization script</secondary>
5130 <tertiary>on first AFS machine</tertiary>
5134 <sect2 id="HDRWQ78">
5135 <title>Activating the Script on Linux Systems</title>
5139 <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>
5140 configuration variables. Based on the instruction in the AFS initialization file that begins with the string
5141 <computeroutput>#chkconfig</computeroutput>, the command automatically creates the symbolic links that incorporate the
5142 script into the Linux startup and shutdown sequence. <programlisting>
5143 # <emphasis role="bold">/sbin/chkconfig --add openafs-client</emphasis>
5144 # <emphasis role="bold">/sbin/chkconfig --add openafs-server</emphasis>
5145 </programlisting></para>
5149 <para><emphasis role="bold">(Optional)</emphasis> There are now copies of the AFS initialization file in both the
5150 <emphasis role="bold">/usr/vice/etc</emphasis> and <emphasis role="bold">/etc/rc.d/init.d</emphasis> directories, and
5151 copies of the <emphasis role="bold">afsd</emphasis> options file in both the <emphasis
5152 role="bold">/usr/vice/etc</emphasis> and <emphasis role="bold">/etc/sysconfig</emphasis> directories. If you want to avoid
5153 potential confusion by guaranteeing that the two copies of each file are always the same, create a link between them. You
5154 can always retrieve the original script or options file from the AFS CD-ROM if necessary. <programlisting>
5155 # <emphasis role="bold">cd /usr/vice/etc</emphasis>
5156 # <emphasis role="bold">rm afs.rc afs.conf</emphasis>
5157 # <emphasis role="bold">ln -s /etc/rc.d/init.d/afs afs.rc</emphasis>
5158 # <emphasis role="bold">ln -s /etc/sysconfig/afs afs.conf</emphasis>
5159 </programlisting></para>
5163 <para>Proceed to <link linkend="HDRWQ80">Configuring the Top Levels of the AFS Filespace</link>.</para>
5168 <primary>Solaris</primary>
5170 <secondary>AFS initialization script</secondary>
5172 <tertiary>on first AFS machine</tertiary>
5176 <sect2 id="HDRWQ79">
5177 <title>Activating the Script on Solaris Systems</title>
5181 <para>Change to the <emphasis role="bold">/etc/init.d</emphasis> directory and issue the <emphasis role="bold">ln
5182 -s</emphasis> command to create symbolic links that incorporate the AFS initialization script into the Solaris startup and
5183 shutdown sequence. <programlisting>
5184 # <emphasis role="bold">cd /etc/init.d</emphasis>
5185 # <emphasis role="bold">ln -s ../init.d/afs /etc/rc3.d/S99afs</emphasis>
5186 # <emphasis role="bold">ln -s ../init.d/afs /etc/rc0.d/K66afs</emphasis>
5187 </programlisting></para>
5191 <para><emphasis role="bold">(Optional)</emphasis> There are now copies of the AFS initialization file in both the
5192 <emphasis role="bold">/usr/vice/etc</emphasis> and <emphasis role="bold">/etc/init.d</emphasis> directories. If you want
5193 to avoid potential confusion by guaranteeing that they are always the same, create a link between them. You can always
5194 retrieve the original script from the AFS CD-ROM if necessary. <programlisting>
5195 # <emphasis role="bold">cd /usr/vice/etc</emphasis>
5196 # <emphasis role="bold">rm afs.rc</emphasis>
5197 # <emphasis role="bold">ln -s /etc/init.d/afs afs.rc</emphasis>
5198 </programlisting></para>
5203 <primary>AFS filespace</primary>
5205 <secondary>configuring top levels</secondary>
5209 <primary>configuring</primary>
5211 <secondary>AFS filespace (top levels)</secondary>
5216 <sect1 id="HDRWQ80">
5217 <title>Configuring the Top Levels of the AFS Filespace</title>
5219 <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
5220 have run a previous version of AFS, the filespace is already configured. Proceed to <link linkend="HDRWQ83">Storing AFS Binaries
5221 in AFS</link>. <indexterm>
5222 <primary>root.cell volume</primary>
5224 <secondary>creating and replicating</secondary>
5225 </indexterm> <indexterm>
5226 <primary>volume</primary>
5228 <secondary>creating</secondary>
5230 <tertiary>root.cell</tertiary>
5231 </indexterm> <indexterm>
5232 <primary>creating</primary>
5234 <secondary>root.cell volume</secondary>
5237 <para>You created the <emphasis role="bold">root.afs</emphasis> volume in <link linkend="HDRWQ60">Starting the File Server,
5238 Volume Server, and Salvager</link>, and the Cache Manager mounted it automatically on the local <emphasis
5239 role="bold">/afs</emphasis> directory when you ran the AFS initialization script in <link linkend="HDRWQ72">Verifying the AFS
5240 Initialization Script</link>. You now set the access control list (ACL) on the <emphasis role="bold">/afs</emphasis> directory;
5241 creating, mounting, and setting the ACL are the three steps required when creating any volume.</para>
5243 <para>After setting the ACL on the <emphasis role="bold">root.afs</emphasis> volume, you create your cell's <emphasis
5244 role="bold">root.cell</emphasis> volume, mount it as a subdirectory of the <emphasis role="bold">/afs</emphasis> directory, and
5245 set the ACL. Create both a read/write and a regular mount point for the <emphasis role="bold">root.cell</emphasis> volume. The
5246 read/write mount point enables you to access the read/write version of replicated volumes when necessary. Creating both mount
5247 points essentially creates separate read-only and read-write copies of your filespace, and enables the Cache Manager to traverse
5248 the filespace on a read-only path or read/write path as appropriate. For further discussion of these concepts, see the chapter
5249 in the <emphasis>OpenAFS Administration Guide</emphasis> about administering volumes. <indexterm>
5250 <primary>root.afs volume</primary>
5252 <secondary>replicating</secondary>
5253 </indexterm> <indexterm>
5254 <primary>volume</primary>
5256 <secondary>replicating root.afs and root.cell</secondary>
5257 </indexterm> <indexterm>
5258 <primary>replicating volumes</primary>
5261 <para>Then replicate both the <emphasis role="bold">root.afs</emphasis> and <emphasis role="bold">root.cell</emphasis> volumes.
5262 This is required if you want to replicate any other volumes in your cell, because all volumes mounted above a replicated volume
5263 must themselves be replicated in order for the Cache Manager to access the replica.</para>
5265 <para>When the <emphasis role="bold">root.afs</emphasis> volume is replicated, the Cache Manager is programmed to access its
5266 read-only version (<emphasis role="bold">root.afs.readonly</emphasis>) whenever possible. To make changes to the contents of the
5267 <emphasis role="bold">root.afs</emphasis> volume (when, for example, you mount another cell's <emphasis
5268 role="bold">root.cell</emphasis> volume at the second level in your filespace), you must mount the <emphasis
5269 role="bold">root.afs</emphasis> volume temporarily, make the changes, release the volume and remove the temporary mount point.
5270 For instructions, see <link linkend="HDRWQ91">Enabling Access to Foreign Cells</link>. <indexterm>
5271 <primary>fs commands</primary>
5273 <secondary>setacl</secondary>
5274 </indexterm> <indexterm>
5275 <primary>commands</primary>
5277 <secondary>fs setacl</secondary>
5278 </indexterm> <indexterm>
5279 <primary>access control list (ACL), setting</primary>
5280 </indexterm> <indexterm>
5281 <primary>setting</primary>
5283 <secondary>ACL</secondary>
5284 </indexterm> <orderedlist>
5286 <para>Issue the <emphasis role="bold">fs setacl</emphasis> command to edit the ACL on the <emphasis
5287 role="bold">/afs</emphasis> directory. Add an entry that grants the <emphasis role="bold">l</emphasis> (<emphasis
5288 role="bold">lookup</emphasis>) and <emphasis role="bold">r</emphasis> (<emphasis role="bold">read</emphasis>) permissions
5289 to the <emphasis role="bold">system:anyuser</emphasis> group, to enable all AFS users who can reach your cell to traverse
5290 through the directory. If you prefer to enable access only to locally authenticated users, substitute the <emphasis
5291 role="bold">system:authuser</emphasis> group.</para>
5293 <para>Note that there is already an ACL entry that grants all seven access rights to the <emphasis
5294 role="bold">system:administrators</emphasis> group. It is a default entry that AFS places on every new volume's root
5298 # <emphasis role="bold">/usr/afs/bin/fs setacl /afs system:anyuser rl</emphasis>
5302 <primary>commands</primary>
5304 <secondary>vos create</secondary>
5306 <tertiary>root.cell volume</tertiary>
5310 <primary>vos commands</primary>
5312 <secondary>create</secondary>
5314 <tertiary>root.cell volume</tertiary>
5318 <primary>fs commands</primary>
5320 <secondary>mkmount</secondary>
5324 <primary>commands</primary>
5326 <secondary>fs mkmount</secondary>
5330 <primary>mount point</primary>
5334 <primary>creating</primary>
5336 <secondary>mount point</secondary>
5340 <primary>volume</primary>
5342 <secondary>mounting</secondary>
5347 <para><anchor id="LIWQ81" />Issue the <emphasis role="bold">vos create</emphasis> command to create the <emphasis
5348 role="bold">root.cell</emphasis> volume. Then issue the <emphasis role="bold">fs mkmount</emphasis> command to mount it as
5349 a subdirectory of the <emphasis role="bold">/afs</emphasis> directory, where it serves as the root of your cell's local
5350 AFS filespace. Finally, issue the <emphasis role="bold">fs setacl</emphasis> command to create an ACL entry for the
5351 <emphasis role="bold">system:anyuser</emphasis> group (or <emphasis role="bold">system:authuser</emphasis> group).</para>
5353 <para>For the <replaceable>partition name</replaceable> argument, substitute the name of one of the machine's AFS server
5354 partitions (such as <emphasis role="bold">/vicepa</emphasis>). For the <replaceable>cellname</replaceable> argument,
5355 substitute your cell's fully-qualified Internet domain name (such as <emphasis role="bold">abc.com</emphasis>).</para>
5358 # <emphasis role="bold">/usr/afs/bin/vos create</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>partition name</replaceable>> <emphasis
5359 role="bold">root.cell</emphasis>
5360 # <emphasis role="bold">/usr/afs/bin/fs mkmount /afs/</emphasis><replaceable>cellname</replaceable> <emphasis role="bold">root.cell</emphasis>
5361 # <emphasis role="bold">/usr/afs/bin/fs setacl /afs/</emphasis><replaceable>cellname</replaceable> <emphasis role="bold">system:anyuser rl</emphasis>
5365 <primary>creating</primary>
5367 <secondary>symbolic link</secondary>
5369 <tertiary>for abbreviated cell name</tertiary>
5373 <primary>symbolic link</primary>
5375 <secondary>for abbreviated cell name</secondary>
5379 <primary>cell name</primary>
5381 <secondary>symbolic link for abbreviated</secondary>
5386 <para><emphasis role="bold">(Optional)</emphasis> Create a symbolic link to a shortened cell name, to reduce the length of
5387 pathnames for users in the local cell. For example, in the <emphasis role="bold">abc.com</emphasis> cell, <emphasis
5388 role="bold">/afs/abc</emphasis> is a link to <emphasis role="bold">/afs/abc.com</emphasis>. <programlisting>
5389 # <emphasis role="bold">cd /afs</emphasis>
5390 # <emphasis role="bold">ln -s</emphasis> <replaceable>full_cellname</replaceable> <replaceable>short_cellname</replaceable>
5391 </programlisting> <indexterm>
5392 <primary>read/write mount point for root.afs volume</primary>
5393 </indexterm> <indexterm>
5394 <primary>root.afs volume</primary>
5396 <secondary>read/write mount point</secondary>
5397 </indexterm> <indexterm>
5398 <primary>creating</primary>
5400 <secondary>read/write mount point</secondary>
5405 <para>Issue the <emphasis role="bold">fs mkmount</emphasis> command to create a read/write mount point for the <emphasis
5406 role="bold">root.cell</emphasis> volume (you created a regular mount point in Step <link
5407 linkend="LIWQ81">2</link>).</para>
5409 <para>By convention, the name of a read/write mount point begins with a period, both to distinguish it from the regular
5410 mount point and to make it visible only when the <emphasis role="bold">-a</emphasis> flag is used on the <emphasis
5411 role="bold">ls</emphasis> command.</para>
5413 <para>Change directory to <emphasis role="bold">/usr/afs/bin</emphasis> to make it easier to access the command
5417 # <emphasis role="bold">cd /usr/afs/bin</emphasis>
5418 # <emphasis role="bold">./fs mkmount /afs/.</emphasis><replaceable>cellname</replaceable> <emphasis role="bold">root.cell -rw</emphasis>
5422 <primary>commands</primary>
5424 <secondary>vos addsite</secondary>
5428 <primary>vos commands</primary>
5430 <secondary>addsite</secondary>
5434 <primary>volume</primary>
5436 <secondary>defining replication site</secondary>
5440 <primary>defining</primary>
5442 <secondary>replication site for volume</secondary>
5447 <para><anchor id="LIWQ82" />Issue the <emphasis role="bold">vos addsite</emphasis> command to define a replication site
5448 for both the <emphasis role="bold">root.afs</emphasis> and <emphasis role="bold">root.cell</emphasis> volumes. In each
5449 case, substitute for the <replaceable>partition name</replaceable> argument the partition where the volume's read/write
5450 version resides. When you install additional file server machines, it is a good idea to create replication sites on them
5451 as well. <programlisting>
5452 # <emphasis role="bold">./vos addsite</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>partition name</replaceable>> <emphasis
5453 role="bold">root.afs</emphasis>
5454 # <emphasis role="bold">./vos addsite</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>partition name</replaceable>> <emphasis
5455 role="bold">root.cell</emphasis>
5456 </programlisting> <indexterm>
5457 <primary>fs commands</primary>
5459 <secondary>examine</secondary>
5460 </indexterm> <indexterm>
5461 <primary>commands</primary>
5463 <secondary>fs examine</secondary>
5468 <para>Issue the <emphasis role="bold">fs examine</emphasis> command to verify that the Cache Manager can access both the
5469 <emphasis role="bold">root.afs</emphasis> and <emphasis role="bold">root.cell</emphasis> volumes, before you attempt to
5470 replicate them. The output lists each volume's name, volumeID number, quota, size, and the size of the partition that
5471 houses them. If you get an error message instead, do not continue before taking corrective action. <programlisting>
5472 # <emphasis role="bold">./fs examine /afs</emphasis>
5473 # <emphasis role="bold">./fs examine /afs/</emphasis><replaceable>cellname</replaceable>
5474 </programlisting> <indexterm>
5475 <primary>commands</primary>
5477 <secondary>vos release</secondary>
5478 </indexterm> <indexterm>
5479 <primary>vos commands</primary>
5481 <secondary>release</secondary>
5482 </indexterm> <indexterm>
5483 <primary>volume</primary>
5485 <secondary>releasing replicated</secondary>
5486 </indexterm> <indexterm>
5487 <primary>releasing replicated volume</primary>
5492 <para>Issue the <emphasis role="bold">vos release</emphasis> command to release a replica of the <emphasis
5493 role="bold">root.afs</emphasis> and <emphasis role="bold">root.cell</emphasis> volumes to the sites you defined in Step
5494 <link linkend="LIWQ82">5</link>. <programlisting>
5495 # <emphasis role="bold">./vos release root.afs</emphasis>
5496 # <emphasis role="bold">./vos release root.cell</emphasis>
5497 </programlisting> <indexterm>
5498 <primary>fs commands</primary>
5500 <secondary>checkvolumes</secondary>
5501 </indexterm> <indexterm>
5502 <primary>commands</primary>
5504 <secondary>fs checkvolumes</secondary>
5509 <para>Issue the <emphasis role="bold">fs checkvolumes</emphasis> to force the Cache Manager to notice that you have
5510 released read-only versions of the volumes, then issue the <emphasis role="bold">fs examine</emphasis> command again. This
5511 time its output mentions the read-only version of the volumes (<emphasis role="bold">root.afs.readonly</emphasis> and
5512 <emphasis role="bold">root.cell.readonly</emphasis>) instead of the read/write versions, because of the Cache Manager's
5513 bias to access the read-only version of the <emphasis role="bold">root.afs</emphasis> volume if it exists.
5515 # <emphasis role="bold">./fs checkvolumes</emphasis>
5516 # <emphasis role="bold">./fs examine /afs</emphasis>
5517 # <emphasis role="bold">./fs examine /afs/</emphasis><replaceable>cellname</replaceable>
5518 </programlisting></para>
5520 </orderedlist></para>
5523 <primary>storing</primary>
5525 <secondary>AFS binaries in volumes</secondary>
5529 <primary>creating</primary>
5531 <secondary>volume</secondary>
5533 <tertiary>for AFS binaries</tertiary>
5537 <primary>volume</primary>
5539 <secondary>for AFS binaries</secondary>
5543 <primary>binaries</primary>
5545 <secondary>storing AFS in volume</secondary>
5549 <primary>usr/afsws directory</primary>
5553 <primary>directories</primary>
5555 <secondary>/usr/afsws</secondary>
5559 <sect1 id="HDRWQ83">
5560 <title>Storing AFS Binaries in AFS</title>
5562 <note><para>Sites with existing binary distribution mechanisms, including
5563 those which use packaging systems such as RPM, may wish to skip this step,
5564 and use tools native to their operating system to manage AFS configuration
5565 information.</para></note>
5567 <para>In the conventional configuration, you make AFS client binaries and configuration files available in the subdirectories of
5568 the <emphasis role="bold">/usr/afsws</emphasis> directory on client machines (<emphasis role="bold">afsws</emphasis> is an
5569 acronym for <emphasis role="bold">AFS w</emphasis><emphasis>ork</emphasis><emphasis
5570 role="bold">s</emphasis><emphasis>tation</emphasis>). You can conserve local disk space by creating <emphasis
5571 role="bold">/usr/afsws</emphasis> as a link to an AFS volume that houses the AFS client binaries and configuration files for
5572 this system type.</para>
5574 <para>In this section you create the necessary volumes. The conventional location to which to link <emphasis
5575 role="bold">/usr/afsws</emphasis> is <emphasis role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
5576 role="bold">/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/usr/afsws</emphasis>, where
5577 <replaceable>sysname</replaceable> is the appropriate system type name as specified in the <emphasis>OpenAFS Release
5578 Notes</emphasis>. The instructions in <link linkend="HDRWQ133">Installing Additional Client Machines</link> assume that you have
5579 followed the instructions in this section.</para>
5581 <para>If you have previously run AFS in the cell, the volumes possibly already exist. If so, you need to perform Step <link
5582 linkend="LIWQ86">8</link> only.</para>
5584 <para>The current working directory is still <emphasis role="bold">/usr/afs/bin</emphasis>, which houses the <emphasis
5585 role="bold">fs</emphasis> and <emphasis role="bold">vos</emphasis> command suite binaries. In the following commands, it is
5586 possible you still need to specify the pathname to the commands, depending on how your PATH environment variable is set.
5589 <primary>commands</primary>
5591 <secondary>vos create</secondary>
5593 <tertiary>volume for AFS binaries</tertiary>
5597 <primary>vos commands</primary>
5599 <secondary>create</secondary>
5601 <tertiary>volume for AFS binaries</tertiary>
5605 <para><anchor id="LIWQ84" />Issue the <emphasis role="bold">vos create</emphasis> command to create volumes for storing
5606 the AFS client binaries for this system type. The following example instruction creates volumes called
5607 <replaceable>sysname</replaceable>, <replaceable>sysname</replaceable>.<emphasis role="bold">usr</emphasis>, and
5608 <replaceable>sysname</replaceable>.<emphasis role="bold">usr.afsws</emphasis>. Refer to the <emphasis>OpenAFS Release
5609 Notes</emphasis> to learn the proper value of <replaceable>sysname</replaceable> for this system type. <programlisting>
5610 # <emphasis role="bold">vos create</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>partition name</replaceable>> <replaceable>sysname</replaceable>
5611 # <emphasis role="bold">vos create</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>partition name</replaceable>> <replaceable>sysname</replaceable><emphasis
5612 role="bold">.usr</emphasis>
5613 # <emphasis role="bold">vos create</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>partition name</replaceable>> <replaceable>sysname</replaceable><emphasis
5614 role="bold">.usr.afsws</emphasis>
5615 </programlisting></para>
5619 <para>Issue the <emphasis role="bold">fs mkmount</emphasis> command to mount the newly created volumes. Because the
5620 <emphasis role="bold">root.cell</emphasis> volume is replicated, you must precede the <emphasis>cellname</emphasis> part
5621 of the pathname with a period to specify the read/write mount point, as shown. Then issue the <emphasis role="bold">vos
5622 release</emphasis> command to release a new replica of the <emphasis role="bold">root.cell</emphasis> volume, and the
5623 <emphasis role="bold">fs checkvolumes</emphasis> command to force the local Cache Manager to access them. <programlisting>
5624 # <emphasis role="bold">fs mkmount -dir /afs/.</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/</emphasis><replaceable>sysname</replaceable> <emphasis
5625 role="bold">-vol</emphasis> <replaceable>sysname</replaceable>
5626 # <emphasis role="bold">fs mkmount -dir /afs/.</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/</emphasis><replaceable>sysname</replaceable><emphasis
5627 role="bold">/usr</emphasis> <emphasis role="bold">-vol</emphasis> <replaceable>sysname</replaceable><emphasis
5628 role="bold">.usr</emphasis>
5629 # <emphasis role="bold">fs mkmount -dir /afs/.</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/</emphasis><replaceable>sysname</replaceable><emphasis
5630 role="bold">/usr/afsws</emphasis> <emphasis role="bold">-vol</emphasis> <replaceable>sysname</replaceable><emphasis
5631 role="bold">.usr.afsws</emphasis>
5632 # <emphasis role="bold">vos release root.cell</emphasis>
5633 # <emphasis role="bold">fs checkvolumes</emphasis>
5634 </programlisting></para>
5638 <para>Issue the <emphasis role="bold">fs setacl</emphasis> command to grant the <emphasis role="bold">l</emphasis>
5639 (<emphasis role="bold">lookup</emphasis>) and <emphasis role="bold">r</emphasis> (<emphasis role="bold">read</emphasis>)
5640 permissions to the <emphasis role="bold">system:anyuser</emphasis> group on each new directory's ACL. <programlisting>
5641 # <emphasis role="bold">cd /afs/.</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/</emphasis><replaceable>sysname</replaceable>
5642 # <emphasis role="bold">fs setacl -dir . usr usr/afsws -acl system:anyuser rl</emphasis>
5643 </programlisting> <indexterm>
5644 <primary>commands</primary>
5646 <secondary>fs setquota</secondary>
5647 </indexterm> <indexterm>
5648 <primary>fs commands</primary>
5650 <secondary>setquota</secondary>
5651 </indexterm> <indexterm>
5652 <primary>quota for volume</primary>
5653 </indexterm> <indexterm>
5654 <primary>volume</primary>
5656 <secondary>setting quota</secondary>
5657 </indexterm> <indexterm>
5658 <primary>setting</primary>
5660 <secondary>volume quota</secondary>
5665 <para><anchor id="LIWQ85" />Issue the <emphasis role="bold">fs setquota</emphasis> command to set an unlimited quota on
5666 the volume mounted at the <emphasis role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
5667 role="bold">/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/usr/afsws</emphasis> directory. This
5668 enables you to copy all of the appropriate files from the CD-ROM into the volume without exceeding the volume's
5671 <para>If you wish, you can set the volume's quota to a finite value after you complete the copying operation. At that
5672 point, use the <emphasis role="bold">vos examine</emphasis> command to determine how much space the volume is occupying.
5673 Then issue the <emphasis role="bold">fs setquota</emphasis> command to set a quota that is slightly larger.</para>
5676 # <emphasis role="bold">fs setquota /afs/.</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/</emphasis><replaceable>sysname</replaceable><emphasis
5677 role="bold">/usr/afsws 0</emphasis>
5682 <para>Unpack the distribution tarball into the <emphasis role="bold">/tmp/afsdist</emphasis> directory,
5683 if it is not already. <indexterm>
5684 <primary>copying</primary>
5686 <secondary>AFS binaries into volume</secondary>
5687 </indexterm> <indexterm>
5688 <primary>CD-ROM</primary>
5690 <secondary>copying AFS binaries into volume</secondary>
5691 </indexterm> <indexterm>
5692 <primary>first AFS machine</primary>
5694 <secondary>copying</secondary>
5696 <tertiary>AFS binaries into volume</tertiary>
5701 <para>Copy the contents of the indicated directories from the
5702 distribution into the <emphasis
5703 role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
5704 role="bold">/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/usr/afsws</emphasis> directory.
5706 # <emphasis role="bold">cd /afs/.</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/</emphasis><replaceable>sysname</replaceable><emphasis
5707 role="bold">/usr/afsws</emphasis>
5708 # <emphasis role="bold">cp -rp /tmp/afsdist/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/bin .</emphasis>
5709 # <emphasis role="bold">cp -rp /tmp/afsdist/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/etc .</emphasis>
5710 # <emphasis role="bold">cp -rp /tmp/afsdist/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/include .</emphasis>
5711 # <emphasis role="bold">cp -rp /tmp/afsdist/</emphasis><replaceable>sysname</replaceable><emphasis role="bold">/lib .</emphasis>
5714 <primary>creating</primary>
5716 <secondary>symbolic link</secondary>
5718 <tertiary>to AFS binaries</tertiary>
5719 </indexterm> <indexterm>
5720 <primary>symbolic link</primary>
5722 <secondary>to AFS binaries from local disk</secondary>
5727 <para><anchor id="LIWQ86" />Create <emphasis role="bold">/usr/afsws</emphasis> on the local disk as a symbolic link to the
5728 directory <emphasis role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
5729 role="bold">/@sys/usr/afsws</emphasis>. You can specify the actual system name instead of <emphasis
5730 role="bold">@sys</emphasis> if you wish, but the advantage of using <emphasis role="bold">@sys</emphasis> is that it
5731 remains valid if you upgrade this machine to a different system type. <programlisting>
5732 # <emphasis role="bold">ln -s /afs/</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/@sys/usr/afsws /usr/afsws</emphasis>
5733 </programlisting> <indexterm>
5734 <primary>PATH environment variable for users</primary>
5735 </indexterm> <indexterm>
5736 <primary>variables</primary>
5738 <secondary>PATH, setting for users</secondary>
5743 <para><emphasis role="bold">(Optional)</emphasis> To enable users to issue commands from the AFS suites (such as <emphasis
5744 role="bold">fs</emphasis>) without having to specify a pathname to their binaries, include the <emphasis
5745 role="bold">/usr/afsws/bin</emphasis> and <emphasis role="bold">/usr/afsws/etc</emphasis> directories in the PATH
5746 environment variable you define in each user's shell initialization file (such as <emphasis
5747 role="bold">.cshrc</emphasis>).</para>
5749 </orderedlist></para>
5752 <primary>storing</primary>
5754 <secondary>AFS documentation in volumes</secondary>
5758 <primary>creating</primary>
5760 <secondary>volume</secondary>
5762 <tertiary>for AFS documentation</tertiary>
5766 <primary>volume</primary>
5768 <secondary>for AFS documentation</secondary>
5772 <primary>documentation, creating volume for AFS</primary>
5776 <primary>usr/afsdoc directory</primary>
5780 <primary>directories</primary>
5782 <secondary>/usr/afsdoc</secondary>
5786 <sect1 id="HDRWQ87">
5787 <title>Storing AFS Documents in AFS</title>
5789 <para>The AFS distribution includes the following documents: <itemizedlist>
5791 <para><emphasis>OpenAFS Release Notes</emphasis></para>
5795 <para><emphasis>OpenAFS Quick Beginnings</emphasis></para>
5799 <para><emphasis>OpenAFS User Guide</emphasis></para>
5803 <para><emphasis>OpenAFS Administration Reference</emphasis></para>
5807 <para><emphasis>OpenAFS Administration Guide</emphasis></para>
5809 </itemizedlist></para>
5811 <note><para>OpenAFS Documentation is not currently provided with all
5812 distributions, but may be downloaded separately from the OpenAFS
5813 website</para></note>
5815 <para>The OpenAFS Documentation Distribution has a directory for each
5816 document format provided. The different formats are suitable for online
5817 viewing, printing, or both.</para>
5819 <para>This section explains how to create and mount a volume to house the documents, making them available to your users. The
5820 recommended mount point for the volume is <emphasis role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
5821 role="bold">/afsdoc</emphasis>. If you wish, you can create a link to the mount point on each client machine's local disk,
5822 called <emphasis role="bold">/usr/afsdoc</emphasis>. Alternatively, you can create a link to the mount point in each user's home
5823 directory. You can also choose to permit users to access only certain documents (most probably, the <emphasis>OpenAFS User
5824 Guide</emphasis>) by creating different mount points or setting different ACLs on different document directories.</para>
5826 <para>The current working directory is still <emphasis role="bold">/usr/afs/bin</emphasis>, which houses the <emphasis
5827 role="bold">fs</emphasis> and <emphasis role="bold">vos</emphasis> command suite binaries you use to create and mount volumes.
5828 In the following commands, it is possible you still need to specify the pathname to the commands, depending on how your PATH
5829 environment variable is set. <orderedlist>
5831 <primary>commands</primary>
5833 <secondary>vos create</secondary>
5835 <tertiary>volume for AFS documentation</tertiary>
5839 <primary>vos commands</primary>
5841 <secondary>create</secondary>
5843 <tertiary>volume for AFS documentation</tertiary>
5847 <para>Issue the <emphasis role="bold">vos create</emphasis> command to create a volume for storing the AFS documentation.
5848 Include the <emphasis role="bold">-maxquota</emphasis> argument to set an unlimited quota on the volume. This enables you
5849 to copy all of the appropriate files from the CD-ROM into the volume without exceeding the volume's quota.</para>
5851 <para>If you wish, you can set the volume's quota to a finite value after you complete the copying operations. At that
5852 point, use the <emphasis role="bold">vos examine</emphasis> command to determine how much space the volume is occupying.
5853 Then issue the <emphasis role="bold">fs setquota</emphasis> command to set a quota that is slightly larger.</para>
5856 # <emphasis role="bold">vos create</emphasis> <<replaceable>machine name</replaceable>> <<replaceable>partition name</replaceable>> <emphasis
5857 role="bold">afsdoc -maxquota 0</emphasis>
5862 <para>Issue the <emphasis role="bold">fs mkmount</emphasis> command to mount the new volume. Because the <emphasis
5863 role="bold">root.cell</emphasis> volume is replicated, you must precede the <emphasis>cellname</emphasis> with a period to
5864 specify the read/write mount point, as shown. Then issue the <emphasis role="bold">vos release</emphasis> command to
5865 release a new replica of the <emphasis role="bold">root.cell</emphasis> volume, and the <emphasis role="bold">fs
5866 checkvolumes</emphasis> command to force the local Cache Manager to access them. <programlisting>
5867 # <emphasis role="bold">fs mkmount -dir /afs/.</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/afsdoc</emphasis> <emphasis
5868 role="bold">-vol</emphasis> <emphasis role="bold">afsdoc</emphasis>
5869 # <emphasis role="bold">vos release root.cell</emphasis>
5870 # <emphasis role="bold">fs checkvolumes</emphasis>
5871 </programlisting></para>
5875 <para>Issue the <emphasis role="bold">fs setacl</emphasis> command to grant the <emphasis role="bold">rl</emphasis>
5876 permissions to the <emphasis role="bold">system:anyuser</emphasis> group on the new directory's ACL. <programlisting>
5877 # <emphasis role="bold">cd /afs/.</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/afsdoc</emphasis>
5878 # <emphasis role="bold">fs setacl . system:anyuser rl</emphasis>
5879 </programlisting></para>
5883 <para>Unpack the OpenAFS documentation distribution into the
5884 <emphasis role="bold">/tmp/afsdocs</emphasis> directory. You may use
5885 a different directory, in which case the location you use should be
5886 subsituted in the following examples. For instructions on unpacking
5887 the distribution, consult the documentation for your operating
5888 system's <emphasis role="bold">tar</emphasis> command.
5890 <primary>copying</primary>
5892 <secondary>AFS documentation from distribution</secondary>
5893 </indexterm> <indexterm>
5894 <primary>OpenAFS Distribution</primary>
5896 <secondary>copying AFS documentation from</secondary>
5897 </indexterm> <indexterm>
5898 <primary>first AFS machine</primary>
5900 <secondary>copying</secondary>
5902 <tertiary>AFS documentation from OpenAFS distribution</tertiary>
5903 </indexterm> <indexterm>
5904 <primary>index.htm file</primary>
5905 </indexterm> <indexterm>
5906 <primary>files</primary>
5908 <secondary>index.htm</secondary>
5913 <para>Copy the AFS documents in one or more formats from the unpacked distribution into subdirectories of the <emphasis
5914 role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/afsdoc</emphasis> directory. Repeat
5915 the commands for each format. <programlisting>
5916 # <emphasis role="bold">mkdir</emphasis> <replaceable>format_name</replaceable>
5917 # <emphasis role="bold">cd</emphasis> <replaceable>format_name</replaceable>
5918 # <emphasis role="bold">cp -rp /tmp/afsdocs/</emphasis><replaceable>format</replaceable> <emphasis role="bold">.</emphasis>
5919 </programlisting></para>
5921 <para>If you choose to store the HTML version of the documents in AFS, note that in addition to a subdirectory for each
5922 document there are several files with a <emphasis role="bold">.gif</emphasis> extension, which enable readers to move
5923 easily between sections of a document. The file called <emphasis role="bold">index.htm</emphasis> is an introductory HTML
5924 page that contains a hyperlink to each of the documents. For online viewing to work properly, these files must remain in
5925 the top-level HTML directory (the one named, for example, <emphasis
5926 role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/afsdoc/html</emphasis>).</para>
5930 <para><emphasis role="bold">(Optional)</emphasis> If you believe it is helpful to your users to access the AFS documents
5931 in a certain format via a local disk directory, create <emphasis role="bold">/usr/afsdoc</emphasis> on the local disk as a
5932 symbolic link to the documentation directory in AFS (<emphasis
5933 role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
5934 role="bold">/afsdoc/</emphasis><replaceable>format_name</replaceable>). <programlisting>
5935 # <emphasis role="bold">ln -s /afs/</emphasis><replaceable>cellname</replaceable><emphasis role="bold">/afsdoc/</emphasis><replaceable>format_name</replaceable> <emphasis
5936 role="bold">/usr/afsdoc</emphasis>
5937 </programlisting></para>
5939 <para>An alternative is to create a link in each user's home directory to the <emphasis
5940 role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
5941 role="bold">/afsdoc/</emphasis><replaceable>format_name</replaceable> directory.</para>
5943 </orderedlist></para>
5946 <primary>storing</primary>
5948 <secondary>system binaries in volumes</secondary>
5952 <primary>creating</primary>
5954 <secondary>volume</secondary>
5956 <tertiary>for system binaries</tertiary>
5960 <primary>volume</primary>
5962 <secondary>for system binaries</secondary>
5966 <primary>binaries</primary>
5968 <secondary>storing system in volumes</secondary>
5972 <sect1 id="HDRWQ88">
5973 <title>Storing System Binaries in AFS</title>
5975 <para>You can also choose to store other system binaries in AFS volumes, such as the standard UNIX programs conventionally
5976 located in local disk directories such as <emphasis role="bold">/etc</emphasis>, <emphasis role="bold">/bin</emphasis>, and
5977 <emphasis role="bold">/lib</emphasis>. Storing such binaries in an AFS volume not only frees local disk space, but makes it
5978 easier to update binaries on all client machines.</para>
5980 <para>The following is a suggested scheme for storing system binaries in AFS. It does not include instructions, but you can use
5981 the instructions in <link linkend="HDRWQ83">Storing AFS Binaries in AFS</link> (which are for AFS-specific binaries) as a
5984 <para>Some files must remain on the local disk for use when AFS is inaccessible (during bootup and file server or network
5985 outages). The required binaries include the following: <itemizedlist>
5987 <para>A text editor, network commands, and so on</para>
5991 <para>Files used during the boot sequence before the <emphasis role="bold">afsd</emphasis> program runs, such as
5992 initialization and configuration files, and binaries for commands that mount file systems</para>
5996 <para>Files used by dynamic kernel loader programs</para>
5998 </itemizedlist></para>
6000 <para>In most cases, it is more secure to enable only locally authenticated users to access system binaries, by granting the
6001 <emphasis role="bold">l</emphasis> (<emphasis role="bold">lookup</emphasis>) and <emphasis role="bold">r</emphasis> (<emphasis
6002 role="bold">read</emphasis>) permissions to the <emphasis role="bold">system:authuser</emphasis> group on the ACLs of
6003 directories that contain the binaries. If users need to access a binary while unauthenticated, however, the ACL on its directory
6004 must grant those permissions to the <emphasis role="bold">system:anyuser</emphasis> group.</para>
6006 <para>The following chart summarizes the suggested volume and mount point names for storing system binaries. It uses a separate
6007 volume for each directory. You already created a volume called <replaceable>sysname</replaceable> for this machine's system type
6008 when you followed the instructions in <link linkend="HDRWQ83">Storing AFS Binaries in AFS</link>.</para>
6010 <para>You can name volumes in any way you wish, and mount them at other locations than those suggested here. However, this
6011 scheme has several advantages: <itemizedlist>
6013 <para>Volume names clearly identify volume contents</para>
6017 <para>Using the <replaceable>sysname</replaceable> prefix on every volume makes it is easy to back up all of the volumes
6018 together, because the AFS Backup System enables you to define sets of volumes based on a string included in all of their
6023 <para>It makes it easy to track related volumes, keeping them together on the same file server machine if desired</para>
6027 <para>There is a clear relationship between volume name and mount point name</para>
6029 </itemizedlist></para>
6031 <informaltable frame="none">
6033 <colspec colwidth="50*" />
6035 <colspec colwidth="50*" />
6039 <entry><emphasis role="bold">Volume Name</emphasis></entry>
6041 <entry><emphasis role="bold">Mount Point</emphasis></entry>
6047 <entry><replaceable>sysname</replaceable></entry>
6050 role="bold">/afs/</emphasis><replaceable>cellname</replaceable>/<replaceable>sysname</replaceable></entry>
6054 <entry><replaceable>sysname</replaceable>.<emphasis role="bold">bin</emphasis></entry>
6057 role="bold">/afs/</emphasis><replaceable>cellname</replaceable>/<replaceable>sysname</replaceable><emphasis
6058 role="bold">/bin</emphasis></entry>
6062 <entry><replaceable>sysname</replaceable>.<emphasis role="bold">etc</emphasis></entry>
6065 role="bold">/afs/</emphasis><replaceable>cellname</replaceable>/<replaceable>sysname</replaceable><emphasis
6066 role="bold">/etc</emphasis></entry>
6070 <entry><replaceable>sysname</replaceable>.<emphasis role="bold">usr</emphasis></entry>
6073 role="bold">/afs/</emphasis><replaceable>cellname</replaceable>/<replaceable>sysname</replaceable><emphasis
6074 role="bold">/usr</emphasis></entry>
6078 <entry><replaceable>sysname</replaceable>.<emphasis role="bold">usr.afsws</emphasis></entry>
6081 role="bold">/afs/</emphasis><replaceable>cellname</replaceable>/<replaceable>sysname</replaceable><emphasis
6082 role="bold">/usr/afsws</emphasis></entry>
6086 <entry><replaceable>sysname</replaceable>.<emphasis role="bold">usr.bin</emphasis></entry>
6089 role="bold">/afs/</emphasis><replaceable>cellname</replaceable>/<replaceable>sysname</replaceable><emphasis
6090 role="bold">/usr/bin</emphasis></entry>
6094 <entry><replaceable>sysname</replaceable>.<emphasis role="bold">usr.etc</emphasis></entry>
6097 role="bold">/afs/</emphasis><replaceable>cellname</replaceable>/<replaceable>sysname</replaceable><emphasis
6098 role="bold">/usr/etc</emphasis></entry>
6102 <entry><replaceable>sysname</replaceable>.<emphasis role="bold">usr.inc</emphasis></entry>
6105 role="bold">/afs/</emphasis><replaceable>cellname</replaceable>/<replaceable>sysname</replaceable><emphasis
6106 role="bold">/usr/include</emphasis></entry>
6110 <entry><replaceable>sysname</replaceable>.<emphasis role="bold">usr.lib</emphasis></entry>
6113 role="bold">/afs/</emphasis><replaceable>cellname</replaceable>/<replaceable>sysname</replaceable><emphasis
6114 role="bold">/usr/lib</emphasis></entry>
6118 <entry><replaceable>sysname</replaceable>.<emphasis role="bold">usr.loc</emphasis></entry>
6121 role="bold">/afs/</emphasis><replaceable>cellname</replaceable>/<replaceable>sysname</replaceable><emphasis
6122 role="bold">/usr/local</emphasis></entry>
6126 <entry><replaceable>sysname</replaceable>.<emphasis role="bold">usr.man</emphasis></entry>
6129 role="bold">/afs/</emphasis><replaceable>cellname</replaceable>/<replaceable>sysname</replaceable><emphasis
6130 role="bold">/usr/man</emphasis></entry>
6134 <entry><replaceable>sysname</replaceable>.<emphasis role="bold">usr.sys</emphasis></entry>
6137 role="bold">/afs/</emphasis><replaceable>cellname</replaceable>/<replaceable>sysname</replaceable><emphasis
6138 role="bold">/usr/sys</emphasis></entry>
6145 <primary>foreign cell, enabling access</primary>
6149 <primary>cell</primary>
6151 <secondary>enabling access to foreign</secondary>
6155 <primary>access</primary>
6157 <secondary>to local and foreign cells</secondary>
6161 <primary>AFS filespace</primary>
6163 <secondary>enabling access to foreign cells</secondary>
6167 <primary>root.cell volume</primary>
6169 <secondary>mounting for foreign cells in local filespace</secondary>
6173 <primary>database server machine</primary>
6175 <secondary>entry in client CellServDB file</secondary>
6177 <tertiary>for foreign cell</tertiary>
6181 <primary>CellServDB file (client)</primary>
6183 <secondary>adding entry</secondary>
6185 <tertiary>for foreign cell</tertiary>
6189 <sect1 id="HDRWQ91">
6190 <title>Enabling Access to Foreign Cells</title>
6192 <para>With current OpenAFS releases, there exist a number of mechanisms for
6193 providing access to foreign cells. You may add mount points in your AFS
6194 filespace for each foreign cell you wish users to access, or you can
6195 enable a 'synthetic' AFS root, which contains mountpoints for either all
6196 AFS cells defined in the client machine's local
6197 <emphasis role="bold">/usr/vice/etc/CellServDB</emphasis>, or for all cells
6198 providing location information in the DNS.
6202 <title>Enabling a Synthetic AFS root</title>
6204 <para>When a synthetic root is enabled, the client cache machine creates its
6205 own root.afs volume, rather than using the one provided with your cell. This
6206 allows clients to access all cells in the
6207 <emphasis role="bold">CellServDB</emphasis> file and, optionally, all cells
6208 registered in the DNS, without requiring system administrator action to
6209 enable this access. Using a synthetic root has the additional advantage that
6210 it allows a client to start its AFS service without a network available, as
6211 it is no longer necessary to contact a fileserver to obtain the root volume.
6214 <para>OpenAFS supports two complimentary mechanisms for creating the
6215 synthetic root. Starting the cache manager with the
6216 <emphasis role="bold">-dynroot</emphasis> option adds all cells listed
6217 in <emphasis role="bold">/usr/vice/etc/CellServDB</emphasis> to the client's
6218 AFS root. Adding the <emphasis role="bold">-afsdb</emphasis> option in
6219 addition to this enables DNS lookups for any cells that are not found in
6220 the client's CellServDB file. Both of these options are added to the AFS
6221 initialisation script, or options file, as detailed in
6222 <link linkend="HDRWQ70">Configuring the Cache Manager</link>.</para>
6225 <title>Adding foreign cells to a conventional root volume</title>
6227 <para>In this section you create a mount point in your AFS filespace for the <emphasis role="bold">root.cell</emphasis> volume
6228 of each foreign cell that you want to enable your users to access. For users working on a client machine to access the cell,
6229 there must in addition be an entry for it in the client machine's local <emphasis
6230 role="bold">/usr/vice/etc/CellServDB</emphasis> file. (The instructions in <link linkend="HDRWQ66">Creating the Client
6231 CellServDB File</link> suggest that you use the <emphasis role="bold">CellServDB.sample</emphasis> file included in the AFS
6232 distribution as the basis for your cell's client <emphasis role="bold">CellServDB</emphasis> file. The sample file lists all of
6233 the cells that had agreed to participate in the AFS global namespace at the time your AFS CD-ROM was created. As mentioned in
6234 that section, the AFS Product Support group also maintains a copy of the file, updating it as necessary.)</para>
6236 <para>The chapter in the <emphasis>OpenAFS Administration Guide</emphasis> about cell administration and configuration issues
6237 discusses the implications of participating in the global AFS namespace. The chapter about administering client machines
6238 explains how to maintain knowledge of foreign cells on client machines, and includes suggestions for maintaining a central
6239 version of the file in AFS. <orderedlist>
6241 <para>Issue the <emphasis role="bold">fs mkmount</emphasis> command to mount each foreign cell's <emphasis
6242 role="bold">root.cell</emphasis> volume on a directory called <emphasis
6243 role="bold">/afs/</emphasis><replaceable>foreign_cell</replaceable>. Because the <emphasis role="bold">root.afs</emphasis>
6244 volume is replicated, you must create a temporary mount point for its read/write version in a directory to which you have
6245 write access (such as your cell's <emphasis role="bold">/afs/.</emphasis><replaceable>cellname</replaceable> directory).
6246 Create the mount points, issue the <emphasis role="bold">vos release</emphasis> command to release new replicas to the
6247 read-only sites for the <emphasis role="bold">root.afs</emphasis> volume, and issue the <emphasis role="bold">fs
6248 checkvolumes</emphasis> command to force the local Cache Manager to access the new replica.</para>
6251 <para>You need to issue the <emphasis role="bold">fs mkmount</emphasis> command only once for each foreign cell's
6252 <emphasis role="bold">root.cell</emphasis> volume. You do not need to repeat the command on each client machine.</para>
6255 <para>Substitute your cell's name for <replaceable>cellname</replaceable>.</para>
6258 # <emphasis role="bold">cd /afs/.</emphasis><replaceable>cellname</replaceable>
6259 # <emphasis role="bold">/usr/afs/bin/fs mkmount temp root.afs</emphasis>
6262 <para>Repeat the <emphasis role="bold">fs mkmount</emphasis> command for each foreign cell you wish to mount at this
6266 # <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>
6269 <para>Issue the following commands only once.</para>
6272 # <emphasis role="bold">/usr/afs/bin/fs rmmount temp</emphasis>
6273 # <emphasis role="bold">/usr/afs/bin/vos release root.afs</emphasis>
6274 # <emphasis role="bold">/usr/afs/bin/fs checkvolumes</emphasis>
6278 <primary>fs commands</primary>
6280 <secondary>newcell</secondary>
6284 <primary>commands</primary>
6286 <secondary>fs newcell</secondary>
6291 <para><anchor id="LIWQ92" />If this machine is going to remain an AFS client after you complete the installation, verify
6292 that the local <emphasis role="bold">/usr/vice/etc/CellServDB</emphasis> file includes an entry for each foreign
6295 <para>For each cell that does not already have an entry, complete the following instructions: <orderedlist>
6297 <para>Create an entry in the <emphasis role="bold">CellServDB</emphasis> file. Be sure to comply with the formatting
6298 instructions in <link linkend="HDRWQ66">Creating the Client CellServDB File</link>.</para>
6302 <para>Issue the <emphasis role="bold">fs newcell</emphasis> command to add an entry for the cell directly to the
6303 list that the Cache Manager maintains in kernel memory. Provide each database server machine's fully qualified
6304 hostname. <programlisting>
6305 # <emphasis role="bold">/usr/afs/bin/fs newcell</emphasis> <<replaceable>foreign_cell</replaceable>> <<replaceable>dbserver1></replaceable> \
6306 [<<replaceable>dbserver2></replaceable>] [<<replaceable>dbserver3></replaceable>]
6307 </programlisting></para>
6311 <para>If you plan to maintain a central version of the <emphasis role="bold">CellServDB</emphasis> file (the
6312 conventional location is <emphasis role="bold">/afs/</emphasis><replaceable>cellname</replaceable><emphasis
6313 role="bold">/common/etc/CellServDB</emphasis>), create it now as a copy of the local <emphasis
6314 role="bold">/usr/vice/etc/CellServDB</emphasis> file. Verify that it includes an entry for each foreign cell you
6315 want your users to be able to access. <programlisting>
6316 # <emphasis role="bold">mkdir common</emphasis>
6317 # <emphasis role="bold">mkdir common/etc</emphasis>
6318 # <emphasis role="bold">cp /usr/vice/etc/CellServDB common/etc</emphasis>
6319 # <emphasis role="bold">/usr/afs/bin/vos release root.cell</emphasis>
6320 </programlisting></para>
6322 </orderedlist></para>
6326 <para>Issue the <emphasis role="bold">ls</emphasis> command to verify that the new cell's mount point is visible in your
6327 filespace. The output lists the directories at the top level of the new cell's AFS filespace. <programlisting>
6328 # <emphasis role="bold">ls /afs/</emphasis><replaceable>foreign_cell</replaceable>
6329 </programlisting></para>
6333 <para>If you wish to participate in the global AFS namespace, and only
6334 intend running one database server, please
6335 register your cell with grand.central.org at this time.
6336 To do so, email the <emphasis role="bold">CellServDB</emphasis> fragment
6337 describing your cell, together with a contact name and email address
6338 for any queries, to cellservdb@grand.central.org. If you intend
6339 on deploying multiple database servers, please wait until you have
6340 installed all of them before registering your cell.</para>
6343 <para>If you wish to allow your cell to be located through DNS lookups,
6344 at this time you should also add the necessary configuration to your
6347 <para>AFS database servers may be located by creating AFSDB records
6348 in the DNS for the domain name corresponding to the name of your cell.
6349 It's outside the scope of this guide to give an indepth description of
6350 managing, or configuring, your site's DNS. You should consult the
6351 documentation for your DNS server for further details on AFSDB
6354 </orderedlist></para>
6358 <sect1 id="HDRWQ93">
6359 <title>Improving Cell Security</title>
6362 <primary>cell</primary>
6364 <secondary>improving security</secondary>
6368 <primary>security</primary>
6370 <secondary>improving</secondary>
6374 <primary>root superuser</primary>
6376 <secondary>controlling access</secondary>
6380 <primary>access</primary>
6382 <secondary>to root and admin accounts</secondary>
6386 <primary>admin account</primary>
6388 <secondary>controlling access to</secondary>
6392 <primary>AFS filespace</primary>
6394 <secondary>controlling access by root superuser</secondary>
6397 <para>This section discusses ways to improve the security of AFS data
6398 in your cell. Also see the chapter in the <emphasis>OpenAFS
6399 Administration Guide</emphasis> about configuration and administration
6402 <sect2 id="HDRWQ94">
6403 <title>Controlling root Access</title>
6405 <para>As on any machine, it is important to prevent unauthorized users from logging onto an AFS server or client machine as
6406 the local superuser <emphasis role="bold">root</emphasis>. Take care to keep the <emphasis role="bold">root</emphasis>
6407 password secret.</para>
6409 <para>The local <emphasis role="bold">root</emphasis> superuser does not have special access to AFS data through the Cache
6410 Manager (as members of the <emphasis role="bold">system:administrators</emphasis> group do), but it does have the following
6411 privileges: <itemizedlist>
6413 <para>On client machines, the ability to issue commands from the <emphasis role="bold">fs</emphasis> suite that affect
6414 AFS performance</para>
6418 <para>On server machines, the ability to disable authorization checking, or to install rogue process binaries</para>
6420 </itemizedlist></para>
6423 <sect2 id="HDRWQ95">
6424 <title>Controlling System Administrator Access</title>
6426 <para>Following are suggestions for managing AFS administrative privilege: <itemizedlist>
6428 <para>Create an administrative account for each administrator named
6430 <replaceable>username</replaceable><emphasis role="bold">.admin</emphasis>.
6431 Administrators authenticate under these identities only when
6432 performing administrative tasks, and destroy the administrative
6433 tokens immediately after finishing the task (either by issuing the
6434 <emphasis role="bold">unlog</emphasis> command, or the
6435 <emphasis role="bold">kinit</emphasis> and
6436 <emphasis role="bold">aklog</emphasis> commands to adopt their
6437 regular identity).</para>
6441 <para>Set a short ticket lifetime for administrator accounts (for example, 20 minutes) by using the
6442 facilities of your KDC. For instance, with a MIT Kerberos KDC, this
6443 can be performed using the
6444 <emphasis role="bold">--max-ticket-life</emphasis> argument to
6445 the <emphasis role="bold">kadmin modify_principal</emphasis>
6446 command. Do not however, use a short lifetime for users
6447 who issue long-running <emphasis role="bold">backup</emphasis> commands.</para>
6451 <para>Limit the number of system administrators in your cell, especially those who belong to the <emphasis
6452 role="bold">system:administrators</emphasis> group. By default they have all ACL rights on all directories in the local
6453 AFS filespace, and therefore must be trusted not to examine private files.</para>
6457 <para>Limit the use of system administrator accounts on machines in public areas. It is especially important not to
6458 leave such machines unattended without first destroying the administrative tokens.</para>
6462 <para>Limit the use by administrators of standard UNIX commands that make connections to remote machines (such as the
6463 <emphasis role="bold">telnet</emphasis> utility). Many of these programs send passwords across the network without
6464 encrypting them.</para>
6466 </itemizedlist></para>
6469 <primary>BOS Server</primary>
6471 <secondary>checking mode bits on AFS directories</secondary>
6475 <primary>mode bits on local AFS directories</primary>
6479 <primary>UNIX mode bits on local AFS directories</primary>
6483 <sect2 id="HDRWQ96">
6484 <title>Protecting Sensitive AFS Directories</title>
6486 <para>Some subdirectories of the <emphasis role="bold">/usr/afs</emphasis> directory contain files crucial to cell security.
6487 Unauthorized users must not read or write to these files because of the potential for misuse of the information they
6490 <para>As the BOS Server initializes for the first time on a server machine, it creates several files and directories (as
6491 mentioned in <link linkend="HDRWQ50">Starting the BOS Server</link>). It sets their owner to the local superuser <emphasis
6492 role="bold">root</emphasis> and sets their mode bits to enable writing by the owner only; in some cases, it also restricts
6495 <para>At each subsequent restart, the BOS Server checks that the owner and mode bits on these files are still set
6496 appropriately. If they are not, it write the following message to the <emphasis role="bold">/usr/afs/logs/BosLog</emphasis>
6500 Bosserver reports inappropriate access on server directories
6503 <para>The BOS Server does not reset the mode bits, which enables you to set alternate values if you wish.</para>
6505 <para>The following charts lists the expected mode bit settings. A question mark indicates that the BOS Server does not check
6506 that mode bit.</para>
6508 <informaltable frame="none">
6510 <colspec colwidth="30*" />
6512 <colspec colwidth="70*" />
6516 <entry><emphasis role="bold">/usr/afs</emphasis></entry>
6518 <entry><computeroutput>drwxr</computeroutput>?<computeroutput>xr-x</computeroutput></entry>
6522 <entry><emphasis role="bold">/usr/afs/backup</emphasis></entry>
6524 <entry><computeroutput>drwx</computeroutput>???<computeroutput>---</computeroutput></entry>
6528 <entry><emphasis role="bold">/usr/afs/bin</emphasis></entry>
6530 <entry><computeroutput>drwxr</computeroutput>?<computeroutput>xr-x</computeroutput></entry>
6534 <entry><emphasis role="bold">/usr/afs/db</emphasis></entry>
6536 <entry><computeroutput>drwx</computeroutput>???<computeroutput>---</computeroutput></entry>
6540 <entry><emphasis role="bold">/usr/afs/etc</emphasis></entry>
6542 <entry><computeroutput>drwxr</computeroutput>?<computeroutput>xr-x</computeroutput></entry>
6546 <entry><emphasis role="bold">/usr/afs/etc/KeyFile</emphasis></entry>
6548 <entry><computeroutput>-rw</computeroutput>????<computeroutput>---</computeroutput></entry>
6552 <entry><emphasis role="bold">/usr/afs/etc/UserList</emphasis></entry>
6554 <entry><computeroutput>-rw</computeroutput>?????<computeroutput>--</computeroutput></entry>
6558 <entry><emphasis role="bold">/usr/afs/local</emphasis></entry>
6560 <entry><computeroutput>drwx</computeroutput>???<computeroutput>---</computeroutput></entry>
6564 <entry><emphasis role="bold">/usr/afs/logs</emphasis></entry>
6566 <entry><computeroutput>drwxr</computeroutput>?<computeroutput>xr-x</computeroutput></entry>
6573 <primary>first AFS machine</primary>
6575 <secondary>client functionality</secondary>
6577 <tertiary>removing</tertiary>
6581 <primary>removing</primary>
6583 <secondary>client functionality from first AFS machine</secondary>
6588 <sect1 id="HDRWQ98">
6589 <title>Removing Client Functionality</title>
6591 <para>Follow the instructions in this section only if you do not wish this machine to remain an AFS client. Removing client
6592 functionality means that you cannot use this machine to access AFS files. <orderedlist>
6594 <para>Remove the files from the <emphasis role="bold">/usr/vice/etc</emphasis> directory. The command does not remove the
6595 directory for files used by the dynamic kernel loader program, if it exists on this system type. Those files are still
6596 needed on a server-only machine. <programlisting>
6597 # <emphasis role="bold">cd /usr/vice/etc</emphasis>
6598 # <emphasis role="bold">rm *</emphasis>
6599 # <emphasis role="bold">rm -rf C</emphasis>
6600 </programlisting></para>
6604 <para>Create symbolic links to the <emphasis role="bold">ThisCell</emphasis> and <emphasis
6605 role="bold">CellServDB</emphasis> files in the <emphasis role="bold">/usr/afs/etc</emphasis> directory. This makes it
6606 possible to issue commands from the AFS command suites (such as <emphasis role="bold">bos</emphasis> and <emphasis
6607 role="bold">fs</emphasis>) on this machine. <programlisting>
6608 # <emphasis role="bold">ln -s /usr/afs/etc/ThisCell ThisCell</emphasis>
6609 # <emphasis role="bold">ln -s /usr/afs/etc/CellServDB CellServDB</emphasis>
6610 </programlisting></para>
6614 <para>On IRIX systems, issue the <emphasis role="bold">chkconfig</emphasis> command to deactivate the <emphasis
6615 role="bold">afsclient</emphasis> configuration variable. <programlisting>
6616 # <emphasis role="bold">/etc/chkconfig -f afsclient off</emphasis>
6617 </programlisting></para>
6621 <para>Reboot the machine. Most system types use the <emphasis role="bold">shutdown</emphasis> command, but the appropriate
6622 options vary. <programlisting>
6623 # <emphasis role="bold">cd /</emphasis>
6624 # <emphasis role="bold">shutdown</emphasis> <replaceable>appropriate_options</replaceable>
6625 </programlisting></para>
6627 </orderedlist></para>