From: Andrew Deason Date: Tue, 15 Apr 2014 17:30:19 +0000 (-0500) Subject: doc: Clarify some BosConfig.new text X-Git-Tag: upstream/1.8.0_pre1^2~709 X-Git-Url: https://git.michaelhowe.org/gitweb/?a=commitdiff_plain;h=3946b50a7ecdfd34681ab471863929b2f82aff4b;p=packages%2Fo%2Fopenafs.git 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. Change-Id: Iab3eaff176305b0b2991a6636e70204b5072b1b0 Reviewed-on: http://gerrit.openafs.org/11076 Reviewed-by: Andrew Deason Tested-by: BuildBot Reviewed-by: Jeffrey Altman --- diff --git a/doc/man-pages/pod5/BosConfig.pod b/doc/man-pages/pod5/BosConfig.pod index e17278901..b610cee0c 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