Jimmy Olgeni bfde8c03da Avoid calling "rabbitmqctl status" in a loop to make sure that RabbitMQ is ... started. "rabbitmqctl wait" alone should suffice, and the loop seems to cause some kind of race condition that causes a segfault in the Erlang VM. RabbitMQ would start anyway, but users would get a segmentation fault message on the console. We also wait on daemon(8)'s pid to make sure that restarts are synchronized (i.e. daemon(8) is stopped before starting it again with the same pidfile). PR: 204147 Submitted by: elofu17@hotmail.com		2015-12-30 22:44:36 +00:00
..
patch-scripts_rabbitmq-plugins
patch-scripts_rabbitmq-server
patch-scripts_rabbitmqctl
rabbitmq.in	Avoid calling "rabbitmqctl status" in a loop to make sure that RabbitMQ is	2015-12-30 22:44:36 +00:00