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
New files or changes in a shared location are not visible in finder to users without upspinfs restart #593
Comments
In my case for my upspin mount to show up at all in Finder I had to make it compile as a network drive. |
Can you explain what you mean by "I had to make it compile as a network drive'? |
On Jun 29, 2018, at 7:54 AM, Sevan Janiyan ***@***.***> wrote:
Can you explain what you mean by "I had to make it compile as a network drive'?
I just use the stock binaries published on upspin.io and use https://github.com/upspin/upspin/blob/master/cmd/upspinfs/scripts/mount_darwin <https://github.com/upspin/upspin/blob/master/cmd/upspinfs/scripts/mount_darwin> script.
I use the upspinfs command directly. In order for it to show up in Finder, I had to comment out this line:
https://github.com/upspin/upspin/blob/master/cmd/upspinfs/fs.go#L1067 <https://github.com/upspin/upspin/blob/master/cmd/upspinfs/fs.go#L1067>
I usually mount upspin as $HOME/u, and I have a symlink in $HOME/h such that it points to the root of my mount in upspin (because I’m lazy).
Under linux, this works fine without any modification. Under OS X, the symlink wouldn’t work in Finder, and I could only access my stuff through the shell, which is less than ideal as the VLC Player couldn’t access my media library stored under ~/h/Music.
|
Thanks for the pointer, I'll give a try next week to see how it works out. |
Not treating the mount as a localvolume doesn't make any difference. |
I have a directory which I share with several people so we can exchange data with each other. Everyone I'm sharing with is a macOS user & accesses the shared space using the integration with finder via FUSE & upspinfs. The problem is that once a new file is copied to my shared directory by someone else, the file appears briefly in finder for that person after the copy has completed and then it disappears. Once they restart upspinfs, the file is actually visible correctly for them.
For other people, propagation is hit and miss, some see the changes/additions when they complete others do not, until upspinfs has restarted.
Everyone is able to see files correctly at all times if they access things using upspin instead.
The question is, is this an issue with upspinfs or FUSE on OS X? Any pointers appreciated.
The text was updated successfully, but these errors were encountered: