Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

rabbitmq-env.conf(5) [debian 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)

Check Out this Related Man Page

AMQP-DECLARE-QUEUE(1)						 RabbitMQ C Client					     AMQP-DECLARE-QUEUE(1)

NAME
amqp-declare-queue - Declare (create or assert the existence of) a queue on an AMQP server SYNOPSIS
amqp-declare-queue [OPTION...] [-d] {-q queue name} DESCRIPTION
amqp-declare-queue attempts to create a queue on an AMQP server, and exits. If the empty-string is supplied as the queue name, a fresh queue name is generated by the server and returned. In all cases, if a queue was successfully declared, the (raw binary) name of the queue is printed to standard output, followed by a newline. OPTIONS
-q, --queue=queue name The name of the queue to declare. If the empty string is supplied, a fresh queue name is generated by the server. -d, --durable Causes the queue to be declared with the "durable" flag set. Durable queues survive server restarts. By default, queues are declared in "transient" mode. EXIT STATUS
If the queue was successfully declared, the exit status is 0. If an error occurs, the exit status is 1. EXAMPLES
Declare the durable queue "myqueue", and display the name of the queue on standard output: $ amqp-declare-queue -d -q myqueue myqueue Declare a fresh, server-named transient queue, and display the name of the queue on standard output (use amqp-delete-queue(1) to delete it from the server once you're done): $ amqp-declare-queue -q "" amq.gen-BW/wvociA8g6LFpb1PlqOA== SEE ALSO
librabbitmq-tools(7) describes connection-related options common to all the RabbitMQ C Client tools. AUTHOR
The RabbitMQ Team <info@rabbitmq.com> RabbitMQ C Client 2011-01-01 AMQP-DECLARE-QUEUE(1)
Man Page