search for: aio_connect

...nection is +established but there are no commands in flight, using an +infinite timeout will permanently block). + +This function is mainly useful as an example of how you might +integrate libnbd with your own main loop, rather than being +intended as something you would use."; }; "aio_connect", { @@ -1838,7 +1846,7 @@ come from some other means such as C<nbd_aio_connect>. We are expected next to read from the server. If using L<poll(2)> you would set C<events = POLLIN>. If C<revents> returns C<POLLIN> -you would then call C<nbd_aio_notify_read&...

...o flag?"; longdesc = "\ Returns true if the server supports the use of the @@ -2374,7 +2375,93 @@ Returns true if libnbd was compiled with libxml2 which is required to support NBD URIs, or false if not."; see_also = ["L<nbd_connect_uri(3)>"; "L<nbd_aio_connect_uri(3)>"]; }; +] +(* The first stable version that the symbol appeared in, for + * example (1, 2) if the symbol was added in development cycle + * 1.1.x and thus the first stable version was 1.2. + *) +let first_version = [ + "set_debug", (1, 0); + "get_debug", (1...

This doesn't include Eric's new APIs, but if you push those then I can rebase this one on top. Rich.

While working on a new test of what happens when the server goes away while commands are in flight, I managed to hit a race where I hit death from SIGPIPE instead of a clean transition to the DEAD state. I also found myself wanting to use nbd_poll from the test, but with a way to distinguish between the state machine progressing vs. hanging. Eric Blake (2): socket: Avoid SIGPIPE where possible

This isn't quite finished because not all of the tests or examples have been updated, but it demonstrates an idea: Should we forget about the concept of having multiple connections managed under a single handle? In this patch there is a single ‘struct nbd_handle *’ which manages a single state machine and connection (and therefore no nbd_connection). To connect to a multi-conn server you must