From cb09cdfc3ea9a50a4c1f4e48cddaac4b55a66c0a Mon Sep 17 00:00:00 2001
From: CentOS Sources
Date: Thu, 14 Apr 2022 16:09:26 +0000
Subject: [PATCH] import rsyslog-8.2102.0-9.el8
---
...-8.2102.0-rhbz1909639-statefiles-doc.patch | 47 +++++
...-8.2102.0-rhbz1909639-statefiles-fix.patch | 162 ++++++++++++++++++
SPECS/rsyslog.spec | 14 +-
3 files changed, 221 insertions(+), 2 deletions(-)
create mode 100644 SOURCES/rsyslog-8.2102.0-rhbz1909639-statefiles-doc.patch
create mode 100644 SOURCES/rsyslog-8.2102.0-rhbz1909639-statefiles-fix.patch
diff --git a/SOURCES/rsyslog-8.2102.0-rhbz1909639-statefiles-doc.patch b/SOURCES/rsyslog-8.2102.0-rhbz1909639-statefiles-doc.patch
new file mode 100644
index 0000000..b717972
--- /dev/null
+++ b/SOURCES/rsyslog-8.2102.0-rhbz1909639-statefiles-doc.patch
@@ -0,0 +1,47 @@
+diff -up rsyslog-8.2102.0/doc/configuration/modules/imfile.html.state-file-leaking-doc rsyslog-8.2102.0/doc/configuration/modules/imfile.html
+--- rsyslog-8.2102.0/doc/configuration/modules/imfile.html.state-file-leaking-doc 2021-02-15 12:53:31.000000000 +0100
++++ rsyslog-8.2102.0/doc/configuration/modules/imfile.html 2022-03-29 10:35:07.187827004 +0200
+@@ -294,6 +294,28 @@ rsyslog needs write permissions to work
+ also might require SELinux definitions (or similar for other enhanced security
+ systems).
+
++
++
deleteStateOnFileMove
++
++
++type |
++default |
++mandatory |
++obsolete legacy directive |
++
++
++
++binary |
++off |
++no |
++none |
++
++
++
++
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.
++
++
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.
++
+
+