qsig(1B)

💖 NAME 💖

okay so this is the tea, bestie: qsig is literally here to signal pbs batch job. The manual name is qsig(1B) — and yes, she's iconic, I'm obsessed, no notes. 💅

🦋 SYNOPSIS 🦋

qsig [-s signal] job_identifier ...

✨ DESCRIPTION ✨

The qsig command is like, “hey server, please send a signal to the executing batch jobs.” The signal gets sent to the session leader of the job. That's the main character of this operation, periodt. ✨

If the -s option is not specified, SIGTERM is sent. Default behavior, slay. 💅

The request to signal a batch job will be rejected if:

• The user is not authorized to signal the job.
• The job is not in the running state.
• The requested signal is not supported by the system upon which the job is executing.

The qsig command sends a Signal Job batch request to the server which owns the job. That's the whole vibe: it's not doing the signal itself, it's asking the server that owns the job. No cap. iykyk. 🫶

🌸 OPTIONS 🌸

• -s signal — declares which signal is sent to the job.

The signal argument is either a signal name, e.g. SIGKILL, the signal name without the SIG prefix, e.g. KILL, or an unsigned signal number, e.g. 9.

The signal name SIGNULL is allowed; the server will send signal 0 to the job, which will have no effect on the job, but will cause an obituary to be sent if the job is no longer executing. 💀

Not all signal names will be recognized by qsig. If it doesn't recognize the signal name, try issuing the signal number instead.

Two special signal names, "suspend" and "resume", are used to suspend and resume jobs. Cray systems use the Cray-specific suspend()/resume() calls.

On non-Cray system, suspend causes a SIGTSTP to be sent to all processes in job's top task, wait 5 seconds, and then send a SIGSTOP to all processes in all tasks on all nodes in the job. This differs from TORQUE 2.0.0 which did not have the ability to propogate signals to sister nodes. resume sends a SIGCONT to all processes in all tasks on all nodes.

When suspended, a job continues to occupy system resources but is not executing and is not charged for walltime. The job will be listed in the "S" state. Manager or operator privilege is required to suspend or resume a job.

Note that interactive jobs may not resume properly because the top-level shell will background the suspended child process. 😭

🎀 OPERANDS 🎀

qsig accepts one or more job_identifier operands of the form:

sequence_number[.server_name][@server]

💀 STANDARD ERROR 💀

The qsig command will write diagnostic messages to standard error for each error occurrence. So if something goes wrong, it's gonna tell you, bestie. 🫶

✅ EXIT STATUS ✅

Upon successful processing of all the operands presented to the qsig command, the exit status will be a value of zero. Slay, ate, no crumbs. 0️⃣

If the qsig command fails to process any operand, the command exits with a value greater than zero. Not slay, but useful. 💀

🌈 SEE ALSO 🌈

• qsub(1B)
• pbs_sigjob(3B)
• pbs_resources_*(7B) where * is system type
• and the PBS ERS.

💖 okay that's the whole manual, bestie — brought to you by the Local source and the qsig(1B) version. The footer didn't give us a date, so no invented date tea from me. 🎀✨