[unison-users] unison-fsmonitor not found

[Damien ROBERT [e-mail] [unison-users]]

I have compiled unison-2.48.3 and my server and put it in my $HOME/bin
folder:

~/bin $ ls
unison@               unison-fsmonitor@
unison-2.48-gtk2-64@

I use 'unison -servercmd bin/unison -repeat watch'
and I get
Fatal error: No file monitoring helper program found
even though 'unison-fsmonitor' is on the same folder as unison and from the
code on fswatch.ml it should be looking at 'exec_dir'.

Even more strange, even when I try to add 'bin/' to the path via
'unison -servercmd bin/unison -repeat watch -sshargs 'PATH=bin:$PATH''
or
'unison -servercmd bin/unison -repeat watch -sshargs 'PATH=$HOME/bin:$PATH''
I still get the same error.

I did not see anything useful when adding '-debug all'.
unison-fsmonitor seems to be working when called manually:

~/bin $ ./unison-fsmonitor
VERSION 1

I thought that maybe unison was looking for 'fsmonitor.py' instead. (I admit that I don't know how unison
chooses between 'unison-fsmonitor' and 'fsmonitor.py') But even copying 'fsmonitor.py' and 'fsmonitor/' from the gitfolder to my ~/bin/ I still get the same error.
Thanks for any help!

[[e-mail] [unison-users]]

Post by Damien ROBERT ***@yahoo.com [unison-users]
I use 'unison -servercmd bin/unison -repeat watch'
and I get
Fatal error: No file monitoring helper program found
even though 'unison-fsmonitor' is on the same folder as unison and from the
code on fswatch.ml it should be looking at 'exec_dir'.
~/bin $ ./unison-fsmonitor
VERSION 1

I don't know the details of unison-fsmonitor, but I would first check
exactly what the name of the "file monitoring helper program" is.
Ideally, the fatal error message specifies the exact string that Unison
is trying ot execute. The second check is whether unison-fsmonitor (or
whatever the proper name is) is accessible through the path. I.e.,

Post by Damien ROBERT ***@yahoo.com [unison-users]
~/bin $ unison-fsmonitor

Also, you can use "which unison-fsmonitor".

Another thing to check is whether the fatal error is coming from the
Unison on this end or the Unison at the server on the far end of the
connection.

Dale