with automated deployment systems to ensure that RabbitMQ is actually
available.
The pid file may exist, but it can still be empty when $rabbitmq_ctl
is executed. In this case the script would not wait for anything
and produce some weird output on the console.
PR: ports/185962 (follow up)
ERL_LIBS was inherited from the current environment, and it may
contain paths to older versions of amqp_client, which may not be
compatible with the current RabbitMQ management plugin.
As a result, RabbitMQ would not start when the management plugin was
enabled, with this error:
{could_not_start,amqp_client,
{{supervisor_data,{invalid_strategy,simple_one_for_one_terminate}},
{amqp_client,start,[normal,[]]}}}
literal name_enable wherever possible, and ${name}_enable
when it's not, to prepare for the demise of set_rcvar().
In cases where I had to hand-edit unusual instances also
modify formatting slightly to be more uniform (and in
some cases, correct). This includes adding some $FreeBSD$
tags, and most importantly moving rcvar= to right after
name= so it's clear that one is derived from the other.
