<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Hi Vishesh, thanks for the reply.<br><br>Out of curiosity, assuming that max_user_watches is high enough, does <br>nepomuk associate one inotify watch for each indexed file (all files, not just dirs)?<br>Because, besides the missed updates, I noticed that when a file X update is<br>reported strigi seems to scan recursively all the files in X's directory, not only X.<br>Kind of like the filewatcher was only notified that some file in X's dir subtree has changed<br>but not which one.<br>Is this supposed to happen?<br><br>Best<br>John<br><br><i><br></i>--- On <b>Thu, 4/28/11, Vishesh Handa <i><handa.vish@gmail.com></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br><div id="yiv323805470"><div><div class="yiv323805470gmail_quote"><div><br></div><div>Confirmed! This is
weird. </div><div><br></div><div>It seems to be some kind of inotify problem. The File watching service doesn't seem to be always sending the required signals. :/ The semi good news is that I think I'll be able to write a test case for the exact steps you've described. I'll let<br>you know what happens. <br></div>
</div></div>
</div></blockquote></td></tr></table>