Max Ehrlich
Max Ehrlich
@sahlberg Trying to add in support now and one thing that I'm running into is that the first thing GVFS does is run ``` export_list = mount_getexports (host); ``` to...
Ok interesting, I hate for it to seem like I'm offloading work, but this implies we should know beforehand whether the server is running NFSv4 or NFSv3, can you think...
OK thanks I'll give option 2 a shot, it sounds like the right way to do it
I was able to implement option 2 and it works quite well, one thing that would be cool is exporting the function `wait_for_reply` and its assoicated `sync_cb_data` callback to allow...
Ah OK I just found ``` nfs_set_error(nfs, "%s does not support NFSv4", __FUNCTION__); ``` in the fstat code, I'll have to come up with a workaround for that
OK one more issue. Reads are fixed by simply using the fstat64. Writes don't work though It appears the GVFS uses the following procedure for writes: 1. Call `nfs_create_async` passing...
Hi @sahlberg just wondering if you have any ideas about this, I still havent been able to figure out a workaround. It really seems like the EEXIST error should be...
OK thanks for taking a look
Thanks for the fast turnaround So now I am seeing the following output from my debugging statements: ``` replace_create_cb -17 try_write 94430055222080 write_cb NFS4: WRITE (path (null)) failed with NFS4ERR_OPENMODE(-5)...
Same behavior with that zip file