https://bugs.kde.org/show_bug.cgi?id=435294
--- Comment #12 from tagwer...@innerjoin.org --- (In reply to Stefan Brüns from comment #10) > Thats wrong. Inotify uses pathes exclusively, so does any code in baloo > based on inotify. > > The storage backend in baloo uses inodes. I see "id's" listed in the journalctl messages, the 5714849124383745 and 5643818955242497 in Comment 2 above... I was assuming these were hashes of the filename or something in combination with a modification time but it seems that they are a construct of the dev number and inode. I assume the "renaming" messages appear because baloo has missed the inotify changes and, after having woken up, discovered that a file it thought it knew about is really a different file. So, not so much "detecting" a rename but realising that one has happened. What I don't know is whether this is bad(tm) (Thanks for the conversation, it helps...) -- You are receiving this mail because: You are watching all bug changes.
