renamed to vm_memory_monitor

2 files changed, 3 insertions, 3 deletions

diff --git a/src/rabbit.erl b/src/rabbit.erl
index 7df187cf..f19facfd 100644
--- a/src/rabbit.erl
+++ b/src/rabbit.erl
@@ -142,7 +142,7 @@ start(normal, []) ->
                 case MemoryWatermark of
                     {ok, false} -> ok;
                     {ok, off} -> ok;
-                    {ok, Float} -> start_child(rabbit_memguard, [Float])
+                    {ok, Float} -> start_child(vm_memory_monitor, [Float])
                 end,
                 
                 ok = rabbit_amqqueue:start(),
diff --git a/src/rabbit_memguard.erl b/src/vm_memory_monitor.erl
index 29e21bdc..2d10f069 100644
--- a/src/rabbit_memguard.erl
+++ b/src/vm_memory_monitor.erl
@@ -43,7 +43,7 @@
 %% causes a side effect of setting the interval on Memsup.
 %% This should rarely be an issue.
 
--module(rabbit_memguard).
+-module(vm_memory_monitor).
 
 -behaviour(gen_server2).
 
@@ -57,7 +57,7 @@
         get_vm_memory_high_watermark/0, set_vm_memory_high_watermark/1]).
 
 
--define(SERVER, rabbit_memguard).
+-define(SERVER, ?MODULE).
 -define(DEFAULT_MEMORY_CHECK_INTERVAL, 1000).
 
 %% For unknown OS, we assume that we have 512 MB of memory, which is pretty