Verifying the AFS Initialization Script

Verifying the AFS Initialization Script
	Chapter 2. Installing the First AFS Machine

At this point you run the AFS initialization script to verify that it correctly invokes all of the necessary programs and AFS processes, and that they start correctly. The following are the relevant commands:

The command that dynamically loads AFS modifications into the kernel, on some system types (not applicable if the kernel has AFS modifications built in)
The bosserver command, which starts the BOS Server; it in turn starts the server processes for which you created entries in the /usr/afs/local/BosConfig file
The afsd command, which initializes the Cache Manager

On system types that use a dynamic loader program, you must reboot the machine before running the initialization script, so that it can freshly load AFS modifications into the kernel.

If there are problems during the initialization, attempt to resolve them. The OpenAFS mailing lists can provide assistance if necessary.

Issue the bos shutdown command to shut down the AFS server processes other than the BOS Server. Include the -wait flag to delay return of the command shell prompt until all processes shut down completely.
```
   # /usr/afs/bin/bos shutdown <machine name> -wait
```
Issue the ps command to learn the bosserver process's process ID number (PID), and then the kill command to stop it.
```
   # ps appropriate_ps_options | grep bosserver
   # kill bosserver_PID
```

Issue the appropriate commands to run the AFS initialization script for this system type.

On Linux systems:

Reboot the machine and log in again as the local superuser root.

   # cd /
   # shutdown -r now
   login: root
   Password: root_password

Run the AFS initialization scripts.

   # /etc/rc.d/init.d/openafs-client  start
   # /etc/rc.d/init.d/openafs-server  start

On Solaris systems:

Reboot the machine and log in again as the local superuser root.

   # cd /
   # shutdown -i6 -g0 -y
   login: root
   Password: root_password

Run the AFS initialization script.
```
   # /etc/init.d/afs  start
```

Wait for the message that confirms that Cache Manager initialization is complete.
On machines that use a disk cache, it can take a while to initialize the Cache Manager for the first time, because the afsd program must create all of the Vn files in the cache directory. Subsequent Cache Manager initializations do not take nearly as long, because the Vn files already exist.
If you are working with an existing cell which uses kaserver for authentication, please recall the note in Using this Appendix detailing the substitution of kinit and aklog with klog.
As a basic test of correct AFS functioning, issue the kinit and aklog commands to authenticate as the admin user. Provide the password (admin_passwd) you defined in Initializing Cell Security.
```
   # kinit admin
   Password:  admin_passwd
   # aklog
```
Issue the tokens command to verify that the aklog command worked correctly. If it did, the output looks similar to the following example for the example.com cell, where admin's AFS UID is 1. If the output does not seem correct, resolve the problem. Changes to the AFS initialization script are possibly necessary. The OpenAFS mailing lists can provide assistance as necessary.
```
   # tokens
   Tokens held by the Cache Manager:
   User's (AFS ID 1) tokens for afs@example.com [Expires May 22 11:52]
       --End of list--
```
Issue the bos status command to verify that the output for each process reads Currently running normally.
```
   # /usr/afs/bin/bos status <machine name>
```
Change directory to the local file system root (/) and issue the fs checkvolumes command.
```
   # cd /
   # /usr/afs/bin/fs checkvolumes
```


Overview: Completing the Installation of the First AFS Machine		Activating the AFS Initialization Script