Distributed Systems Administration Utilities User's Guide, Linux, March 2009

9. The file /var/opt/dsau/cfengine_master/inputs/cfservd.conf controls which
managed clients have access to the files served by cfservd on the master. Make the following
edits to cfservd.conf:
• Replace the “<%CFSERVD_DOMAIN_LISTS%>“token with a comma-separated list of
wildcarded DNS domains or hostnames for the systems that are allowed to access this
server. For example:
domain_list = ( “*.abc.xyz.com,*.cde.xyz.com“ )
This statement allows all hosts in the abc.xyz.com and cde.xyz.com domains to access
the master server.
IMPORTANT: No spaces are allowed in this comma-separated list.
Prefix each domain name with the “*.” wildcard.
NOTE: The csync_wizard only supports specifying wildcarded domain names in
cfservd.conf. If you manually edit cfservd.conf and include a combination of specific
hostnames or IP address and wildcarded domains, then subsequent runs of csync_wizard
will replace this line with a list of wildcarded domains based on the list of hosts present
in cfrun.hosts.
10. On the master server, start cfservd:
# /etc/init.d/cfservd start
Repeat this for each managed client.
NOTE: cfservd.conf must be present in /var/opt/dsau/cfengine/inputs
before executing this command.
11. Test the configuration by performing the following steps:
a. On a managed client, use the command:
# cfagent --no-lock --verbose --no-splay
The verbose output will display the client checking for updated copies of the master
policy files, copying them down to /var/opt/cfengine/inputs if needed, and then
executing the contents of cfagent.conf/cf.main.
b. On the master server, test the cfrun command:
# cfrun -- --inform
The --inform syntax instructs the remote cfagent to use the --inform flag which
will produce messages for all changes cfengine performs on the system. For additional
information, the --verbose can also be helpful:
# cfrun -v -- --verbose
The -v instructs cfrun itself to be more verbose and the --verbose is passed on to
the remote cfagent.
For additional troubleshooting information, refer to “cfengine Troubleshooting” (page 42).
2.3.2.2 Manually Configuring a Serviceguard Cluster Synchronization Server
Configuring cfengine for high availability in a Serviceguard cluster is similar to configuring it
for a standalone machine, which is described in the section “Using the Wizard to Configure a
Standalone Synchronization Server” (page 21). The primary differences are the creation of the
32 Configuration Synchronization