uurate(1)

💖 uurate(1) — the Taylor UUCP stats girly 💖

okay bestie, welcome to uurate — section 1 of the General Commands Manual, the one and only tool that reports your Taylor UUCP statistics. she's a tabular girlie and she ate ✨

---

🌸 NAME 🌸

uurate — Report Taylor UUCP statistics 📊💅

---

✨ SYNOPSIS ✨

uurate [ -acdefhipqtvx ] [ -s host  ] [ -I config  ][ logfile... ]

or simply, no args, no thoughts, just vibes:

uurate

and that gives you a traffic summary report 🎀

---

🦋 DESCRIPTION 🦋

So uurate is out here providing tabular summary reports on how your Taylor UUCP system is doing. She pulls her data from the currently active log files, from standard input, or from a list of log files you hand her on the command line. The output? Tabular reports summarising call, file transfer, and command execution (uuxqt) activity. Iconic behaviour, fr fr.

Okay important tea 🫖: the log and stats files you give to uurate must be in the Taylor''</red> or <red>V2'' format. Also — and this is the part people fumble — call activity and file transfer activity get logged in separate files, nominally called Log and Stats, respectively. For your reports to actually mean something, you should give the Log and Stats files to uurate together, and they gotta cover the same time period. No mixing eras, bestie 😭

If you give her neither the -i or -I option nor any logfile options, uurate defaults to taking her input from the current Taylor Log and Stats files. Those names are either defined at compilation time (if there's no config file), or taken from the arguments of the keywords logfile and statfile when she encounters them in the config file. This is the normal mode of operation. 👑

The reporting options described below let you pick which set of reports you want. If you give no options at all, a summary report is displayed. And if there's no relevant data for a particular report or host, that report or host just gets suppressed — she's not gonna show you an empty table, she has taste 💅

---

💅 OPTIONS 💅

Here are the options you can hand to uurate:

• -a — All reports. Identical to -cfexp. ✨
• -c — Report on call statistics. Requires data from a Log file.
• -d — will print the default config file to be used.
• -e — Report on efficiency (total connect time versus time spent transferring files). Requires data from both a Log and a Stats file, and they must span the same time period.
• -f — Report on file transfer statistics. Requires data from a Stats file.
• -h — will print a short help information.
• -i — tells uurate to read any logfile information from standard input.
• -p — report on protocol errors and packets sent/received 🍓
• -q — do not print the Environment information.
• -t — All reports. Identical to -cfexp. plus the Compact summary.
• -v — will print the version id string.
• -x — Report on remote execution requests (e.g., rmail). Requires data from a Log file.
• -s host — Restrict report output to host. 🎯
• -I config file — an alternate config file may be passed by this option.

---

🌈 DESCRIPTION OF REPORTS 🌈

There are four reports available: the call, file transfer, efficiency, and remote execution reports. Each one may be selected by a command line option. All reports may be selected via the options -a or -t. And if you give no report selection options, uurate displays a compact traffic summary report (see below, bestie 👇).

🎀 Summary report 🎀

If no report options are given, uurate displays a traffic summary report. This is especially useful in daily cron jobs which report on errors and the like. Traffic statistics for each active system are reported on a single line. And if more than one system was active, a 'totals' line is included at the end of the report. ✨

🍓 Protocol packet report 🍓

The protocol report gives statistics on min/max packet and window sizes used during transmission. Further on, data is collected for packets transferred. The data is collected for each host/protocol type. The fields are described below:

• site — UUCP node name of neighbor host system
• typ — Type of protocol used
• Min — minimum packet/window size
• Max — maximum packet/window size
• sent — packets sent
• resent — packets resent
• received — packets received

💀 Protocol error report 💀

The protocol report gives statistics on packet errors during transmission. The data is collected for each host/protocol type. The fields are described below:

• site — UUCP node name of neighbor host system
• typ — Type of protocol used
• header — number of errors in header
• checksum — number of checksum errors
• order — number of order errors
• resent — number packets resent
• rem-reject — packets that the remote site rejected

🌸 Call report 🌸

The call report gives statistics on inbound and outbound calls for each active host system. The fields are described below:

• site — UUCP node name of neighbor host system
• succ. — Successful calls attempted to/by that system
• failed — Failed calls to/by that system
• total — Total calls to/by that system
• time — Collected connect time (hh:mm:ss) for all calls

🧚 File transfer reports 🧚

The file transfer reports give statistics on inbound and outbound file transfers (regardless of which end initiated the transfer) for each active host system. There are two reports — one for files sent to the remote system and one for files received from the remote system. The fields in each report are described below:

• site — UUCP node name of neighbor host system
• files — Number of files transferred
• Bytes/1000 — Total size of files transferred given in thousands
• xfr time — Total time (hh:mm:ss) spent on transfer the files
• B/sec — Average transfer rate (bytes/sec)

👑 Efficiency report 👑

The efficiency report describes the utilization of the links to each active remote system, giving the ratio of total connect time to the time spent actually transferring files. The fields are described below:

• site — UUCP node name of neighbor host system
• connected — Total connect time for that system (turn-around)
• xfr time — Total file transfer time for that system
• overhead — Connect time not used to transfer files
• eff. % — Ratio of connect time to transfer time (xfer*100/conn)

⭐ Command executions report ⭐

The remote execution report describes remotely requested command executions from each active host system, like rmail and rnews. Up to eight command names are displayed. If there are more, the rest get bundled together in an Misc. column. The fields are described below:

• site — UUCP node name of neighbor host system
• (command) — Number of requests of this command
• Misc. — Number of other requests, if more than eight

---

🎀 FILES 🎀

The file names below may be changed at compilation time or by the configuration file, so these are only approximations. Don't come for her if they're different on your box, bestie 💖

• /usr/spool/uucp/Log — V2/Taylor format call/execution log
• /usr/spool/uucp/Stats — V2/Taylor format file transfer log

---

🌈 SEE ALSO 🌈

• uucico(8)

---

😭 BUGS 😭

Real talk, here's where she struggles. No sugarcoating this part.

• Does not understand other than V2/TAYLOR logging formats. Anyone care to volunteer to add the not mentioned? 🙈
• Scanning the arguments of logfile and statfile keywords in config should handle lines continued with the backslash as well.
• The failfm field in the call statistics table is always zero, unless something really serious happens, e.g. uucico got SIGQUIT or the whole system crashed. 💀

---

💜 AUTHOR 💜

• Robert B. Denny (denny@alisa.com).
• Loosely based on the DECUS UUCP program uurate by Mark Pizzolato.
• Modified by Stephan Niemz (stephan@sunlab.ka.sub.org).
• Modified by Klaus Dahlenburg (kdburg@incoahe.hanse.de).

---

and that's the whole page, bestie 🫶 shoutout to the General Commands Manual for hosting her, and to uurate(1) itself — yes, the footer is literally just her own name again, she's her own main character and she knows it 👑💅✨