r23783: Processing the UAS change message was causing problems on ppc64 Linux

systems. Rather than trying to fix this, it's much better just to
remove the code, as it serves no purpose at all (the message that is
generated is ignored by smbd).

This sort of parsing should really be done by PIDL generated code.
(This used to be commit 22e8404cef4961f7468a9f24e23024c827233b84)

1 files changed, 0 insertions, 23 deletions

diff --git a/source3/smbd/server.c b/source3/smbd/server.c
index 5f19f865be..61e79b75cc 100644
--- a/source3/smbd/server.c
+++ b/source3/smbd/server.c
@@ -166,27 +166,6 @@ static void msg_sam_sync(struct messaging_context *msg,
         DEBUG(10, ("** sam sync message received, ignoring\n"));
 }
 
-/****************************************************************************
- Process a sam sync replicate message - not sure whether to do this here or
- somewhere else.
-****************************************************************************/
-
-static void msg_sam_repl(struct messaging_context *msg,
-			 void *private_data,
-			 uint32_t msg_type,
-			 struct server_id server_id,
-			 DATA_BLOB *data)
-{
-        uint32 low_serial;
-
-        if (data->length != sizeof(low_serial))
-                return;
-
-        low_serial = *((uint32 *)data->data);
-
-        DEBUG(3, ("received sam replication message, serial = 0x%04x\n",
-                  low_serial));
-}
 
 /****************************************************************************
  Open the socket communication - inetd.
@@ -376,8 +355,6 @@ static BOOL open_sockets_smbd(enum smb_server_mode server_mode, const char *smb_
 	messaging_register(smbd_messaging_context(), NULL,
 			   MSG_SMB_SAM_SYNC, msg_sam_sync);
 	messaging_register(smbd_messaging_context(), NULL,
-			   MSG_SMB_SAM_REPL, msg_sam_repl);
-	messaging_register(smbd_messaging_context(), NULL,
 			   MSG_SHUTDOWN, msg_exit_server);
 	messaging_register(smbd_messaging_context(), NULL,
 			   MSG_SMB_FILE_RENAME, msg_file_was_renamed);