[Unison-hackers] fsmonitor watching ignored paths?

[Benjamin C. Pierce]

That's right: It should just be watching the paths specified in the -paths preference.  (But this functionality is new and not well tested -- might take a little hacking to get it really working.)

   - B

On Jan 18, 2011, at 12:03 PM, Jay Levitt wrote:

> 
> 
> On Tue, Jan 18, 2011 at 11:39 AM, Jay Levitt <jay.levitt at gmail.com> wrote:
> What is it that fails here?  inotify itself?  Or fswatcher?
> 
> 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..
> 
> 
> 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? _______________________________________________
> Unison-hackers mailing list
> Unison-hackers at lists.seas.upenn.edu
> http://lists.seas.upenn.edu/mailman/listinfo/unison-hackers