mirror of
https://github.com/rsyslog/rsyslog.git
synced 2025-12-15 10:30:40 +01:00
b7e18513fd
root cause seems to be that SIGTERM is delivered differently under FreeBSD. This causes the main thread to not be awaken, and so it takes until the next janitor interval to come back to life - which can be far too long. Fixed this bug explicitley awaking the main thread. also * re-enable test that did not work because of this * fix invalid message on SIGTERM in debug log
18 lines
588 B
Bash
Executable File
18 lines
588 B
Bash
Executable File
#!/bin/bash
|
|
# check that info-severity messages are actually emitted; we use
|
|
# lookup table as a simple sample to get such a message.
|
|
# addd 2019-05-07 by RGerhards, released under ASL 2.0
|
|
. ${srcdir:=.}/diag.sh init
|
|
generate_conf
|
|
add_conf '
|
|
global(internalmsg.severity="info")
|
|
lookup_table(name="xlate" file="'$RSYSLOG_DYNNAME'.xlate.lkp_tbl" reloadOnHUP="on")
|
|
action(type="omfile" file="'$RSYSLOG_OUT_LOG'")
|
|
'
|
|
cp -f $srcdir/testsuites/xlate.lkp_tbl $RSYSLOG_DYNNAME.xlate.lkp_tbl
|
|
startup
|
|
shutdown_when_empty
|
|
wait_shutdown
|
|
content_check "lookup table 'xlate' loaded from file"
|
|
exit_test
|