summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/rsyslog_conf.html45
1 files changed, 45 insertions, 0 deletions
diff --git a/doc/rsyslog_conf.html b/doc/rsyslog_conf.html
index 2e781201..33742223 100644
--- a/doc/rsyslog_conf.html
+++ b/doc/rsyslog_conf.html
@@ -103,6 +103,25 @@ $FileCreateMode 0644<br>
*.* /var/log/file-with-0644</b></code></p>
<p>As you can see, open modes depend on position in the config file. Note the
first line, which is created with the hardcoded default creation mode.</p>
+<h2>DebugPrintTemplateList</h2>
+<p>Specifies whether or not the template list should be written to the debug
+log. Possible values: on/off. Does not affect operation if debugging is
+disabled.</p>
+<h2>DirCreateMode</h2>
+<p>This is the same as $FileCreateMode, but for directories automatically
+generated.</p>
+<h2>DirGroup</h2>
+<p>Set the group for directories newly created. Please note that this setting
+does not affect the group of directories already existing. The parameter is a
+group name, for which the groupid is obtained by rsyslogd on startup and on
+HUPing. Interim changes to the user mapping are not detected.</p>
+<p><code><b>$DirGroup loggroup</b></code></p>
+<h2>DirOwner</h2>
+<p>Set the file owner for directories newly created. Please note that this
+setting does not affect the owner of directories already existing. The parameter
+is a user name, for which the userid is obtained by rsyslogd on startup and on
+HUPing. Interim changes to the user mapping are not detected.</p>
+<p><code><b>$DirOwner loguser</b></code></p>
<h2>RepeatedMsgReduction</h2>
<p>This directive specifies whether or not repeated messages should be reduced
(this is the &quot;Last line repeated n times&quot; feature). If set to on, repeated messages are reduced. If set to off, every
@@ -166,6 +185,32 @@ on.</p>
<li>turning on this option destroys digital signutures if such exists inside
the message</li>
</ul>
+<h2>FailOnChownFailure</h2>
+<p>This option modifies behaviour of dynaFile creation. If different owners or
+groups are specified for new files or directories and rsyslogd fails to set
+these new owners or groups, it will log an error and NOT write to the file in
+question if that option is set to &quot;on&quot;. If it is set to &quot;off&quot;, the error will be
+ignored and processing continues. Keep in mind, that the files in this case may
+be (in)accessible by people who should not have permission. The default is &quot;on&quot;.</p>
+<p><code><b>$FailOnChownFailure off</b></code></p>
+<h2>FileGroup</h2>
+<p>Set the group for dynaFiles newly created. Please note that this setting does
+not affect the group of files already existing. The parameter is a group name,
+for which the groupid is obtained by rsyslogd on startup and on HUPing. Interim
+changes to the user mapping are not detected.</p>
+<p><code><b>$FileGroup loggroup</b></code></p>
+<h2>FileOwner</h2>
+<p>Set the file owner for dynaFiles newly created. Please note that this setting
+does not affect the owner of files already existing. The parameter is a user
+name, for which the userid is obtained by rsyslogd on startup and on HUPing.
+Interim changes to the user mapping are not detected.</p>
+<p><code><b>$FileOwner loguser</b></code></p>
+<h2>ResetConfigVariables</h2>
+<p>Resets all configuration variables to their default value. Any settings made
+will not be applied to configuration lines following the $ResetConfigVariables.
+This is a good method to make sure no side-effects exists from previous
+directives. This directive has no parameters.</p>
+<p><code><b>$ResetConfigVariables</b></code></p>
<h2>Templates</h2>
<p>Templates are a key feature of rsyslog. They allow to specify any format a user
might want. They are also used for dynamic file name generation. Every output in rsyslog uses templates - this holds true for files,