From d219b5ee742984ad17f520ca5913840dbe51ff81 Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Mon, 11 Feb 2008 13:01:35 +0000 Subject: doc fixes thanks to Peter Vrabec --- ...sconf1_actionexeconlyifpreviousissuspended.html | 29 ---------------------- ...onf1_actionexeconlywhenpreviousissuspended.html | 29 ++++++++++++++++++++++ doc/rsyslog_conf.html | 2 +- 3 files changed, 30 insertions(+), 30 deletions(-) delete mode 100644 doc/rsconf1_actionexeconlyifpreviousissuspended.html create mode 100644 doc/rsconf1_actionexeconlywhenpreviousissuspended.html (limited to 'doc') diff --git a/doc/rsconf1_actionexeconlyifpreviousissuspended.html b/doc/rsconf1_actionexeconlyifpreviousissuspended.html deleted file mode 100644 index 2568ccfb..00000000 --- a/doc/rsconf1_actionexeconlyifpreviousissuspended.html +++ /dev/null @@ -1,29 +0,0 @@ - - -rsyslog.conf file - - -

$ActionExecOnlyIfPreviousIsSuspended

-

Type: global configuration directive

-

Default: off

-

Description:

-

This directive allows to specify if actions should always be executed ("off," the default) or only if the previous action is suspended ("on"). This directive works hand-in-hand with the multiple actions per selector feature. It can be used, for example, to create rules that automatically switch destination servers or databases to a (set of) backup(s), if the primary server fails. Note that this feature depends on proper implementation of the suspend feature in the output module. All built-in output modules properly support it (most importantly the database write and the syslog message forwarder).

-

This selector processes all messages it receives (*.*). It tries to forward every message to primary-syslog.example.com (via tcp). If it can not reach that server, it tries secondary-1-syslog.example.com, if that fails too, it tries secondary-2-syslog.example.com. If neither of these servers can be connected, the data is stored in /var/log/localbuffer. Please note that the secondaries and the local log buffer are only used if the one before them does not work. So ideally, /var/log/localbuffer will never receive a message. If one of the servers resumes operation, it automatically takes over processing again.

-

We strongly advise not to use repeated line reduction together with ActionExecOnlyIfPreviousIsSuspended. It may lead to "interesting" and undesired results (but you can try it if you like).

-

Sample:

-

*.* @@primary-syslog.example.com -
$ActionExecOnlyIfPreviousIsSuspended on -
& @@secondary-1-syslog.example.com # & is used to have more than one action for -
& @@secondary-2-syslog.example.com # the same selector - the mult-action feature -
& /var/log/localbuffer -
$ActionExecOnlyIfPreviousIsSuspended off # to re-set it for the next selector

- -

[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 diff --git a/doc/rsconf1_actionexeconlywhenpreviousissuspended.html b/doc/rsconf1_actionexeconlywhenpreviousissuspended.html new file mode 100644 index 00000000..3f18e243 --- /dev/null +++ b/doc/rsconf1_actionexeconlywhenpreviousissuspended.html @@ -0,0 +1,29 @@ + + +rsyslog.conf file + + +

$ActionExecOnlyWhenPreviousIsSuspended

+

Type: global configuration directive

+

Default: off

+

Description:

+

This directive allows to specify if actions should always be executed ("off," the default) or only if the previous action is suspended ("on"). This directive works hand-in-hand with the multiple actions per selector feature. It can be used, for example, to create rules that automatically switch destination servers or databases to a (set of) backup(s), if the primary server fails. Note that this feature depends on proper implementation of the suspend feature in the output module. All built-in output modules properly support it (most importantly the database write and the syslog message forwarder).

+

This selector processes all messages it receives (*.*). It tries to forward every message to primary-syslog.example.com (via tcp). If it can not reach that server, it tries secondary-1-syslog.example.com, if that fails too, it tries secondary-2-syslog.example.com. If neither of these servers can be connected, the data is stored in /var/log/localbuffer. Please note that the secondaries and the local log buffer are only used if the one before them does not work. So ideally, /var/log/localbuffer will never receive a message. If one of the servers resumes operation, it automatically takes over processing again.

+

We strongly advise not to use repeated line reduction together with ActionExecOnlyIfPreviousIsSuspended. It may lead to "interesting" and undesired results (but you can try it if you like).

+

Sample:

+

*.* @@primary-syslog.example.com +
$ActionExecOnlyIfPreviousIsSuspended on +
& @@secondary-1-syslog.example.com # & is used to have more than one action for +
& @@secondary-2-syslog.example.com # the same selector - the mult-action feature +
& /var/log/localbuffer +
$ActionExecOnlyIfPreviousIsSuspended off # to re-set it for the next selector

+ +

[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 diff --git a/doc/rsyslog_conf.html b/doc/rsyslog_conf.html index f2b2f6ba..63f92d6e 100644 --- a/doc/rsyslog_conf.html +++ b/doc/rsyslog_conf.html @@ -33,7 +33,7 @@ development and quite unstable...). So you have been warned ;)

- many parameter settings modify queue parameters. If in doubt, use the default, it is usually well-chosen and applicable in most cases.