rsyslog/rsyslog
1
0
Fork 0
mirror of https://github.com/rsyslog/rsyslog.git synced 2025-12-20 01:30:42 +01:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1347 from dsahern/man-page

Browse Source 
Update the rsyslog.conf man page for device option
This commit is contained in:
Rainer Gerhards 2017-01-11 09:02:17 +01:00 committed by GitHub
commit c5f2e64bcb
1 changed files with 13 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
tools/rsyslog.conf.5
View File

@ -267,6 +267,19 @@ port defaults to 514. Due to the nature of UDP, you will probably lose some mess
If you expect high traffic volume, you can expect to lose a quite noticeable number of messages
(the higher the traffic, the more likely and severe is message loss).
Sockets for forwarded messages can be bound to a specific device using the "device" option for
the omfwd module.
.B Example:
.RS
action(type="omfwd" Target="192.168.0.1" Device="eth0" Port=514 Protocol="udp")
.RE
.sp
In the example above, messages are forwarded via UDP to the machine 192.168.0.1 at port 514 over
the device eth0. TCP can be used by setting Protocol to "tcp" in the above example.
For Linux with VRF support, the device option is used to specify the VRF to send messages.
.B If you would like to prevent message loss, use RELP:
.RS
*.* :omrelp:192.168.0.1:2514