search for: free_export

These patches aren't related to each other, but both are quite simple. The second one requires particular attention - it's my experience that printing out the state transitions in debug mode has never helped me to diagnose a bug, but it has made the debug logs huge and hard to follow. However that might just be me! Has it helped anyone else? Also I'm open to the concept of debug

...ynamically modified such as providing a list of filenames present in a directory). We'd have to figure out lifetimes - would the plugin return a malloc()d list that nbdkit frees, or would we need a pair of functions, where the .list_exports function returns a const list, and then nbdkit calls .free_exports (if defined) to let the plugin clean up any allocations. (The latter is slightly nicer, in case the plugin is using some other memory management scheme, such as a language binding, rather than requiring the copying of data into a form where nbdkit calling free() is safe). > > The implement...

Of course at the moment nbdkit parses the NBD export name option but doesn't really do anything with it (except logging it). I wonder if we should make this available to plugins, in case they wish to serve different content to different clients based on the export name. Note I'm not suggesting that we use this feature in any existing plugins. If we wanted to do this there seem like two