On 03/02/2017 11:22, Richard W.M. Jones wrote: > > I think that the --fork option is mainly intended for command line use > of qemu-nbd. If you're running qemu-nbd from a program there's no > real reason to use --fork, since you can control the fork process > better yourself. > > LISTEN_PID isn't settable from the command line. It's also not > settable from a shell script (as far as I can tell when I was trying > to write a shell script to test nbdkit). It has to be set between the > fork and exec calls, because it is set to the qemu-nbd PID. > > So I don't think --fork and socket activation are really features that > it makes any sense to mix.
I agree it doesn't really make sense, but I also don't see why it wouldn't work. Paolo
