.ig
################################################################################
#
# File:         udtd.1
# RCS:          $Revision: 1.8 $
#               $Date: 99/07/20 07:16:51 $
# ClearCase:    main/9
# Description:  ttd man pages
#
# (c) Copyright 1989-2005, Hewlett-Packard Company, all rights reserved.
#
################################################################################
.\" @(#) $Header: ttd.1,v main/9 99/07/20 07:16:51 markk Exp $
..
.TH ttd 1
.ds )H Hewlett-Packard Company
.ds ]W HP Measurement Interface
.SH NAME
ttd - transaction tracking registration daemon.
.SH SYNOPSIS
.BR ttd 
[options]
.SH DESCRIPTION
The  
.I transaction tracking
daemon,
.B ttd,
reads and registers transaction definitions 
from the configuration file
.B /var/opt/perf/ttd.conf.
The
.B ttd
also assigns IDs to the transaction names passed to it via
.B arm_getid
calls that come from the ARM library. The
.B ttd 
synchronizes these transaction definitions with the
HP \fIMeasurement Interface\fP daemon process,
.B midaemon.

You must execute the registration daemon,
.B ttd,
as root or with the set-user-id bit set to root.
.B ttd
runs in background mode when dispatched, and errors are written 
to the error file:
.B /var/opt/perf/status.ttd.

.SH COMMAND LINE OPTIONS

.B ttd
recognizes the following command line options:
.TP 10
.B \-?
Displays the available options on standard error.

.TP
.B \-hup
Tells a running
.B ttd
process to reread the configuration file without 
explicitly killing and restarting.  The -hup option should be
used in conjunction with  the -mi option to synchronize the 
.B midaemon
with the 
.B ttd.
To have the changes synchronized with the
.B midaemon,
specify -mi after -hup.

.TP
.B \-fc
Disables the processing of the
.B ttd.conf
configuration file during the start of
.B ttd
daemon.

.TP
.B \-fg
Starts  
.B ttd
as a foreground process instead of running in background.

.TP
.B \-k
Kills the 
.B ttd 
process.  The 
.B ttd 
process should only be killed if the
.B midaemon 
process is likewise killed.  Killing and restarting the 
.B ttd
process without stopping the midaemon can result in 
unsynchronized TT data in the
.B midaemon
process.

.TP
.B \-mi
Tells a running
.B ttd
process to synchronize its entries with the midaemon without
explicitly killing and restarting.
This option is typically used after ttd -hup to
reread the
.B ttd.conf
file and synchronize any changes with the 
.B midaemon.

.SH ERROR MESSAGES
.I ttd
was designed to use exit values and to write explicit error 
messages in the 
.I status.ttd
file. The error messages are formatted using these conventions:
.br
- name of the running ttd program - timestamp,
.br
- name of the routine generating the error - error message,
.br
- error message generated by a perror(3C) call if a system call 
  has failed.

.SH DEPENDENCIES
The ARM library registration calls \fIarm_init()\fP,
\fIarm_getid()\fP and the control call \fIarm_stop
(...,ARM_ABORT,...)\fP fail if the 
.B ttd
daemon is not running.
However, ARM operations
.I arm_start()
or 
.I arm_stop()
can execute successfully without the
.B ttd 
daemon process if 
.I arm_getid
was successfully called before
.B ttd
was stopped.

The Measurement Interface processing daemon
.B midaemon
must also be running to process the user-defined transactions
and to measure performance metrics associated with these 
transactions.

The localhost loopback interface must be configured in order for
ttd to receive the client RPC connection requests.  Client 
applications connect to ttd via RPC connections when the 
arm_getid() function is called.

The number of active client processes that can register 
transactions with ttd via the arm_getid() call is limited to
the maxfiles kernel parameter.  This parameter controls the 
number of open files per process.  Each client registration 
request results in ttd opening a socket (an open file) for the
RPC connection.  The socket is closed when the client 
application terminates; therefore, this limit affects only the 
number of active clients that have registered a transaction via
the arm_getid call.  Once this limit is reached, ttd will return
TT_TTDNOTRUNNING to a client's arm_getid() request.  The 
maxfiles kernel parameter can be increased to raise this limit
above the number of active applications that will register 
transactions with ttd.

.SH EXAMPLES
.br
The standard
.I ttd
process execution is
.P
% ttd
.P
To signal an active 
.B ttd
daemon process to reread the configuration file and synchronize
with the
.B midaemon
process:
.P
% ttd -hup -mi
.P
To stop an active
.B ttd
daemon process:
.P
% ttd -k
.P

.SH EXTENSIONS
.br
An active 
.B ttd
daemon process stores its pid in the file: 
.I ttd.pid
located in the same directory as the 
.I status.ttd
file.

.SH SEE ALSO
\fBttd.conf(4)\fP, \fBarm(3)\fP, \fBmidaemon(1)\fP.