From 2f94256e2f9759484826cf338ca32669cf8764e0 Mon Sep 17 00:00:00 2001 From: Rainer Gerhards Date: Wed, 20 Jul 2005 16:52:01 +0000 Subject: rsyslogd improved startup message, doc updates to reflect changes --- sample.conf | 23 ++++++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-) (limited to 'sample.conf') diff --git a/sample.conf b/sample.conf index d24a821d..c6353bec 100644 --- a/sample.conf +++ b/sample.conf @@ -186,6 +186,27 @@ $template dbFormat,"insert into SystemEvents (Message, Facility,FromHost, Priori # And this one uses the template defined above: *.* >hostname,dbname,userid,password;dbFormat + +# +# Rsyslog supports TCP-based syslog. To enable receiving TCP messages, +# use the -t command line option (where port is the port it +# shall listen to. To forward messages to the remote host, you must +# specify a forwarding action and include the host and port. TCP +# and UDP-based forwarding has basically the same syntax, except that +# TCP delivery is triggered by specifying a second at-sign (@) in the +# message. +# This is UDP forwarding to port 514: +*.* @172.19.2.16 +# This is UDP forwarding to port 1514: +*.* @172.19.2.16:1514 +# This is TCP forwarding to port 1514: +*.* @@172.19.2.16:1514 +# The second @-sign is all you need (except, of course, a tcp-capable +# syslogd like rsyslogd ;)). +# Of course, you can also specify a template with TCP: +*.* @@172.19.2.16:1514;RFC3164Fmt + + # # A final world. rsyslog is considered a part of Adiscon's MonitorWare product line. # As such, you can find current information as well as information on the @@ -196,5 +217,5 @@ $template dbFormat,"insert into SystemEvents (Message, Facility,FromHost, Priori # as a web-based front-end to a syslog message database. # # I hope this work is useful. -# 2005-03-18 Rainer Gerhards +# 2005-07-20 Rainer Gerhards # -- cgit