【原创】rabbitmq-server用户手册（翻译）

      为了方便工做中使用，周末抽空对rabbitmq-server用户手册进行了翻译，鉴于本身水平有限，翻译中不免有纰漏产生，若是疑问，欢迎指出探讨。

官方原文：http://www.rabbitmq.com/man/rabbitmq-server.1.man.html

================= 我是分割线 ==================

经过 http://www.rabbitmq.com/manpages.html 可知 RabbitMQ 有5个 General Command ：

1. rabbitmqctl
2. rabbitmq-plugins
3. rabbitmq-server
4. rabbitmq-service
5. rabbitmq-echopid

若要对 server 进行高级配置，则须要参考 administrator's guide（http://www.rabbitmq.com/admin-guide.html）

命令名
rabbitmq-server — 启动 RabbitMQ AMQP server

概要
rabbitmq-server [-detached]

描述
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.（翻译略）

前台运行 rabbitmq-server 将会显示一个兔子标志，以及按照启动序列给出的加载过程的输出，并以“broker running”做为结尾打印，代表 RabbitMQ broker 已经成功的启动了。若是想要停掉当前的 server ，只须要终止进程或者使用 rabbitmqctl 命令进行操做。

环境变量

RABBITMQ_MNESIA_BASE
默认指向 /var/lib/rabbitmq/mnesia ，更改该环境变量能够使您存放 Mnesia 数据库文件到但愿的位置。

RABBITMQ_LOG_BASE
默认指向 /var/log/rabbitmq ，server 产生的 log 文件将存放于该目录。

RABBITMQ_NODENAME
默认指向 rabbit，当你打算在单台物理机上运行多于 1 个 node 时该环境变量有用 - RABBITMQ_NODENAME 在每个 erlang-node-and-machine 搭配中应该是惟一的。 参见 clustering on a single machine 中的具体说明。

RABBITMQ_NODE_IP_ADDRESS
默认状况 RabbitMQ 将绑定到所有 interface (IPv4 和 IPv6，若是存在的话) 上。经过设置该环境变量能够让您只绑定到一个网络 interface 或者 address family 上。

RABBITMQ_NODE_PORT
默认为 5672。

选项
-detached
后台启动 server 进程

For example:

# rabbitmq-server -detached

运行 RabbitMQ AMQP server 于后台。

================= 我是分割线 ==================

E:\Program Files\RabbitMQ Server\rabbitmq_server-2.8.7\sbin>rabbitmq-server.bat
Activating RabbitMQ plugins ...
0 plugins activated:


+---+   +---+
|   |   |   |
|   |   |   |
|   |   |   |
|   +---+   +-------+
|                   |
| RabbitMQ  +---+   |
|           |   |   |
|   v2.8.7  +---+   |
|                   |
+-------------------+
AMQP 0-9-1 / 0-9 / 0-8
Copyright (C) 2007-2012 VMware, Inc.
Licensed under the MPL.  See http://www.rabbitmq.com/

node           : rabbit@SUNFEI
app descriptor : e:/Program Files/RabbitMQ Server/rabbitmq_server-2.8.7/sbin/../ebin/rabbit.app
home dir       : C:\Documents and Settings\sunfei
config file(s) : (none)
cookie hash    : SjAetukIbWXBgKcToETEYQ==
log            : C:/Documents and Settings/sunfei/Application Data/RabbitMQ/log/rabbit@SUNFEI.log
sasl log       : C:/Documents and Settings/sunfei/Application Data/RabbitMQ/log/rabbit@SUNFEI-sasl.log
database dir   : c:/Documents and Settings/sunfei/Application Data/RabbitMQ/db/rabbit@SUNFEI-mnesia
erlang version : 5.9.2

-- rabbit boot start
starting file handle cache server                                     ...done
starting worker pool                                                  ...done
starting database                                                     ...done
starting database sync                                                ...done
starting codec correctness check                                      ...done
-- external infrastructure ready
starting plugin registry                                              ...done
starting auth mechanism cr-demo                                       ...done
starting auth mechanism amqplain                                      ...done
starting auth mechanism plain                                         ...done
starting statistics event manager                                     ...done
starting logging server                                               ...done
starting exchange type direct                                         ...done
starting exchange type fanout                                         ...done
starting exchange type headers                                        ...done
starting exchange type topic                                          ...done
-- kernel ready
starting alarm handler                                                ...done
starting node monitor                                                 ...done
starting cluster delegate                                             ...done
starting guid generator                                               ...done
starting memory monitor                                               ...done
-- core initialized
starting empty DB check                                               ...done
starting exchange, queue and binding recovery                         ...done
starting mirror queue slave sup                                       ...done
starting adding mirrors to queues                                     ...done
-- message delivery logic ready
starting error log relay                                              ...done
starting networking                                                   ...done
starting direct client                                                ...done
starting notify cluster nodes                                         ...done

broker running