mirror of
https://git.openafs.org/openafs.git
synced 2025-01-19 07:20:11 +00:00
f64a78e701
This completes the first editing pass of the man pages. Very little content editing has been done, but the server and client versions of various man pages have been combined into a single man page for the file (affects CellServDB, ThisCell, NetInfo, and NetRestrict), the descriptions of the various AFS cache files have been combined into one afs_cache man page, and the descriptions of the two butc log files have been combined into one butc_logs man page. For man pages for databases with two files, symlinks are now created on installation for the secondary file name. All of the man pages should now be ready for public review, additional editing and cleanup, and content editing.
60 lines
2.2 KiB
Plaintext
60 lines
2.2 KiB
Plaintext
=head1 NAME
|
|
|
|
VLLog - Traces Volume Location Server operations
|
|
|
|
=head1 DESCRIPTION
|
|
|
|
The F<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 F<VLLog> file does not already exist in the
|
|
F</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 F<VLLog.old>,
|
|
overwriting the existing F<VLLog.old> file if it exists.
|
|
|
|
The file is in ASCII format. Administrators listed in the
|
|
F</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 F<VLLog> file grant the required C<r> (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 C<root>.
|
|
|
|
# kill -TSTP <vlserver_pid>
|
|
|
|
where <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 <vlserver_pid>
|
|
|
|
To decrease the level of logging, first completely disable it and then
|
|
issue the C<kill -TSTP> command as many times as necessary to reach the
|
|
desired level.
|
|
|
|
=head1 SEE ALSO
|
|
|
|
L<UserList(5)>,
|
|
L<bos_getlog(8)>,
|
|
L<vlserver(8)>
|
|
|
|
=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.
|