From: rse@angle.sub.org (Ralf S. Engelschall)
Newsgroups: alt.sys.amiga.uucp
Subject: Re: Understanding XferStat
Date: Thu, 13 Aug 1992 11:26:34 GMT
Reply-To: rse@angle.sub.org
X-Newsreader: Arn V1.00 beta rel3

In article <ptdur*EM6@stile.stonemarche.org>, Mark Eklof writes:

> 	I recently installed the UUcico that writes XferStat data.
> Now, I'd like to know exactly what it's writing so I can write
> something that will decode it.  (UUtraf is nice, but doesn't give me
> the flexibility or detail that I want.)

  You want more details?  Which?  I think UUTRAF gives enough
information to have an good overview to the UUCP traffic.  If you want
to know what the fields are indicating you should have a look either at
my UUTRAF source code or at the following sheet of text:

|   XFERSTAT Format
|   ---------------
|   Xferstat, by default, writes two lines for each session.
|   The format fits on a normal full sized window and is human readable.
|
|   The frequently asked question: What is my CPS ?
|
|   Now some explanation of a log record ( 2 lines )
|
| d hostname dd-mm-yy hh:mm:ss > dd-mm-yy hh:mm:ss hh:mm:ss BR_CPS NE_CPS ppp%
| | p option bytes_i  bytes_o    fbytes_i fbytes_o fcnt_i fcnt_o
|
|   where:
| 	d  direction of the call
| 	   < outgoing
| 	   > incoming
|
| 	hostname        who calls/ whom we call
|
| 	dd-mm-yy        date of start/stop session
| 	hh:mm:ss        time of start/stop session
|                         or total time of sessions
| 	BR_CPS          brutto cps calculation
| 	NE_CPS          netto cps calculation
| 	ppp%            netto/brutto in percent
| 	bytes_i         total number of bytes (including protocol
| 	bytes_o	        overhead) in/out
| 	fbytes_i
| 	fbytes_o	total number of file bytes in/out
| 	fcnt_i
| 	fcnt_o		total number of files in/out
|
| 	p option        protocol key (mostly g|G)
|
| 	for g|G option format is n mmmm with
|
| 		n ... number of sliding windows
| 		m ... number of bytes/packets
|
|   A "real world" example:
|   -----------------------
|   from uuspool:xferstat
|
| < horga    23-10-91 07:38:06 > 23-10-91 07:51:04 (00:12:58)  1401   1169  83%
| | g 3   64  1000935    89605 #   909846        0 #   26    0
|
|   "I call host 'horga' on the 23. october at 7:38am.
|    The used protocol was 'g' with 3 windows and 64 byte packets.
|    The session terminates at 7:51am (logtime 00:12:58).
|    I recieve 1000935 total bytes or 909846 data characters in
|    26 files. I send 89605 total bytes for protocol/ 0 bytes of data.
|
|    The calculation return 1401 bytes/sec OR 1169 bytes/sec
|    for usable data. The protocol overhead needs 17% of the total
|    cps rate."
|
|   Both sides here use a TB2500 with PEP and spoofing enabled.
|
|   !!! (AREXX) developers !!!
|   -----------------------------------
|   If you write anything based on xferstat's output,
|   NEVER assume a fix number of lines/log !
|
|   A log-record allways begins with a direction character and ends
|   one byte before the next direction character or EOF.
|   Valid direction characters are '<','>' or '=' as the first character
|   on a line.
|
|   After '<' or '>' the two lines above are the valid scan format.
|   The '=' value is reserved.
|
|   other character handling in first place of a line:
|
|   - Interpret '|' as a continue line of the current running format.
|     For '>' '<' this is the 'p option ... format'
|
|   - Interpret '#' followed by a valid isspace() char as a comment line.
|
|   - Treat '#anything' as a comment in general until you know what follows.
|
|   - For any other leading characters ignore the whole line.
|
|   Future Xferstat implementations log much more informations like modem
|   extended result codes, packet i/o, retrans i/o and dump internal
|   modem statistics (e.x. TBxxxx) on request.
|
|
|   -> DONNOT IGNORE THIS NOTE, ELSE YOU NEED MANY UPDATES <-

  Feel free to write another program which will give traffic statistics
as all others still do...  ;_)

                              ___  _______
                              /__)(_  /_    Ralf S. Engelschall
                             / \____)(___   rse@angle.sub.org
                            /