Re: File watcher process for BSD

That matches my experience. 

-- 
http://matthewlmcclure.com/
http://cens.io/

> On Aug 27, 2015, at 12:21, Chris Stankevitz <[email protected]> wrote:
> 
>> On 8/21/15 9:41 AM, Chris Stankevitz wrote:
>> When using '-repeat watch', how does unison discover the PID of the FWP?
>>  Or, if unison launches the FWP, how does unison learn the FWP's name?
> 
> I think I found the answer in NEWS:  "Unison will now look for fsmonitor.py in the same directory where the Unison executable itself lives."
> 
> So it appears that the file watcher process must be named "fsmonitor.py" and it must live in the same directory as the unison binary.
> 
> Chris
> _______________________________________________
> Unison-hackers mailing list
> [email protected]
> http://lists.seas.upenn.edu/mailman/listinfo/unison-hackers