summaryrefslogtreecommitdiff
path: root/source4/torture/rpc
diff options
context:
space:
mode:
authorAndrew Tridgell <tridge@samba.org>2005-01-15 10:38:12 +0000
committerGerald (Jerry) Carter <jerry@samba.org>2007-10-10 13:08:50 -0500
commite89fd49df7e63dcf37ee1aa7e2f50965851725c9 (patch)
tree8484d3930707d1e8f97496f5b58ca3c1a8291dba /source4/torture/rpc
parentd327eb01bdc5ae196ece3707510629d95a8857b4 (diff)
downloadsamba-e89fd49df7e63dcf37ee1aa7e2f50965851725c9.tar.gz
samba-e89fd49df7e63dcf37ee1aa7e2f50965851725c9.tar.bz2
samba-e89fd49df7e63dcf37ee1aa7e2f50965851725c9.zip
r4757: added the ability of the clisocket level of libcli to handle async
socket connections. This was complicated by a few factors: - it meant moving the event context from clitransport to clisocket, so lots of structures changed - we need to asynchronously handle connection to lists of port numbers, not just one port number. The code internally tries each port in the list in turn, without ever blocking - the man page on how connect() is supposed to work asynchronously doesn't work in practice (now why doesn't this surprise me?). The getsockopt() for SOL_ERROR is supposed to retrieve the error, but in fact the next (unrelated) connect() call on the same socket also gets an error, though not the right error. To work around this I need to tear down the whole socket between each attempted port. I hate posix. Note that clisocket.c still does a blocking name resolution call in smbcli_sock_connect_byname(). That will be fixed when we add the async NBT resolution code. Also note that I arranged things so that every SMB connection is now async internally, so using plain smbclient or smbtorture tests all the async features of this new code. (This used to be commit 468f8ebbfdbdf37c757fdc4863626aa9946a8870)
Diffstat (limited to 'source4/torture/rpc')
0 files changed, 0 insertions, 0 deletions