-
Notifications
You must be signed in to change notification settings - Fork 154
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
Unable to relocate staged file across filesystem boundaries #15
Comments
Thanks for reporting this. Sorry I've been slow to respond, I've been traveling until just recently. This is definitely a bug and something that needs to be fixed, especially since this is a common setup on shared Linux systems. Utilities like I'm hesitant to stage directly into the synchronization root because it could leave a lot of garbage sitting around. It's easier to have a staging directory that can be wiped after each successful synchronization cycle. I'll investigate potential solutions and aim to have something done later this week. Probably doing whatever Unison does is the "right" thing to do, though at first glance it seems to just call down to the |
Hi, |
Hey, not just yet, but it's at the top of the priority queue. Life's just been a bit hectic until this week. I've just updated everything to take advantage of some new Go 1.8 features, and so far the performance seems a bit better just by virtue of the new 1.8 toolchain (probably due to the SSA and GC improvements). I'm not sure I'll get around to fixing this tonight, but I want it done ASAP. |
I've just opened pull request #18 which should fix this. CI builds are running and I still need to test this on Windows, but I should be able to put out version 0.1.1 this weekend to fix this. Thanks for your patience! |
This should be fixed by #18. I'll do a release (v0.1.1) later this weekend with this change. I've closed for now, but please re-open if this does not resolve the issue. |
When home directory and sync target directory are not on the same filesystem I get the following errors:
The text was updated successfully, but these errors were encountered: