blob: ae191df60ce65ba6a168bd718ac6c1234707d1fe (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
|
RFC3195D(8) Linux System Administration RFC3195D(8)
NAME
rfc3195d - RFC 3195 listener
SYNOPSIS
rfc3195d [ -d ] [ -p socket ] [ -r port ] [ -v ]
DESCRIPTION
Rfc3195d is a utility for receiving syslog messages via RFC 3195. Both RAW and COOKED pro-
files are supported (but COOKED only without relay-specific PATH elements). rfc3195d ac-
cepts 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, be-
cause it has special handling for the messages 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. Documentation is also very sparse. The situ-
ation 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 specified, /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 ALSO
rsyslog.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 protocol handling.
Rainer Gerhards <rgerhards@adiscon.com>
Version 3.14.0 02 April 2008 RFC3195D(8)
|
