Blame SOURCES/rsyslog-8.2102.0-rhbz1909639-statefiles-doc.patch

537b07
diff -up rsyslog-8.2102.0/doc/configuration/modules/imfile.html.state-file-leaking-doc rsyslog-8.2102.0/doc/configuration/modules/imfile.html
537b07
--- rsyslog-8.2102.0/doc/configuration/modules/imfile.html.state-file-leaking-doc	2021-02-15 12:53:31.000000000 +0100
537b07
+++ rsyslog-8.2102.0/doc/configuration/modules/imfile.html	2022-03-29 10:35:07.187827004 +0200
537b07
@@ -294,6 +294,28 @@ rsyslog needs write permissions to work
537b07
 also might require SELinux definitions (or similar for other enhanced security
537b07
 systems).

537b07
 
537b07
+
537b07
+

deleteStateOnFileMove

537b07
+
537b07
+
537b07
+type
537b07
+default
537b07
+mandatory
537b07
+obsolete legacy directive
537b07
+
537b07
+
537b07
+
537b07
+binary
537b07
+off
537b07
+no
537b07
+none
537b07
+
537b07
+
537b07
+
537b07
+

This parameter controls if state files are deleted if their associated main file is rotated via move. Usually, this is a good idea, because otherwise state files are not deleted when log rotation occurs.

537b07
+
537b07
+

However, there is one situation where not deleting associated state file after log rotation makes sense: this is the case if a monitored file is later moved back to the same location as it was before.

537b07
+
537b07
 
537b07
 
537b07
 

Input Parameters

537b07
@@ -1214,6 +1236,7 @@ and Others.

537b07
 
  • sortFiles
  • 537b07
     
  • PollingInterval
  • 537b07
     
  • statefile.directory
  • 537b07
    +
  • deleteStateOnFileMove
  • 537b07
     
    537b07
     
    537b07
     
  • Input Parameters
    • 537b07
      @@ -1311,4 +1334,4 @@ and Others.

      537b07
           
      537b07
           
      537b07
         </body>
      537b07
      -</html>
      537b07
      \ No newline at end of file
      537b07
      +</html>