Provided by: openafs-client_1.4.12+dfsg-3_i386 bug

NAME

       butc_logs - Message logs from the Tape Coordinator process

DESCRIPTION

       The Backup System Tape Coordinator (butc) process generates two log
       files per device, one for error messages and one for actions.

   Error Message Log
       The TE_device_name file logs error messages generated by the Backup
       System Tape Coordinator that controls the tape device or backup data
       file indicated by device_name.

       As the Tape Coordinator initializes, it creates the file in ASCII
       format in the /var/lib/openafs/backup directory. If there is an
       existing file, the Tape Coordinator renames it to TE_device_name.old>,
       overwriting the existing TE_device_name.old> file if it exists.

       For a tape device, the Tape Coordinator derives the variable
       device_name portion of the filename from the device pathname listed in
       the local /var/lib/openafs/backup/tapeconfig file, by stripping off the
       initial "/dev/" string and replacing any other slashes in the name with
       underscores. For example, the filename for a device called /dev/rmt/4m
       is TE_rmt_4m. Similarly, for a backup data file the Tape Coordinator
       strips off the initial slash ("/") and replaces any other slashes in
       the name with underscores. For example, the filename for a backup data
       file called /var/tmp/FILE is TE_var_tmp_FILE.

       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 /var/lib/openafs/backup/TL_device_name
       file, which traces most of the Tape Coordinator’s actions.

   Action Log
       The TL_device_name file logs the actions performed by the Backup System
       Tape Coordinator that controls the tape device or backup data file
       indicated by device_name. It also records the same error and warning
       messages written to the TE_device_name file.

       As the Tape Coordinator initializes, it creates the file in ASCII
       format in the /var/lib/openafs/backup directory. If there is an
       existing file, the Tape Coordinator renames it to TL_device_name.old,
       overwriting the existing TL_device_name.old file if it exists.

       For a tape device, the Tape Coordinator derives the variable
       device_name portion of the filename from the device pathname listed in
       the local /var/lib/openafs/backup/tapeconfig file, by stripping off the
       initial "/dev/" string and replacing any other slashes in the name with
       underscores. For example, the filename for a device called /dev/rmt/4m
       is TL_rmt_4m. Similarly, for a backup data file the Tape Coordinator
       strips off the initial slash ("/") and replaces any other slashes in
       the name with underscores. For example, the filename for a backup data
       file called /var/tmp/FILE is TL_var_tmp_FILE.

SEE ALSO

       tapeconfig(5), butc(8)

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.