Unix socket control interface

Control applications running in the same Linux OS should be able to communicate
with the DLT Daemon via a socket connection.
To be able to do that, the DLT Client library need to be extended. DLT
Clients connected via this UNIX socket are not handled as normal DLT
Clients and no log messages will be forwarded to them. This avoids
problems in situations when a control application is connected to the
DLT Daemon before any other 'real' DLT Client (e.g. DLT Viewer) is
connected. In this situations, all already stored log messages are
flushed to the control application and therefore lost, because the
control application most likely ignore all incoming messages besides the
one in which it is interested in.

Signed-off-by: Christoph Lipka <clipka@jp.adit-jv.com>

1 files changed, 5 insertions, 1 deletions

diff --git a/src/daemon/dlt_daemon_common_cfg.h b/src/daemon/dlt_daemon_common_cfg.h
index e0f99da..d08a20e 100644
--- a/src/daemon/dlt_daemon_common_cfg.h
+++ b/src/daemon/dlt_daemon_common_cfg.h
@@ -74,6 +74,7 @@
 /* Changable */
 /*************/
 
+
 /* Default Path for runtime configuration */
 #define DLT_RUNTIME_DEFAULT_DIRECTORY "/tmp"
 /* Path and filename for runtime configuration (applications) */
@@ -83,6 +84,10 @@
 /* Path and filename for runtime configuration */
 #define DLT_RUNTIME_CONFIGURATION     "/dlt-runtime.cfg"
 
+/* Default Path for control socket */
+#define DLT_DAEMON_DEFAULT_CTRL_SOCK_PATH DLT_RUNTIME_DEFAULT_DIRECTORY \
+                                          "/dlt-ctrl.sock"
+
 /* Size of text buffer */
 #define DLT_DAEMON_COMMON_TEXTBUFSIZE          255
 
@@ -120,4 +125,3 @@
 #define DLT_DAEMON_REMO_STRING "remo"
 
 #endif /* DLT_DAEMON_COMMON_CFG_H */
-