Displaying 2 results from an estimated 2 matches for "after_ready".
2020 Jun 22
0
Re: [PATCH nbdkit 1/2] server: Add .after_fork callback, mainly for plugins to create threads.
...g, the solution is
version dependencies: you could make it so that installing the
nbdkit-vddk-plugin package forces an upgrade of the nbdkit package to
1.22 - but this is more a question for situations not covered by distro
packaging setups]
> +=head2 C<.after_fork>
> +
> + int after_ready (void);
Typo in the function name.
> +
> +This optional callback is called before the server starts serving. It
> +is called after the server forks and changes directory. If a plugin
> +needs to create background threads (or uses an external library that
> +creates threads) it sh...
2020 Jun 22
4
[PATCH nbdkit 1/2] server: Add .after_fork callback, mainly for plugins to create threads.
...rver forks or changes directory. It is
+ordinarily the last chance to do any global preparation that is needed
+to serve connections.
If there is an error, C<.get_ready> should call C<nbdkit_error> with
an error message and return C<-1>.
+=head2 C<.after_fork>
+
+ int after_ready (void);
+
+This optional callback is called before the server starts serving. It
+is called after the server forks and changes directory. If a plugin
+needs to create background threads (or uses an external library that
+creates threads) it should do so here, because background threads are
+kille...