Would you like to manage clients? [N]:

The wizard now has all the data it needs to configure the cluster and proceeds to do so:

******* WARNING!!!! ********

To protect against possible corruption of sensitive configuration files, control-c has been disabled for the remainder of this configuration.

Configuring the “csync” Serviceguard package.

Applying the “csync” Serviceguard package configuration file. This will take a moment.

Starting the “csync” Serviceguard package. This will take a few moments...

The “csync” Serviceguard package has been started on local_hostname.

Configuration of the cfengine master server is starting.

Configuration files have been saved at: /var/opt/dsau/cfengine/backups

cfengine keys are being created...

cfengine keys have been created, now distributing....

Verifying that the master has an entry in the /etc/hosts file

on each client...

Starting cfengine on the master server and any managed clients.

This may take a few minutes....

When the configuration is done, the wizard displays the following summary screens which direct the administrator to the main policy file, /mount_point/cfengine_master/inputs/cf.main, and the recorded answer file for this run of the wizard. The policy file is located on the newly configured filesystem associated with the package. In our example, the administrator chose to mount the filesystem for the package as /csync.

If the administrator had previously configured cfengine, before overwriting any existing configuration files, the wizard creates backups in the directory:

/var/opt/dsau/cfengine/backups

The top level files in this directory are the most recent backup files. Any configurations before that are saved in timestamped subdirectories named v_timestamp.

The Configuration Synchronization Wizard has completed the configuration of cfengine:

-The master configuration description template is here:

</csync/dsau/cfengine_master/inputs/cf.main>

This default template has examples of typical configuration synchronization actions performed in a cluster. For example, synchronizing critical files such as /etc/hosts, package scripts, etc.

All the actions in the template are disabled by default (commented out).

Uncomment the lines corresponding to the desired synchronization actions for this cluster. See the cfengine reference documentation for a description of additional cfengine features: /opt/dsau/doc/cfengine/

22 Configuration Synchronization