From e47d97c8ae316c90ecb636a497c52cdb9a27a935 Mon Sep 17 00:00:00 2001 From: Andrew Deason Date: Tue, 15 Apr 2014 12:30:19 -0500 Subject: [PATCH] doc: Clarify some BosConfig.new text It is not always clear to users whether BosConfig.new is noticed during an automatic restart, or if it requires stopping and starting the bosserver. Slightly reword the relevant text and add a small note that a "general restart" does cause BosConfig.new to be noticed, so this is explicitly clear. Reviewed-on: http://gerrit.openafs.org/11076 Reviewed-by: Andrew Deason Tested-by: BuildBot Reviewed-by: Jeffrey Altman (cherry picked from commit 3946b50a7ecdfd34681ab471863929b2f82aff4b) Change-Id: Ia630aec6ef5259fc3c3fd531fdf8fda8a4152c54 Reviewed-on: http://gerrit.openafs.org/11216 Tested-by: BuildBot Reviewed-by: Ken Dreyer Reviewed-by: Andrew Deason Reviewed-by: Stephan Wiesand --- doc/man-pages/pod5/BosConfig.pod | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/doc/man-pages/pod5/BosConfig.pod b/doc/man-pages/pod5/BosConfig.pod index e17278901d..b610cee0c5 100644 --- a/doc/man-pages/pod5/BosConfig.pod +++ b/doc/man-pages/pod5/BosConfig.pod @@ -213,8 +213,11 @@ The B command starts a process. When the BOS Server shuts down, it rewrites F, discarding any changes made manually to that file. To change the configuration for the next BOS Server restart, instead write a new file to F. If -F exists when the BOS Server starts, it will rename that -file to F before reading its configuration. +F exists when the BOS Server starts, F will be +replaced by F before the BOS Server reads its configuration. +Note that the BOS Server will notice a new F file whenever the +I time is reached, if one is configured, since the BOS Server +restarts itself at that time. =head1 SEE ALSO