RSYSLOGD(8) Linux System Administration RSYSLOGD(8)NAMErfc3195d - RFC 3195 listener
SYNOPSISrfc3195d [ -d ] [ -p socket ] [ -r port ] [ -v ]
DESCRIPTION
Rfc3195d is a utility for receiving syslog messages via RFC 3195. Both
RAW and COOKED profiles are supported (but COOKED only without relay-
specific PATH elements). rfc3195d accepts messages via RFC 3195 and
forwards them to the local domain socket specified in the -p option
(/dev/log3195 by default). There, the messages can be picked up by the
system syslogd. While rfc3195d can work with any syslogd, we highly
recommend using rsyslogd, because it has special handling for the mes‐
sages forwarded by rfc3195d. To enable message reception in rsyslogd,
use the "-a :/dev/log3195" command line option (the colon in front of
the socket name tells rsyslogd that the messages contain hostnames -
this is vital to get the right sender name into your logs).
Rfc3195d currently has very limited functionality. Most importantly, it
does not allow to limit the senders it receives messages from. Docu‐
mentation is also very sparse. The situation should improve over time
as the rsyslog project is continously being enhanced.
OPTIONS-p socket
The socket the received messages are to be sent to. If not spec‐
ified, /dev/log3195 is used.
-r port
The listen port to use. If not specified, IANA-assigned port 601
is used.
-d Turns on debug mode. In it, rfc3195d spits out diagnostic
information to stdout.
-v Print version and exit.
SIGNALS
Rfc3195d reacts to a set of signals.
SIGTERM
Rfc3195d terminates.
SIGUSR1
Rfc3195d terminates.
SEE ALSOrsyslog.conf(5), rsyslogd(8)MORE INFORMATION
Is available on the project home page at http://www.rsyslog.com
COLLABORATORS
Rfc3195d uses liblogging (http://www.liblogging.org) for RFC 3195 pro‐
tocol handling.
Rainer Gerhards <rgerhards@adiscon.com>
Version 2.0.2 12 February 2008 RSYSLOGD(8)
