Date: Sat, 20 Jan 2007 23:44:38 -0500 From: Christopher Sean Hilton <chris@vindaloo.com> To: freebsd-gnome@freebsd.org Subject: nautilus + amd/am-utils is bad news. Message-ID: <1169354678.3308.10.camel@dagobah.vindaloo.com>
next in thread | raw e-mail | index | archive | help
Hi,
I use the automounter, amd to manage my usb flash drives and the like
into directories in the custom /volume hierarchy. I've also managed to
avoid ever navigating into this hierarchy with nautilus because it
breaks the automounter's ability to umount the filesystem when I'm done
with my flash drive. The symptom is this:
Mount the flash drive:
$ ls -l /volume/ufs0
Navigate to the flashdrive with nautilus and do some work.
Either wait for the mount to timeout or for it to with amq:
$ amq -u /volume/ufs0
At this point nautilus is holding a resource open in /volume/ufs0
and the automounter cannot timeout the mount and umount the flashdrive.
If I suspend my laptop at this time The flashdrive will be umounted
dirty and I will have to fsck it before I can use it again.
Is there any way to tell nautilus that the directory /volume is under
control of the automounter and that it shouldn't be probing/holding
resources open within it after the user stops actively manipulating
things there e.g. closes the nautilus window on /volume/ufs0 or changes
the directory?
-- Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1169354678.3308.10.camel>