summaryrefslogtreecommitdiff
path: root/buildtools/wafsamba/samba3.py
diff options
context:
space:
mode:
authorStefan Metzmacher <metze@samba.org>2011-09-13 13:12:09 +0200
committerStefan Metzmacher <metze@samba.org>2011-09-13 14:52:35 +0200
commit924b2d5b7fdfc562765ffe7181ffb479bb05ae84 (patch)
tree3af4f124cde12033f85b7d7c017db8b41c1332c2 /buildtools/wafsamba/samba3.py
parenta4548efe675881ce745368f1e8dc7649a2bba8e2 (diff)
downloadsamba-924b2d5b7fdfc562765ffe7181ffb479bb05ae84.tar.gz
samba-924b2d5b7fdfc562765ffe7181ffb479bb05ae84.tar.bz2
samba-924b2d5b7fdfc562765ffe7181ffb479bb05ae84.zip
s3:torture: use CLI_BUFFER_SIZE instead of cli->max_xmit
The max_data parameter of trans2/nttrans calls are not bound to cli->max_xmit. Even with cli->max_xmit, which means the max size of the whole SMB pdu, we would get fragmented trans2/nttrans replies. That's why we can also use our maximum, which is CLI_BUFFER_SIZE. metze Autobuild-User: Stefan Metzmacher <metze@samba.org> Autobuild-Date: Tue Sep 13 14:52:35 CEST 2011 on sn-devel-104
Diffstat (limited to 'buildtools/wafsamba/samba3.py')
0 files changed, 0 insertions, 0 deletions