rabbitmq-server/scripts
Dmitry Mescheryakov 67cdbe3067 Correctly return exit code from stop
Panicking and returning non-success on stop often leads to resource
becoming unmanaged on that node.

Before we called get_status to verify that RabbitMQ is dead. But
sometimes it returns error even though RabbitMQ is not running. There
is no reason to call it - we will just verify that there is no beam
process running.

Related fuel bug - https://bugs.launchpad.net/fuel/+bug/1626933
2016-10-17 19:43:46 +03:00
..
rabbitmq-script-wrapper scripts/rabbitmq-script-wrapper: Moved from rabbitmq-server 2016-09-21 12:32:15 +02:00
rabbitmq-server-ha.ocf Correctly return exit code from stop 2016-10-17 19:43:46 +03:00
rabbitmq-server.ocf scripts: Take package-specific files from rabbitmq-server 2016-09-21 16:25:24 +02:00
travis_test_ocf_ra.sh scripts: Take package-specific files from rabbitmq-server 2016-09-21 16:25:24 +02:00