Release Notes: document cache_store_log changes in 3.2

Store log uses logFile*() infrastructure and was caught in the access.log
change upgrades (in a good way). But was not documented.

diff --git a/doc/release-notes/release-3.2.sgml b/doc/release-notes/release-3.2.sgml
index 26bfeee8e6f061903908b3affb4481552185fef7..fcb0a576330800618385c185a508bafe68768e13 100644 (file)
--- a/doc/release-notes/release-3.2.sgml
+++ b/doc/release-notes/release-3.2.sgml
@@ -341,7 +341,8 @@ Most user-facing changes are reflected in squid.conf (see below).
   direct filesystem logging (stdio, daemon) to network logging (syslog, UDP and TCP). The daemon logging
   interface allows for a custom helper to be written to process logs in real-time.
 
-<p>Upgrading: the <em>access_log</em> was previously logged via what is now called the <em>stdio</em> module.
+<p>Upgrading: the <em>access_log</em> and <em>cache_store_log</em> were previously logged via what is
+  now called the <em>stdio</em> module.
   This is still supported and used by default if no module is named. For best performance particularly in SMP
   environments we recommend the <em>daemon</em> be used. The provided <em>log_file_daemon</em> helper
   performs the traditional logging to local filesystem.
@@ -353,8 +354,8 @@ Most user-facing changes are reflected in squid.conf (see below).
   logging a single cache.log at relatively high debug levels on a high-traffic system. Or one which is
   required to store a long period of access.log and needs to conserve disk space.
 
-<p>The referer_log and useragent_log directives have been converted to built-in log formats.
-  These logs are now created using an access_log line with the format "referrer" or "useragent".
+<p>The <em>referer_log</em> and <em>useragent_log</em> directives have been converted to built-in log formats.
+  These logs are now created using an <em>access_log</em> line with the format "referrer" or "useragent".
   They also now log all client requests, if there was no Referer or User-Agent header a dash (-) is logged.
 
 <p>Known Issue: The TCP logging module does not recover from broken connections well.
@@ -610,6 +611,10 @@ This section gives a thorough account of those changes in three categories:
        <p><em>htcp-*</em> options collapsed into <em>htcp=</em> taking an optional comma-separated list of flags.
           The old form is deprecated but still accepted.
 
+       <tag>cache_store_log</tag>
+       <p>Now uses logging modules. Example: stdio:/file/path
+          see <em>access_log</em> for a list of supported modules and their parameters.
+
        <tag>clientside_mark</tag>
        <p>New configuration parameter <em>clientside_mark</em>
        <p>Allows packets leaving Squid on the client side to be marked with a Netfilter mark value in the same way as the existing clientside_tos feature.

diff --git a/src/cf.data.pre b/src/cf.data.pre
index 814ae05ea0be8de137c0202fd0f9d45c5813fff6..f640b8d943678e831615c1070bc3abfa7fadf14f 100644 (file)
--- a/src/cf.data.pre
+++ b/src/cf.data.pre
@@ -3642,12 +3642,16 @@ LOC: Config.Log.store
 DOC_START
        Logs the activities of the storage manager.  Shows which
        objects are ejected from the cache, and which objects are
-       saved and for how long.  To disable, enter "none" or remove the line.
+       saved and for how long.
        There are not really utilities to analyze this data, so you can safely
-       disable it.
-
+       disable it (the default).
+       
+       Store log uses modular logging outputs. See access_log for the list
+       of modules supported.
+       
        Example:
-               cache_store_log @DEFAULT_STORE_LOG@
+               cache_store_log stdio:@DEFAULT_STORE_LOG@
+               cache_store_log daemon:@DEFAULT_STORE_LOG@
 DOC_END
 
 NAME: cache_swap_state cache_swap_log