logo

oasis-root

Compiled tree of Oasis Linux based on own branch at <https://hacktivis.me/git/oasis/> git clone https://anongit.hacktivis.me/git/oasis-root.git

qdel.1p (6504B)

    

  1. '\" et
  2. .TH QDEL "1P" 2017 "IEEE/The Open Group" "POSIX Programmer's Manual"
  3. .\"
  4. .SH PROLOG
  5. This manual page is part of the POSIX Programmer's Manual.
  6. The Linux implementation of this interface may differ (consult
  7. the corresponding Linux manual page for details of Linux behavior),
  8. or the interface may not be implemented on Linux.
  9. .\"
  10. .SH NAME
  11. qdel
  12. \(em delete batch jobs
  13. .SH SYNOPSIS
  14. .LP
  15. .nf
  16. qdel \fIjob_identifier\fP...
  17. .fi
  18. .SH DESCRIPTION
  19. A batch job is deleted by sending a request to the batch server that
  20. manages the batch job. A batch job that has been deleted is no longer
  21. subject to management by batch services.
  22. .P
  23. The
  24. .IR qdel
  25. utility is a user-accessible client of batch services that requests the
  26. deletion of one or more batch jobs.
  27. .P
  28. The
  29. .IR qdel
  30. utility shall request a batch server to delete those batch jobs for
  31. which a batch
  32. .IR job_identifier
  33. is presented to the utility.
  34. .P
  35. The
  36. .IR qdel
  37. utility shall delete batch jobs in the order in which their batch
  38. .IR job_identifier s
  39. are presented to the utility.
  40. .P
  41. If the
  42. .IR qdel
  43. utility fails to process any batch
  44. .IR job_identifier
  45. successfully, the utility shall proceed to process the remaining batch
  46. .IR job_identifier s,
  47. if any.
  48. .P
  49. The
  50. .IR qdel
  51. utility shall delete each batch job by sending a
  52. .IR "Delete Job Request"
  53. to the batch server that manages the batch job.
  54. .P
  55. The
  56. .IR qdel
  57. utility shall not exit until the batch job corresponding to each
  58. successfully processed batch
  59. .IR job_identifier
  60. has been deleted.
  61. .SH OPTIONS
  62. None.
  63. .SH OPERANDS
  64. The
  65. .IR qdel
  66. utility shall accept one or more operands that conform to the syntax
  67. for a batch
  68. .IR job_identifier
  69. (see
  70. .IR "Section 3.3.1" ", " "Batch Job Identifier").
  71. .SH STDIN
  72. Not used.
  73. .SH "INPUT FILES"
  74. None.
  75. .SH "ENVIRONMENT VARIABLES"
  76. The following environment variables shall affect the execution of
  77. .IR qdel :
  78. .IP "\fILANG\fP" 10
  79. Provide a default value for the internationalization variables that are
  80. unset or null. (See the Base Definitions volume of POSIX.1\(hy2017,
  81. .IR "Section 8.2" ", " "Internationalization Variables"
  82. the precedence of internationalization variables used to determine the
  83. values of locale categories.)
  84. .IP "\fILC_ALL\fP" 10
  85. If set to a non-empty string value, override the values of all the
  86. other internationalization variables.
  87. .IP "\fILC_CTYPE\fP" 10
  88. Determine the locale for the interpretation of sequences of bytes of
  89. text data as characters (for example, single-byte as opposed to
  90. multi-byte characters in arguments).
  91. .IP "\fILC_MESSAGES\fP" 10
  92. .br
  93. Determine the locale that should be used to affect the format and
  94. contents of diagnostic messages written to standard error.
  95. .IP "\fILOGNAME\fP" 10
  96. Determine the login name of the user.
  97. .SH "ASYNCHRONOUS EVENTS"
  98. Default.
  99. .SH STDOUT
  100. An implementation of the
  101. .IR qdel
  102. utility may write informative messages to standard output.
  103. .SH STDERR
  104. The standard error shall be used only for diagnostic messages.
  105. .SH "OUTPUT FILES"
  106. None.
  107. .SH "EXTENDED DESCRIPTION"
  108. None.
  109. .SH "EXIT STATUS"
  110. The following exit values shall be returned:
  111. .IP "\00" 6
  112. Successful completion.
  113. .IP >0 6
  114. An error occurred.
  115. .SH "CONSEQUENCES OF ERRORS"
  116. In addition to the default behavior, the
  117. .IR qdel
  118. utility shall not be required to write a diagnostic message to standard
  119. error when the error reply received from a batch server indicates that
  120. the batch
  121. .IR job_identifier
  122. does not exist on the server. Whether or not the
  123. .IR qdel
  124. utility waits to output the diagnostic message while attempting to
  125. locate the job on other servers is implementation-defined.
  126. .LP
  127. .IR "The following sections are informative."
  128. .SH "APPLICATION USAGE"
  129. None.
  130. .SH EXAMPLES
  131. None.
  132. .SH RATIONALE
  133. The
  134. .IR qdel
  135. utility allows users and administrators to delete jobs.
  136. .P
  137. The
  138. .IR qdel
  139. utility provides functionality that is not otherwise available. For
  140. example, the
  141. .IR kill
  142. utility of the operating system does not suffice. First, to use the
  143. .IR kill
  144. utility, the user might have to log in on a remote node, because the
  145. .IR kill
  146. utility does not operate across the network. Second, unlike
  147. .IR qdel ,
  148. .IR kill
  149. cannot remove jobs from queues. Lastly, the arguments of the
  150. .IR qdel
  151. utility are job identifiers rather than process identifiers, and so
  152. this utility can be passed the output of the
  153. .IR qselect
  154. utility, thus providing users with a means of deleting a list of jobs.
  155. .P
  156. Because a set of jobs can be selected using the
  157. .IR qselect
  158. utility, the
  159. .IR qdel
  160. utility has not been complicated with options that provide for
  161. selection of jobs. Instead, the batch jobs to be deleted are identified
  162. individually by their job identifiers.
  163. .P
  164. Historically, the
  165. .IR qdel
  166. utility has been a component of NQS, the existing practice on which it
  167. is based. However, the
  168. .IR qdel
  169. utility defined in this volume of POSIX.1\(hy2017 does not provide an option for specifying a
  170. signal number to send to the batch job prior to the killing of the
  171. process; that capability has been subsumed by the
  172. .IR qsig
  173. utility.
  174. .P
  175. A discussion was held about the delays of networking and the
  176. possibility that the batch server may never respond, due to a down
  177. router, down batch server, or other network mishap. The DESCRIPTION
  178. records this under the words ``fails to process any job identifier''.
  179. In the broad sense, the network problem is also an error, which causes
  180. the failure to process the batch job identifier.
  181. .SH "FUTURE DIRECTIONS"
  182. The
  183. .IR qdel
  184. utility may be removed in a future version.
  185. .SH "SEE ALSO"
  186. .IR "Chapter 3" ", " "Batch Environment Services",
  187. .IR "\fIkill\fR\^",
  188. .IR "\fIqselect\fR\^",
  189. .IR "\fIqsig\fR\^"
  190. .P
  191. The Base Definitions volume of POSIX.1\(hy2017,
  192. .IR "Chapter 8" ", " "Environment Variables"
  193. .\"
  194. .SH COPYRIGHT
  195. Portions of this text are reprinted and reproduced in electronic form
  196. from IEEE Std 1003.1-2017, Standard for Information Technology
  197. -- Portable Operating System Interface (POSIX), The Open Group Base
  198. Specifications Issue 7, 2018 Edition,
  199. Copyright (C) 2018 by the Institute of
  200. Electrical and Electronics Engineers, Inc and The Open Group.
  201. In the event of any discrepancy between this version and the original IEEE and
  202. The Open Group Standard, the original IEEE and The Open Group Standard
  203. is the referee document. The original Standard can be obtained online at
  204. http://www.opengroup.org/unix/online.html .
  205. .PP
  206. Any typographical or formatting errors that appear
  207. in this page are most likely
  208. to have been introduced during the conversion of the source files to
  209. man page format. To report such errors, see
  210. https://www.kernel.org/doc/man-pages/reporting_bugs.html .