Displaying 3 results from an estimated 3 matches for "set_export".
Did you mean:
send_export
2020 Jul 22
2
Re: [PATCH nbdkit] server: Deprecate the -e/--exportname parameter.
...> possible:
>
> nbdkit ... --run 'exportname=foo; nbdsh -u $uri ...'
Not as written, but we _can_ do the following. Right now, --run creates
a shell fragment, which prepends this code in front of the user's:
uri=...
nbd=...
...
exportname=...
we could instead prepend:
set_export() {
uri=...
nbd=...
...
exportname=$1
}
set_export ...
where that last line uses .default_export (defaulting to "" as usual).
The user can now run:
nbdkit ... --run 'set_export foo; nbdsh -u "$uri" ... '
Oh, and I just realized, because $uri can contain ?...
2020 Jul 22
0
Re: [PATCH nbdkit] server: Deprecate the -e/--exportname parameter.
...o; nbdsh -u $uri ...'
>
> Not as written, but we _can_ do the following. Right now, --run
> creates a shell fragment, which prepends this code in front of the
> user's:
>
> uri=...
> nbd=...
> ...
> exportname=...
>
> we could instead prepend:
>
> set_export() {
> uri=...
> nbd=...
> ...
> exportname=$1
> }
> set_export ...
>
> where that last line uses .default_export (defaulting to "" as
> usual). The user can now run:
>
> nbdkit ... --run 'set_export foo; nbdsh -u "$uri" ... '
C...
2020 Jul 22
2
Re: [PATCH nbdkit] server: Deprecate the -e/--exportname parameter.
On 7/21/20 12:46 PM, Eric Blake wrote:
>> (2) The --run option no longer sets $exportname (to -e) nor puts the
>> export name into the $uri. However this was always the wrong
>> thing to do since export names are per connection, not per server.
>> Existing --run scripts will see $exportname expand to "" which is
>> most likely what they