Hi Chris,
I've tracked down and fixed some of the problems in smbclient, and will
post a patch tomorrow. Smbfs now recovers from making an NT share
unshared.
The problem was twofold -- smbfs needed to recognize a fatal server
error sooner and invalidate the connection, and then the smbclient
process was terminating if it got an error while trying to reopen the
socket. I don't know whether these changes will fix all of the lost
connection problems, but it should be a good start.
> P.S. Why has the connection stuff been moved into user space? Its seems a
> tad unreliable having to keep a user-space program around just to
> access volumes, which may be an very infrequent times.
>
> Things like shutdown scripts can also interfere here surely...
> (likewise with killall5)
Maintaining connections with SMB servers is somewhat complicated, and
since Samba already does that pretty well it makes sense to leverage the
code. I think we can make it work reliably once a few more bugs are
tracked down.
Regards,
Bill