Skip to content
Snippets Groups Projects
Select Git revision
  • dname_limiting
  • declarative-config-stabilization
  • local-data_rules_records_tags
  • root-fallback-addresses
  • module-tunnel-filter
  • dname_kru
  • defer-hard-timeout
  • ci-jobs-reorganization
  • master default protected
  • nightly protected
  • manager-api-config-fix
  • tls-authority-whitelist
  • rfc-list
  • manager-files-watchdog
  • tmp/test-deckard
  • forward-tls-insecure
  • doh-stuck-status
  • module-filter
  • coverity protected
  • ci-docker-tests-update
  • v6.0.11 protected
  • v6.0.10 protected
  • v6.0.9 protected
  • v6.0.8 protected
  • v5.7.4 protected
  • v5.7.3 protected
  • v6.0.7 protected
  • v5.7.2 protected
  • v6.0.6 protected
  • v5.7.1 protected
  • v6.0.5 protected
  • v6.0.4 protected
  • v6.0.3 protected
  • v6.0.2 protected
  • v5.7.0 protected
  • v6.0.1 protected
  • v6.0.0a1 protected
  • v5.6.0 protected
  • v5.5.3 protected
  • v5.5.2 protected
40 results
Blame History Permalink
  • Oto Šťáva's avatar
    daemon/engine: warning when log_groups contains a non-existent group · a614818b
    Oto Šťáva authored and Vladimír Čunát's avatar Vladimír Čunát committed 
    Until now, kresd would refuse to start when a log_groups Lua call
contained a non-existent group. After this change, only a warning is
printed, which helps during development while switching between branches
with new logging groups. I don't think changing the configuration all
the time just for a logging group is warranted.
    a614818b