Commit | Line | Data |
---|---|---|
9a0f4f0c KM |
1 | .\" Copyright (c) 1983 Regents of the University of California. |
2 | .\" All rights reserved. The Berkeley software License Agreement | |
3 | .\" specifies the terms and conditions for redistribution. | |
4 | .\" | |
058a6e1e | 5 | .\" @(#)uusnap.8 6.1 (Berkeley) %G% |
9a0f4f0c | 6 | .\" |
058a6e1e | 7 | .TH UUSNAP 8C "" |
9a0f4f0c KM |
8 | .UC 5 |
9 | .SH NAME | |
10 | uusnap \- show snapshot of the UUCP system | |
11 | .SH SYNOPSIS | |
12 | .B uusnap | |
13 | .SH DESCRIPTION | |
14 | Uusnap displays in tabular format a synopsis of the current UUCP | |
15 | situation. The format of each line is as follows: | |
16 | .PP | |
17 | .ti +10 | |
18 | site N Cmds N Data N Xqts Message | |
19 | .PP | |
20 | Where "site" is the name of the site with work, "N" is a count of | |
21 | each of the three possible types of work (command, data, or remote execute), | |
22 | and "Message" is the current status message for that | |
23 | site as found in the STST file. | |
24 | .PP | |
25 | Included in "Message" may be the time left before UUCP can re-try the | |
26 | call, and the count of the number of times that UUCP has tried to | |
27 | reach the site. | |
28 | .SH SEE ALSO | |
29 | uucp(1C), | |
30 | UUCP Implementation Guide | |
31 | .SH AUTHOR | |
32 | Randy King |