summaryrefslogtreecommitdiff
path: root/VERSION
diff options
context:
space:
mode:
authorStefan Metzmacher <metze@samba.org>2011-08-02 22:59:54 +0200
committerStefan Metzmacher <metze@samba.org>2011-08-09 15:30:04 +0200
commit70c2bbecde434264e0b54279f13159e9991efade (patch)
treef01a9018a7114d51192fc327d84d06e419291f7b /VERSION
parent46eacae8b516c0a2b9c372af0baadc436f64d957 (diff)
downloadsamba-70c2bbecde434264e0b54279f13159e9991efade.tar.gz
samba-70c2bbecde434264e0b54279f13159e9991efade.tar.bz2
samba-70c2bbecde434264e0b54279f13159e9991efade.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
Diffstat (limited to 'VERSION')
0 files changed, 0 insertions, 0 deletions