


TUA(1L)                LOCAL USER COMMANDS                TUA(1L)


NNAAMMEE
       TUA - The Uucp Analyzer

SSYYNNOOPPSSIISS
       ttuuaa [ option ]

NNOOTTEE
       This  manual  page is no longer supported. See _t_u_a_._t_e_x_i_n_f_o
       for up-to-dated information.

DDEESSCCRRIIPPTTIIOONN
       The purpose of the _T_U_A utility is to  produce  a  readable
       and complete analysis of the _H_o_n_e_y_D_a_n_B_e_r UUCP connections.
       This manual page describes the _T_U_A  command  line  options
       and shortly explains its output.

OOPPTTIIOONNSS
       To  specify  any  of  the  options, you can use either the
       short form or the more mnemonic long form. In  the  latter
       case, you can abbreviate the name as long as it is unique.
       For more information on the long format, please  refer  to
       the _G_N_U _g_e_t_o_p_t package description.


       --SS,, ++nnoo--ssyyss--rreepp
            Do  not  print the ppeerr SSyysstteemm rreeppoorrtt.  The default is
            to print it out.

       --UU,, ++nnoo--uusseerr--rreepp
            Do not print the ppeerr UUsseerr rreeppoorrtt.  The default is  to
            print it out.

       --DD,, ++nnoo--ddaaiillyy--rreepp
            Do  not  print  the  DDaaiillyy rreeppoorrtt.  The default is to
            print it out.

       --CC,, ++ccoommmmaanndd--lliissttss
            Show also the command lists. It  is  off  by  default
            because it makes _T_U_A very hungry of memory.

       --OO,, ++oonnllyy--ssyysstteemm _S_Y_S_T_E_M
            Consider  just  system _S_Y_S_T_E_M in the reports. You can
            specify more than one of this option, so you can have
            _T_U_A consider just those systems.

       --mm,, ++nnoo--mmoonntthhllyy--aacctt
            Do not output the last 12 months activity summary.

       --hh,, ++nnoo--hhiissttoorryy
            Do  not output the history at the end of the reports.

       --cc,, ++sseeppaarraattee--ccoomm
            Separate command lists from the other data. So  there
            will  be  two  tables with the header _B_y _S_y_s_t_e_m _, the



Release 3.4              16 November 1991                       1





TUA(1L)                LOCAL USER COMMANDS                TUA(1L)


            first containing only the amounts and the  timing  of
            each  transfer,  the  second  with  all  the commands
            invoked by each System. You must specify also the  --CC
            option to make it works.

       --kk,, ++kkiillll--ssyysstteemm _S_Y_S_T_E_M
            Eliminate  each reference to _S_Y_S_T_E_M from the reports.
            Neither the transfer table  nor  the  _S_Y_S_T_E_M  command
            list will be printed.

       --KK,, ++kkiillll--uusseerr _U_S_E_R
            Like --kk , but it applies to the user called _U_S_E_R _.

       --HH,, ++uuppddaattee--hhiisstt
            Update  the  _h_i_s_t_o_r_y  database (see the FILES section
            below) with the new values. You must  have  the  uuuuccpp
            write permission.

       --00,, ++rreesseett--hhiisstt
            Reset  the  _h_i_s_t_o_r_y database, deleting any systems in
            it. Then put in the database the analysis  since  the
            last  _u_u_c_l_e_a_n  _.  You have to specify also --HH to make
            this option do his job.

       --yy,, ++nnoo--hhoouurrllyy--cchhaarrtt
            Do not display the hourly activity chart.

       --zz,, ++cchhaarrtt--ssiizzee _S_I_Z_E
            Set the size of the hourly  activity  chart  to  _S_I_Z_E
            rows.  The greater is this number, the smaller is the
            scale. By default it is set to 10.

       --oo,, ++cchhaarrtt--oonnllyy
            Display only the hourly activity  chart.  Since  with
            this  options  _T_U_A reads only ..AAddmmiinn//xxffeerrssttaattss, it is
            faster.

       --vv,, ++vveerrbboossee
            Print, on standard error, what is going on. While _T_U_A
            reads  the various logs, it displays a counter of the
            loaded lines.

       --pp,, ++pprreeffiixx--ppaatthh _P_A_T_H
            By   default,   _T_U_A   looks   for   uucp   data    in
            //uussrr//ssppooooll//uuuuccpp//  and  in  the relative subdirectory.
            For debugging purpose, this option  lets  you  change
            this directory, so that _T_U_A looks for the data in the
            specified _P_A_T_H_.  Below this point _T_U_A needs a hierar-
            chy like the standard one (see FILES below).

       --uu,, ++uusseerr--aalliiaass _U_S_E_R_=_A_L_I_A_S
            Inserts  ALIAS  as  the new name for USER. Where ever
            appears USER it will be replaced  with  ALIAS.  Since
            this  occurs  at  the  lowest  level, if happens that



