UUSTAT(1POSIX)

📦 version 2017a, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu resolute, ubuntu stonking

🦋 PROLOG 🦋

okay so bestie, quick heads up before we dive in: this manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ — so pls consult the corresponding Linux manual page for the deets on Linux behavior — or honestly the interface might not even be implemented on Linux at all. 💀 no cap.

✨ NAME ✨

uustat — uucp status enquiry and job control 👑

🌸 SYNOPSIS 🌸

uustat [-q|-k jobid|-r jobid]

uustat [-s system] [-u user]

💖 DESCRIPTION 💖

So the uustat utility shall display the status of, or cancel, previously specified uucp requests — or it can just hand you general status on uucp connections to other systems. it's giving switchboard operator energy fr fr.

When you give it no options at all, uustat shall write to standard output the status of all uucp requests issued by the current user. that's you. hi. 🫶

Typical implementations of this utility require a communications line configured to use the Base Definitions volume of POSIX.1‐2017, Chapter 11, General Terminal Interface — but other communications means may be used, so it's not the only way. On systems where there are no available communications means (either temporarily or permanently, like it's just not happening bestie), this utility shall write an error message describing the problem and exit with a non-zero exit status. 😭

💅 OPTIONS 💅

The uustat utility shall conform to the Base Definitions volume of POSIX.1‐2017, Section 12.2, Utility Syntax Guidelines. (iconic behavior, we love standards.)

The following options shall be supported:

  • -q — Write the jobs queued for each machine. 📋
  • -k jobid — Kill the uucp request whose job identification is jobid. The application shall ensure that the killed uucp request belongs to the person invoking uustat — unless that user has appropriate privileges. so like, don't go killing other people's jobs, that's not the vibe. 🔥
  • -r jobid — Rejuvenate jobid. The files associated with jobid are touched so that their modification time is set to the current time. This prevents the cleanup program from deleting the job until the job's modification time reaches the limit imposed by the program. it's basically a glow-up for a doomed job, we love that for it. ✨
  • -s system — Write the status of all uucp requests for remote system system. 🌈
  • -u user — Write the status of all uucp requests issued by user. 🎀

🧚 OPERANDS 🧚

None. nothing. zero. the void. 🙈

🍓 STDIN 🍓

Not used. it's not even looking at it bestie.

💜 INPUT FILES 💜

None.

🌸 ENVIRONMENT VARIABLES 🌸

The following environment variables shall affect the execution of uustat:

  • LANG — Provide a default value for the internationalization variables that are unset or null. (See the Base Definitions volume of POSIX.1‐2017, Section 8.2, Internationalization Variables for the precedence of internationalization variables used to determine the values of locale categories.)
  • LC_ALL — If set to a non-empty string value, override the values of all the other internationalization variables. it said "I'm the main character" and honestly? correct. 👑
  • LC_CTYPE — Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multi-byte characters in arguments).
  • LC_MESSAGES — Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error, and informative messages written to standard output.
  • NLSPATH — Determine the location of message catalogs for the processing of LC_MESSAGES.

🦋 ASYNCHRONOUS EVENTS 🦋

Default. nothing extra, nothing spicy. 💅

⭐ STDOUT ⭐

The standard output shall consist of information about each job selected, in an unspecified format. The information shall include at least:

  • the job ID
  • the user ID or name
  • the remote system name

like, the format is a mystery but those three things are mandatory, no skipping. 🫶

💀 STDERR 💀

The standard error shall be used only for diagnostic messages. that's its whole job, that's its whole personality.

🌈 OUTPUT FILES 🌈

None.

🎀 EXTENDED DESCRIPTION 🎀

None. we keep it simple around here.

🔥 EXIT STATUS 🔥

The following exit values shall be returned:

  • 0 — Successful completion. slay. ✨
  • >0 — An error occurred. 😭

💜 CONSEQUENCES OF ERRORS 💜

Default.

and just so you know, the following sections are informative. they're the commentary track, not the rules. 📝

🫶 APPLICATION USAGE 🫶

This utility is part of the UUCP Utilities option and need not be supported by all implementations. so if it's not there, it's not you, it's the system. 🙈

💖 EXAMPLES 💖

None.

🧚 RATIONALE 🧚

None.

🌸 FUTURE DIRECTIONS 🌸

None.

👑 SEE ALSO 👑

  • uucp

The Base Definitions volume of POSIX.1‐2017, Chapter 8, Environment Variables, Chapter 11, General Terminal Interface, Section 12.2, Utility Syntax Guidelines

Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1-2017, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group.

In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html .

Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html .

okay that's the whole thing bestie, we ate and left absolutely no crumbs 💅✨ this one came to you from IEEE/The Open Group, dated 2017, and it lives in the POSIX Programmer's Manual as UUSTAT(1POSIX) — mwah, go read uucp next, iykyk. 🦋💖

📦 where this page comes from