Re: [PATCH] gnome-vfs: Don't monitor read-only filesystems

[nf <nf2 scheinwelt at>]

On Mon, 2004-04-19 at 20:49, Alexander Larsson wrote:
> On Mon, 2004-04-19 at 17:52, nf wrote:
> > On Mon, 2004-04-19 at 17:29, Alexander Larsson wrote:
> > > On Mon, 2004-04-19 at 15:53, nf wrote:
> > > > 
> > > > I have written a little prototype of such a tool ("wbumount" - who/what
> > > > is blocking umount?)
> > > > 
> > > > http://www.scheinwelt.at/~norbertf/wbumount/
> > > > (doc, sourcecode, screenshot)
> > > > 
> > > > ... something like that could pop up instead of the goddamn "device
> > > > is busy" messages...
> > > 
> > > Why does it list the file managers next to fam? All gnome-vfs using
> > > gnome apps can use fam, and many do.
> > 
> > Well - it's just a guess. Most of the times i had problems unmounting,
> > nautilus was the reason. Is there a way to find out, which application
> > has triggered fam?
> 
> Unfortunately not. Not without running fam w/ verbose output on.

I took a quick look at the fam sources and docs. Something i really
miss, is a "control-api". Fam creates monitors in the space the user
"owns" (like user-mounts), but the user can not control them. This seems
to be an inconsitency.

At least a command-line utlity to...

famctl -user=xyx -listmonitors
famctl -user=xyx -listclientprocesses
famctl -user=xyz -supendmonitor
famctl -user=xyz -resumemonitor
famctl -user=xyz -removemonitor

.. would be practical. Just a consideration - might not make sense...

Norbert