From 10bef02e8f8f6bec4f1c18d9c634aa6927f4611a Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Thu, 13 Sep 2012 09:30:20 +0200 Subject: bugfix: missing support for escape sequences in RainerScript Only \' was supported. Now the usual set is supported. Note that v5 used \x as escape where x was any character (e.g. "\n" meant "n" and NOT LF). This also means there is some incompatibility to v5 for well-know sequences. Better break it now than later. --- doc/v6compatibility.html | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'doc/v6compatibility.html') diff --git a/doc/v6compatibility.html b/doc/v6compatibility.html index 1f830854..c1799974 100644 --- a/doc/v6compatibility.html +++ b/doc/v6compatibility.html @@ -162,6 +162,15 @@ As you see, here you may include spaces between user names. so it is a wise decision to change config files at least to the legacy format (with ":omusrmsg:" in front of the name). +

Escape Sequences in Script-Based Filters

+

In v5, escape sequences were very simplistic. Inside a string, "\x" meant +"x" with x being any character. This has been changed so that the usual set of +escapes is supported, must importantly "\n", "\t", "\xhh" (with hh being hex digits) +and "\ooo" with (o being octal digits). So if one of these sequences was used +previously, results are obviously different. However, that should not create any +real problems, because it is hard to envision why someone should have done that +(why write "\n" when you can also write "n"?). +---------------------------------------------------------------------------

[manual index] [rsyslog site]

This documentation is part of the rsyslog project.
-- cgit