From b88b98d07e91cbf1ab7642f544c20ed0f2447603 Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Mon, 31 Mar 2008 08:56:08 +0000 Subject: fixed typo in directive name (ouch...) --- doc/queues.html | 4 ++-- 1 file 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).

-

iQueue Modes

+

Queue Modes

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 "$<object>QueueType" @@ -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.

It, however, does not make sense to have too many worker threads running in -parall. Thus, the upper limit ca be set via "$<object>QueueMaxWorkerThreads". +parall. Thus, the upper limit ca be set via "$<object>QueueWorkerThreads". If it, for example, is set to four, no more than four workers will ever be started, no matter how many elements are enqueued.

Worker threads that have been started are kept running until an inactivity -- cgit