From bb6f6abe9621e86f3081c0db46db7cf4beb611d3 Mon Sep 17 00:00:00 2001 From: Mark Craig <mark.craig@forgerock.com> Date: Wed, 23 Sep 2015 11:58:51 +0000 Subject: [PATCH] OPENDJ-2285 dsconfig --batchFile does connect for each command --- opendj-sdk/opendj-server-legacy/src/main/docbkx/man-pages/description-dsconfig.xml | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/opendj-sdk/opendj-server-legacy/src/main/docbkx/man-pages/description-dsconfig.xml b/opendj-sdk/opendj-server-legacy/src/main/docbkx/man-pages/description-dsconfig.xml index ed92468..528f6c8 100644 --- a/opendj-sdk/opendj-server-legacy/src/main/docbkx/man-pages/description-dsconfig.xml +++ b/opendj-sdk/opendj-server-legacy/src/main/docbkx/man-pages/description-dsconfig.xml @@ -63,7 +63,9 @@ then reading from the batch file with the <option>--batchFilePath</option> option in script mode. Batch files can be useful when you have many <command>dsconfig</command> commands to run - and want to avoid starting the JVM and setting up a new connection for each command. + and want to avoid starting the JVM for each command. + Alternatively, you can read commands from standard input + by using the <option>--batch</option> option. </para> <para> -- Gitblit v1.10.0