diff options
| author | kundatipradeep <35292742+kundatipradeep@users.noreply.github.com> | 2018-04-27 17:36:53 +0530 |
|---|---|---|
| committer | Christoph Lipka <clipka@users.noreply.github.com> | 2018-04-27 14:06:53 +0200 |
| commit | a7452aa09ae2442c83ef879c7076ed57b9e9ece5 (patch) | |
| tree | 397a78a3f0fdb3c57a9c475d5a8cc02dcfd97e69 /src/console | |
| parent | 90c8b5b2890a227088b5a67a21bdc24028b156d5 (diff) | |
| download | DLT-daemon-a7452aa09ae2442c83ef879c7076ed57b9e9ece5.tar.gz | |
Fix ForceContextLogLevelAndTraceStatus handling in dlt_daemon_client.c (#50)
Even Forcing log level and trace status of context to not exceed "ContextLogLevel" and "ContextTraceStatus" in dlt.conf file with ForceContextLogLevelAndTraceStatus = 1, the default log level is being overwritten with high value than expected by client(DLT_Viewer when default trace data request is sent ) and by dlt-control application on usage of (dlt-control -d loglevel IP_ADDRESS)
With provided patch/changes in place, when ForceContextLogLevelAndTraceStatus is enabled the requested log level is checked with ContextLogLevel and if it satisfied the daemon default loglevel gets updated.
Added a conditional checks to not to overwrite the individual contextLoglevel and ContextTracesStatus when ForceContextLogLevelAndTraceStatus is enabled in dlt.conf file and taken care of review comments.
Diffstat (limited to 'src/console')
0 files changed, 0 insertions, 0 deletions