From: mark@infocomm.com
Newsgroups: vmsnet.uucp
Subject: Re: uustat -m doesn't work in 2.0?
Date: 25 Jul 92 00:05:59 PDT
Organization: INFO COMM - Computer Consulting, Redwood City, Ca

In article <1992Jul24.225148.4551@ecl.psu.edu>, fenner@jazz.psu.edu (Bill Fenner) writes:
> After upgrading to version 2.0, I find that "uustat -m" does not work.
> I reran uucp_bin:uucp_systartup.com on every cluster node.
> 
> I can still run uucp_bin:uusnap.exe and get the machine status, so the
> status is being kept, uustat just doesn't seem to find it.

Well, as shipped, the -m flag only means something when specified with another
flag that causes a queue scan (-q or -a).  The next version will perform a 
display site status in any case if the -m flag is specified.  This version 
will be available via E-mail if anyone really needs it.

> "uustat -q" also provides no output, although "uustat -a" and my UUQ.COM
> both show jobs queued.  Or is the "-q" option supposed to tell about
> jobs waiting for UUXQT?


It reports on all possible jobs:
        - Outbound C jobs in UUCP_SPOOL
        - Inbound XQT jobs in the per site subdirectories of UUCP_SPOOL
        - Pending REMAIL_X jobs in the per site subdirectories of UUCP_SPOOL
        - old style Inbound XQT jobs in the UUCP_SPOOL directory
        - old style Pending REMAIL_X jobs in the UUCP_SPOOL directory

I have lots of trouble understanding why you might see no output from:

        uustat -q

and some output from:

        uustat -a

Please send a copy of the output that is reported in this case.

This is how it should look:

$ uustat -q
               tcad:   2 jobs,   0 files in,   4 files out,    4511 bytesout

              scvax:   3 jobs,   0 files in,   3 files out,   39700 bytesout

Total Callout:         5 jobs,   0 files in,   7 files out,   44211 bytesout


$ uustat -a
Job: tcad_nd0b        7/24-23:00:16
         Send to tcad, User: netnews, 2527 byte file: D.infopizD0B
         Send to tcad, User: netnews, Execute Command: rnews
Job: tcad_nd0j        7/24-23:09:59
         Send to tcad, User: netnews, 1840 byte file: D.infopizD0J
         Send to tcad, User: netnews, Execute Command: rnews
               tcad:   2 jobs,   0 files in,   4 files out,    4511 bytesout

Job: scvax_gcz902     7/24-18:40:44
         Send to scvax, User: mark@infocomm.com, 7818 byte file: dte_hayes.exe
Job: scvax_gcza02     7/24-18:48:29
         Send to scvax, User: mark@infocomm.com, 24064 byte file: decw$cd.exe
Job: scvax_gczw02     7/24-21:01:19
         Send to scvax, User: mark@infocomm.com, 7818 byte file: dte_hayes.exe
              scvax:   3 jobs,   0 files in,   3 files out,   39700 bytesout

Total Callout:         5 jobs,   0 files in,   7 files out,   44211 bytesout

> It would be nice to have a "No jobs queued." message, or something, instead
> of just having it exit with no output, if this is the case.

"No output" means EXACTLY that there are "no jobs queued", there is no 
ambiguity here.

--
Mark Pizzolato - INFO COMM Computer Consulting, Redwood City, Ca
PHONE:	(415)369-9366	UUCP:  decwrl!infopiz!mark or uunet!lupine!infopiz!mark
DOMAIN:	mark@infocomm.com
Xref: sparky vmsnet.uucp:592 vmsnet.mail.pmdf:1966 vmsnet.networks.tcp-ip.cmu-tek:595 vmsnet.tpu:378 vmsnet.pdp-11:556