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 <adeason@sinenomine.net>
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Jeffrey Altman <jaltman@your-file-system.com>
(cherry picked from commit
3946b50a7ecdfd34681ab471863929b2f82aff4b)
Change-Id: Ia630aec6ef5259fc3c3fd531fdf8fda8a4152c54
Reviewed-on: http://gerrit.openafs.org/11216
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Ken Dreyer <ktdreyer@ktdreyer.com>
Reviewed-by: Andrew Deason <adeason@sinenomine.net>
Reviewed-by: Stephan Wiesand <stephan.wiesand@desy.de>
When the BOS Server shuts down, it rewrites F<BosConfig>, 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<BosConfig.new>. If
-F<BosConfig.new> exists when the BOS Server starts, it will rename that
-file to F<BosConfig> before reading its configuration.
+F<BosConfig.new> exists when the BOS Server starts, F<BosConfig> will be
+replaced by F<BosConfig.new> before the BOS Server reads its configuration.
+Note that the BOS Server will notice a new F<BosConfig.new> file whenever the
+I<general restart> time is reached, if one is configured, since the BOS Server
+restarts itself at that time.
=head1 SEE ALSO