Displaying 3 results from an estimated 3 matches for "check_fail_one".
2020 Aug 28
0
[nbdkit PATCH 3/3] nbd: Implement .list_exports
...--list --json nbd+unix://\?socket=$sock2 > $base.out2
+ cat $base.out2
+ diff -u $base.out1 $base.out2
+}
+
+# check_success EXPORT... - both sub-tests, on all EXPORTs
+check_success()
+{
+ for exp; do
+ check_success_one "$exp"
+ done
+ check_success_list
+}
+
+# check_fail_one EXPORT
+# - nbdinfo of EXPORT on both servers should fail
+check_fail_one ()
+{
+ if nbdinfo --no-content "nbd+unix:///$1?socket=$sock1" > $base.out1; then
+ fail=1
+ fi
+ if nbdinfo --no-content "nbd+unix:///$1?socket=$sock2" > $base.out2; then
+ fa...
2020 Aug 28
4
[nbdkit PATCH 0/3] .list_exports in nbd plugin
Another series on top of my exportname filter, marking off another
todo bullet point. With this, you can now use the NBD plugin as a
transparent passthrough of all export names served by the remote
server in both directions (list advertisement server to client, and
export name from client to server).
Eric Blake (3):
nbd: Implement .default_export, .export_description
nbd: Add
2020 Sep 21
18
[nbdkit PATCH v3 00/14] exportname filter
It's been several weeks since I posted v2 (I got distracted by
improving libnbd to better test things, which in turn surfaced some
major memory leak problems in nbdsh that are now fixed). Many of the
patches are minor rebases from v2, with the biggest changes being
fallout from:
- patch 2: rename nbdkit_add_default_export to nbdkit_use_default_export
- overall: this missed 1.22, so update