Re: [gamin] [RFC][PATCH] inotify 0.10.0 [u]

Martin Schlemmer [c]
2004-09-27T16:31:36Z

[-- Attachment #1: Type: text/plain, Size: 1851 bytes --]

On Mon, 2004-09-27 at 12:24 -0400, Robert Love wrote:
> On Mon, 2004-09-27 at 18:21 +0200, Martin Schlemmer [c] wrote:
>
> > I have just looked quickly at the inotify backend this weekend, so not
> > really clued up yet, so excuse the stupid question: Does this mean
> > inotify is now up to par with dnotify/poll feature wise? Or should we
> > still look at getting inotify backend to use poll?
>
> inotify supports poll in the sense that you can poll() or select()
> on /dev/inotify.
>
> dnotify does not support poll() at all (it is signal based), so your
> question is kind of confusing.
>

(Sorry for double posting - keep forgetting with what email addy I am
subscribed to this list)

Right, but using gamin, dnotify+poll support some things that inotify
do not support. Basically the dnotify backend also use the poll backend
to enhance it to be able to monitor some events that dnotify by itself
cannot (Daniel will be the better person to ask here). Here is a small
snippit from another thread:

----
> > > > inotify should be able to fallback to poll too, otherwise it's
> > > > > a bug in the inotify back-end, think for example for NFS resources.
> > > > >
> > > >
> > > > Hmm - well it does not use poll. I will see if I can have a
> > > > look at at dnotify backend and cook something up. I assume
> > > > John never got to it, or you added the poll support to dnotify
> > > > after inotify was added?
> > >
> > > I added it after, yes.
> > >
> >
> > Ok, thanks.
> >
>
> Actually, initially the inotify backend did support using the poll
> backend as well. I got rid of it because at the time inotify provided
> everything we needed. Now gamin supports watching things that inotify
> can't, like directories that don't exist.
----

Thanks,

--
Martin Schlemmer

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]