On Tuesday January 22, [EMAIL PROTECTED] wrote:
> i was only testing for IN_OPEN and IN_CLOSE_NOWRITE (
> http://inotify-tools.sourceforge.net/api/inotifytools_8h.html )
>
> can do more in depth test tomorrow.
If you are watching for inotify events on the server, and performing
accesses on some client, then I would expect you to get an IN_OPEN
followed immediately by an IN_CLOSE_{NO,}WRITE each time the client
sends a READ or WRITE request respectively.
So if the client just opens the file and then closes it, you would get
no INOTIFY events.
If the client performs open/read/close repeatedly, subsequent reads
would come from cache, so you would only get one
IN_OPEN/IN_CLOSE_NOWRITE
pair.
If the client performs writes, you should get a more predictable
stream of IN_OPEN/IN_CLOSE_WRITE pairs, though they could be delayed a
bit.
You results will probably be different (and possible more like what
you expect) if you use NFSv4.
NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
