 |
Index for
Section 1 |
|
 |
Alphabetical
listing for U |
|
 |
Bottom of
page |
|
uustat(1)
NAME
uustat - Reports status of and provides job control for remote file
transfer requests and other operations
SYNOPSIS
uustat [-a | -k job_number | -m | -p | -q | -r job_number] [-s system]
[-u user]
The uustat command displays status information about several types of file
transfer operations.
STANDARDS
Interfaces documented on this reference page conform to industry standards
as follows:
uustat: XCU5.0
Refer to the standards(5) reference page for more information about
industry standards and associated tags.
OPTIONS
The following options are mutually exclusive; you can use only one at a
time with the uustat command:
-a [Tru64 UNIX] Displays information about all the jobs in the holding
queue, regardless of the user who issued the original command.
There are two types of queues:
· The current queue lists the jobs queued to run on or currently
running on one or more specified computers. Use the uustat -q
command to examine this queue.
· The holding queue, displayed with uustat -a, lists all jobs that
have not executed during a set period of time.
After the set time period has elapsed, the entries in the holding
queue are deleted manually with the uucleanup command or
automatically with the file /var/spool/cron/crontabs/uucp
(includes uudemon.cleanu), which is started by cron. When sending
files to a system that was not contacted recently, it is a good
idea to use the uustat command to see when the last access
occurred, as the remote system might be out of service.
-k job_number
Cancels (kills) the process specified by job_number. The person using
this option must be the one who made the uucp request now being
canceled, or must be operating with superuser authority.
This option cancels a process only when that job is still on the local
computer. Once the job has been moved to a remote system for
execution, -kjob_number cannot be used to cancel the remote job.
-m [Tru64 UNIX] Reports the status of the most recent attempt to contact
the specified system. If the request was completed, the status report
is SUCCESSFUL. If the job was not completed, the status report is an
error message, such as LOGIN FAILED.
-p [Tru64 UNIX] Runs a ps -flp (process status: a full, long list of
specified process IDs) for all PID numbers in the lock files.
-q Lists the jobs currently queued to run on each system; these jobs are
either waiting to execute or are in the process of executing. If a
status file exists for the system, its date, time, and status
information are reported. Once the job is finished, that job listing
is removed from the current queue.
In a status report, a number in parentheses next to the number of a C.*
(command) file or an X.* (execute) file represents the age in days of
the oldest C.*/X.* file for that system. The retry field represents
the number of times the command could not be executed because of such
factors as a failed login, locked files, an unavailable device, and so
on.
-r job_number
Marks the files in the holding queue specified by job_number with the
current date and time. Use this option to ensure that a cleanup
operation does not delete files until the job's modification time
reaches the end of the specified period.
You can use either one or both of the following options with uustat:
-s system
Reports the status of requests for the system specified by system. The
system name must contain only ASCII characters.
-u user
Reports the status of requests by the specified user for any system.
DESCRIPTION
The uustat command is particularly useful in monitoring transfer (copy)
requests issued with the uucp and uuto commands, and requests made with the
uux command to run commands on a remote system.
In addition, uustat also gives a user limited control over jobs queued to
run on remote systems. By issuing the command with the appropriate option,
a user can check the general status of connections to other systems, and
cancel copy requests made with uucp and uuto.
If uustat is issued without any options, the command reports the status of
all requests issued by the current user since the last time the holding
queue was cleaned up. Such status reports are displayed in the following
format:
job_number date/time
status system user size file
See EXAMPLES for an explanation of this format.
EXAMPLES
1. To display the status of all jobs in the holding queue, enter:
uustat -a
The system responds with a message similar to the following:
heraC3113 Wed Nov 06 17:47:25 1991 S hera amy 289 D.venus471afd8
zeusN3130 Wed Nov 06 09:14:30 1991 R zeus geo 338 D.venus471bc0a
merlinC3120 Tue Nov 05 16:02:33 1991 S merlin amy 828 /u/amy/tt
merlinC3119 Tue Nov 05 12:32:01 1991 S merlin msg rmail amy
The first field is the job ID of the operation, which is followed by
the date and time the command was issued. The third field is either
an S or an R, depending on whether the job is to send or request a
file. The fourth field is the name of the system on which the command
was entered, followed by the user ID of the person who issued the
command. The sixth field is the size of the file, or, in the case of a
remote execution like the last entry in the example, the name of the
remote command. When the size of the file is given, the filename is
also displayed. The filename can be either the name given by the
user, as in the /u/amy/tt entry, or a name that is assigned internally
to data files associated with remote executions, such as
D.venus471afd8.
2. To display the status of all jobs in the current queue, enter:
uustat -q
The system responds with a message similar to the following:
merlin 3C Mon Jul 15 11:02:35 1991 NO DEVICES AVAILABLE
hera 2C Mon Jul 15 10:55:22 1991 SUCCESSFUL
zeus 1C (2) Mon Jul 15 10:59:48 1991 CAN'T ACCESS DEVICE
The output tells how many C.* (command) files are waiting for each
system. The date and time refer to the current interaction with the
system, followed by a report of the status of the interaction. The
(2) in the third line of the example indicates that the C.* file has
been in the queue for 2 days.
3. [Tru64 UNIX] To display all process IDs in the lock file, enter:
uustat -p
4. [Tru64 UNIX] To cancel a job in the current queue, first determine
the job ID and then issue the command (uustat -k) to cancel the job.
To determine the job ID, enter:
uustat -a
The system responds with a message similar to the following:
heraC3113 Wed Nov 06 17:47:14 1991 S hera amy 289 D.venus471afd8
merlinC3119 Wed Nov 06 17:49:37 1991 S merlin geo 338 D.venus471bc0a
To cancel the job with the ID of heraC3113:
uustat -k heraC3113
5. To report the status of jobs requested by system hera, enter:
uustat -s hera
The system responds with a message similar to the following:
heraNlbd7 Mon Jul 15 12:09:44 1991 S hera amy 522 /user/amy/A
heraClbd8 Mon Jul 15 12:10:30 1991 S hera amy 59 D.3b2a12ce4924
heraC3119 Mon Jul 15 12:11:11 1991 S hera amy rmail msg
6. To report the status of jobs requested by user amy, enter:
uustat -u amy
This option displays output similar to that produced by the -s option.
FILES
/usr/spool/uucp/locks/LCK*
Prevents multiple use of device.
/usr/spool/uucp
Spooling directory.
SEE ALSO
Commands: cron(8), ct(1), cu(1), echo(1), ps(1), rmail(1), stty(1),
tip(1), uucico(8), uucleanup(8), uucp(1), uulog(1), uuname(1), uupick(1),
uusched(8), uusend(1), uuto(1), uux(1)
Standards: standards(5)
|
Index for
Section 1 |
|
|
Alphabetical
listing for U |
|
 |
Top of
page |
|