On Thu, May 22, 2008 at 5:13 PM, Colin Walters <<a href="mailto:walters@verbum.org">walters@verbum.org</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Thu, May 22, 2008 at 4:44 PM, Bill Nottingham <<a href="mailto:notting@redhat.com">notting@redhat.com</a>> wrote:<br>
><br>
> I mean, right now we have a static init script that runs once<br>
> on boot to mount NFS, SMB, etc, and set up network block devices.<br>
> It's also (in F9) kicked when NM brings up a new default route.<br>
><br>
> What would be sane is to have it just mount things when it can<br>
> reach the proper network, and lazily unmount them when that<br>
> network goes away.<br>
<br>
</div>The issue with this is that at least last time I checked, at least<br>
some file systems like NFS basically don't handle the network going<br>
away from underneath them; if you have any userspace processes<br>
accessing them they'll be wedged unrecoverably in D state. I gave up<br>
long ago on using kernel-based network filesystems on my laptop for<br>
this reason.<br></blockquote></div><br>It should be noted that anything using gnome-vfs, that is, most anything gnome, seems to like to happily stat every mounted filesystem constantly, often for no apparent reason, even if that app isn't even doing anything with that mount. This means your entire desktop locks the f-ck up if an NFS mount goes dead, gnome panel and all. It also seems to prevent automounts from ever timing out.<br>