Displaying 7 results from an estimated 7 matches for "vddk_config_help".
2020 Feb 13
2
[nbdkit PATCH] vddk: Make 'file=' a magic key
...meters>.
+
=item B<libdir=>PATHNAME
This sets the path of the VMware VDDK distribution.
diff --git a/plugins/vddk/vddk.c b/plugins/vddk/vddk.c
index 6deb0a0b..344b4e6b 100644
--- a/plugins/vddk/vddk.c
+++ b/plugins/vddk/vddk.c
@@ -416,7 +416,7 @@ vddk_config_complete (void)
}
#define vddk_config_help \
- "file=<FILENAME> (required) The filename (eg. VMDK file) to serve.\n" \
+ "[file=]<FILENAME> (required) The filename (eg. VMDK file) to serve.\n" \
"Many optional parameters are supported, see nbdkit-vddk-plugin(3)."
static void
@@ -901,6 +...
2020 Jun 22
0
[PATCH nbdkit 2/2] vddk: Defer library initialization to .after_fork().
...28 ++++++++++++++++++++++------
1 file changed, 22 insertions(+), 6 deletions(-)
diff --git a/plugins/vddk/vddk.c b/plugins/vddk/vddk.c
index e6639b4d..a481e8bf 100644
--- a/plugins/vddk/vddk.c
+++ b/plugins/vddk/vddk.c
@@ -431,12 +431,31 @@ vddk_config_complete (void)
return 0;
}
+#define vddk_config_help \
+ "[file=]<FILENAME> (required) The filename (eg. VMDK file) to serve.\n" \
+ "Many optional parameters are supported, see nbdkit-vddk-plugin(3)."
+
static int
vddk_get_ready (void)
{
- VixError err;
-
load_library (true);
+ return 0;
+}
+
+/* Defer VDDK init...
2020 Feb 17
0
Re: [nbdkit PATCH] vddk: Make 'file=' a magic key
...> This sets the path of the VMware VDDK distribution.
> diff --git a/plugins/vddk/vddk.c b/plugins/vddk/vddk.c
> index 6deb0a0b..344b4e6b 100644
> --- a/plugins/vddk/vddk.c
> +++ b/plugins/vddk/vddk.c
> @@ -416,7 +416,7 @@ vddk_config_complete (void)
> }
>
> #define vddk_config_help \
> - "file=<FILENAME> (required) The filename (eg. VMDK file) to serve.\n" \
> + "[file=]<FILENAME> (required) The filename (eg. VMDK file) to serve.\n" \
> "Many optional parameters are supported, see nbdkit-vddk-plugin(3)."
>
>...
2020 Feb 17
1
Re: [nbdkit PATCH] vddk: Make 'file=' a magic key
...VDDK distribution.
> > diff --git a/plugins/vddk/vddk.c b/plugins/vddk/vddk.c
> > index 6deb0a0b..344b4e6b 100644
> > --- a/plugins/vddk/vddk.c
> > +++ b/plugins/vddk/vddk.c
> > @@ -416,7 +416,7 @@ vddk_config_complete (void)
> > }
> >
> > #define vddk_config_help \
> > - "file=<FILENAME> (required) The filename (eg. VMDK file) to serve.\n" \
> > + "[file=]<FILENAME> (required) The filename (eg. VMDK file) to serve.\n" \
> > "Many optional parameters are supported, see nbdkit-vddk-plugin(3).&q...
2019 Oct 11
3
[PATCH NOT WORKING nbdkit v2 0/2] vddk: Restructure plugin to allow greater parallelism.
This is my second attempt at this. The first version (also not
working) was here:
https://www.redhat.com/archives/libguestfs/2019-October/msg00062.html
In part 1/2 I introduce a new .ready_to_serve plugin method which is
called after forking and just before accepting any client connection.
The idea would be that plugins could start background threads here.
However this doesn't work well in
2020 Jun 22
4
[PATCH nbdkit 1/2] server: Add .after_fork callback, mainly for plugins to create threads.
If you have a plugin which either creates background threads itself or
uses a library that creates background threads, it turns out you
cannot create these in .get_ready (or earlier). The reason is that
nbdkit forks when either daemonizing itself or using the --run option,
and fork cancels all the background threads in the child process (the
daemonized or captive nbdkit).
The only good solution
2020 Feb 25
6
[PATCH nbdkit 0/5] server: Add .get_ready callback.
I like this change. I think we were overloading the config_complete
method before to do two different things (complete configuration; do
any allocation/housekeeping necessary before we can start serving).
The only questions in my mind are whether we want this before 1.18,
and whether the name ("get_ready") is a good one.
Rich.