summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRainer Gerhards <rgerhards@adiscon.com>2008-03-31 08:56:08 +0000
committerRainer Gerhards <rgerhards@adiscon.com>2008-03-31 08:56:08 +0000
commitb88b98d07e91cbf1ab7642f544c20ed0f2447603 (patch)
treed12e0c230f2b55c27a22cb5ef68e6ee09489bc4f
parentaf1b9c5140e0258d4576568968337cc77b016cd7 (diff)
downloadrsyslog-b88b98d07e91cbf1ab7642f544c20ed0f2447603.tar.gz
rsyslog-b88b98d07e91cbf1ab7642f544c20ed0f2447603.tar.xz
rsyslog-b88b98d07e91cbf1ab7642f544c20ed0f2447603.zip
fixed typo in directive name (ouch...)
-rw-r--r--doc/queues.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/queues.html b/doc/queues.html
index 2498da1b..80641d8c 100644
--- a/doc/queues.html
+++ b/doc/queues.html
@@ -16,7 +16,7 @@ rule processor, which then evaluates which actions are to be carried out. In
front of each action, there is also a queue, which potentially de-couples the
filter processing from the actual action (e.g. writing to file, database or
forwarding to another host).</p>
-<h1>iQueue Modes</h1>
+<h1>Queue Modes</h1>
<p>Rsyslog supports different queue modes, some with submodes. Each of them has
specific advantages and disadvantages. Selecting the right queue mode is quite
important when tuning rsyslogd. The queue mode (aka "type") is set via the "<i>$&lt;object&gt;QueueType</i>"
@@ -215,7 +215,7 @@ a new worker thread is automatically started. Similarily, a third worker will be
started when there are at least 300 messages, a forth when reaching 400 and so
on.</p>
<p>It, however, does not make sense to have too many worker threads running in
-parall. Thus, the upper limit ca be set via "<i>$&lt;object&gt;QueueMaxWorkerThreads</i>".
+parall. Thus, the upper limit ca be set via "<i>$&lt;object&gt;QueueWorkerThreads</i>".
If it, for example, is set to four, no more than four workers will ever be
started, no matter how many elements are enqueued. </p>
<p>Worker threads that have been started are kept running until an inactivity