summaryrefslogtreecommitdiff
path: root/src/rabbit_plugins_main.erl
diff options
context:
space:
mode:
authorTim Watson <watson.timothy@gmail.com>2014-01-12 15:10:59 +0000
committerTim Watson <watson.timothy@gmail.com>2014-01-12 15:10:59 +0000
commit8f6cd45060f3604b78d36799aac27574850ae516 (patch)
treee9bf59860a2a5bf7d03e435841b6c79a513088c8 /src/rabbit_plugins_main.erl
parent5d62fd7c480df4f5ddffde15e2ea32f8f63ece4c (diff)
downloadrabbitmq-server-8f6cd45060f3604b78d36799aac27574850ae516.tar.gz
Refactor - remove unused functions/comments/todos
Diffstat (limited to 'src/rabbit_plugins_main.erl')
-rw-r--r--src/rabbit_plugins_main.erl4
1 files changed, 0 insertions, 4 deletions
diff --git a/src/rabbit_plugins_main.erl b/src/rabbit_plugins_main.erl
index 47ece039..408fc4e1 100644
--- a/src/rabbit_plugins_main.erl
+++ b/src/rabbit_plugins_main.erl
@@ -287,10 +287,6 @@ rpc_call(Node, Mod, Action, Args) ->
case rpc:call(Node, Mod, Action, Args, ?RPC_TIMEOUT) of
{badrpc, nodedown} -> io:format("Plugin configuration has changed.~n");
ok -> io:format("Plugin(s) ~pd.~n", [Action]);
- %% QA question: if we get into a situation where the rpc call fails,
- %% does it make sense to suggest a restart as we do here? The restart
- %% would only succeed if the failure (here) was due to a bug in the
- %% rabbit_plugins:enable/1 code afaict.
Error -> io:format("Unable to ~p plugin(s). "
"Please restart the broker "
"to apply your changes.~nError: ~p~n",