6.9.2

# scchkcfg

Checks a module configuration.

## Description

scchkcfg checks for case-sensitivity issues of parameter names of the module configuration file for a module. It reads all defined configuration stages (see Modules) and checks for each parameter read if it exists again with a different spelling.

If standalone is not given, it checks all 6 configurations files (including `global.cfg`), 3 otherwise.

## Examples

    $ scchkcfg scautopick
    Read configuration files OK
    No possible conflict detected

scchkcfg checks only for possible conflicts since it does not know what parameters a module will read eventually.

    $ scchkcfg scautopick
    Read configuration files OK
    Conflict #1
     connection.server    /home/sysop/seiscomp/etc/global.cfg:8
     connection.Server    /home/sysop/.seiscomp/scautopick.cfg:1
    1 conflict detected

In this case everything is ok and the conflict needs to be fixed. `connection.Server` is not a valid parameter name (but `connection.server` is) in `/home/sysop/.seiscomp/scautopick.cfg` and thus will not be used.

    $ scchkcfg scautopick
    Read configuration files OK
    Conflict #1
     module.trunk.global.amplitudes.mb.signalEnd    \
          /home/sysop/.seiscomp/scautopick.cfg:1
     module.trunk.global.amplitudes.mB.signalEnd    \
          /home/sysop/.seiscomp/scautopick.cfg:2
    1 conflict detected

In this case the configuration is OK and this is an example why the case-sensitivity has changed from previous versions: mb != mB. scchkcfg detects a possible conflicts but does not know that this case is well defined. But it helps the user to decide whether it needs a fix or not.

## Command-Line Options

scchkcfg {mod-name} [standalone]