From bc7d4087b2299bf7ee627e314c46ccaa0169b673 Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Fri, 28 Mar 2008 11:18:42 +0000 Subject: added build-in templates --- doc/rsyslog_conf.html | 23 +++++++++++++++++++++-- 1 file changed, 21 insertions(+), 2 deletions(-) (limited to 'doc/rsyslog_conf.html') diff --git a/doc/rsyslog_conf.html b/doc/rsyslog_conf.html index 80c87233..5931a241 100644 --- a/doc/rsyslog_conf.html +++ b/doc/rsyslog_conf.html @@ -293,7 +293,7 @@ $template TraditionalFormat,%timegenerated% %HOSTNAME%
Properties can be accessed by the property replacer (see there for details).

-

Please note that as of 1.15.0, templates can also by +

Please note that templates can also by used to generate selector lines with dynamic file names. For example, if you would like to split syslog messages from different hosts to different files (one per host), you can define the following @@ -302,7 +302,26 @@ template:

DynFile,"/var/log/system-%HOSTNAME%.log"

This template can then be used when defining an output selector line. It will result in something like -"/var/log/system-localhost.log"

+"/var/log/system-localhost.log"

Template +names beginning with "RSYSLOG_" are reserved for rsyslog use. Do NOT +use them if, otherwise you may receive a conflict in the future (and +quite unpredictable behaviour). There is a small set of pre-defined +templates that you can use without the need to define it:

Output Channels

Output Channels are a new concept first introduced in rsyslog 0.9.0. As of this writing, it is most likely that they will -- cgit