Redundant, conflicting, or unused configuration entries should result in warning or error

[Jennifer Richards]

Conflicting configuration directives in the configuration files should at least cause a warning to the user. For example, if there are multiple definitions of hostname or TID / TRP port, these will silently overrule each other, the last one to be loaded being put into the active configuration. This is probably not intended by the user, so a warning should be issued to inform the user of the situation and what has actually been configured. Alternatively, the configuration could be rejected.

Unrecognized entries in the configuration files are currently ignored; these should result in warnings because they likely represent erros, but might conceivably be intended.