L<fs_rxstatproc(1)>,
L<fs_setacl(1)>,
L<fs_setcachesize(1)>,
-L<fs_setcbattr(1)>,
+L<fs_setcbaddr(1)>,
L<fs_setcell(1)>,
L<fs_setclientaddrs(1)>,
L<fs_setcrypt(1)>,
volume. By convention, the read/write path is indicated by placing a
period before the cell name at the pathname's second level (for example,
F</afs/.abc.com>). For further discussion of the concept of read/write and
-read-only paths through the filespace, see L<DESCRIPTION>.
+read-only paths through the filespace, see L</DESCRIPTION>.
=item B<-vol> <I<volume name>>
Granting the C<l> (lookup) and C<i> (insert) permissions without
granting the C<w> (write) and/or C<r> (read) permissions is a special
case, and grants rights approrpriate for "dropbox" directories. See the
-L<DROPBOXES> section for details.
+L</DROPBOXES> section for details.
If setting ACLs on a pathname in DFS filespace, see the DFS documentation
for the proper format and acceptable values for DFS ACL entries.
still remain to be written to the File Server when the Cache Manager
returns control to the application. It is useful if users working on the
machine commonly work with very large files, but also introduces the
-complications discussed in the L<CAUTIONS>.
+complications discussed in the L</CAUTIONS>.
Set either or both of the following in a single command:
To display the settings that currently apply to individual files or to all
files, provide the command's arguments in certain combinations as
-specified in L<OUTPUT>.
+specified in L</OUTPUT>.
=head1 CAUTIONS
Most often, this command is issued without arguments. The appropriate
password is for the person currently logged into the local system. The
-ticket's lifetime is calculated as described in L<DESCRIPTION>.
+ticket's lifetime is calculated as described in L</DESCRIPTION>.
% klog.krb5
Password for user@EXAMPLE.ORG:
Requests a specific lifetime for the token. Provide a number of hours and
optionally minutes and seconds in the format I<hh>[B<:>I<mm>[B<:>I<ss>]].
The value is used in calculating the token lifetime as described in
-L<DESCRIPTION>.
+L</DESCRIPTION>.
=item B<-setpag>
Most often, this command is issued without arguments. The appropriate
password is for the person currently logged into the local system. The
-ticket's lifetime is calculated as described in L<DESCRIPTION> (if no
+ticket's lifetime is calculated as described in L</DESCRIPTION> (if no
defaults have been changed, it is 25 hours for a user whose Authentication
Database entry was created in AFS 3.1 or later).
In the following, the issuer requests a ticket lifetime of 104 hours 30
minutes (4 days 8 hours 30 minutes). Presuming that this lifetime is
allowed by the maximum ticket lifetimes and other factors described in
-L<DESCRIPTION>, the token's lifetime is 110:44:28, which is the next
+L</DESCRIPTION>, the token's lifetime is 110:44:28, which is the next
largest possible value.
% klog -lifetime 104:30
B<-setpag> argument to the B<klog> command). If a PAG is not acquired, the
Cache Manager stores the token in a credential structure identified by
local UID rather than PAG. This creates the potential security exposure
-described in L<DESCRIPTION>.
+described in L</DESCRIPTION>.
If users of NFS client machines for which AFS is supported are to issue
this command as part of authenticating with AFS, do not use the B<fs
it is impossible to authenticate as a group or machine.
Similarly, some privacy flag settings do not have a sensible
-interpretation. L<OPTIONS> specifies the appropriate settings.
+interpretation. L</OPTIONS> specifies the appropriate settings.
=head1 OPTIONS
packet usage and availability, how many calls are waiting for a thread,
how many threads are free, and so on (this is the only information
provided by the B<-noconns> flag). Adding other options produces
-additional information as described in L<OPTIONS>. The output is intended
+additional information as described in L</OPTIONS>. The output is intended
for debugging purposes and is meaningful to someone familiar with the
implementation of Rx.
The scout command displays statistics gathered from the File Server
process running on each machine specified with the B<-server>
-argument. L<OUTPUT> explains the meaning of the statistics and describes
+argument. L</OUTPUT> explains the meaning of the statistics and describes
how they appear in the command shell, which is preferably a window managed
by a window manager program.
(brought online), which can happen either because the volume is extremely
damaged or because the Salvager functioned abnormally. Without this flag,
this command cannot remove volumes that are not attachable. See also
-L<CAUTIONS>.
+L</CAUTIONS>.
To remove the specified read/write volume's backup version at the same
time, include the B<-backup> flag.
jukebox or stacker, to mount a tape (insert it into the tape reader). The
operator must write the routine to invoke the mount command specified by
the device's manufacturer; AFS does not include any scripts, although an
-example appears in L<EXAMPLES>. The script or program inherits the Tape
+example appears in L</EXAMPLES>. The script or program inherits the Tape
Coordinator's AFS authentication status.
When the Tape Coordinator needs to mount a tape, it checks the
jukebox or stacker, to unmount a tape (remove it from the tape reader).
The operator must write the routine to invoke the unmount command
specified by the device's manufacturer; AFS does not include any scripts,
-although an example appears in L<EXAMPLES>. The script or program
+although an example appears in L</EXAMPLES>. The script or program
inherits the Tape Coordinator's AFS authentication status.
After closing a tape device, the Tape Coordinator checks the configuration
The administrator includes the following five lines in the
F</usr/afs/backup/CFG_stacker0.1> file. To review the meaning of each
-instruction, see L<DESCRIPTION>.
+instruction, see L</DESCRIPTION>.
MOUNT /usr/afs/backup/stacker0.1
UNMOUNT /usr/afs/backup/stacker0.1
The administrator includes the following lines in the
F</usr/afs/backup/CFG_HSM_device> file. To review the meaning of each
-instruction, see L<DESCRIPTION>.
+instruction, see L</DESCRIPTION>.
MOUNT /usr/afs/backup/file
FILE YES
To override the default chunk size for either type of cache, use the
B<-chunksize> argument to provide an integer to be used as an exponent of
-two; see L<OPTIONS> for details. For a memory cache, if total cache size
+two; see L</OPTIONS> for details. For a memory cache, if total cache size
divided by chunk size leaves a remainder, the B<afsd> program rounds down
the number of dcache entries, resulting in a slightly smaller cache.
Specifies the number of F<VI<n>> files to create in the cache directory
for a disk cache, overriding the default that is calculated as described
-in L<DESCRIPTION>. Each F<VI<n>> file accommodates a chunk of data, and
+in L</DESCRIPTION>. Each F<VI<n>> file accommodates a chunk of data, and
can grow to a maximum size of 64 KB by default. Do not combine this
argument with the B<-memcache> argument.
For the B<-volumes> argument, specify a combination of alphanumeric
characters and one or more metacharacters to wildcard part or all of the
-volume name. L<OPTIONS> lists the acceptable metacharacters.
+volume name. L</OPTIONS> lists the acceptable metacharacters.
=head1 CAUTIONS
has accessed all of the necessary tapes, each volume is only partially
written and is never brought online. It is best to restart the restore
operation from scratch to avoid possible inconsistencies. See also
-L<CAUTIONS>.
+L</CAUTIONS>.
=back
name> field of the output from the B<backup readlabel> command.
To write an AFS tape name on the label, provide a value for the B<-name>
-argument in the required format described in L<OPTIONS>. Include the
+argument in the required format described in L</OPTIONS>. Include the
B<-name> argument or the B<-pname> argument, but not both. If this
argument is omitted, the AFS tape name is set to C<< <NULL> >>, but the
Backup System automatically assigns the appropriate name when the tape is
The B<-n> flag produces a list of the volumes to be restored if the B<-n>
flag were not included, without actually restoring any volumes. See
-L<OUTPUT> for a detailed description of the output, and suggestions on how
+L</OUTPUT> for a detailed description of the output, and suggestions on how
to combine it most effectively with the B<-file> and B<-name> arguments.
The execution time for a B<backup volsetrestore> command depends on the
=item B<-n>
Displays a list of the volumes to be restored if the flag were not
-included, without actually restoring them. L<OUTPUT> details the format of
+included, without actually restoring them. L</OUTPUT> details the format of
the output. When combined with the B<-name> argument, its output is easily
edited for use as input to the B<-file> argument on a subsequent B<backup
volsetrestore> command.
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
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>>
L<UserList(5)>,
L<bos(8)>,
L<salvager(8)>,
-L<salvagserver(8)>,
+L<salvageserver(8)>,
L<vos_backup(1)>,
L<vos_release(1)>,
L<vos_remove(1)>,
If there are errors in the database, the output always reports them on the
standard error stream. If any options other than B<-database> or B<-help>
are provided, the output written to the standard output stream includes
-additional information as described for each option in L<OPTIONS>. The
+additional information as described for each option in L</OPTIONS>. The
output is intended for debugging purposes and is meaningful to someone
familiar with the internal structure of the Authentication Database.
The AFS distribution includes an example B<kpwvalid> program that checks
that the password is at least eight characters long; the code for it
-appears in L<EXAMPLES> below.
+appears in L</EXAMPLES> below.
The script or program must accept a sequence of password strings, one per
line, on the standard input stream. The first is the current password and
If there are errors in the database, the output always reports them on the
standard error stream. If any options other than B<-database> or B<-help>
are provided, the output written to the standard output stream includes
-additional information as described for each option in L<OPTIONS>. The
+additional information as described for each option in L</OPTIONS>. The
output is intended for debugging purposes and is meaningful to someone
familiar with the internal structure of the Protection Database.
L<BosConfig(5)>,
L<SalvageLog(5)>,
-L<Salvager(8)>,
+L<salvager(8)>,
L<bos_create(8)>,
L<bos_getlog(8)>,
L<bos_salvage(8)>,
If there are errors in the database, the output always reports them on the
standard error stream. If any options other than B<-database> or B<-help>
are provided, the output written to the standard output stream includes
-additional information as described for each option in L<OPTIONS>. The
+additional information as described for each option in L</OPTIONS>. The
output is intended for debugging purposes and is meaningful to someone
familiar with the internal structure of the VLDB.
By default, the command produces several line of statistics for each
volume. Adding other options produces or substitutes additional
-information as described in L<OPTIONS>. The output is intended for
+information as described in L</OPTIONS>. The output is intended for
debugging purposes and is meaningful to someone familiar with the internal
structure of volume headers.
git://git.openafs.org / openafs.git / commitdiff