I discovered a problem with the dnotify API while fixing a FAM bug today.
The problem occurs when you want to watch a file in a directory, and that
file is changed several times in the same second. When I get the directory
notify signal on the directory I need to stat the file to see if the
change was actually in the file. If the file already changed in the
current second the stat() result will be identical to the previous stat()
call, since the resolution of mtime and ctime is one second.
This leads to missed notifications, leaving clients (such as Nautilus or
Konqueror) displaying an state not representing the current state.
The only userspace solutions I see is to delay all change notifications to
the end of the second, so that clients always read the correct state. This
is somewhat countrary to the idea of FAM though, as it does not give
instant feedback.
Is there any possibility of extending struct stat with a generation
counter? Or is there another solution to this problem?
/ Alex
Please CC any reply to me, i'm not on the list.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Oct 07 2001 - 21:00:25 EST