[snip]
> The dropping mounts, however, were not cured. With 2.0.36 there is no problem
> with NT (or other smb server) closing the socket -- smbfs seems to transparently
> reconnect when needed. With 2.2.1, the mounts drop after few minutes of idle time
> when NT closes the socket. (With samba, the problem does not show up, at least
> that often, since samba does not close the socket all that often.) I suppose this
> behaviour has something to do with the recent smbfs delayed mount discussion. As
> I understood, in 2.0 the smbmount would fork a child that did remounting in the
> background every time smbfs asked it to. Now that the smbmount scheme has changed,
> this does not happen any more, am I correct?
Yes, smbmount forks a child that maintains the connection. This behavior
was broken when someone unsuccessfully tried to fix the race problem that
smbmount had with autmount. This problem (amongst others) has been fixed
in Samba 2.0.2. Anyway, the problem of dropping mounts is on the client
side.
Paul Laufer
> Ville Herva Ville.Herva@netspan.fi +358-50-5164500
> Netspan Oy netspan@netspan.fi PL 65 FIN-02151 Espoo
> http://www.netspan.fi
> For my PGP key, finger vherva@netspan.fi.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/