From 21284731a374cbea335b8b80348e643d9bda8872 Mon Sep 17 00:00:00 2001 From: Oliver Giles Date: Fri, 12 Oct 2018 17:20:09 +0300 Subject: [PATCH] UserManual: remove obsolete reference to locks --- UserManual.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/UserManual.md b/UserManual.md index b72e46e..c70a3f9 100644 --- a/UserManual.md +++ b/UserManual.md @@ -607,7 +607,5 @@ Finally, variables supplied on the command-line call to `laminarc queue`, `lamin - `start [JOB [PARAMS...]]...` starts one or more jobs with optional parameters, returning when the jobs begin execution. - `run [JOB [PARAMS...]]...` triggers one or more jobs with optional parameters and waits for the completion of all jobs. Returns a non-zero error code if any job failed. - `set [VARIABLE=VALUE]...` sets one or more variables to be exported in subsequent scripts for the run identified by the `$JOB` and `$RUN` environment variables -- `lock [NAME]` acquires the [lock](#Locks) named `NAME` -- `release [NAME]` releases the lock named `NAME` `laminarc` connects to `laminard` using the address supplied by the `LAMINAR_HOST` environment variable. If it is not set, `laminarc` will first attempt to use `LAMINAR_BIND_RPC`, which will be available if `laminarc` is executed from a script within `laminard`. If neither `LAMINAR_HOST` nor `LAMINAR_BIND_RPC` is set, `laminarc` will assume a default host of `unix-abstract:laminar`.