QSIG(1P)

📦 version 2017a, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, nixpkgs unstable, opensuse-leap 16.0

🦋 PROLOG 🦋

okay bestie, real talk before we get into it: this manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (so like, go check the corresponding Linux manual page for details on Linux behavior, fr), or honestly the interface may not even be implemented on Linux at all. 💀

✨ NAME ✨

qsig — signal batch jobs. yes queen, that's the whole job.

🎀 SYNOPSIS 🎀

qsig [-s signal] job_identifier...

💅 DESCRIPTION 💅

okay so. To signal a batch job means you're sending a signal to the session leader of that batch job. That's it, that's the vibe.

A batch job gets signaled by sending a request to the batch server that manages the batch job. And qsig is literally just a user-accessible batch client that requests the signaling of a batch job. main character utility behavior tbh.

The qsig utility shall signal those batch jobs for which a job_identifier is presented to the utility. And it shall not signal any batch jobs whose batch job_identifiers are not presented to the utility. no extras, no surprises, we're not out here freelancing 🌸

The qsig utility shall signal batch jobs in the order in which the corresponding batch job_identifiers are presented to the utility. So order matters, bestie. And if the qsig utility fails to process a batch job_identifier successfully? It shall proceed to process the remaining batch job_identifiers, if any. we do not stop the whole party for one flop. 🙈

The qsig utility shall signal batch jobs by sending a Signal Job Request to the batch server that manages the batch job.

For each successfully processed batch job_identifier, the qsig utility shall have received a completion reply to each Signal Job Request sent to a batch server at the time the utility exits. yes, we wait for the receipts. ✨

🌈 OPTIONS 🌈

The qsig utility shall conform to the Base Definitions volume of POSIX.1‐2017, Section 12.2, Utility Syntax Guidelines. (iconic behavior, as always)

The following option shall be supported by the implementation:

  • -s signal — Define the signal to be sent to the batch job.

The qsig utility shall accept a signal option-argument that is either a symbolic signal name or an unsigned integer signal number (see the POSIX.1‐1990 standard, Section 3.3.1.1). The qsig utility shall accept signal names for which the SIG prefix has been omitted. yes, you can drop the SIG, it's chill.

If the signal option-argument is a signal name, the qsig utility shall send that name.

If the signal option-argument is a number, the qsig utility shall send the signal value represented by the number.

If the -s option is not presented to the qsig utility, the utility shall send the signal SIGTERM to each signaled batch job. so like, no option = SIGTERM, that's the default, periodt. 💜

🌸 OPERANDS 🌸

The qsig utility shall accept one or more operands that conform to the syntax for a batch job_identifier (see Section 3.3.1, Batch Job Identifier).

🫶 STDIN 🫶

Not used. she does not read your vibes from stdin, sorry.

🍓 INPUT FILES 🍓

None.

🧚 ENVIRONMENT VARIABLES 🧚

The following environment variables shall affect the execution of qsig:

  • 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. she's the boss of everyone else, lowkey.
  • 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.
  • LOGNAME — Determine the login name of the user. yeah that's you 💅

⭐ ASYNCHRONOUS EVENTS ⭐

Default.

💖 STDOUT 💖

An implementation of the qsig utility may write informative messages to standard output. cute little updates, if it wants to.

💀 STDERR 💀

The standard error shall be used only for diagnostic messages. only for the messy stuff.

🦋 OUTPUT FILES 🦋

None.

👑 EXTENDED DESCRIPTION 👑

None.

🔥 EXIT STATUS 🔥

The following exit values shall be returned:

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

🎀 CONSEQUENCES OF ERRORS 🎀

In addition to the default behavior, the qsig utility shall not be required to write a diagnostic message to standard error when the error reply received from a batch server indicates that the batch job_identifier does not exist on the server. Whether or not the qsig utility waits to output the diagnostic message while attempting to locate the batch job on other servers is implementation-defined. so like, don't come for her for being quiet, okay?

The following sections are informative.

🌈 APPLICATION USAGE 🌈

None.

✨ EXAMPLES ✨

None.

💅 RATIONALE 💅

The qsig utility allows users to signal batch jobs. (that's the whole thesis, bestie)

A user may be unable to signal a batch job with the kill utility of the operating system for a number of reasons. First, the process ID of the batch job may be unknown to the user. Second, the processes of the batch job may be on a remote node. However, by virtue of communication between batch nodes, the qsig utility can arrange for the signaling of a process. networking ate that one up fr fr 🌐

Because a batch job that is not running cannot be signaled, and because the signal may not terminate the batch job, the qsig utility is not a substitute for the qdel utility. read that again. qsig ≠ qdel. they are different girls. 🙈

The options of the qsig utility allow the user to specify the signal that is to be sent to the batch job.

The -s option allows users to specify a signal by name or by number, and thus override the default signal. The POSIX.1‐1990 standard defines signals by both name and number. both! iconic.

The qsig utility is a new utility, vis-a-vis existing practice; it has been defined in this volume of POSIX.1‐2017 in response to user-perceived shortcomings in existing practice. she's new here and she's already serving. 👑

🌸 FUTURE DIRECTIONS 🌸

The qsig utility may be removed in a future version. 💀

not to be dramatic but she might get cancelled in a future version, so use her while she's here.

💜 SEE ALSO 💜

  • Chapter 3, Batch Environment Services
  • kill
  • qdel
  • The Base Definitions volume of POSIX.1‐2017, Chapter 8, Environment Variables, 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 page, bestie — this one's from IEEE/The Open Group, 2017, and it's the QSIG(1P) page in the POSIX Programmer's Manual. go signal some batch jobs, you absolute icon. 💖✨🎀

📦 where this page comes from