.\" -*- mode: troff; coding: utf-8 -*-
.\" Automatically generated by Pod::Man 5.01 (Pod::Simple 3.43)
.\"
.\" Standard preamble:
.\" ========================================================================
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.de Vb \" Begin verbatim text
.ft CW
.nf
.ne \\$1
..
.de Ve \" End verbatim text
.ft R
.fi
..
.\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
.ie n \{\
.    ds C` ""
.    ds C' ""
'br\}
.el\{\
.    ds C`
.    ds C'
'br\}
.\"
.\" Escape single quotes in literal strings from groff's Unicode transform.
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\"
.\" If the F register is >0, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
.\" entries marked with X<> in POD.  Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.\"
.\" Avoid warning from groff about undefined register 'F'.
.de IX
..
.nr rF 0
.if \n(.g .if rF .nr rF 1
.if (\n(rF:(\n(.g==0)) \{\
.    if \nF \{\
.        de IX
.        tm Index:\\$1\t\\n%\t"\\$2"
..
.        if !\nF==2 \{\
.            nr % 0
.            nr F 2
.        \}
.    \}
.\}
.rr rF
.\" ========================================================================
.\"
.IX Title "BUTC_LOGS 5"
.TH BUTC_LOGS 5 2024-03-20 OpenAFS "AFS File Reference"
.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
.nh
.SH NAME
butc_logs \- Message logs from the Tape Coordinator process
.SH DESCRIPTION
.IX Header "DESCRIPTION"
The Backup System Tape Coordinator (\fBbutc\fR) process generates two log
files per device, one for error messages and one for actions.
.SS "Error Message Log"
.IX Subsection "Error Message Log"
The \fITE_device_name\fR file logs error messages generated by the Backup
System Tape Coordinator that controls the tape device or backup data file
indicated by \fIdevice_name\fR.
.PP
As the Tape Coordinator initializes, it creates the file in ASCII format
in the \fI/var/lib/openafs/backup\fR directory. If there is an existing file, the
Tape Coordinator renames it to \fITE_device_name.old\fR>, overwriting the
existing \fITE_device_name.old\fR> file if it exists.
.PP
For a tape device, the Tape Coordinator derives the variable
\&\fIdevice_name\fR portion of the filename from the device pathname listed in
the local \fI/var/lib/openafs/backup/tapeconfig\fR file, by stripping off the initial
\&\f(CW\*(C`/dev/\*(C'\fR string and replacing any other slashes in the name with
underscores. For example, the filename for a device called \fI/dev/rmt/4m\fR
is \fITE_rmt_4m\fR. Similarly, for a backup data file the Tape Coordinator
strips off the initial slash (\f(CW\*(C`/\*(C'\fR) and replaces any other slashes in the
name with underscores. For example, the filename for a backup data file
called \fI/var/tmp/FILE\fR is \fITE_var_tmp_FILE\fR.
.PP
The messages in the file describe the error and warning conditions the
Tape Coordinator encounters as it operates. For instance, a message can
list the volumes that are inaccessible during a dump operation, or warn
that the Tape Coordinator is overwriting a tape or backup data file. The
messages also appear in the \fI/var/lib/openafs/backup/TL_device_name\fR file,
which traces most of the Tape Coordinator's actions.
.SS "Action Log"
.IX Subsection "Action Log"
The \fITL_device_name\fR file logs the actions performed by the Backup
System Tape Coordinator that controls the tape device or backup data file
indicated by \fIdevice_name\fR. It also records the same error and warning
messages written to the \fITE_device_name\fR file.
.PP
As the Tape Coordinator initializes, it creates the file in ASCII format
in the \fI/var/lib/openafs/backup\fR directory. If there is an existing file, the
Tape Coordinator renames it to \fITL_device_name.old\fR, overwriting the
existing \fITL_device_name.old\fR file if it exists.
.PP
For a tape device, the Tape Coordinator derives the variable
\&\fIdevice_name\fR portion of the filename from the device pathname listed in
the local \fI/var/lib/openafs/backup/tapeconfig\fR file, by stripping off the initial
\&\f(CW\*(C`/dev/\*(C'\fR string and replacing any other slashes in the name with
underscores. For example, the filename for a device called \fI/dev/rmt/4m\fR
is \fITL_rmt_4m\fR. Similarly, for a backup data file the Tape Coordinator
strips off the initial slash (\f(CW\*(C`/\*(C'\fR) and replaces any other slashes in the
name with underscores. For example, the filename for a backup data file
called \fI/var/tmp/FILE\fR is \fITL_var_tmp_FILE\fR.
.SH "SEE ALSO"
.IX Header "SEE ALSO"
\&\fBtapeconfig\fR\|(5),
\&\fBbutc\fR\|(8)
.SH COPYRIGHT
.IX Header "COPYRIGHT"
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved.
.PP
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.