From 68b8149d1fb26b2fe1138c99d971754b0a30378b Mon Sep 17 00:00:00 2001 From: Stefan Metzmacher Date: Sun, 20 Sep 2009 23:29:11 +0200 Subject: s3:rpc_client: don't randomly fragment rpc pdu's in developer mode This is really confusing and also breaks against windows, as it doesn't accept fragmented bind requests. metze --- source3/rpc_client/cli_pipe.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'source3/rpc_client') diff --git a/source3/rpc_client/cli_pipe.c b/source3/rpc_client/cli_pipe.c index 5392d1f78f..34b8616907 100644 --- a/source3/rpc_client/cli_pipe.c +++ b/source3/rpc_client/cli_pipe.c @@ -1296,7 +1296,7 @@ static struct tevent_req *rpc_api_pipe_send(TALLOC_CTX *mem_ctx, max_recv_frag = cli->max_recv_frag; -#ifdef DEVELOPER +#if 0 max_recv_frag = RPC_HEADER_LEN + 10 + (sys_random() % 32); #endif @@ -2005,7 +2005,7 @@ static uint32 calculate_data_len_tosend(struct rpc_pipe_client *cli, { uint32 data_space, data_len; -#ifdef DEVELOPER +#if 0 if ((data_left > 0) && (sys_random() % 2)) { data_left = MAX(data_left/2, 1); } -- cgit