From b0b98179d914b751b9413e4c1b00a1fb5e9f0631 Mon Sep 17 00:00:00 2001 From: Michal Bloch Date: Fri, 19 Oct 2018 20:56:15 +0200 Subject: [PATCH] documentation: describe some common mistakes Change-Id: Ib18b454042a50152bc0815fe42780d2fb8a05004 Signed-off-by: Michal Bloch --- documentation/dlog_ctl.txt | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/documentation/dlog_ctl.txt b/documentation/dlog_ctl.txt index 0a46c36..c924a85 100644 --- a/documentation/dlog_ctl.txt +++ b/documentation/dlog_ctl.txt @@ -8,12 +8,23 @@ the default (i.e. `/run/dlog/filters.d`): $ echo "dynamic_config_path=/run/dlog/filters.d" >> /opt/etc/dlog.conf +If you're doing this through creating a new file in the config directory, +remember that it also needs to be readable by everyone (common mistake): + + $ echo "dynamic_config_path=/run/dlog/filters.d" > /opt/etc/dlog.conf.d/30-dynamic.conf + $ chsmack -a _ /opt/etc/dlog.conf.d/30-dynamic.conf + Now dynamic control can be exerted. There are two features configurable at runtime, the first is an extension of the filtering limiter. Of course to use it, the basic (static) version of the feature has to be enabled as well: $ echo "limiter=1" >> /opt/etc/dlog.conf +Remember that for backward-compatiblity reasons, the limiter does not apply +to the `apps` buffer by default. Don't forget to change this behaviour: + + $ echo "limiter_apply_to_all_buffers=1" >> /opt/etc/dlog.conf + The static config might have already defined some filtering rules. Let's dump the whole filterset to see what we are working with: -- 2.7.4