Starting the Cache Manager and Installing the AFS Initialization Script

In this section you run the AFS initialization script to start the Cache Manager. If the script works correctly, perform the steps that incorporate it into the machine's startup and shutdown sequence. If there are problems during the initialization, attempt to resolve them. The AFS Product Support group can provide assistance if necessary.

On machines that use a disk cache, it can take a while for the afsd program to run the first time on a machine, because it 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.

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.

Proceed to the instructions for your system type:

Running the Script on Fedora / RHEL Systems

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

       # cd /
       # shutdown -r now
       login: root
       Password: root_password
    
  2. Run the AFS initialization script.

       # /etc/rc.d/init.d/openafs-client  start
    
  3. Issue the chkconfig command to activate the openafs-client configuration variable. Based on the instruction in the AFS initialization file that begins with the string #chkconfig, the command automatically creates the symbolic links that incorporate the script into the Linux startup and shutdown sequence.

       # /sbin/chkconfig  --add openafs-client
    

Running the Script on other Linux Systems

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

       # cd /
       # shutdown -r now
       login: root
       Password: root_password
    
  2. Run the AFS initialization script.

       # /etc/rc.d/init.d/afs  start
    
  3. Issue the chkconfig command to activate the afs configuration variable. Based on the instruction in the AFS initialization file that begins with the string #chkconfig, the command automatically creates the symbolic links that incorporate the script into the Linux startup and shutdown sequence.

       # /sbin/chkconfig  --add afs
    
  4. (Optional) There are now copies of the AFS initialization file in both the /usr/vice/etc and /etc/rc.d/init.d directories, and copies of the afsd options file in both the /usr/vice/etc and /etc/sysconfig directories. If you want to avoid potential confusion by guaranteeing that the two copies of each file are always the same, create a link between them. You can always retrieve the original script or options file from the AFS CD-ROM if necessary.

       # cd /usr/vice/etc
       # rm afs.rc afs.conf
       # ln -s  /etc/rc.d/init.d/afs  afs.rc
       # ln -s  /etc/sysconfig/afs  afs.conf
    
  5. If a volume for housing AFS binaries for this machine's system type does not already exist, proceed to Setting Up Volumes and Loading Binaries into AFS. Otherwise, the installation is complete.

Running the Script on Solaris Systems

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

       # cd /
       # shutdown -i6 -g0 -y
       login: root
       Password: root_password
    
  2. Run the AFS initialization script.

       # /etc/init.d/afs  start
    
  3. Change to the /etc/init.d directory and issue the ln -s command to create symbolic links that incorporate the AFS initialization script into the Solaris startup and shutdown sequence.

       # cd /etc/init.d
       # ln -s ../init.d/afs /etc/rc3.d/S99afs
       # ln -s ../init.d/afs /etc/rc0.d/K66afs
    
  4. (Optional) There are now copies of the AFS initialization file in both the /usr/vice/etc and /etc/init.d directories. If you want to avoid potential confusion by guaranteeing that they are always the same, create a link between them. You can always retrieve the original script from the OpenAFS Binary Distribution if necessary.

       # cd /usr/vice/etc
       # rm afs.rc
       # ln -s  /etc/init.d/afs  afs.rc
    
  5. If a volume for housing AFS binaries for this machine's system type does not already exist, proceed to Setting Up Volumes and Loading Binaries into AFS. Otherwise, the installation is complete.