Release 3.4              16 November 1991                       2





TUA(1L)                LOCAL USER COMMANDS                TUA(1L)


            ALIAS is another user name, this will cause that  all
            the  data  that  belongs to USER will be added to the
            ALIAS user.

       --rr,, ++ppoorrtt--aalliiaass _P_O_R_T_=_A_L_I_A_S
            Like --uu , but it applies to the  serial  port  names.
            This  can be useful on those OS where a single serial
            port has two names, one for normal use and the  other
            with modem control (eg.  ttttyy11aa and ttttyy11AA ).

       --ss,, ++ssyyss--aalliiaass _S_Y_S_=_A_L_I_A_S
            Like --uu , but it applies to the systems names.

       --EE,, ++gglloobb--uusseerr--aalliiaass _G_L_O_B_=_A_L_I_A_S

       --RR,, ++gglloobb--ppoorrtt--aalliiaass _G_L_O_B_=_A_L_I_A_S

       --MM,, ++gglloobb--ssyyss--aalliiaass _G_L_O_B_=_A_L_I_A_S
            These are the counterpart respectively of --uu , --rr and
            --ss with mmeettaa--cchhaarraacctteerrss searches.  You  can  use  for
            example

                    tua +glob-user-alias uu*=UUCPUSERS

            and  every  user  name  that  begins  with uuuu will be
            mapped in a meta user called UUUUCCPPUUSSEERRSS  _s_h_(_1_)  for  a
            description of mmeettaa--cchhaarraacctteerrss

       --ii,, ++hheellpp
            Show  a summary and a description of all the options.

OOUUTTPPUUTT
       All reports are printed on the standard output, so you can
       easily  redirect  them wherever you want. Assuming, unless
       otherwise stated, that you do  not  explicity  request  to
       disable  some  of the reports (eg. when you do not specify
       any command line option), here is a short  description  of
       what you get.

       BByy SSyysstteemm

       With  this report, you get all the information relative to
       all the nodes that talk with your machine but those  which
       didn't sent or received something. The data are divided in
       _i_n_b_o_u_n_d and  _o_u_t_b_o_u_n_d_.   For  each  system,  displayed  in
       alphabetical  order, you have the total count of the files
       transferred, with the relative bytes and times, as well as
       an  average  transfer  rate (ATP).  If ++ccoommmmaannddss--lliissttss was
       specified, next there is the list of the commands  invoked
       by that node, or directed to it. If a command is preceeded
       by a number between brackets, that  number  indicates  how
       many times that command was invoked.





Release 3.4              16 November 1991                       3





TUA(1L)                LOCAL USER COMMANDS                TUA(1L)


       BByy UUsseerr

       This  report is similar to the previous one, but it shows,
       in alphabetical order for each local user,  all  the  com-
       mands the user invoked, and the transfers he caused.

       BByy DDaayy

       This  report  summarize  the per day activity on the local
       machine. It doesn't depend on the destinations and on  the
       users.

       SSUUMMMMAARRYY bbyy SSyysstteemm

       It shows a summary of the activity of each system, and the
       number of calls (inbound and outbound) for it. Please note
       that  sometimes  _T_U_A fails in calculating the exact number
       of calls, because of the misleading log  of  uucico.  Note
       also  that the "total connection time" always differs from
       the sum of the trasmissions times, because it  takes  care
       also  of the various uucp dead time. In fact, it is calcu-
       lated from the difference between the time  in  which  the
       nodes  are really connected (ie. at the end of dial phase,
       when the modem answers) and the time in which the link  is
       dropped, due to the the end of the conversation as well as
       to any error.  Then comes the time of the last  connection
       with  that  system.   There is also the subdivision of the
       connection time  based  on  the  phone  costs,  ie  "day",
       "evening", "night". This is completely configurable, so if
       your telephone company uses a  different  hourly  division
       you can adjust it (see ccoonnffiigg..hh and pphhoonneessww..cc.)

       SSUUMMMMAARRYY bbyy SSyysstteemm ((ttaabbllee ffoorrmmaatt))

       Substancially, this report summarizes some of the previous
       informations in a tabular form. Nothing new...

       aanndd ssiinnccee ......

       This is the historical data maintained by _T_U_A_.   It  looks
       like  the  previous  table, but it includes the history of
       the system, incrementally.

       LLaasstt 1122 MMoonntthhss AAccttiivviittyy

       This table shows the activity of the local machine  during
       the last 12 months.  Only the transferred amounts are com-
       puted.
       The months are displayed in a manner so that the last col-
       umn  contains  the current one, so it is very readable (of
       course, it is a matter of opinions!)






