=back
+Finally, there is an entry specifying whether the BOS Server will start in
+restricted mode.
+
Although the F<BosConfig> file is in ASCII format, it is normally best not
to use a text editor to alter it. The parser is very picky, and
incorrectly formatted entries can prevent server startup in ways that are
=item *
+The B<bos getrestricted> command to display whether the BOS Server is running
+in restricted mode.
+
+=item *
+
The B<bos setrestart> command to set the times at which the BOS Server
performs automatic process restarts.
=item *
+The B<bos setrestricted> command to place the BOS Server in restricted mode.
+Since there is no command to revert this, setting the C<restrictmode>
+parameter back to 0 is only possible with an editor.
+
+=item *
+
The B<bos start> command to change an entry's status flag to C<Run> and
start the associated process.
L<bos_create(8)>,
L<bos_delete(8)>,
L<bos_getrestart(8)>,
+L<bos_getrestricted(8)>,
L<bos_restart(8)>,
L<bos_setrestart(8)>,
+L<bos_setrestricted(8)>,
L<bos_shutdown(8)>,
L<bos_start(8)>,
L<bos_startup(8)>,
The F</usr/afs/local/BosConfig> file defines which AFS server processes
run on the server machine, and whether the BOS Server restarts them
automatically if they fail. It also defines when all processes restart
-automatically (by default once per week), and when the BOS Server restarts
-processes that have new binary files (by default once per day). To
+automatically (by default once per week), when the BOS Server restarts
+processes that have new binary files (by default once per day), and
+whether the BOS Server will start in restricted mode. To
administer the F<BosConfig> file, use the following commands: B<bos
-create>, B<bos delete>, B<bos getrestart>, B<bos setrestart>, B<bos
-start>, and B<bos stop>.
+create>, B<bos delete>, B<bos getrestart>, B<bos getrestricted>, B<bos
+setrestart>, B<bos setrestricted>, B<bos start>, and B<bos stop>.
=item *