[hcoop/debian/openafs.git] / doc / man-pages / pod5 / VolserLog.pod

=head1 NAME

VolserLog - Traces Volume Server operations

=head1 DESCRIPTION

The F<VolserLog> file records a trace of Volume Server (B<volserver>
process) operations on the local machine and describes any error
conditions it encounters.

If the VolserLog file does not already exist in the F</usr/afs/logs>
directory when the Volume Server starts, the server process creates it and
writes initial start-up messages to it.

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 file 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<VolserLog> file grant the required C<r>
(read) permission to all users.

The Volume Server records operations only as it completes them, and so
cannot recover from failures by reviewing the file. The log contents are
useful for administrative evaluation of process failures and other
problems.

=head1 SEE ALSO

L<UserList(5)>,
L<bos_getlog(8)>,
L<volserver(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.
Commit	Line	Data
805e021f CE	1	=head1 NAME
	2
	3	VolserLog - Traces Volume Server operations
	4
	5	=head1 DESCRIPTION
	6
	7	The F<VolserLog> file records a trace of Volume Server (B<volserver>
	8	process) operations on the local machine and describes any error
	9	conditions it encounters.
	10
	11	If the VolserLog file does not already exist in the F</usr/afs/logs>
	12	directory when the Volume Server starts, the server process creates it and
	13	writes initial start-up messages to it.
	14
	15	The file is in ASCII format. Administrators listed in the
	16	F</usr/afs/etc/UserList> file can use the B<bos getlog> command to display
	17	its contents. Alternatively, log onto the file server machine and use a
	18	text editor or a file display command such as the UNIX B<cat> command. By
	19	default, the mode bits on the F<VolserLog> file grant the required C<r>
	20	(read) permission to all users.
	21
	22	The Volume Server records operations only as it completes them, and so
	23	cannot recover from failures by reviewing the file. The log contents are
	24	useful for administrative evaluation of process failures and other
	25	problems.
	26
	27	=head1 SEE ALSO
	28
	29	L<UserList(5)>,
	30	L<bos_getlog(8)>,
	31	L<volserver(8)>
	32
	33	=head1 COPYRIGHT
	34
	35	IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
	36
	37	This documentation is covered by the IBM Public License Version 1.0. It was
	38	converted from HTML to POD by software written by Chas Williams and Russ
	39	Allbery, based on work by Alf Wachsmann and Elizabeth Cassell.