【原創】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