summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSalim Alam <salam@chef.io>2015-12-02 18:58:40 -0800
committerSalim Alam <salam@chef.io>2015-12-02 18:58:40 -0800
commitd00f3850154a6b27795a908bf840effef04e0b35 (patch)
tree63c6dff98478f7c802e4d1fe2cd33d44b81459f6
parent83f18849da6d85df0381139c55ef47d80cf18c12 (diff)
downloadchef-salam/relnote.tar.gz
Address review feedbacksalam/relnote
-rw-r--r--RELEASE_NOTES.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
index aabecc13a2..5176f99ccb 100644
--- a/RELEASE_NOTES.md
+++ b/RELEASE_NOTES.md
@@ -36,13 +36,13 @@ This debugging feature will mostly be useful to people who are already Ruby expe
### New ksh resource
-ksh is now available to use as a resource and is available as an interpreter in the script resource.
+Korn Shell scripts can now be run using the ksh resource, or by setting the interpreter parameter of the script resource to ksh.
-Please see the DOC_CHANGES for more details.
+Please see the following for more details : https://docs.chef.io/release/12-6/resource_ksh.html
-## Better handling of Windows service logging
+## Better handling of log_location with chef client service (Windows)
-Currently, the windows service manager passes in a default log_location to the Chef windows service at startup. Once the service is installed, this log_location overrides any log_location set in the client.rb. In 12.6.0, this behavior is changed to allow the Chef windows service to prefer the log_location in client.rb instead. Now, the windows service manager will not explicitly pass in a log_location, and therefore the Chef service will always use what is in the client.rb or the typical default path if none is configured. This enables scenarios such as logging to the Windows event log when running chef client as a Windows service.
+This change is for the scenario when running chef client as a Windows service. Currently, a default log_location gets used by the chef client windows service. This log_location overrides any log_location set in the client.rb. In 12.6.0, the behavior is changed to allow the Chef client running as a Windows service to prefer the log_location in client.rb instead. Now, the windows_service_manager will not explicitly pass in a log_location, and therefore the Chef service will always use what is in the client.rb or the typical default path if none is configured. This enables scenarios such as logging to the Windows event log when running chef client as a Windows service.
## Dsc_resource changes and fixes