Ronnie Sahlberg

FYI. NFSv4 support in libnfs is coming along and should be reasonably complete and to the state where one can use it for for example fuse-nfs. This is likely going...

Libnfs has support for both lockf() and fcntl() locking now but only for nfs v4. With this, it should be fairly straightforward to add locking support to fuse-nfs.

On Wed, Nov 6, 2019 at 9:10 PM David Disseldorp wrote: > CHAP with MD5 currently uses the in-tree lib/md5.c library. For the new > algorithms I think it'd make...

Hi, sorry must have missed this email. Libnfs caches directory content based on the mtime timestamp for the directory. This check is done every time the application opens the directory...

UUID=386cb49b-6b69-41bd-ab8c-111af6cb0fd1 /mnt/Odin xfs defaults,nofail,relatime 0 2 -snip- /mnt/Odin /srv/nfs/Odin none bind,nofail 0 2 You are accessing the files via /srv/nfs/Odin which is a bind mount. That should not make any...

I think it might be a case of libnfs not having a workaround for servers that return neither a handle nor attributes for a directory entry. This is interesting :...

Can you collect a wirestark trace for each of osz and libnfs+kodi so I can compare. It shouldn't be too hard to implement a workaround once I know exactly how...

Hi, I would want to avoid integrating libev into libnfs, just because I want to limit the number external dependencies. It should however not be too to integrate it into...

On Fri, Feb 16, 2018 at 2:33 PM, crusader-mike wrote: > No, integrating libev would be a bad idea. I was thinking about having > tools to integrate libnfs event...

On Fri, Feb 16, 2018 at 3:04 PM, crusader-mike wrote: > I think libnfs should work for you and it is designed primarily to use the > async interface. >...