The use of SIGKILL does not guarantee the immediate termination of sub
background task. Using SIGTERM allows the generator to finish cleanly.
Signed-off-by: Jonathan Rajotte <jonathan.rajotte-julien@efficios.com>
Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
test_multi_app ust $generator_pid
test_multi_app ust $generator_pid
- kill -9 $generator_pid 2> /dev/null
+ kill -s SIGTERM $generator_pid 2> /dev/null
wait $generator_pid 2> /dev/null
rm -rf ${TESTAPP_STATE_FILE} 2> /dev/null
}
wait $generator_pid 2> /dev/null
rm -rf ${TESTAPP_STATE_FILE} 2> /dev/null
}
test_multi_app kernel $generator_pid
test_multi_app kernel $generator_pid
- kill -9 $generator_pid 2>/dev/null
+ kill -s SIGTERM $generator_pid 2> /dev/null
wait $generator_pid 2> /dev/null
rm -rf ${TESTAPP_STATE_FILE} 2> /dev/null
wait $generator_pid 2> /dev/null
rm -rf ${TESTAPP_STATE_FILE} 2> /dev/null
test_on_register_evaluation ust $generator_pid
test_on_register_evaluation ust $generator_pid
- kill -9 $generator_pid 2> /dev/null
+ kill -s SIGTERM $generator_pid 2> /dev/null
wait $generator_pid 2> /dev/null
rm -rf ${TESTAPP_STATE_FILE} 2> /dev/null
wait $generator_pid 2> /dev/null
rm -rf ${TESTAPP_STATE_FILE} 2> /dev/null
test_on_register_evaluation kernel $generator_pid
test_on_register_evaluation kernel $generator_pid
- kill -9 $generator_pid 2> /dev/null
+ kill -s SIGTERM $generator_pid 2> /dev/null
wait $generator_pid 2> /dev/null
rm -rf ${TESTAPP_STATE_FILE} 2> /dev/null
wait $generator_pid 2> /dev/null
rm -rf ${TESTAPP_STATE_FILE} 2> /dev/null
destroy_lttng_session_ok $SESSION_NAME
stop_lttng_sessiond
destroy_lttng_session_ok $SESSION_NAME
stop_lttng_sessiond
+ kill -s SIGTERM $generator_pid 2> /dev/null
wait $generator_pid 2> /dev/null
for pipe in "${consumerd_pipe[@]}"; do
wait $generator_pid 2> /dev/null
for pipe in "${consumerd_pipe[@]}"; do