uustat(1)uustat(1)NAMEuustat - uucp status inquiry and job control
SYNOPSIS
jobid]
jobid]
sys] user]
DESCRIPTION
displays the status of, or cancels, previously specified commands, or
provide general status on connections to other systems (see uucp(1)).
Only one of the following options can be specified with per command
execution:
Output all jobs in queue.
Report the status of accessibility of all machines.
Execute a for all the process IDs that are in the lock files.
List the jobs queued for each machine.
If a status file exists for the machine, its date,
time and status information are reported. In addi‐
tion, if a number appears in next to the number of or
files it is the age in days of the oldest or file for
that system. The Retry field is the number of hours
until the next possible call. The Count field is the
number of failure attempts. Note that for systems
with a moderate number of outstanding jobs, this could
take 30 seconds or more of real time to execute. As
an example of the output produced by
The above output tells how many command files are
waiting for each system. Each command file can have
zero or more files to be sent (a command file with no
files to be sent causes the system to call the remote
system and see if work is waiting). The date and time
refer to the previous interaction with the system fol‐
lowed by the status of interaction.
Kill the request whose job identification is jobid. The killed
request must belong to the person issuing the command
unless the command is executed by the super-user.
Rejuvenate
jobid. The files associated with jobid are touched so
that their modification time is set to the current
time. This prevents the cleanup daemon from deleting
the job until the jobs modification time reaches the
limit imposed by the cleanup daemon.
The following options can be used singly or together but cannot be used
with the options listed above:
Report the status of all
requests for remote system sys.
Report the status of all
requests issued by user.
Output for both the and options has the following format:
With the and options, the first field is the jobid of the job.
This is followed by the date and time. The next field is either
an or depending on whether the job is to send or request a file.
The next field is the destination system name. This is followed
by the user ID of the user who queued the job. The next field
contains the size of the file, or in the case of a remote execu‐
tion the name of the command (such as which is the command used
for remote mail). When the size appears in this field, the file
name is also given. This can either be the name given by the
user or an internal name (such as that is created for data files
associated with remote execution in this example).
When no options are given, outputs the status of all requests issued by
the current user. The format used is the same as with the or options.
EXTERNAL INFLUENCES
Environment Variables
determines the format and contents of date and time strings.
determines the language in which messages are displayed.
If is not specified in the environment or is set to the empty string,
the value of is used as a default for each unspecified or empty vari‐
able. If is not specified or is set to the empty string, a default of
"C" (see lang(5)) is used instead of If any internationalization vari‐
able contains an invalid setting, behaves as if all internationaliza‐
tion variables are set to "C". See environ(5).
FILES
spool directories
SEE ALSOuucp(1).
Tim O'Reilly and Grace Todino,
O'Reilly & Associates, Inc. USA.
Grace Todino and Dale Dougherty,
O'Reilly & Associates, Inc. USA.
STANDARDS CONFORMANCEuustat(1)
