Hi Wouter, * Wouter Verhelst <wou...@debian.org> [09. Aug. 2010]: > tags 592256 + pending > thanks > > On Sun, Aug 08, 2010 at 08:08:37PM +0200, Gregor Zattler wrote: >> Package: nbd-client >> Version: 1:2.9.16-2 >> Severity: normal >> >> >> Dear Wouter Verhelst (or to whom it may concern), >> >> according to the man page: >> >> -c Check whether the specified nbd device is connected. >> >> If the device is connected, nbd-client will exit >> with an exit state of 0 and print the PID of the >> nbd-client instance that connected it to stdout. >> >> If the device is not connected or does not exist >> (for example because the nbd module was not >> loaded), nbd-client will exit with an exit state of >> 1 and not print anything on stdout. >> >> nbd-client -c /dev/nbdNOTCONNECTED should exit with exitstate 1 >> but it exits with exit state of 0: > > Yes; 2.9.16 introduced that bug due to a silly mistake on my end. I've > already fixed it upstream for 2.9.17, and locally in my debian working > directory, but that upload still needs to happen; hopefully I'll be able > to do so today, once it passes my tests.
I upgraded to version 1:2.9.16-3. Now testing a not connected nbd device results in exit status 1 $ sudo nbd-client -c /dev/nbd2 ; echo $? 1 When I connect to a nbd-server: sudo nbd-client hardy 2002 /dev/nbd2 Negotiation: ..size = 577070833KB bs=1024, sz=577070833 When I test the connection: sudo nbd-client -c /dev/nbd2 ; echo $? 17568 0 That's o.k. *But* it's not possible to close this connection: sudo nbd-client -d /dev/nbd2 ; echo $? Disconnecting: que, disconnect, Error: Ioctl failed: Invalid argument Exiting. 1 This is a test connection no actual data is transfered. Ciao, gregor Ciao, Gregor -- -... --- .-. . -.. ..--.. ...-.- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
