summaryrefslogtreecommitdiff
path: root/source4/torture/rpc/samsync.c
diff options
context:
space:
mode:
authorMichael Adam <obnox@samba.org>2008-10-27 14:28:44 +0100
committerMichael Adam <obnox@samba.org>2008-10-27 14:59:33 +0100
commitb881d2ee78f685aea7ae8b67b3e0fb3c4f5205ed (patch)
treeec38f392e15daf1cdf05ea1d11114486ea8911fd /source4/torture/rpc/samsync.c
parent68aa9bd67f9556f608bfb321d593617bd346915f (diff)
downloadsamba-b881d2ee78f685aea7ae8b67b3e0fb3c4f5205ed.tar.gz
samba-b881d2ee78f685aea7ae8b67b3e0fb3c4f5205ed.tar.bz2
samba-b881d2ee78f685aea7ae8b67b3e0fb3c4f5205ed.zip
[s3]winbind: fix smbd hanging on Solaris when winbindd closes socket.
On some versions of Solaris, we observed a strange effect of close(2) on a socket: After the server (here winbindd) called close, the client fd was not marked as readable for select. And a write call to the fd did not produce an error EPIPE but just returned as if successful. So while winbindd had called remove_client(), the corresponding smbd still thought that it was connected, but failed to retrieve answers for its queries. This patch works around the problem by forcing the client fd to the readable state: Just write one byte into the socket before closing. Michael
Diffstat (limited to 'source4/torture/rpc/samsync.c')
0 files changed, 0 insertions, 0 deletions