summaryrefslogtreecommitdiff
path: root/DOC_CHANGES.md
diff options
context:
space:
mode:
authorClaire McQuin <claire@getchef.com>2014-05-06 16:29:38 -0700
committerClaire McQuin <claire@getchef.com>2014-05-06 16:29:38 -0700
commit8b3a0f45c8e4fe3dd7cc147ff679d179d2e140db (patch)
tree65644965e02fd20028416e770c01f8dde2b45f27 /DOC_CHANGES.md
parent21517f01c1caa58a689ecb985eea89d34da617e6 (diff)
downloadchef-8b3a0f45c8e4fe3dd7cc147ff679d179d2e140db.tar.gz
document config option for runlock timeout
Diffstat (limited to 'DOC_CHANGES.md')
-rw-r--r--DOC_CHANGES.md10
1 files changed, 8 insertions, 2 deletions
diff --git a/DOC_CHANGES.md b/DOC_CHANGES.md
index 27706774f6..504b6d688e 100644
--- a/DOC_CHANGES.md
+++ b/DOC_CHANGES.md
@@ -9,10 +9,16 @@ Description of the required change.
### --run-lock-timeout for chef-client and chef-solo
You can now add a timeout for the maximum time a client run waits on another client run to finish.
The default is to wait indefinitely.
-Setting the run lock timeout to 0 causes the second client run to exit immediately:
+Setting the run lock timeout to 0 causes the second client run to exit immediately.
+This can be configured in your config file:
```
-chef-client --run-lock-timeout 0
+run_lock_timeout SECONDS
+```
+
+Or via the command line:
+```
+chef-client --run-lock-timeout SECONDS
```
#### New knife command: knife node environment set