3 bosserver - Initializes the BOS Server
13 S<<< [B<-enable_peer_stats>] >>>
14 S<<< [B<-auditlog> <I<log path>>] >>>
15 S<<< [B<-audit-interface> ( file | sysvmq )] >>>
16 S<<< [B<-enable_process_stats>] >>>
17 S<<< [B<-allow-dotted-principals>] >>>
18 S<<< [B<-cores>[=none|<I<path>>]] >>>
19 S<<< [B<-restricted>] >>>
20 S<<< [B<-rxmaxmtu> <I<bytes>>] >>>
22 S<<< [B<-syslog>[=<I<facility>>]>] >>>
23 S<<< [B<-pidfiles>[=<I<path>>]] >>>
32 The bosserver command initializes the Basic OverSeer (BOS) Server
33 (B<bosserver> process). In the conventional configuration, the binary file
34 is located in the F</usr/afs/bin> directory on a file server machine.
36 The BOS Server must run on every file server machine and helps to automate
37 file server administration by performing the following tasks:
43 Monitors the other AFS server processes on the local machine, to make sure
44 they are running correctly.
48 Automatically restarts failed processes, without contacting a human
49 operator. When restarting multiple server processes simultaneously, the
50 BOS Server takes interdependencies into account and initiates restarts in
55 Processes commands from the bos suite that administrators issue to verify
56 the status of server processes, install and start new processes, stop
57 processes either temporarily or permanently, and restart halted processes.
61 Manages system configuration information: the files that list the cell's
62 server encryption keys, database server machines, and users privileged to
63 issue commands from the B<bos> and B<vos> suites.
67 The BOS Server is configured via the F<BosConfig> configuration file.
68 Normally, this file is managed via the B<bos> command suite rather than
69 edited directly. See the L<BosConfig(5)> man page for the syntax of this
72 The BOS Server will rewrite B<BosConfig> when shutting down, so changes
73 made manually to it will be discarded. Instead, to change the BOS Server
74 configuration only for the next restart of B<bosserver>, create a file
75 named F</usr/afs/local/BosConfig.new>. If B<BosConfig.new> exists when
76 B<bosserver> starts, it is renamed to F</usr/afs/local/BosConfig>,
77 removing any existing file by that name, before B<bosserver> reads its
80 The BOS Server logs a default set of important events in the file
81 F</usr/afs/logs/BosLog>. To record the name of any user who performs a
82 privileged B<bos> command (one that requires being listed in the
83 F</usr/afs/etc/UserList> file), add the B<-log> flag. To display the
84 contents of the B<BosLog> file, use the B<bos getlog> command.
86 The first time that the BOS Server initializes on a server machine, it
87 creates several files and subdirectories in the local F</usr/afs>
88 directory, and sets their mode bits to protect them from unauthorized
89 access. Each time it restarts, it checks that the mode bits still comply
90 with the settings listed in the following chart. A question mark indicates
91 that the BOS Server initially turns off the bit (sets it to the hyphen),
92 but does not check it at restart.
95 /usr/afs/backup drwx???---
96 /usr/afs/bin drwxr?xr-x
97 /usr/afs/db drwx???---
98 /usr/afs/etc drwxr?xr-x
99 /usr/afs/etc/KeyFile -rw????---
100 /usr/afs/etc/UserList -rw?????--
101 /usr/afs/local drwx???---
102 /usr/afs/logs drwxr?xr-x
104 If the mode bits do not comply, the BOS Server writes the following
105 warning to the F<BosLog> file:
107 Bosserver reports inappropriate access on server directories
109 However, the BOS Server does not reset the mode bits, so the administrator
110 can set them to alternate values if desired (with the understanding that
111 the warning message then appears at startup).
113 This command does not use the syntax conventions of the AFS command
114 suites. Provide the command name and all option names in full.
122 Turns off all authorization checks, and allows all connecting users to act as
123 administrators, even unauthenticated users. The use of this option is
124 inherently insecure, and should only be used in controlled environments for
125 experimental or debug purposes. See L<NoAuth(5)>.
129 Records in the F</usr/afs/logs/BosLog> file the names of all users who
130 successfully issue a privileged B<bos> command (one that requires being
131 listed in the F</usr/afs/etc/UserList> file).
133 =item B<-cores=>none|<I<path>>
135 The argument none turns off core file generation. Otherwise, the
136 argument is a path where core files will be stored.
138 =item B<-auditlog> <I<log path>>
140 Turns on audit logging, and sets the path for the audit log. The audit
141 log records information about RPC calls, including the name of the RPC
142 call, the host that submitted the call, the authenticated entity (user)
143 that issued the call, the parameters for the call, and if the call
146 =item B<-audit-interface> (file | sysvmq)
148 Specifies what audit interface to use. Defaults to C<file>. See
149 L<fileserver(8)> for an explanation of each interface.
151 =item B<-enable_peer_stats>
153 Activates the collection of Rx statistics and allocates memory for their
154 storage. For each connection with a specific UDP port on another machine,
155 a separate record is kept for each type of RPC (FetchFile, GetStatus, and
156 so on) sent or received. To display or otherwise access the records, use
157 the Rx Monitoring API.
159 =item B<-enable_process_stats>
161 Activates the collection of Rx statistics and allocates memory for their
162 storage. A separate record is kept for each type of RPC (FetchFile,
163 GetStatus, and so on) sent or received, aggregated over all connections to
164 other machines. To display or otherwise access the records, use the Rx
167 =item B<-allow-dotted-principals>
169 By default, the RXKAD security layer will disallow access by Kerberos
170 principals with a dot in the first component of their name. This is to avoid
171 the confusion where principals user/admin and user.admin are both mapped to the
172 user.admin PTS entry. Sites whose Kerberos realms don't have these collisions
173 between principal names may disable this check by starting the server
178 In normal operation, the bos server allows a super user to run any command.
179 When the bos server is running in restricted mode (either due to this
180 command line flag, or when configured by L<bos_setrestricted(8)>) a number
181 of commands are unavailable. Note that this flag persists across reboots.
182 Once a server has been placed in restricted mode, it can only be opened up
183 by sending the SIGFPE signal.
185 =item B<-rxmaxmtu> <I<bytes>>
187 Sets the maximum transmission unit for the RX protocol.
191 Bind the Rx socket to the primary interface only. If not specified, the
192 Rx socket will listen on all interfaces.
194 =item B<-syslog>[=<I<facility>>]>
196 Specifies that logging output should go to syslog instead of the normal
197 log file. B<-syslog>=I<facility> can be used to specify to which facility
198 the log message should be sent.
200 =item B<-pidfiles>[=<I<path>>]
202 Create a one-line file containing the process id (pid) for each non-cron
203 process started by the BOS Server. This file is removed by the BOS Server when
204 the process exits. The optional <I<path>> argument specifies the path where
205 the pid files are to be created. The default location is C</usr/afs/local>.
207 The name of the pid files for C<simple> BOS Server process types are the BOS
208 Server instance name followed by C<.pid>.
210 The name of the pid files for C<fs> and C<dafs> BOS Server process types are
211 the BOS Server type name, C<fs> or C<dafs>, followed by the BOS Server core
212 name of the process, followed by C<.pid>. The pid file name for the
213 C<fileserver> process is C<fs.file.pid>. The pid file name for the C<volserver>
216 BOS Server instance names are specfied using the B<bos create> command. See
217 L<bos_create> for a description of the BOS Server process types and instance
222 Run the BOS Server in the foreground. By default, the BOS Server process will
223 fork and detach the stdio, stderr, and stdin streams.
227 Prints the online help for this command. All other valid options are
234 The following command initializes the BOS Server and logs the names of
235 users who issue privileged B<bos> commands.
239 =head1 PRIVILEGE REQUIRED
241 The issuer most be logged onto a file server machine as the local
252 L<bos_getrestart(8)>,
254 L<bos_setrestricted(8)>,
263 IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
265 This documentation is covered by the IBM Public License Version 1.0. It was
266 converted from HTML to POD by software written by Chas Williams and Russ
267 Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.