Administering BNU

Performance log

The performance log contains statistics about the operation of uucico. uucico writes the log entries to /var/spool/uucp/.Admin/perflog. Statistics are collected only if perflog exists when uucico starts and is writable by uucico. The perflog file is not created automatically. The system administrator can therefore start or stop the collection of performance statistics by creating or removing the performance log file, or by making it writable or not writable by uucico. In processing terms, if the performance log file can be opened for writing, logging is performed; if the file cannot be opened for writing, logging is not performed. In either case, processing continues.

Two types of records are written to the file; each is identified by a mnemonic type at the beginning of the record. The fields of a record are separated by the ``|'' character. The record types are:

conn: contains statistics about the successful establishment of a connection
xfer: contains statistics about a file transfer

NOTE: Fields that are not applicable or unknown are marked by double quotes ("").

Their formats are as follows:

Connection (conn) performance log

An entry has the following format:

type stamp procID mach master remote device proto netw realt usert syst

where:

type: record type (always conn)
stamp: time stamp YYMMDDhhmmss for sorting
procID: uucico's process ID
mach: the name of the machine where the record was written
master: M = master, S = slave
remote: name of remote system
device: device name of media
proto: the protocol that was used for communications
netw: physical network ID (always "")
realt: real time to connect
usert: user time to connect
syst: system (kernel) time to connect

An example entry is:

conn 860516175047 23517 mach1 M ihnp1 DKH d "" 20.85 3.15 0.94

File transfer (xfer) performance log

An entry has the following format:

type grade stamp procID mach master remote device proto netwID \
jobID qtime turntime size command rstart ustart sstart \
rtrans utrans strans rterm uterm sterm status

where:

type: record type (always xfer)
grade: job grade ID
stamp: time stamp (YYMMDDhhmmss) for sorting
procID: uucico's process ID
mach: the name of the machine where the record was written
master: M = master, S = slave
remote: name of remote system
device: device name of media
proto: the protocol that was used for communications
netwID: physical network ID (always "")
jobID: job ID if master, "" if slave
qtime: time in seconds that job was in queue if master, "" if slave
turntime: turn around time in seconds if master, "" if slave
size: size of the file that was actually transferred successfully or partially because of transmission error
command: command line options if master, "" if slave
rstart: real time to start up transfer
ustart: user time to start up transfer
sstart: system (kernel) time to start up transfer
rtrans: real time to transfer file
utrans: user time to transfer file
strans: system (kernel) time to transfer file
rterm: real time to terminate the transfer
uterm: user time to terminate the transfer
sterm: system (kernel) time to terminate the transfer
status: ``PARTIAL FILE'' if the file was not completed because of transmission error; "" if the file was transmitted completely (as in this record)

An example entry is:

xfer N 860516175051 23517 mach1 M ihnp1 DKH d \
ihnp1N2c76 118.00 121.00 1000 -dc 0.08 0.00 \
0.04 0.91 0.06 0.13 0.22 0.02 0.06 ""

NOTE: Fields that are not applicable or unknown are marked by double quotes ("").

Start-up time includes the time for the master to search the queues for the next job, for the master and slave to exchange work vectors, and the time to open files.

Transfer time is the time it takes to transfer the data, close the file, and exchange confirmation messages.

Termination time is the time it takes to send mail notifications and write status files.

Turnaround time is the difference between the time that the job was queued and the time that the final notification was sent.