debugmode=1
# Limiter - whether it's enabled and the rules (check the documentation for how to create rules).
-limiter=0
+limiter=1
limiter|*|*=allow
# A flag indicating if apps/events buffer entries are always checked against static/dynamic limiter rules
limiter_apply_to_all_buffers=0
# dynamic config_path - specifies the path to a DIRECTORY to enable dynamic runtime config changes (use dlogctl for control)
-# dynamic_config_path=/run/dlog/filters.d/
+dynamic_config_path=/run/dlog/filters.d/
##### Settings used by the logging daemon
# See also 20-pipe.conf for more info
To use it, runtime control has to be enabled (before the program first calls
the library, as else static configuration is used). You must have a directory
to which all users of the library have read access; put path to this directory
-to the `dynamic_config_path` config entry. For example, if that directory is
-the default (i.e. `/run/dlog/filters.d`):
+to the `dynamic_config_path` config entry. By default, this is already defined
+to `/run/dlog/filters.d`, but you could change it:
- $ echo "dynamic_config_path=/run/dlog/filters.d" >> /opt/etc/dlog.conf
+ $ echo "dynamic_config_path=/my/custom/path.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
+ $ echo "dynamic_config_path=/my/custom/path.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:
+use it, the basic (static) version of the feature has to be enabled as well.
+This should already be the case by default, but if not, here's how to:
$ echo "limiter=1" >> /opt/etc/dlog.conf