---
name: "ccs_config_validate"
section: "8"
platform: "linux"
package: "cman"
version: "3.1.8-1.2+b1"
release: "Debian 8 (Jessie)"
platforms: ["linux"]
url: "https://new.carta.tech/ccs_config_validate"
---

# ccs\_config\_validate(8)

## NAME

ccs\_config\_validate

## DESCRIPTION

Usage:

ccs\_config\_validate \[options\]

## OPTIONS

- **-h**

  Print this help, then exit

- **-V**

  Print program version information, then exit

- **-v**

  Produce verbose output

### Validating XML configuraton files:

- **-f** configfile

  Validate an alternate config file without preloading it with default values.

- **-l** configfile

  Validate an alternate config file with preloading of default values (recommended option).

### Advanced options:

- **-u**

  Do not update relaxng schema (see ccs\_update\_schema.8)

- **-r**

  Force validation of runtime config

**-C** config\_loader Override config plugin loader

- **-t** tempfile

  Force temporay file to tempfile

- **-n**

  Do not remove temporary file

- **-o**

  Overwrite temporary file (dangerous)

## DEFAULT

Default operation for ccs\_config\_validate is to load the currently configured environment and verify the outcoming configuration.

- Example 1: current environment uses a configuration file (/etc/cluster/cluster.conf).

  The user modifies cluser.conf and executes ccs\_config\_validate without options. The tool will validate the modified cluster.conf after including default values.

- Example 2: current environment is set to load the configuration from LDAP. Users

  modifies LDAP databse and before pushing the change to the nodes, she/he can issue ccs\_config\_validate to verify the contents o the LDAP database automatically (as long as the correct LDAP environment is set in the cman/cluster sysconfig/defaults files).