https://bugs.kde.org/show_bug.cgi?id=353874
--- Comment #28 from Oded Arbel <o...@geek.co.il> --- (In reply to tagwerk19 from comment #27) > (In reply to Oded Arbel from comment #26) > > ... I believe this should still be good enough for Baloo's purposes ... > What does fanotify beyond inotify? > Also that when unpacking a .tar folders can be created and files > extracted into them faster than baloo can set up notify watches on the > folders. fanotify allows you to ignore that issue by setting up one watch on each of the folders configured in Baloo's KCM and that's it - there are no more race conditions between applications creating folders and Baloo putting inotify watches on them. > I know deleting "too many things all at once" can overflow the inotify > queue. That is possibly still going to be an issue with fanotify - the default event queue with fanotify is 16384 events, and without `CAP_SYS_ADMIN` you can't increase that size - thought it is likely that baloo can consume events fast enough for this not to be a serious issue. -- You are receiving this mail because: You are watching all bug changes.
