1
.\" Copyright 2005 Rainer Gerhards and Adiscon for the rsyslog modifications
2
.\" Distributed under the GNU General Public License.
4
.TH RSYSLOGD 8 "03 July 2007" "Version 1.14.2 (devel)" "Linux System Administration"
6
rfc3195d \- RFC 3195 listener
20
is a utility for receiving syslog messages via RFC 3195. Both
21
RAW and COOKED profiles are supported (but COOKED only without
22
relay-specific PATH elements).
23
rfc3195d accepts messages via RFC 3195 and forwards them to
24
the local domain socket specified in the -p option
25
(/dev/log3195 by default). There, the messages can be picked up
26
by the system syslogd. While rfc3195d can work with any syslogd,
27
we highly recommend using
29
because it has special handling
30
for the messages forwarded by rfc3195d. To enable message
33
use the "-a :/dev/log3195" command line
34
option (the colon in front of the socket name tells
36
that the messages contain hostnames - this is vital to get the
37
right sender name into your logs).
40
currently has very limited functionality. Most importantly,
41
it does not allow to limit the senders it receives messages from.
42
Documentation is also very sparse. The situation should improve over
43
time as the rsyslog project is continously being enhanced.
48
The socket the received messages are to be sent to. If not specified,
52
The listen port to use. If not specified, IANA-assigned port 601 is used.
55
Turns on debug mode. In it, rfc3195d spits out diagnostic information
59
Print version and exit.
62
reacts to a set of signals.
77
Is available on the project home page at http://www.rsyslog.com
80
Rfc3195d uses liblogging (http://www.liblogging.org) for RFC 3195
84
Rainer Gerhards <rgerhards@adiscon.com>
added
removed
rfc3195d.8
