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

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

018e0b
 
018e0b
+
018e0b
+

deleteStateOnFileMove

018e0b
+
018e0b
+
018e0b
+type
018e0b
+default
018e0b
+mandatory
018e0b
+obsolete legacy directive
018e0b
+
018e0b
+
018e0b
+
018e0b
+binary
018e0b
+off
018e0b
+no
018e0b
+none
018e0b
+
018e0b
+
018e0b
+
018e0b
+

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.

018e0b
+
018e0b
+

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.

018e0b
+
018e0b
 
018e0b
 
018e0b
 

Input Parameters

018e0b
@@ -1214,6 +1236,7 @@ and Others.

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

      018e0b
           
      018e0b
           
      018e0b
         </body>
      018e0b
      -</html>
      018e0b
      \ No newline at end of file
      018e0b
      +</html>