mirror of
https://github.com/rsyslog/rsyslog.git
synced 2025-12-17 11:40:42 +01:00
87b29734f3
if no parser can handle a message, the message object is leaked. If this happens frequently, a rather large leak exists. see also https://github.com/rsyslog/rsyslog/issues/102
20 lines
597 B
Bash
Executable File
20 lines
597 B
Bash
Executable File
#!/bin/bash
|
|
# add 2017-03-06 by Rainer Gerhards, released under ASL 2.0
|
|
. $srcdir/diag.sh init
|
|
. $srcdir/diag.sh generate-conf
|
|
. $srcdir/diag.sh add-conf '
|
|
module(load="../plugins/imtcp/.libs/imtcp")
|
|
input(type="imtcp" port="13514" ruleset="ruleset")
|
|
ruleset(name="ruleset" parser="rsyslog.rfc5424") {
|
|
action(type="omfile" file="rsyslog2.out.log")
|
|
}
|
|
'
|
|
. $srcdir/diag.sh startup-vg
|
|
. $srcdir/diag.sh tcpflood -m10
|
|
. $srcdir/diag.sh shutdown-when-empty
|
|
. $srcdir/diag.sh wait-shutdown-vg
|
|
# note: we just check the valgrind output, the log file itself does not
|
|
# interest us
|
|
|
|
. $srcdir/diag.sh exit
|