#Unison fsmonitor windows#

+ File system monitoring: more robust communication. but I am not confident that fsmonitor.py is the correct starting place. In unison 2.48.3, a native fsmonitor is introduced, with the new fsmonitor, unison can impliment dropbox like sync on demand,following is quotad from upstream NEWS: File system monitoring: + The file watcher now fails when unable to watch a directory, rather than silently ignoring the issue. > The reason I am asking: I would like to add freebsd support to the fsmonitor process. fsmonitor.py implements the protocol in (3) Furthermore it does not send commands to stdout, rather it writes them to a file called 'changes' in a way that does not agree with (1). fsmonitor.py implements a notification protocol but it does not send or receive any of the commands in (1). fswatch.ml describes (and implements) a notification protocol in which stdin/stdout is used to communicate messages such as VERSION, OK, DIR, LINK, CHANGE, etc > Can someone explain this discrepancy in the 2.48.3 source distribution: There are two mailinglists: unison-users and unison-hackers.

Therefore, you must use the same Unison minor version built with the same ocaml version on all systems. > On Dec 31, 2015, at 2:01 AM, Chris Stankevitz wrote: Additionally, Unison has incompatible changes across minor releases (e.g. You probably want to clone fsmonitor/linux and go from there. This implementation was originally made for macOS but shall work on other platforms as well like Linux, Windows. So you’re correct that fsmonitor.py is not the right place to start for you. But calls to Fswatchold functions are forwarded to Fswatch if the newer monitor is running. If you look around the rest of the code, you’ll see calls to both modules. They use a somewhat fancier protocol to communicate.

#Unison fsmonitor windows#

There are currently two file-watching modules in Unison:įswatchold.ml, the older one (surprisingly enough), calls fsmonitor.pyįswatch.ml, the newer one, seems to work only on Linux and Windows it calls unison-fsmonitor, which is an OCaml program (found in the fsmonitor subdirectory) that is built separately from Unison. OK, after a little detective work, I think I understand… :-) Discrepancy in fswatch.ml and fsmonitor.py Benjamin C. Discrepancy in fswatch.ml and fsmonitor.py