Document asynchronous delay in DLT_REGISTER_APP

Signed-off-by: Alexander Wenzel <Alexander.AW.Wenzel@bmw.de>

1 files changed, 4 insertions, 2 deletions

diff --git a/doc/dlt_user_manual.txt b/doc/dlt_user_manual.txt
index d6f02a4..54773e9 100644
--- a/doc/dlt_user_manual.txt
+++ b/doc/dlt_user_manual.txt
@@ -204,10 +204,12 @@ DLT_REGISTER_CONTEXT(mycontext,"TEST","Test Context for Logging");
 }
 ----
 
-Important note: 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.
+.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.
+* 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:
-Here we use the macro interface of DLT
+Here we use the macro interface of DLT. 
 
 ----
 DLT_LOG(mycontext,DLT_LOG_WARN,DLT_INT(5),DLT_STRING("This is a warning"));