summaryrefslogtreecommitdiff
path: root/libcli/samsync
diff options
context:
space:
mode:
authorStefan Metzmacher <metze@samba.org>2011-08-02 23:05:31 +0200
committerStefan Metzmacher <metze@samba.org>2011-08-09 18:14:38 +0200
commit81e765582bb231a3e182c96777a0eef045095c9a (patch)
treeef866b2baadba9eef827d97ec58e9456d44beb4a /libcli/samsync
parent70c2bbecde434264e0b54279f13159e9991efade (diff)
downloadsamba-81e765582bb231a3e182c96777a0eef045095c9a.tar.gz
samba-81e765582bb231a3e182c96777a0eef045095c9a.tar.bz2
samba-81e765582bb231a3e182c96777a0eef045095c9a.zip
s3:libsmb/cli*: 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 Aug 9 18:14:38 CEST 2011 on sn-devel-104
Diffstat (limited to 'libcli/samsync')
0 files changed, 0 insertions, 0 deletions