diff options
| author | Jeremy Allison <jra@samba.org> | 2013-03-21 13:47:07 -0700 |
|---|---|---|
| committer | David Disseldorp <ddiss@samba.org> | 2013-03-22 20:10:11 +0100 |
| commit | 84dad60672aa5fdc0ff20f5fb8471d5209174063 (patch) | |
| tree | 314fed87469f79619ad6ef06d72dffe968f99d39 /callcatcher-exceptions.grep | |
| parent | 566a2e6828bb5d6ea3a35e24938675a296bbe95b (diff) | |
| download | samba-84dad60672aa5fdc0ff20f5fb8471d5209174063.tar.gz samba-84dad60672aa5fdc0ff20f5fb8471d5209174063.tar.bz2 samba-84dad60672aa5fdc0ff20f5fb8471d5209174063.zip | |
Fix bug #9733 - smbcontrol close-share is not working.
As part of forcibly disconnecting a client from a share,
smbd must atomically call reload_services() to ensure that
the entry in the ServicePtrs[] array corresponding to
that share is removed if the share was removed from
the smb.conf or registry entries.
Otherwise the ServicePtrs[] array entry for the share
remains active and the client races to auto-reconnect to
the share before a second message to reload the smb.conf
file can be sent.
This has to be done as part of the close-share message
processing, as removing the share from the smb.conf file
first, then telling the smbd to reload followed by the
forcible disconnect message doesn't work as in this
sequence of events when the reload message is received
the client is still connected to the share, so the
ServicePtrs[] entry is still left active.
The forcible-disconnect + service reload has to be done
together as an atomic operation in order for this to work.
Signed-off-by: Jeremy Allison <jra@samba.org>
Reviewed-by: David Disseldorp <ddiss@samba.org>
Autobuild-User(master): David Disseldorp <ddiss@samba.org>
Autobuild-Date(master): Fri Mar 22 20:10:11 CET 2013 on sn-devel-104
Diffstat (limited to 'callcatcher-exceptions.grep')
0 files changed, 0 insertions, 0 deletions