mirror of
https://github.com/rsyslog/rsyslog.git
synced 2025-12-19 23:10:41 +01:00
31fae7b93d
Note that, as it looks, the directive was already broken in previous v5 versions. So while I solved what looked like a (intentional) regression from the performance tuning, I actually solved a previous regression as well ;) I have also added new test cases to the testbench in order to capture such problems in the future. This version does now look pretty good in shape.
18 lines
808 B
Bash
Executable File
18 lines
808 B
Bash
Executable File
# we test the execonly if previous is suspended directive.
|
|
# This test checks if, within the same rule, one action can be set
|
|
# to emit only if the previous was suspended while the next action
|
|
# always sends data.
|
|
# rgerhards, 2010-06-24
|
|
echo ===============================================================================
|
|
echo \[execonlywhenprevsuspended3.sh\]: test execonly...suspended functionality
|
|
source $srcdir/diag.sh init
|
|
source $srcdir/diag.sh startup execonlywhenprevsuspended3.conf
|
|
source $srcdir/diag.sh injectmsg 0 1000
|
|
source $srcdir/diag.sh shutdown-when-empty # shut down rsyslogd when done processing messages
|
|
source $srcdir/diag.sh wait-shutdown
|
|
echo check file 1
|
|
source $srcdir/diag.sh seq-check 1 999
|
|
echo check file 2
|
|
source $srcdir/diag.sh seq-check2 0 999
|
|
source $srcdir/diag.sh exit
|