Chapter 15. File reference

This section lists all the main files, sockets and directories used by the CD1.1 subsystem.

15.1 Operation

/usr/bin/data-in-cd11
/usr/bin/data-out-cd11
/usr/bin/data-mux-cd11
/usr/bin/gdi2cd11 - the module binaries.

/usr/bin/cd11-backfilldb-tool
/usr/bin/cd11-frame-analyser-tool
/usr/bin/cd11-framedb-tool
/usr/bin/cd11-timedb-tool - command-line tools for examining and modifying various databases, as described in Section 10.2.

/usr/bin/cd11-management-tool
/usr/sbin/cd11-spyrus-tool.sh - command-line tools for authentication management, as described in chapter 11.

/srv/http/cgi-bin/cd11-analyser.cgi - CGI (web interface) binary implementing the CD1.1 log analyser tools.

/usr/lib/libdata-cd11.so.6 (link to libdata-cd11.so.6.2) - the CD1.1 support library.

libframesettrack.so.2.1 (link to libframesettrack.so.2) - the subframe database support library.

15.2 Database directories

/var/lib/data-in-cd11.n - default database directory for the (n+1)th instance of the CD1.1 receiver. Contains a file named SENDER.framesetdb for each DP recognised by this receiver instance. These directories are only created when required.

/var/lib/data-out-cd11.n - default database directory for the (n+1)th instance of the CD1.1 sender. Contains the files backfilldb, framedb and transmission_log. These directories are only created when required.

/var/lib/data-mux-cd11.n - default database directory for the (n+1)th instance of the CD1.1 multiplexer. Contains the daily database files. These directories are only created when required.

15.3 Inter-process communication

/var/run/data-in-cd11.n.management
/var/run/data-out-cd11.n.management
/var/run/gdi2cd11.n.management - IPC sockets for controlling the (n+1)th instances of the CD1.1 receiver, the CD1.1 sender and the GDI gateway, respectively. These sockets are only created when required.

/var/run/data-mux-cd11.n - IPC socket for data exchange between the (n+1)th instance of the CD1.1 multiplexer and the other CD1.1 modules. These sockets are only created when required.

15.4 Configuration

/etc/data-in-cd11/n.local
/etc/data-in-cd11/n.ctl.local
/etc/data-out-cd11/n.local
/etc/data-out-cd11/n.ctl.local
/etc/data-mux-cd11/n.local
/etc/data-mux-cd11/n.ctl.local
/etc/gdi2cd11/n.local
/etc/gdi2cd11/n.ctl.local - configuration settings for the (n+1)th instances of the various CD1.1 modules. These files are only created when required.

/etc/spyrus/spyrus.local
/etc/spyrus/dsaparam.pem.local
/etc/spyrus/cd11-spyrus-tool.local
/etc/spyrus/reqparam.local - configuration settings for authentication management. DSA parameters are cached for fast key generation, and default certificate signing request parameters are also stored.

/usr/share/webconfig/menu/cd11-analyser - An XML file which defines the logic that the web interface subsystem uses to show or hide the “CD1.1 log analyser” menu.

/usr/share/config-base/services/data-in-cd11/info
/usr/share/config-base/services/data-out-cd11/info
/usr/share/config-base/services/data-mux-cd11/info
/usr/share/config-base/services/gdi2cd11/info - text files containing information for dynamically configuring CD1.1 module entries in the configuration system's “Services” menu.

/usr/share/config-base/scripts/data-in-cd11.sh
/usr/share/config-base/scripts/data-out-cd11.sh
/usr/share/config-base/scripts/data-mux-cd11.sh
/usr/share/config-base/scripts/gdi2cd11.sh
/usr/share/config-base/scripts/cd11mux_link.sh - shell scripts that define how the configuration system reads and writes the configuration files for the various CD1.1 modules. The script cd11mux_link.sh is used to generate the list of active multiplexers which appears as drop-down menus in the configuration screens for the other modules.

/usr/share/config-base/templates/data-in-cd11.tpl
/usr/share/config-base/templates/data-out-cd11.tpl
/usr/share/config-base/templates/data-mux-cd11.tpl
/usr/share/config-base/templates/gdi2cd11.tpl - text files which define the appearance and behaviour of the configuration screens for the CD1.1 modules.

15.5 Run Control

/etc/init.local/data-in-cd11.n
/etc/init.local/data-out-cd11.n
/etc/init.local/data-mux-cd11.n
/etc/init.local/gdi2cd11.n - run control scripts for the (n+1)th instances of the various CD1.1 modules. These files are only created when required.

/var/run/svc/data-in-cd11.n.started
/var/run/svc/data-in-cd11.n.pid
/var/run/svc/data-out-cd11.n.started
/var/run/svc/data-out-cd11.n.pid
/var/run/svc/data-mux-cd11.n.started
/var/run/svc/data-mux-cd11.n.pid
/var/run/svc/gdi2cd11.n.started
/var/run/svc/gdi2cd11.n.pid - text files containing invocation time-stamps (*.started) and process IDs (*.pid) for all running instances of the various CD1.1 modules. These files are only created when required.

Under /usr/share/config-base/services/…
./data-in-cd11/svc-script.in
./data-out-cd11/svc-script.in
./data-mux-cd11/svc-script.in
./gdi2cd11/svc-script.in - templates for the run control scripts.

15.6 Miscellaneous

/usr/share/platinum-versions/data-in-cd11
/usr/share/platinum-versions/data-out-cd11
/usr/share/platinum-versions/data-mux-cd11
/usr/share/platinum-versions/gdi2cd11
/usr/share/platinum-versions/data-cd11-misc
/usr/share/platinum-versions/libdata-cd11 - version control signatures for the various CD1.1 packages.

/usr/share/data-mux-cd11/example-cmdframe-script.sh - example script that could be used when executing CD1.1 command frames (or IMS2.0 messages).

/srv/http/img/cd11-analyser/* - web images for the subframe status icons in the multiplexer log analysis tool (see Section 10.1.1).

/usr/lib/libtamper.so.1 (link to libtamper.so.1.0) - library providing tamper detection monitoring functions.

/usr/lib/libenvirolog.so.0 (link to libenvirolog.so.0.0) - library providing voltage, current etc monitoring functions.

/usr/lib/libspyrus.so.3 (link to libspyrus.so.3.1) - library providing cryptographic support for signed frames.