From 182c2cafceef701cfcd79e2a7994faa9fc5d4672 Mon Sep 17 00:00:00 2001
From: Rainer Gerhards
Currently, queues are used for the main message queue and for the actions.
@@ -304,7 +306,20 @@ message queue.There are multiple action queues, one for each configured action. By default, these queues operate in direct (non-queueing) mode. Action queues are fully configurable and thus can be changed to whatever is best for the given use case.
-Future versions of rsyslog will utilize queues at other places, too.
+Future versions of rsyslog will most probably utilize queues at other places, +too.
+Whereever "<object>" was used above in the config file +statements, substitute "<object>" with either "MainMsg" or "Action". The +former will set main message queue paremeters, the later parameters for the next +action that will be created. Action queue parameters can not be modified once +the action has been specified. For example, to tell the main message queue to +save its content on shutdown, use $MainMsgQueueSaveOnShutdown on".
+If the same parameter is specified multiple times before a queue is created, +the last one specified takes precedence. The main message queue is created after +parsing the config file and all of its potential includes. An action queue is +created each time an action selector is specified. Action queue parameters are +reset to default after an action queue has been created (to provide a clean +environment for the next action).
Not all queues necessarily support the full set of queue configuration parameters, because not all are applicable. For example, in current output module design, actions do not support multi-threading. Consequently, the number -- cgit