Comment 94 for bug 211631

Hi Thierry,

Thierry Carrez wrote:
> I am trying to solve the bug in the (2) case here. If you are in the
> (3) case (and a lot of you probably are) you should either switch to
> "system setting" mode or drop usage of CIFS mounts in favor of
> Nautilus gvfs-smb mounts.

Thanks very much for the detailed explanation. I switched to "system
setting" mode and this did solve the problem for me. This option is very
well hidden however, so this is probably one of the reasons why there
are many users who use fstab in combination with per-user network
settings. (The gvfs option is not suitable for me BTW because I access
the mounts mostly from scripts. And also from KDE programs -- I'm not
sure those can access gvfs. :-) )

I do still think that there is something fishy going on with the long
timeouts while I have nothing open on the network fs.

I admit that I'm applying the same kind of logic that people do actually
use for things like thumb drives -- if you don't write to them (or
haven't written to them in a while) then you can remove them without
thinking. It's not *technically* correct, but it's only not technically
correct because the system works that way. And then we are typically
trying to make the users behave in a certain way to match the behaviour
of the system, instead of making sure the system behaves as the users
quite reasonably expect it to. :-) Personally I think that it would be
very much in line with Ubuntu's "human" philosophy to try and make the
system behave as humans expect it to, which in this case is that if they
haven't written anything to the fs, then there's no reason to wait for
the server. Steve's analysis might give some pointers to WTF is going on
here...

Cheers,
Bart