Several small fixes for spelling and grammar.
Change-Id: I5c1cbc933cd683f997b8bb649408d57d84a110f2
Reviewed-on: http://gerrit.openafs.org/3890
Reviewed-by: Derrick Brashear <shadow@dementia.org>
Tested-by: Derrick Brashear <shadow@dementia.org>
=head1 PRIVILEGE REQUIRED
-No special priviledges are required for this command.
+No special privileges are required for this command.
=head1 SEE ALSO
If a mount point resides in a read/write volume and the volume name does
not have a C<.readonly> or a C<.backup> extension, the Cache Manager
-attempts to access only the a read/write version of the volume. The access
+attempts to access only the read/write version of the volume. The access
attempt fails with an error if the read/write version is inaccessible,
even if a read-only version is accessible. In this situation the Cache
Manager is said to be on a I<read/write path> and cannot switch back to
% fs newalias -alias openafs -name openafs.org
Both of the above examples create an alias C<openafs> for the cell
-C<openafs.org>. Two links wil be created in F</afs>:
+C<openafs.org>. Two links will be created in F</afs>:
/afs/openafs -> /afs/openafs.org
/afs/.openafs -> /afs/.openafs.org
The Cache Manager sets default VL Server preference ranks as it
initializes, randomly assigning a rank from the range 10,000 to 10,126 to
-each of the machines liste din the local F</usr/vice/etc/CellServDB>
+each of the machines listed in the local F</usr/vice/etc/CellServDB>
file. If DNS is used to locate VL Servers, the Cache Manager will assign a
rank to every server configured in an AFSDB or SRV record for that
cell. Currently, the priority and weight information from SRV records is
List the groups to which each group specified by the B<-nameorid>
argument belongs, in addition to user and machine members. Group
-membership may be nested when B<ptserver> is compilied with the
+membership may be nested when B<ptserver> is compiled with the
SUPERGROUPS option enabled.
=item B<-expandgroups>
are members due to nested groups, for each group specified by the B<-nameorid>
argument.
-Group membership may be nested when B<ptserver> is compilied with the
+Group membership may be nested when B<ptserver> is compiled with the
SUPERGROUPS option enabled.
=include fragments/pts-common.pod
=item auth
-Cconnections at authentication level rxkad_auth
+Connections at authentication level rxkad_auth
=item clear
stack will grow linearly with respect to the number of nodes in the list
(so it's wise to increase the Rx LWP stack if huge amounts of data are
expected back -- default stack size is 4K). The advantages should
-outweight the disadvantages here.
+outweigh the disadvantages here.
It's important to pay attention to the comments of the three array
examples above particularly when they're references to when the user
does not query the Cache Manager for the current value and it does not
report sysname lists. If you have changed the local system type with B<fs
sysname>, or if you run a version of B<sys> compiled differently than the
-Cache Manager running on the system, the value retured will not match the
+Cache Manager running on the system, the value returned will not match the
behavior of the Cache Manager. The only reason to use B<sys> is that
B<livesys> wasn't available in older versions of AFS.
=item B<-partition> <I<partition name>>
Specifies the partition where the VLDB should believe the volume resides.
-entries. Provide the B<-server> argument along with this one. Provide the
+Provide the B<-server> argument along with this one. Provide the
partition's complete name with preceding slash (for example, C</vicepa>)
or use one of the three acceptable abbreviated forms. For details, see
L<vos(1)>.
parent volume. Cloning is a primitive operation that is used by the B<vos
move>, B<vos backup>, and B<vos release> commands. A clone functions using
the same mechanism as a backup volume, but it is persistent. Clone volumes
-can be used as point-in-time copies of the parent vollume, but they must be
+can be used as point-in-time copies of the parent volume, but they must be
used with care.
=head1 CAUTIONS
=head1 DESCRIPTION
-Ths B<vos endtrans> command ends a specific transaction on the Volume
+The B<vos endtrans> command ends a specific transaction on the Volume
Server for a specific volume. Under normal operation this command should
never need to be used, but it can be useful to reduce the amount of time
a volume is offline after an accidental command, or a L<B<vos>|vos(1)>
(C<< > >>), followed immediately by the cell's name without an intervening
space. Optionally, a comment can follow any number of spaces and a octothorpe
(C<#>), perhaps to identify the organization associated with the
-cell. A variant of this allows the defintion of a linked cell: after the
+cell. A variant of this allows the definition of a linked cell: after the
leading (C<< > >>) and cell name, a space and a second cell name may be
listed before the optional spaces, octothorpe and comment.
Optionally, the File Server can be forced to use an IP address that does
not belong to one of the server interfaces. To do this, add a line to the
F<NetInfo> file with the IP address prefixed with "f" and a space. This is
-useful when the File Server is on the interal side of a NAT firewall.
+useful when the File Server is on the internal side of a NAT firewall.
To display the File Server interface addresses registered in the VLDB, use
the B<vos listaddrs> command.
The B<afsd> command initializes the Cache Manager on an AFS client machine
by transferring AFS-related configuration information into kernel memory
and starting several daemons. B<afsd.fuse> is an experimental variant that
-inititalizes a FUSE-based Cache Manager instead of one based on a kernel
+initializes a FUSE-based Cache Manager instead of one based on a kernel
module.
The B<afsd> command performs the following actions:
=head1 COPYRIGHT
-Copyright 2009 Simon wilkinson <simon@sxw.org.uk>
+Copyright 2009 Simon Wilkinson <simon@sxw.org.uk>
This documentation is covered by the BSD License as written in the
doc/LICENSE file. This man page was written by Simon Wilkinson for
a password from standard input, convert it to a key, and add it to the
F<KeyFile>; list the keys in the F<KeyFile>; or remove a key from thet
F<KeyFile>. It is very similar in function to B<asetkey>, but B<asetkey>
-works with keytab files wheras B<bos_util> works with passwords directly.
+works with keytab files whereas B<bos_util> works with passwords directly.
B<bos_util> expects one of the following subcommands:
=item B<-vattachpar> <I<number of volume attach threads>>
The number of threads assigned to attach and detach volumes. The default
-is 1. Warning: many of the I/O parallism features of Demand-Attach
+is 1. Warning: many of the I/O parallelism features of Demand-Attach
Fileserver are turned off when the number of volume attach threads is only
1.
=head1 EXAMPLES
-Forward AFS Authentication Server reqests to the B<fakeka> servers on
+Forward AFS Authentication Server requests to the B<fakeka> servers on
kdc1.example.com and kdc2.example.com:
% ka-forwarder kdc1.example.com kdc2.example.com &
authentication attempts is exceeded, following the string C<The lock time
for this user is>. Use the B<kas> command's B<-locktime> argument to set
the lockout time. This line appears only if a limit on the number of
-unsuccessful authentication attempts has been set with the the B<kas
+unsuccessful authentication attempts has been set with the B<kas
setfields> command's B<-attempts> argument.
=item *
Sets one or more of four toggling flags, adding them to any flags
currently set. Either specify one or more of the following strings, or
-specify a hexidecimal number that combines the indicated values. To return
+specify a hexadecimal number that combines the indicated values. To return
all four flags to their defaults, provide a value of C<0> (zero). To set
more than one flag at once using the strings, connect them with plus signs
(example: C<NOTGS+ADMIN+CPW>). To remove all the current flag settings
output is intended for debugging purposes and is meaningful to someone
familiar with the internal structure of the VLDB.
-The B<-quiet> option can be used to supress the standard output stream
+The B<-quiet> option can be used to suppress the standard output stream
so that the command can be used more easily inside scripts.
The command exits with one of the following completion codes: