Guralp Systems CD1.1 - Manual (Page 65)

Operator's Guide
Module Configuration file locations for 1 st
and 2 nd instances
Multiplexor
(data-mux-
cd11) /etc/data-mux-cd11/0.local
/etc/data-mux-cd11/1.local
Converter
(gdi2cd11) /etc/gdi2cd11/0.local
/etc/gdi2cd11/1.local
Receiver
(data-in-cd11) /etc/data-in-cd11/0.local
/etc/data-in-cd11/1.local
Sender
(data-out-
cd11) /etc/data-out-cd11/0.local
/etc/data-out-cd11/1.local
If passed the -a (or --all) option, it will apply the changes to
all configured instances of all CD1.1 modules. If passed the -C
(or --save-config) option, it will first update the configuration
file(s) with the new settings, so that if the instance is restarted
the new settings will be remembered.
It will then use IPC to communicate the the new settings to the
running instance(s), which take effect immediately. The
configuration file must contain the path to the management
socket for the instance (the default configuration tool always
provides this).
Note that the management tool is not able to turn
authentication on/off while the module is running. It can only
change the Spyrus slot and the authentication ID field.
•
To change the logging level, pass the -l (or --log-
level) flag with an argument of “LOG_DEBUG”,
“LOG_INFO”,
“LOG_NOTICE”, “LOG_WARNING”,
“LOG_ERR”, “LOG_CRIT”, “LOG_ALERT” or “LOG_EMERG”.
These arguments correspond to the standard Linux
syslog logging levels.
•
To change the authentication key slot and/or ID, pass
the -k (or --auth-key-id) flag with an argument of
slot,ID
Full usage details for this program can be produced by passing
it the -h (or --help) flag:
Usage:
June 2010 65