<br><br><div class="gmail_quote">On Tue, Jan 18, 2011 at 11:39 AM, Jay Levitt <span dir="ltr"><<a href="mailto:jay.levitt@gmail.com">jay.levitt@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">What is it that fails here? inotify itself? Or fswatcher?<br><br></blockquote>
</div><div>I think it's inotify itself; when I change sysctl fs.inotify.max_user_watches, the errors happen in different parts of my filesystem. I could probably find a max_user_watches value that's high enough to include every file in the directory, but I don't know what bad effects that might have..</div>
<div><br></div></div><br>
</blockquote></div>Wait, I've looked at the code and now I'm confused. Shouldn't fsmonitor.py be looking only at paths defined in "paths"? Even if it's not processing ignores, the large directories aren't in any of the defined paths; they're just below the root. Bug, or part of the "unison semantics are too complex" change?