From d471e71adabdad4fba8b59c4017a1c5f1f111073 Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Fri, 7 Mar 2008 16:34:51 +0000 Subject: fixed potential infinite loop condition when module load failed on startup --- doc/rsyslog_conf.html | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) (limited to 'doc/rsyslog_conf.html') diff --git a/doc/rsyslog_conf.html b/doc/rsyslog_conf.html index 11f80a2d..03b15c17 100644 --- a/doc/rsyslog_conf.html +++ b/doc/rsyslog_conf.html @@ -505,7 +505,7 @@ once they are implemented, it can make very much sense regex -Compares the property against the provided regular +Compares the property against the provided POSIX regular expression. @@ -547,7 +547,11 @@ code), this can be done easily by:

This filter will match when the message contains the string "ID-4711". Please note that the comparison is case-sensitive, so it would not match if "id-4711" would be contained in the message.

-

Getting property-based filters right can sometimes be +

:msg, regex, "fatal .* error"

+

This filter uses a POSIX regular expression. It matches when the +string contains the words "fatal" and "error" with anything in between +(e.g. "fatal net error" and "fatal lib error" but not "fatal error" as +two spaces are required by the regular expression!).

Getting property-based filters right can sometimes be challenging. In order to help you do it with as minimal effort as possible, rsyslogd spits out debug information for all property-based filters during their evaluation. To enable this, run rsyslogd in -- cgit