Russ Allbery d053825374 STABLE14-man-page-conversion-20051208
This is the initial conversion of the AFS Adminstrators Reference into POD
for use as man pages.  The man pages are now generated via pod2man from
regen.sh so that only those working from CVS have to have pod2man
available.  The Makefile only installs.  The pages have also been sorted
out into pod1, pod5, and pod8 directories, making conversion to the right
section of man page easier without maintaining a separate list and allowing
for names to be duplicated between pod5 and pod1 or pod8 (which will likely
be needed in a few cases).

This reconversion is done with a new script based on work by Chas Williams.
In some cases, the output is worse than the previous POD pages, but this is
a more comprehensive conversion.

This is only the first step, and this initial conversion has various
problems.  In addition, the file man pages that didn't have simple names
have not been converted in this pass and will be added later.  Some of the
man pages have syntax problems and all of them have formatting errors.  The
next editing pass, coming shortly, will clean up most of the remaining
mess.


(cherry picked from commit e3dfba8e6c10c296c09e9b0ac0c0355658ce0be7)
2006-01-05 18:28:16 +00:00

65 lines
2.2 KiB
Plaintext

=head1 NAME
VLLog - Traces Volume Location Server operations
=head1 DESCRIPTION
The VLLog file records a trace of Volume Location (VL) Server
(B<vlserver> process) operations on the local machine and describes
any error conditions it encounters.
If the VLLog file does not already exist in the
B</usr/afs/logs> directory when the VL Server starts, the server
process creates it and writes initial start-up messages to it. If there
is an existing file, the VL Server renames it to B<VLLog.old>,
overwriting the existing B<VLLog.old> file if it exists.
The file is in ASCII format. Administrators listed in the
B</usr/afs/etc/UserList> file can use the B<bos getlog>
command to display its contents. Alternatively, log onto the server
machine and use a text editor or a file display command such as the UNIX
B<cat> command. By default, the mode bits on the
B<VLLog> file grant the required B<r> (B<read>)
permission to all users.
The VL Server records operations only as it completes them, and cannot
recover from failures by reviewing the file. The log contents are
useful for administrative evaluation of process failures and other
problems.
The VL Server can record messages at three levels of detail. By
default, it records only very rudimentary messages. To increase logging
to the first level of detail, issue the following command while logged onto
the database server machine as the local superuser B<root>.
# kill -TSTP I<vlserver_pid>
where I<vlserver_pid> is the process ID of the vlserver
process, as reported in the output from the standard UNIX B<ps>
command. To increase to the second and third levels of detail, repeat
the command.
To disable logging, issue the following command.
# kill -HUP I<vlserver_pid>
To decrease the level of logging, first completely disable it and then
issue the B<kill -TSTP> command as many times as necessary to reach
the desired level.
=head1 SEE ALSO
L<UserList(1)>,
L<bos_getlog(1)>,
L<vlserver(1)>
=head1 COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
This documentation is covered by the IBM Public License Version 1.0. It was
converted from HTML to POD by software written by Chas Williams and Russ
Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.