diff options
| author | Bryan McLellan <btm@loftninjas.org> | 2017-05-31 15:29:35 -0400 |
|---|---|---|
| committer | Bryan McLellan <btm@loftninjas.org> | 2017-05-31 20:45:42 -0400 |
| commit | f089c8a94e2db502c381efda4fc0268ad928326f (patch) | |
| tree | a393cde3789a34acc8114bc95abdae4719e86490 | |
| parent | a1e38709047c3afd0ad6ced65e959b68a37075a5 (diff) | |
| download | chef-btm/release-hup.tar.gz | |
Add release notes related to SIGHUP changes [ci skip]btm/release-hup
Signed-off-by: Bryan McLellan <btm@loftninjas.org>
| -rw-r--r-- | RELEASE_NOTES.md | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md index 9cf4783024..9f04749633 100644 --- a/RELEASE_NOTES.md +++ b/RELEASE_NOTES.md @@ -2,6 +2,18 @@ _This file holds "in progress" release notes for the current release under devel # Chef Client Release Notes +# 13.2 + +## Reconfigure between runs when daemonized + +When Chef performs a reconfigure, it re-reads the configuration files. It also re-opens its log files, which facilitates log file rotation. + +Chef normally will reconfigure when sent a HUP signal. As of this release if you send a HUP signal while it is converging, the reconfigure +happens at the end of the run. This is avoids potential Ruby issues when the configuration file contains additional Ruby code that is executed. +While the daemon is sleeping between runs, sending a SIGHUP will still cause an immediate reconfigure. + +Additionally, Chef now always performs a reconfigure after every run when daemonized. + # 13.1 ## Socketless local mode by default |