Documentation update

Signed-off-by: Manikandan C <mchockalingam@de.adit-jv.com>
Signed-off-by: Christoph Lipka <clipka@de.adit-jv.com>

1 files changed, 23 insertions, 4 deletions

diff --git a/doc/dlt_user_manual.txt b/doc/dlt_user_manual.txt
index c8f444e..54a252e 100644
--- a/doc/dlt_user_manual.txt
+++ b/doc/dlt_user_manual.txt
@@ -17,6 +17,8 @@ DLT User Manual
 ===============
 Alexander Wenzel <Alexander.AW.Wenzel@bmw.de>
 0.0.1, 2012/10/10: Initial version
+Christoph Lipka <clipka@de.adit-jv.com>
+0.0.2, 2018/12/13: updated version
 
 image::images/genivi_chrome_1_transparent.png[width=128]
 
@@ -138,15 +140,16 @@ See Manpage dlt-system(1).
 See Manpage dlt-system.conf(5).
 
 == DLT command line tools
-Four command line tools are provided together with DLT daemon implementation.
+six command line tools are provided together with DLT daemon implementation.
 
 These tools are:
 
 * Data logger: dlt-receive
 * Converter: dlt-convert
 * Sorter: dlt-sortbytimestamp
-* Configuration: dlt-control (planned)
-
+* Configuration: dlt-control
+* Logstorage: dlt-logstorage-ctrl
+* Multinode: dlt-passive-node-ctrl
 
 === dlt-receive
 
@@ -178,6 +181,22 @@ Ranges are essential when processing a DLT file covering more than a single rebo
 ==== Command line interface
 See Manpage dlt-sortbytimestamp(1).
 
+=== dlt-logstorage-ctrl
+
+==== Overview
+The dlt-logstorage-ctrl console utility is used to send a trigger to DLT Daemon to connect/disconnect/sync a certain offline logstorage device.
+
+==== Command line interface
+See Manpage dlt-logstorage-ctrl(1).
+
+=== dlt-passive-node-ctrl
+
+==== Overview
+The dlt-passive-node-ctrl console utility is used to send a trigger to DLT daemon to (dis)connect a passive node or get current passive node status.
+
+==== Command line interface
+See Manpage dlt-passive-node-ctrl(1).
+
 == DLT adaptors
 The DLT adaptors are used to interface legacy linux applications with the DLT daemon. Therefore, there are two adaptors:
 
@@ -248,7 +267,7 @@ DLT_REGISTER_CONTEXT(mycontext,"TEST","Test Context for Logging");
 ----
 
 .Important notes:
-* If your application uses fork(), you may not call DLT_REGISTER_APP before fork(). And fork() should never be called after DLT_REGISTER_APP. This is because of state information and inter process communication channel to daemon would be copied to new process, but threads would be not.
+* if fork() is called from an application after DLT_REGISTER_APP, dlt is reset in child process and user application needs to re-register application and contexts in child-process
 * DLT_REGISTER_APP is asynchronous. It may take some milliseconds to establish the IPC channel. Because of this, you might lose messages if you log immediately after registering. Typically this is not a problem, but may arise especially with simple examples.
 
 ==== Use one of the DLT macros or the DLT function interface: