for a demand-attach File Server will not work with a traditional File
Server. When switching from one File Server implementation to another,
remove the existing server process entry and create a new one. See
-L<EXAMPLES> below for an example of switching from a traditional File
+L</EXAMPLES> below for an example of switching from a traditional File
Server to a demand-attach File Server.
=head1 OPTIONS
=item dafs
The process that combines the Demand Attach File Server, Volume Server,
-Salvageserver and Salvager processes (B<fileserver>, B<volserver>,
-B<salvageserver>, and B<salvager>).
+Salvageserver and Salvager processes (B<dafileserver>, B<davolserver>,
+B<salvageserver>, and B<dasalvager>).
=item fs
The Protection Server process.
-=item runntp
-
-The controller process for the Network Time Protocol Daemon (obsolete).
-
=item upclientbin
The client portion of the Update Server process that retrieves binary
command's options, surround the entire command in double quotes (C<"">).
For the B<dafs> process, provide the complete pathname of the local disk
-binary file for each of the component processes: B<fileserver>,
-B<volserver>, B<salvageserver>, and B<salvager>, in that order. The
+binary file for each of the component processes: B<dafileserver>,
+B<davolserver>, B<salvageserver>, and B<dasalvager>, in that order. The
standard binary directory is F</usr/afs/bin>. If including any of an
initialization command's options, surround the entire command in double
quotes (C<"">).
Specifies the complete pathname on the local disk of a program that the
BOS Server invokes when the process terminates. The AFS distribution does
not include any notifier programs, but this argument is available for
-administrator use. See L<NOTES>.
+administrator use. See L</NOTES>.
=item B<-cell> <I<cell name>>
=item B<-localauth>
Constructs a server ticket using a key from the local
-F</usr/afs/etc/KeyFile> file. The B<bos> command interpreter presents the
+F</usr/afs/etc/KeyFile> or F</usr/afs/etc/KeyFileExt> file.
+The B<bos> command interpreter presents the
ticket to the BOS Server during mutual authentication. Do not combine this
flag with the B<-cell> or B<-noauth> options. For more details, see
L<bos(8)>.
=head1 EXAMPLES
The following command defines and starts the simple process
-C<ptserver> on the machine C<fs3.abc.com>:
+C<ptserver> on the machine C<fs3.example.com>:
- % bos create -server fs3.abc.com -instance ptserver -type simple \
+ % bos create -server fs3.example.com -instance ptserver -type simple \
-cmd /usr/afs/bin/ptserver
The following command defines and starts the simple process C<upclientbin>
-on the machine C<fs4.abc.com>. It references C<fs1.abc.com> as the source
-for updates to binary files, checking for changes to the F</usr/afs/bin>
-directory every 120 seconds.
+on the machine C<fs4.example.com>. It references C<fs1.example.com> as the
+source for updates to binary files, checking for changes to the
+F</usr/afs/bin> directory every 120 seconds.
- % bos create -server fs4.abc.com -instance upclientbin -type simple \
- -cmd "/usr/afs/bin/upclient fs1.abc.com -clear -t 120 \
+ % bos create -server fs4.example.com -instance upclientbin -type simple \
+ -cmd "/usr/afs/bin/upclient fs1.example.com -clear -t 120 \
/usr/afs/bin"
The following command creates the B<fs> process C<fs> on the machine
-C<fs4.abc.com> (a traditional File Server with associated processes). Type
+C<fs4.example.com> (a traditional File Server with associated processes). Type
the command on a single line.
- % bos create -server fs4.abc.com -instance fs -type fs \
+ % bos create -server fs4.example.com -instance fs -type fs \
-cmd /usr/afs/bin/fileserver /usr/afs/bin/volserver \
/usr/afs/bin/salvager
The following command creates the B<dafs> process C<dafs> on the machine
-C<fs4.abc.com> (a demand-attach File Server with associated processes).
+C<fs4.example.com> (a demand-attach File Server with associated processes).
Type the command on a single line.
- % bos create -server fs4.abc.com -instance dafs -type dafs \
- -cmd /usr/afs/bin/fileserver /usr/afs/bin/volserver \
- /usr/afs/bin/salvageserver /usr/afs/bin/salvager
+ % bos create -server fs4.example.com -instance dafs -type dafs \
+ -cmd /usr/afs/bin/dafileserver \
+ /usr/afs/bin/davolserver \
+ /usr/afs/bin/salvageserver /usr/afs/bin/dasalvager
The following command creates a cron process called C<userbackup> on the
-machine C<fs5.abc.com>, so that the BOS Server issues the indicated B<vos
+machine C<fs5.example.com>, so that the BOS Server issues the indicated B<vos
backupsys> command each day at 3:00 a.m. (the command creates a backup
version of every volume in the file system whose name begins with
C<user>). Note that the issuer provides the complete pathname to the
B<vos> command, includes the B<-localauth> flag on it, and types the
entire B<bos create> command on one line.
- % bos create -server fs5.abc.com -instance userbackup -type cron \
+ % bos create -server fs5.example.com -instance userbackup -type cron \
-cmd "/usr/afs/bin/vos backupsys -prefix user -localauth" 03:00
To switch from a traditional File Server to a demand-attach File Server,
% bos stop localhost fs -localauth
% bos delete localhost fs -localauth
% bos create localhost dafs dafs \
- "/usr/afs/bin/fileserver <fileserver-flags>" \
- "/usr/afs/bin/volserver <volserver-flags>" \
- /usr/afs/bin/salvageserver /usr/afs/bin/salvager
+ "/usr/afs/bin/dafileserver <fileserver-flags>" \
+ "/usr/afs/bin/davolserver <volserver-flags>" \
+ /usr/afs/bin/salvageserver /usr/afs/bin/dasalvager
replacing <fileserver-flags> and <volserver-flags> with the flags from the
previous configuration. This will stop the traditional File Server and
L<BosConfig(5)>,
L<KeyFile(5)>,
+L<KeyFileExt(5)>,
L<UserList(5)>,
L<bos(8)>,
L<buserver(8)>,
+L<dafileserver(8)>,
+L<dasalvager(8)>,
+L<davolserver(8)>,
L<fileserver(8)>,
L<kaserver(8)>,
L<ptserver(8)>,