Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unison-fsmonitor symlink is not created #24

Open
bedrich-schindler opened this issue Mar 16, 2018 · 2 comments
Open

unison-fsmonitor symlink is not created #24

bedrich-schindler opened this issue Mar 16, 2018 · 2 comments

Comments

@bedrich-schindler
Copy link

Hello,

I would like to report the problem that occurs after successful installation of unox. We use unox with unison and docker-sync on MacOS High Sierra, we have everything is up-to-date and we install unox using brew.

I installed unison, unox and docker-sync on my device more than 6 months ago and everything went good that time. When we tried to install same stack few days ago (also today) on other devices, we observed that file watcher does not work. I started to debug it on one of our company device and I found that unison is installed in /usr/bin/Cellar/unison/2.48.4_1/bin/unison and symlink /usr/local/bin/unison points to that executable. Although unox is installed in /usr/bin/Cellar/unox/0.2.0_1/bin/unison-fsmonitor, symlink /usr/local/bin/unison-fsmonitor does NOT exist. When I manually create this symlink then everything works as expected.

I am afraid that I cannot provide you more details about this problem. On my Mac works everything as expected, on three other Mac it does not create symlink, so I had to fix like this ln -s /usr/local/bin/Cellar/unox/0.2.0_1/bin/unison-fsmonitor unison-fsmonitor.

Thank you for your time you spent on tools like this, it helps a lot!

@greggilbert
Copy link

greggilbert commented Mar 26, 2018

We've been seeing the issue here a few times. For us, it manifests as this error when starting docker-sync: Fatal error: No file monitoring helper program found

brew unlink unox && brew link unox seems to solve the issue for us, and is a bit cleaner than manually doing ln -s.

But yes, this is an issue that should probably be fixed.

@uzkjzjjz
Copy link

Is your problem solved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants