1CCS_CONFIG_VALIDATE(8) System Manager's Manual CCS_CONFIG_VALIDATE(8)
2
3
4
6 ccs_config_validate
7
9 Usage:
10
11 ccs_config_validate [options]
12
14 -h Print this help, then exit
15
16 -V Print program version information, then exit
17
18 -v Produce verbose output
19
20 Validating XML configuraton files:
21 -f configfile
22 Validate an alternate config file without preloading it with
23 default values.
24
25 -l configfile
26 Validate an alternate config file with preloading of default
27 values (recommended option).
28
29 Advanced options:
30 -u Do not update relaxng schema (see ccs_update_schema.8)
31
32
33
34 -r Force validation of runtime config
35
36 -C config_loader Override config plugin loader
37
38 -t tempfile
39 Force temporay file to tempfile
40
41 -n Do not remove temporary file
42
43 -o Overwrite temporary file (dangerous)
44
46 Default operation for ccs_config_validate is to load the currently con‐
47 figured environment and verify the outcoming configuration.
48
49 Example 1: current environment uses a configuration file (/etc/clus‐
50 ter/cluster.conf).
51 The user modifies cluser.conf and executes ccs_config_validate
52 without options. The tool will validate the modified clus‐
53 ter.conf after including default values.
54
55 Example 2: current environment is set to load the configuration from
56 LDAP. Users
57 modifies LDAP databse and before pushing the change to the
58 nodes, she/he can issue ccs_config_validate to verify the con‐
59 tents o the LDAP database automatically (as long as the correct
60 LDAP environment is set in the cman/cluster sysconfig/defaults
61 files).
62
63
64
65 September 2009 CCS_CONFIG_VALIDATE(8)