There is the tall of a hanging gnome. A long time ago, an automount was available, whose name was /net/maison. As content of this automonted directory was useful two thing happen: - .gtk-bookmarks contain file:///net/maison/mp3/newmp3 - .nautilus/metafiles/ contain several filed named file:%2F%2F%2Fnet%2Fmaison.xml containing metainformation about file that were in it.
Then, I chose to change my automount, using something that automatically try to mount say the home share of the foo host if one try to access to /net/foo/home. And as maison was not the dns name of the host where the useful directory was I began to acess it under a different name, *and* the old path failed silently, with no timeout (maison did not resolv to anything) Then, my ISP change the configuration of dhcp generated resolv.conf adding a "search neuf.fr" part to it, and maison.neuf.fr does resolv to a machine that drop sunrpc conexion, so when someone try to acces to /net/maison/mp3/newmp3 for example, there is a timeout before failure. So I've solved my problem, but still it seem that gnome-panel and nautilus are doing some synchron file check that could make them hang. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
