Managing Systems and Workgroups: A Guide for HP-UX System Administrators

Configuring a System
Using Distributed Systems Administration Utilities
Chapter 3166
“domain = <%DOMAIN_NAMER%>” and replace the token with the DNS
domain of the client systems. This restricts all the clients to be
members of that single domain.
8. The file /var/opt/dsau/cfengine_master/inputs/cfagent.conf
is the master policy file. The default cfagent.conf includes the
default template cf.main which is a commented template file with
examples of common synchronization actions for both standalone
systems and Serviceguard clusters. cf.main contains the same
<%HOST_NAMER%> and <%DOMAIN_NAMER%> tokens as those in
update.conf. Perform the same edits described in Step 3 above.
Note that this default cf.main file performs no management actions.
All the action lines are commented out. This is a starting point for
creating a custom set of cfengine policies and actions for your
managed clients. The cfengine reference manual that documents
the syntax and all the management actions defined in this file is
located in /opt/dsau/doc/cfengine. Other example cfengine
configuration files which are included with the open source cfengine
distribution are located in /opt/dsau/share/cfengine/examples.
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. Perform the following edits to cfservd.conf.
• Delete the following line entirely:
domain_name = ( “<%DOMAIN_NAMER%>” )
• Change the line reading
domain = ( “${domain_name}” )
to the following:
domain = ( ExecResult(/sbin/awk ‘/domain/ {print $2}’
/etc/resolv.conf) )
• The “admit:” stanza controls which remote clients have access to
files on the server. Change each “*.${domain_name}” to a space
separated list of managed client DNS domains. For example:
/var/opt/dsau/cfengine_master/master_files
*.abc.xyz.com *.cde.xyz.com