21.5 Configuration Variables (rc.config, rc.config.common)

Prior to version 5.0 of Tru64 UNIX (and the V5.X TruCluster Server software that came along with it), all the configuration variables were stored in the rc.config file and managed by the rcmgr (8) utility. With version 5.0A of TruCluster Server, a few of the variables are member-specific but others are actually common throughout the cluster, thus the split in rc.config. As you may remember from Chapter 6, the rc.config file is a CDSL and contains the member-specific variables. Here's some of what you'll see in rc.config that is cluster-related:

 [gilligan] # grep -E "CLU|TCR" /etc/rc.config CLU_BOOT_FILESYSTEM="root2_domain#root" export CLU_BOOT_FILESYSTEM CLUSTER_NET="gilligan-mc0" export CLUSTER_NET TCR_INSTALL="TCR" export TCR_INSTALL TCR_PACKAGE="TCR" export TCR_PACKAGE CLU_NEW_MEMBER="0" export CLU_NEW_MEMBER CLU_VERSION="TruCluster Server V5.1 (Rev. 389)" export CLU_VERSION

Note

An rc.config.site file is supported but Tru64 UNIX doesn't ship this file by default and the system administrator would have to create and maintain it.

Let's also take a quick peek at rc.config.common to see the sorts of variables defined there.

 ... NUM_NFSIOD="7" export NUM_NFSIOD NFS_CONFIGURED="1" export NFS_CONFIGURED NFSSERVING="1" export NFSSERVING ... NIS_DOMAIN="BRAVO" export NIS_DOMAIN NIS_ARGS="-s -S OSD,fathom.abc.net,reverse.abc.net" export NIS_ARGS NIS_SERVERARGS="" export NIS_SERVERARGS SECURITY="BASE" export SECURITY ...

Things like security settings, NIS setup, NFS, etc. are common to the cluster, and it makes sense that they would be in a cluster-common variable definition file. The important point here is that there are two files to keep in mind when setting and checking variable definitions.

For more on rc.config, check back to Chapter 6 and Chapter 12.