Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

rabbitmq-server(1) [debian man page]

RABBITMQ-SERVER(1)						  RabbitMQ Server						RABBITMQ-SERVER(1)

NAME
rabbitmq-server - start RabbitMQ AMQP server SYNOPSIS
rabbitmq-server [-detached] DESCRIPTION
RabbitMQ is an implementation of AMQP, the emerging standard for high performance enterprise messaging. The RabbitMQ server is a robust and scalable implementation of an AMQP broker. Running rabbitmq-server in the foreground displays a banner message, and reports on progress in the startup sequence, concluding with the message "broker running", indicating that the RabbitMQ broker has been started successfully. To shut down the server, just terminate the process or use rabbitmqctl(1). ENVIRONMENT
RABBITMQ_MNESIA_BASE Defaults to /var/lib/rabbitmq/mnesia. Set this to the directory where Mnesia database files should be placed. RABBITMQ_LOG_BASE Defaults to /var/log/rabbitmq. Log files generated by the server will be placed in this directory. RABBITMQ_NODENAME Defaults to rabbit. This can be useful if you want to run more than one node per machine - RABBITMQ_NODENAME should be unique per erlang-node-and-machine combination. See the clustering on a single machine guide[1] for details. RABBITMQ_NODE_IP_ADDRESS By default RabbitMQ will bind to all interfaces, on IPv4 and IPv6 if available. Set this if you only want to bind to one network interface or address family. RABBITMQ_NODE_PORT Defaults to 5672. OPTIONS
-detached start the server process in the background SEE ALSO
rabbitmq-env.conf(5) rabbitmqctl(1) EXAMPLES
rabbitmq-server -detached Runs RabbitMQ AMQP server in the background. AUTHOR
The RabbitMQ Team <info@rabbitmq.com> NOTES
1. clustering on a single machine guide http://www.rabbitmq.com/clustering.html#single-machine RabbitMQ Server 06/22/2012 RABBITMQ-SERVER(1)

Check Out this Related Man Page

RABBITMQ-ENV.CONF(5)						  RabbitMQ Server					      RABBITMQ-ENV.CONF(5)

NAME
rabbitmq-env.conf - default settings for RabbitMQ AMQP server DESCRIPTION
/etc/rabbitmq/rabbitmq-env.conf contains variable settings that override the defaults built in to the RabbitMQ startup scripts. The file is interpreted by the system shell, and so should consist of a sequence of shell environment variable definitions. Normal shell syntax is permitted (since the file is sourced using the shell "." operator), including line comments starting with "#". In order of preference, the startup scripts get their values from the environment, from /etc/rabbitmq/rabbitmq-env.conf and finally from the built-in default values. For example, for the RABBITMQ_NODENAME setting, RABBITMQ_NODENAME from the environment is checked first. If it is absent or equal to the empty string, then NODENAME from /etc/rabbitmq/rabbitmq-env.conf is checked. If it is also absent or set equal to the empty string then the default value from the startup script is used. The variable names in /etc/rabbitmq/rabbitmq-env.conf are always equal to the environment variable names, with the RABBITMQ_ prefix removed: RABBITMQ_NODE_PORT from the environment becomes NODE_PORT in the /etc/rabbitmq/rabbitmq-env.conf file, etc. # I am a complete /etc/rabbitmq/rabbitmq-env.conf file. # Comment lines start with a hash character. # This is a /bin/sh script file - use ordinary envt var syntax NODENAME=hare SEE ALSO
rabbitmq-server(1) rabbitmqctl(1) EXAMPLES
# I am a complete /etc/rabbitmq/rabbitmq-env.conf file. # Comment lines start with a hash character. # This is a /bin/sh script file - use ordinary envt var syntax NODENAME=hare This is an example of a complete /etc/rabbitmq/rabbitmq-env.conf file that overrides the default Erlang node name from "rabbit" to "hare". AUTHOR
The RabbitMQ Team <info@rabbitmq.com> RabbitMQ Server 06/22/2012 RABBITMQ-ENV.CONF(5)
Man Page