From da4ac57d87108d8b2690979c273c000a798a59f5 Mon Sep 17 00:00:00 2001 From: Christoph Lipka Date: Wed, 18 Nov 2015 19:19:22 +0900 Subject: 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 --- src/daemon/dlt.conf | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'src/daemon/dlt.conf') diff --git a/src/daemon/dlt.conf b/src/daemon/dlt.conf index d9b0987..23d40ec 100644 --- a/src/daemon/dlt.conf +++ b/src/daemon/dlt.conf @@ -53,6 +53,11 @@ RingbufferMaxSize = 10000000 # The step size the Ringbuffer is increased, used for storing temporary DLT messages, until client is connected (Default: 500000) RingbufferStepSize = 500000 +######################################################################## +# Control Application # +######################################################################## +ControlSocketPath = /tmp/dlt-ctrl.sock + ######################################################################## # Offline Trace memory # ######################################################################## -- cgit v1.2.1