For now, this API breakage and zero-copy read is contained in the
special libnfs-next-gen branch.
On Tue, 27 Jun 2023 at 22:23, ronnie sahlberg wrote:
>
> As the developer of libnfs I am asking for advice here.
> In order to implement "zero-copy" read support I had to break
As the developer of libnfs I am asking for advice here.
In order to implement "zero-copy" read support I had to break he API for read(),
which realistically breaks the API for every single application. So I
took the opportunity to fix other
warts in the interface as well (like rpc_* functions shoul
Package: git
Severity: wishlist
The hold_lock_file_for_update should return any helpful error string
using a strbuf argument.
This also means that unable_to_lock_message should be made private to
lockfile.c.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
Serge,
Thanks for confirming that this version works and solves your issue.
regards
ronnie sahlberg
On Sun, Jun 29, 2014 at 3:43 PM, Serge Rijkers wrote:
> Dear Ronnie and Ritesh,
>
> I hope Ritesh has the 1.9.4 release of libnfs in the debian archive soon. In
> the meantime I
Please try libnfs version 1.9.4 which has just been released.
If this version also fails, can you check that you have set the export
to "insecure" in /etc/exports for the shares on the server?
Also, can you collect a network trace with wireshark showing the failure?
regards
ronnie sah
5 matches
Mail list logo
