rsyslog.conf file

From 4459faa3799e4804402327e8fc4ea92abc96a0e1 Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Wed, 8 Aug 2007 13:59:43 +0000 Subject: somewhat improved config file doc - thanks to Florian Riedl for doing the bulk of work --- doc/rsconf1_mainmsgqueuesize.html | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 doc/rsconf1_mainmsgqueuesize.html (limited to 'doc/rsconf1_mainmsgqueuesize.html') diff --git a/doc/rsconf1_mainmsgqueuesize.html b/doc/rsconf1_mainmsgqueuesize.html new file mode 100644 index 00000000..b9501e09 --- /dev/null +++ b/doc/rsconf1_mainmsgqueuesize.html @@ -0,0 +1,22 @@ + + +rsyslog.conf file + + +

$MainMsgQueueSize

Type: global configuration directive

Default: 10000

Description:

This allows to specify the maximum size of the message queue. This directive is only available when rsyslogd has been compiled with multithreading support. In this mode, receiver and output modules are de-coupled via an in-memory queue. This queue buffers messages when the output modules are not capable to process them as fast as they are received. Once the queue size is exhausted, messages will be dropped. The slower the output (e.g. MySQL), the larger the queue should be. Buffer space for the actual queue entries is allocated on an as-needed basis. Please keep in mind that a very large queue may exhaust available system memory and swap space. Keep this in mind when configuring the max size. The actual size of a message depends largely on its content and the orginator. As a rule of thumb, typically messages should not take up more then roughtly 1k (this is the memory structure, not what you see in a network dump!). For typical linux messages, 512 bytes should be a good bet. Please also note that there is a minimal amout of memory taken for each queue entry, no matter if it is used or not. This is one pointer value, so on 32bit systems, it should typically be 4 bytes and on 64bit systems it should typically be 8 bytes. For example, the default queue size of 10,000 entries needs roughly 40k fixed overhead on a 32 bit system.

Sample:

$MainMsgQueueSize 100000 # 100,000 may be a value to handle bursty traffic

+ +

[rsyslog.conf overview] [manual +index] [rsyslog site]

This documentation is part of the +rsyslog project.
+Copyright © 2007 by Rainer Gerhards and +Adiscon. Released under the GNU GPL +version 2 or higher.

+ + \ No newline at end of file -- cgit v1.2.3 From 601393acd7fcd4446b57314cb070cfd17abda2ee Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Thu, 18 Oct 2007 16:17:32 +0000 Subject: added doc fixes provided by Michael Biebl - thanks --- doc/rsconf1_mainmsgqueuesize.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/rsconf1_mainmsgqueuesize.html') diff --git a/doc/rsconf1_mainmsgqueuesize.html b/doc/rsconf1_mainmsgqueuesize.html index b9501e09..acf88e94 100644 --- a/doc/rsconf1_mainmsgqueuesize.html +++ b/doc/rsconf1_mainmsgqueuesize.html @@ -7,9 +7,9 @@

Type: global configuration directive

Default: 10000

Description:

This allows to specify the maximum size of the message queue. This directive is only available when rsyslogd has been compiled with multithreading support. In this mode, receiver and output modules are de-coupled via an in-memory queue. This queue buffers messages when the output modules are not capable to process them as fast as they are received. Once the queue size is exhausted, messages will be dropped. The slower the output (e.g. MySQL), the larger the queue should be. Buffer space for the actual queue entries is allocated on an as-needed basis. Please keep in mind that a very large queue may exhaust available system memory and swap space. Keep this in mind when configuring the max size. The actual size of a message depends largely on its content and the originator. As a rule of thumb, typically messages should not take up more then roughly 1k (this is the memory structure, not what you see in a network dump!). For typical linux messages, 512 bytes should be a good bet. Please also note that there is a minimal amount of memory taken for each queue entry, no matter if it is used or not. This is one pointer value, so on 32bit systems, it should typically be 4 bytes and on 64bit systems it should typically be 8 bytes. For example, the default queue size of 10,000 entries needs roughly 40k fixed overhead on a 32 bit system.

Sample:

$MainMsgQueueSize 100000 # 100,000 may be a value to handle bursty traffic

$MainMsgQueueSize 100000 # 100,000 may be a value to handle burst traffic

[rsyslog.conf overview] [manual index] [rsyslog site]

- \ No newline at end of file + -- cgit v1.2.3 From 47bbd838bdaa200d89d8210a6a0ba9c322129bca Mon Sep 17 00:00:00 2001 From: Tom Bergfeld Date: Fri, 31 Oct 2008 14:47:30 +0100 Subject: restructured rsyslog.conf documentation Signed-off-by: Rainer Gerhards --- doc/rsconf1_mainmsgqueuesize.html | 2 ++ 1 file changed, 2 insertions(+) (limited to 'doc/rsconf1_mainmsgqueuesize.html') diff --git a/doc/rsconf1_mainmsgqueuesize.html b/doc/rsconf1_mainmsgqueuesize.html index acf88e94..ffed1c09 100644 --- a/doc/rsconf1_mainmsgqueuesize.html +++ b/doc/rsconf1_mainmsgqueuesize.html @@ -3,6 +3,8 @@ rsyslog.conf file +back +

$MainMsgQueueSize

Type: global configuration directive

Default: 10000

-- cgit v1.2.3