The following systypes are currently on the production DCSLIB servers:

1. decalpha
2. linux-6
3. linux-7
4. rhel-3-i686
5. sgi-n32
6. sun4-5
7. solaris-2.6

The methods

1. Static mounting
   • Pro's:
     1. The simplest method in most cases
   • Con's:
     1. Poor fault tolerance: If the one DCSLIB server you've selected goes down, and you reboot, you'll still be stuck if the DCSLIB server hasn't come back up yet
     2. It isn't always clear which file to edit, to folks without sysadmin experience. This method actually comprises a class of methods that vary from OS to OS.
   • How to do it:
     1. mkdir /dcs /dcslib
     2. Locate your "fstab" file, or the equivalent. It'll most likely be /etc/fstab, /etc/vfstab, /etc/filesystems, /etc/checklist, or something along those lines.
     3. Edit this file and add something like, for example:
        1. Sun:
           dcslib1.nacs.uci.edu:/dcspdb/sun4-5 - /dcs nfs - yes ro
           dcslib1.nacs.uci.edu:/dcspda - /dcslib nfs - yes ro
        2. Linux:
           okazaki.nac.uci.edu:/dcspdb/rhel-3-i686 /dcs nfs rsize=8192,wsize=8192
           okazaki.nac.uci.edu:/dcspda /dcslib nfs rsize=8192,wsize=8192
     4. Reboot or execute static mount commands
2. "dyn-dcslib" mounting
   • Pro's:
     1. Moderate complexity
     2. Moderate fault tolerance - you can usually reboot to change to a different DCSLIB server if you need to, as long as you can reach any of the DCSLIB servers at reboot time.
   • Con's:
     1. Moderate complexity
     2. Moderate fault tolerance
   • How to do it:
     1. Determine your default runlevel. You can frequently get this with the "who -r" command
     2. Copy S14dyn-dcslib into, for example, /etc/rc3.d, if your default runlevel is 3. Change the "systype" in the script to whatever you need - the version presented is for Solaris systems, which the script knows as "sun4-5".
     3. On some systems, you will need to chmod +x this file, to make it executable (especially on linux systems).
     4. Reboot, or run the command manually.
3. Automounting DCSLIB
   • Pro's:
     1. The best fault tolerance: as long as you can get a network connection to any of the production DCSLIB servers, you should be able to fail over to another one transparently.
   • Con's:
     1. Probably the most complicated method
     2. Doesn't work on all that many OS's. DCS uses this method on recent releases of Solaris, and rumor has it this can be done on recent releases of Redhat. IRIX and Tru64 likely cannot.
   • How to do it:
     1. Put a line like "/- auto_dcslib" in /etc/auto_master
     2. Put a lines like the following into your /etc/auto_dcslib file:
        • /dcs -ro dcslib1.nacs.uci.edu,dcslib2.nacs.uci.edu,dcslib3.nacs.uci.edu:/dcspdb/sun4-5
        • /dcslib -ro dcslib1.nacs.uci.edu,dcslib2.nacs.uci.edu,dcslib3.nacs.uci.edu:/dcspda
     3. Reboot, run the "automount" command (untested), or kill and restart automountd using signal 15, not signal 9.