serious kfind and famd problems, help needed

[Josef Weidendorfer]

On Tuesday 18 January 2005 15:05, Waldo Bastian wrote:
> Yes, those are good points and that would probably help a lot. I'm not sure
> that it explains http://bugs.kde.org/show_bug.cgi?id=77854 though, that
> very much suggests a FAM deadlock. (Disabling the above if-body would get
> rid of that as well of course)

You are right. Perhaps for every command we send to FAM we should do 
famEventReceived() before.
Ideally, this should be done by the FAM library itself. Or better, the library 
should use nonblocking syscalls for communication with the server.

Deadlock races like this probably would not exist if event merging would be 
done either by the kernel (enhanced dnotify) or the FAM server: i.e. a change 
notification for some file should be sent at a maximum rate of 5 per second. 
OTOH, if kfind watches 1000 dirs which all are removed with a "rm -rf *", 
this will produce an event storm...

Josef

>
> Cheers,
> Waldo