Release 3.4              16 November 1991                       4





TUA(1L)                LOCAL USER COMMANDS                TUA(1L)


       HHoouurrllyy AAccttiivviittyy ((ppeerr ccoommmmuunniiccaattiioonn ppoorrtt))

       This chart shows the uucp hourly load for each used commu-
       nication port.  Each hour is divided in 20 minutes slices.

       GGlloobbaall HHoouurrllyy AAccttiivviittyy

       The same as the previous chart, but it reports the sums of
       all the ports.

HHIISSTTOORRYY
       _T_U_A  maintains  a database with the history of each system
       and of the activity in each of the last 12 months  activi-
       ties.       It       is       usually      located      in
       //uussrr//ssppooooll//uuuuccpp//..AAddmmiinn//ttuuaa..hhiissttoorryy and it is  actually  an
       ASCII  file.  It is up to you to update it or not, because
       probably you will like to run _T_U_A simply to have a  notion
       of  what  is  going  on. To make it working correctly, you
       have to run _T_U_A with the option ++uuppddaattee--hhiisstt  just  before
       you  run uuclean. So probably you will have to modify that
       script including in it a line like

               tua +update-hist {whatever options you like} | mail lele

       before it cleans up the uucp logs.

BBUUGGSS
       Since HDB-Uucp doesn't put a  complete  datestamp  in  its
       logs,  but  omits  the  year,  it may be possible that _T_U_A
       fails to compute the various times in the  first  analysis
       of  the  year.   This is in my opinion its major weakness.
       For this silliness, _T_U_A cannot correctly handle logs  that
       cover several years. There is little that I can do to cor-
       rect the situation; I tried to adjust the  year  when  the
       to-be-parsed  date  refers obviously to the previous year,
       but this is just a work-around...

       There is a limit: if your  system  spent  more  than  9999
       hours  linked with someone (or the sum exceed that value),
       the reports will be garbaged...

DDIISSCCLLAAIIMMEERR
       _T_U_A is ffrreeee, and it is redistribuitable under the terms of
       the  GNU General Public License. You can find a copy of it
       in the file CCOOPPYYIINNGG in the distribution package.  I reject
       any  responsability about it. It is simple and safe, but I
       did not try it under all the possible conditions and envi-
       ronments,  so  if  it causes you some trouble, I'll be sad
       for a while, but that's it. However, I will try to correct
       any bugs you will tell me.

       And  pplleeaassee,, forgive my poor english, but I put my soul in
       it...




Release 3.4              16 November 1991                       5





TUA(1L)                LOCAL USER COMMANDS                TUA(1L)


AAUUTTHHOORR
       Lele Gaifas, Idea Informatica, Rovereto (TN) - Italy
       ( piggy@idea.sublink.org )

FFIILLEESS
        .../.Log/uucico/*       uucico's logs
        .../.Log/uucp/*         uucp's logs
        .../.Log/uux/*          uux's logs
        .../.Log/uuxqt/*        uuxqt's logs
        .../.Admin/xferstat     Transfer stats
        .../.Admin/tua.history  TUA's system history

BBUUGGSS RREEPPOORRTT TTOO
       Lele Gaifas, piggy@idea.sublink.org

AACCKKNNOOLLEEDDGGMMEENNTT
       I  want  to  thank  expecially   Marco   Lorenzini   (mar-
       lor@gear.sublink.org) for his help in debugging the previ-
       ous releases of _T_U_A on the SCO Unix architecture, and  for
       his  suggestions  on the layout of the reports. And to the
       "omnipresent" Paolo Ventafridda  (venta@i2ack.sublink.org)
       for  his  support  and  interest, and several other people
       that encouraged me to add more and more functionality,  or
       that let me scan their huge logs.
       Thanks  also  to all the people that, with their PD or GPL
       software, helped me indirectly with ideas or examples.































Release 3.4              16 November 1991                       6


