TruCluster Server Handbook
This text authoritatively details how to plan, design, install, configure, and administer a cluster of Tru64 UNIX systems, and explains how to configure and optimize hardware underlying a TruCluster server and more.
TABLE OF CONTENTS TruCluster Server Handbook
Part IV: Cluster Hooks
- Chapter 6: Tru64 UNIX Cluster Hooks File System Hierarchy, CDSL, & PID
- Chapter 7: Tru64 UNIX Cluster Hooks Device Naming & Hardware Management
- Chapter 8: Tru64 UNIX Cluster Hooks Event Manager
- Chapter 9: Tru64 UNIX Cluster Hooks NIFF, NetRAIN, & LAG
Overview
In this chapter we will begin the discussion of the various components included in the base Tru64 UNIX operating system that enable a more seamless transition from a standalone system to a cluster.
We will cover the following components:
| Section | |
| 6.1.1, 6.4 |
| 6.1.2 |
| 6.2 |
| 6.5 |
The first and most significant change that was made to Tru64 UNIX was to have a transparent method for the operating system to locate its configuration information, executables, layered applications, etc., as well as to structure the basic file system hierarchy in such a way that it would not matter whether the system is standalone or in a cluster.
The method adopted is to split information into member-specific and cluster-common files for all Tru64 UNIX systems, whether they are in a cluster or standalone configuration. The cluster-common files are located in the files' normal location, while the member-specific files are located somewhere new (but appear to be located in the files' normal location more on this in the following sections). The member-specific files are actually located in one of three primary locations:
-
/cluster/members/member n
-
/usr/cluster/members/member n
-
/var/cluster/members/member n
(Where " n" is...
Copyright Scott Fafrak, Jim Lola, Dennis O'Brien, Greg Yates, and Brad Nichols 2003 under license agreement with Books24x7
