summaryrefslogtreecommitdiffstats
path: root/doc/rsyslog_conf_global.html
diff options
context:
space:
mode:
authorRainer Gerhards <rgerhards@adiscon.com>2010-03-23 07:10:03 +0100
committerRainer Gerhards <rgerhards@adiscon.com>2010-03-23 07:10:03 +0100
commitd2f242edcb25e69ae7de5a142229330070f2e70b (patch)
tree8f25fa8de784c877cda4c17452955234cdc2f95e /doc/rsyslog_conf_global.html
parent396e211e5cfd195b7135947d425b089a0447fa88 (diff)
parent2f1d5a12037453792eb1000c79daf737b41c5ba4 (diff)
downloadrsyslog-d2f242edcb25e69ae7de5a142229330070f2e70b.tar.gz
rsyslog-d2f242edcb25e69ae7de5a142229330070f2e70b.tar.xz
rsyslog-d2f242edcb25e69ae7de5a142229330070f2e70b.zip
Merge branch 'v4-stable' into v4-stable-solaris
Diffstat (limited to 'doc/rsyslog_conf_global.html')
-rw-r--r--doc/rsyslog_conf_global.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/rsyslog_conf_global.html b/doc/rsyslog_conf_global.html
index 50d83a50..e7897f90 100644
--- a/doc/rsyslog_conf_global.html
+++ b/doc/rsyslog_conf_global.html
@@ -211,9 +211,9 @@ supported in order to be compliant to the upcoming new syslog RFC series.
of the output file. The higher the number, the better the compression, but also the
more CPU is required for zipping.</li>
<li><b>$OMFileIOBufferSize</b> &lt;size_nbr&gt;, default 4k, size of the buffer used to writing output data. The larger the buffer, the potentially better performance is. The default of 4k is quite conservative, it is useful to go up to 64k, and 128K if you used gzip compression (then, even higher sizes may make sense)</li>
-<li><b>$OMFileFlushOnTXEnd</b> &lt;[<b>on</b>/off]&gt;, default on. Omfile has the
+<li><b>$OMFileFlushOnTXEnd</b> &lt;[on/<b>off</b>]&gt;, default ff. Omfile has the
capability to
-writes output using a buffered writer. Disk writes are only done when the buffer is
+write output using a buffered writer. Disk writes are only done when the buffer is
full. So if an error happens during that write, data is potentially lost. In cases where
this is unacceptable, set $OMFileFlushOnTXEnd to on. Then, data is written at the end
of each transaction (for pre-v5 this means after <b>each</b> log message) and the usual