]> git.ipfire.org Git - thirdparty/squid.git/commit
Place more msgs under cache_log_message control, downgrade some (#1273)
authorAlex Rousskov <rousskov@measurement-factory.com>
Tue, 14 Feb 2023 00:00:20 +0000 (00:00 +0000)
committerSquid Anubis <squid-anubis@squid-cache.org>
Tue, 14 Feb 2023 03:42:05 +0000 (03:42 +0000)
commit9259c796ff1ede2ef255d4d8578bdf66ab296ebf
treed011d336182515b5891dfa1df9cde3f5245f4de8
parentea21def9238252672ca213b2ef2dc49ce67798d0
Place more msgs under cache_log_message control, downgrade some (#1273)

Also support cache_log_message-controlled messages in ::Config-unaware
libraries (e.g., libip) used by tools (e.g., cachemgr.cgi).

Restricting the very first (i.e. "depth 0") "Processing Configuration
File" message does not work during startup (before that file is parsed),
and does not work during reconfiguration (because the old configuration
is reset shortly before logging that line). Future reconfiguration
support improvements may fix the reset problem. Restrictions do work as
expected for included files (i.e. positive "depth" levels).

Restricting "BCP 177 violation" WARNINGs does not work because the
warnings are printed _before_ Squid configuration is parsed. Future
initialization improvements may fix this.

Also downgraded the importance of a few (re)configuration
progress-reporting messages from level 1 to level 2.
doc/debug-messages.dox
src/AuthReg.cc
src/SquidConfig.h
src/adaptation/icap/ServiceRep.cc
src/cache_cf.cc
src/cf.data.pre
src/debug/Messages.h
src/ip/tools.cc
src/security/KeyData.cc
src/ssl/support.cc