Remove duplicate "tallocdump" message from tdb messaging system. The

same functionality exists as "pool-usage".

Move initialisation of this and dmalloc messages inside message_init().
(This used to be commit af6ecafcbbf65dbedc49b3a86da39ce608bdadac)

1 files changed, 0 insertions, 23 deletions

diff --git a/source3/smbd/server.c b/source3/smbd/server.c
index ae587ea251..8ce20c87a4 100644
--- a/source3/smbd/server.c
+++ b/source3/smbd/server.c
@@ -501,25 +501,6 @@ BOOL reload_services(BOOL test)
 	return(ret);
 }
 
-/*******************************************************************
- Print out all talloc memory info.
-********************************************************************/
-
-void return_all_talloc_info(int msg_type, pid_t src_pid, void *buf, size_t len)
-{
-	TALLOC_CTX *ctx = talloc_init("info context");
-	char *info = NULL;
-
-	if (!ctx)
-		return;
-
-	info = talloc_describe_all(ctx);
-	if (info)
-		DEBUG(10,(info));
-	message_send_pid(src_pid, MSG_TALLOC_USAGE, info, info ? strlen(info) + 1 : 0, True);
-	talloc_destroy(ctx);
-}
-
 #if DUMP_CORE
 /*******************************************************************
 prepare to dump a core file - carefully!
@@ -821,10 +802,6 @@ static BOOL init_structs(void )
 	if (!message_init())
 		exit(1);
 
-	register_msg_pool_usage();
-	register_dmalloc_msgs();
-	message_register(MSG_REQ_TALLOC_USAGE, return_all_talloc_info);
-
 	if (!print_backend_init())
 		exit(1);