mirror of
https://github.com/samba-team/samba.git
synced 2025-03-01 04:58:35 +03:00
e89fd49df7
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)
This is the 'CIFS on CIFS' backend for Samba. It provides a NTVFS backend that talks to a remote CIFS server. The primary aim of this backend is for debugging and development, although some poeple may find it useful as a CIFS gateway. Here is a typical config: [myshare] ntvfs handler = cifs cifs:server = myserver cifs:user = tridge cifs:password = mypass cifs:domain = TESTDOM cifs:share = test