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

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

6e9fa2
 
6e9fa2
+
6e9fa2
+

deleteStateOnFileMove

6e9fa2
+
6e9fa2
+
6e9fa2
+type
6e9fa2
+default
6e9fa2
+mandatory
6e9fa2
+obsolete legacy directive
6e9fa2
+
6e9fa2
+
6e9fa2
+
6e9fa2
+binary
6e9fa2
+off
6e9fa2
+no
6e9fa2
+none
6e9fa2
+
6e9fa2
+
6e9fa2
+
6e9fa2
+

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.

6e9fa2
+
6e9fa2
+

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.

6e9fa2
+
6e9fa2
 
6e9fa2
 
6e9fa2
 

Input Parameters

6e9fa2
@@ -1214,6 +1236,7 @@ and Others.

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

      6e9fa2
           
      6e9fa2
           
      6e9fa2
         </body>
      6e9fa2
      -</html>
      6e9fa2
      \ No newline at end of file
      6e9fa2
      +</html>