summaryrefslogtreecommitdiff
path: root/Makefile
diff options
context:
space:
mode:
authorFrancesco Mazzoli <francesco@rabbitmq.com>2012-07-11 13:16:22 +0100
committerFrancesco Mazzoli <francesco@rabbitmq.com>2012-07-11 13:16:22 +0100
commitb740677bf32ed4bb92d0373297723ec82cc24afd (patch)
tree3a69bf8cf4e38141cc5fb0ac933dfe4c8a17679f /Makefile
parent95092ed26876699c42118d37fda5222fff137257 (diff)
downloadrabbitmq-server-git-b740677bf32ed4bb92d0373297723ec82cc24afd.tar.gz
let `rabbit_alarm' handle everything in place of `alarm_handler'
No logging on set/clear alarm yet, me and Simon agree that we should do logging only on the events that rabbit knows it should be receiving (right now the resource limits ones)
Diffstat (limited to 'Makefile')
-rw-r--r--Makefile4
1 files changed, 2 insertions, 2 deletions
diff --git a/Makefile b/Makefile
index 0e3960dcfa..3681a7878d 100644
--- a/Makefile
+++ b/Makefile
@@ -217,11 +217,11 @@ stop-rabbit-on-node: all
echo "rabbit:stop()." | $(ERL_CALL)
set-resource-alarm: all
- echo "alarm_handler:set_alarm({{resource_limit, $(SOURCE), node()}, []})." | \
+ echo "rabbit_alarm:set_alarm({{resource_limit, $(SOURCE), node()}, []})." | \
$(ERL_CALL)
clear-resource-alarm: all
- echo "alarm_handler:clear_alarm({resource_limit, $(SOURCE), node()})." | \
+ echo "rabbit_alarm:clear_alarm({resource_limit, $(SOURCE), node()})." | \
$(ERL_CALL)
stop-node: