nbd-proxy: replace hook dir with a single executable
A future change will run the executable asynchronously. With a directory
of hooks, this gets overly complicated.
Replace the directory-of-hooks concept with a single hook. The hook
itself can then spawn multiple hooks if required (eg, with run-parts).
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
diff --git a/README b/README
index 0d3030e..d7e1ec7 100644
--- a/README
+++ b/README
@@ -54,12 +54,12 @@
websocket proxy should implement proper authentication before nbd-proxy is
connected to the websocket endpoint.
-State hooks
------------
+State hook
+----------
-The nbd-proxy has a facility to run hooks on state change. When a
-nbd session is established or shut down, the proxy will run any executables
-found under the hook path (by default, /etc/nbd-proxy/state.d/).
+The nbd-proxy has a facility to run an program on state change. When a nbd
+session is established or shut down, the proxy will run the executable at
+/etc/nbd-proxy/state.
-These hooks are called with two arguments: the action ("start" or "stop"),
+This executable is called with two arguments: the action ("start" or "stop"),
and the name of the configuration (as specified in the config.json file).