search for: mode_socket_activ

...(EXIT_SUCCESS); +} + +static bool +is_directory (const char *path) +{ + struct stat statbuf; + + if (stat (path, &statbuf) == -1) + return false; + return S_ISDIR (statbuf.st_mode); +} + +int +main (int argc, char *argv[]) +{ + enum { + MODE_URI, + MODE_COMMAND, + MODE_FD, + MODE_SOCKET_ACTIVATION, + MODE_TCP, + MODE_UNIX, + } mode = MODE_URI; + enum { + HELP_OPTION = CHAR_MAX + 1, + FUSE_HELP_OPTION, + }; + /* Note the "+" means we stop processing as soon as we get to the + * first non-option argument (the mountpoint) and then we parse the + * rest of the...

...statbuf) == -1) > + return false; > + return S_ISDIR (statbuf.st_mode); Accepts a symlink-to-directory, but that's fine by me. > +} > + > +int > +main (int argc, char *argv[]) > +{ > + enum { > + MODE_URI, > + MODE_COMMAND, > + MODE_FD, > + MODE_SOCKET_ACTIVATION, > + MODE_TCP, > + MODE_UNIX, > + } mode = MODE_URI; > + enum { > + HELP_OPTION = CHAR_MAX + 1, > + FUSE_HELP_OPTION, > + }; > + /* Note the "+" means we stop processing as soon as we get to the > + * first non-option argument (the mountpo...

...PORT\n" " nbdfuse MOUNTPOINT[/FILENAME] --unix SOCKET\n" +" nbdfuse MOUNTPOINT[/FILENAME] --vsock CID PORT\n" "\n" "Please read the nbdfuse(1) manual page for full usage.\n" "\n" @@ -139,6 +141,7 @@ main (int argc, char *argv[]) MODE_SOCKET_ACTIVATION, MODE_TCP, MODE_UNIX, + MODE_VSOCK, } mode = MODE_URI; enum { HELP_OPTION = CHAR_MAX + 1, @@ -161,6 +164,7 @@ main (int argc, char *argv[]) { NULL } }; int c, fd, r; + uint32_t cid, port; int64_t ssize; const char *s; struct fuse_args fuse_args = FU...

This is a series of patches to libnbd and nbdkit adding AF_VSOCK support. On the host side it allows you to start an nbdkit instance which listens on a virtio-vsock socket: $ ./nbdkit -fv --vsock memory 1G ... nbdkit: debug: bound to vsock 2:10809 On the guest side you can then use libnbd to connect to the server: $ ./run nbdsh -c 'h.connect_vsock(2, 10809)' -c