diff options
| author | Jean-Sebastien Pedron <jean-sebastien@rabbitmq.com> | 2015-01-29 13:27:40 +0100 |
|---|---|---|
| committer | Jean-Sebastien Pedron <jean-sebastien@rabbitmq.com> | 2015-01-29 13:27:40 +0100 |
| commit | ec851de0e9a9d70620aacef5ad59592fbea75c81 (patch) | |
| tree | 444d86b9a142f89c9fb912c12acab8555be13666 /src | |
| parent | 05d9b5dbda524e492dfcef81ede5006c5d107da6 (diff) | |
| download | rabbitmq-server-git-ec851de0e9a9d70620aacef5ad59592fbea75c81.tar.gz | |
rabbitmq-script-wrapper: Use "exec" to execute the subsequent script
Without this, a new process is spawned to execute the script. This new
process won't receive the signals delivered to the process initially
started.
A user reported this problem with RabbitMQ in Docker: when the service
must be stopped, the SIGTERM doesn't make it to the server which
continues to run.
Diffstat (limited to 'src')
0 files changed, 0 insertions, 0 deletions