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

uux.1p (10296B)


  1. '\" et
  2. .TH UUX "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. uux
  12. \(em remote command execution
  13. .SH SYNOPSIS
  14. .LP
  15. .nf
  16. uux \fB[\fR-jnp\fB] \fIcommand-string\fR
  17. .fi
  18. .SH DESCRIPTION
  19. The
  20. .IR uux
  21. utility shall gather zero or more files from various systems, execute a
  22. shell pipeline (see
  23. .IR "Section 2.9" ", " "Shell Commands")
  24. on a specified system, and then send the standard output of the command
  25. to a file on a specified system. Only the first command of a pipeline
  26. can have a
  27. .IR system-name !
  28. prefix. All other commands in the pipeline shall be executed on the
  29. system of the first command.
  30. .P
  31. The following restrictions are applicable to the shell pipeline
  32. processed by
  33. .IR uux :
  34. .IP " *" 4
  35. In gathering files from different systems, pathname expansion shall
  36. not be performed by
  37. .IR uux .
  38. Thus, a request such as:
  39. .RS 4
  40. .sp
  41. .RS 4
  42. .nf
  43. uux "c99 remsys!\(ti/*.c"
  44. .fi
  45. .P
  46. .RE
  47. .P
  48. would attempt to copy the file named literally
  49. .BR *.c
  50. to the local system.
  51. .RE
  52. .IP " *" 4
  53. The redirection operators
  54. .BR \(dq>>\(dq ,
  55. .BR \(dq<<\(dq ,
  56. .BR \(dq>|\(dq ,
  57. and
  58. .BR \(dq>&\(dq
  59. shall not be accepted. Any use of these redirection operators shall
  60. cause this utility to write an error message describing the problem
  61. and exit with a non-zero exit status.
  62. .IP " *" 4
  63. The reserved word
  64. .BR !
  65. cannot be used at the head of the pipeline to modify the exit status.
  66. (See the
  67. .IR command-string
  68. operand description below.)
  69. .IP " *" 4
  70. Alias substitution shall not be performed.
  71. .P
  72. A filename can be specified as for
  73. .IR uucp ;
  74. it can be an absolute pathname, a pathname preceded by ~\c
  75. .IR name
  76. (which is replaced by the corresponding login directory), a pathname
  77. specified as ~/\^\c
  78. .IR dest
  79. (\c
  80. .IR dest
  81. is prefixed by the public directory called
  82. .IR PUBDIR ;
  83. the actual location of
  84. .IR PUBDIR
  85. is implementation-defined), or a simple filename (which is prefixed
  86. by
  87. .IR uux
  88. with the current directory). See
  89. .IR "\fIuucp\fR\^"
  90. for the details.
  91. .P
  92. The execution of commands on remote systems shall take place in an
  93. execution directory known to the
  94. .IR uucp
  95. system. All files required for the execution shall be put into this
  96. directory unless they already reside on that machine. Therefore, the
  97. application shall ensure that non-local filenames (without path or
  98. machine reference) are unique within the
  99. .IR uux
  100. request.
  101. .P
  102. The
  103. .IR uux
  104. utility shall attempt to get all files to the execution system. For
  105. files that are output files, the application shall ensure that the
  106. filename is escaped using parentheses.
  107. .P
  108. The remote system shall notify the user by mail if the requested
  109. command on the remote system was disallowed or the files were not
  110. accessible. This notification can be turned off by the
  111. .BR \-n
  112. option.
  113. .P
  114. Typical implementations of this utility require a communications line
  115. configured to use the Base Definitions volume of POSIX.1\(hy2017,
  116. .IR "Chapter 11" ", " "General Terminal Interface",
  117. but other communications means may be used. On systems where there are
  118. no available communications means (either temporarily or permanently),
  119. this utility shall write an error message describing the problem and
  120. exit with a non-zero exit status.
  121. .P
  122. The
  123. .IR uux
  124. utility cannot guarantee support for all character encodings in all
  125. circumstances. For example, transmission data may be restricted to 7
  126. bits by the underlying network, 8-bit data and filenames need not be
  127. portable to non-internationalized systems, and so on. Under these
  128. circumstances, it is recommended that only characters defined in the
  129. ISO/IEC\ 646:\|1991 standard International Reference Version (equivalent to ASCII) 7-bit range
  130. of characters be used and that only characters defined in the portable
  131. filename character set be used for naming files.
  132. .SH OPTIONS
  133. The
  134. .IR uux
  135. utility shall conform to the Base Definitions volume of POSIX.1\(hy2017,
  136. .IR "Section 12.2" ", " "Utility Syntax Guidelines".
  137. .P
  138. The following options shall be supported:
  139. .IP "\fB\-j\fP" 10
  140. Write the job identification string to standard output. This job
  141. identification can be used by
  142. .IR uustat
  143. to obtain the status or terminate a job.
  144. .IP "\fB\-n\fP" 10
  145. Do not notify the user if the command fails.
  146. .IP "\fB\-p\fP" 10
  147. Make the standard input to
  148. .IR uux
  149. the standard input to the
  150. .IR command-string .
  151. .SH OPERANDS
  152. The following operand shall be supported:
  153. .IP "\fIcommand-string\fR" 10
  154. .br
  155. A string made up of one or more arguments that are similar to normal
  156. command arguments, except that the command and any filenames can be
  157. prefixed by
  158. .IR system-name !.
  159. A null
  160. .IR system-name
  161. shall be interpreted as the local system.
  162. .SH STDIN
  163. The standard input shall not be used unless the
  164. .BR '\-'
  165. or
  166. .BR \-p
  167. option is specified; in those cases, the standard input shall be made
  168. the standard input of the
  169. .IR command-string .
  170. .SH "INPUT FILES"
  171. Input files shall be selected according to the contents of
  172. .IR command-string .
  173. .SH "ENVIRONMENT VARIABLES"
  174. The following environment variables shall affect the execution of
  175. .IR uux :
  176. .IP "\fILANG\fP" 10
  177. Provide a default value for the internationalization variables that are
  178. unset or null. (See the Base Definitions volume of POSIX.1\(hy2017,
  179. .IR "Section 8.2" ", " "Internationalization Variables"
  180. for the precedence of internationalization variables used to determine
  181. the values of locale categories.)
  182. .IP "\fILC_ALL\fP" 10
  183. If set to a non-empty string value, override the values of all the
  184. other internationalization variables.
  185. .IP "\fILC_CTYPE\fP" 10
  186. Determine the locale for the interpretation of sequences of bytes of
  187. text data as characters (for example, single-byte as opposed to
  188. multi-byte characters in arguments).
  189. .IP "\fILC_MESSAGES\fP" 10
  190. .br
  191. Determine the locale that should be used to affect the format and
  192. contents of diagnostic messages written to standard error.
  193. .IP "\fINLSPATH\fP" 10
  194. Determine the location of message catalogs for the processing of
  195. .IR LC_MESSAGES .
  196. .SH "ASYNCHRONOUS EVENTS"
  197. Default.
  198. .SH STDOUT
  199. The standard output shall not be used unless the
  200. .BR \-j
  201. option is specified; in that case, the job identification string shall
  202. be written to standard output in the following format:
  203. .sp
  204. .RS 4
  205. .nf
  206. "%s\en", <\fIjobid\fR>
  207. .fi
  208. .P
  209. .RE
  210. .SH STDERR
  211. The standard error shall be used only for diagnostic messages.
  212. .SH "OUTPUT FILES"
  213. Output files shall be created or written, or both, according to the
  214. contents of
  215. .IR command-string .
  216. .P
  217. If
  218. .BR \-n
  219. is not used, mail files shall be modified following any command or
  220. file-access failures on the remote system.
  221. .SH "EXTENDED DESCRIPTION"
  222. None.
  223. .SH "EXIT STATUS"
  224. The following exit values shall be returned:
  225. .IP "\00" 6
  226. Successful completion.
  227. .IP >0 6
  228. An error occurred.
  229. .SH "CONSEQUENCES OF ERRORS"
  230. Default.
  231. .LP
  232. .IR "The following sections are informative."
  233. .SH "APPLICATION USAGE"
  234. This utility is part of the UUCP Utilities option and need not be
  235. supported by all implementations.
  236. .P
  237. Note that, for security reasons, many installations limit the list of
  238. commands executable on behalf of an incoming request from
  239. .IR uux .
  240. Many sites permit little more than the receipt of mail via
  241. .IR uux .
  242. .P
  243. Any characters special to the command interpreter should be quoted
  244. either by quoting the entire
  245. .IR command-string
  246. or quoting the special characters as individual arguments.
  247. .P
  248. As noted in
  249. .IR uucp ,
  250. shell pattern matching notation
  251. characters appearing in pathnames are expanded on the appropriate local
  252. system. This is done under the control of local settings of
  253. .IR LC_COLLATE
  254. and
  255. .IR LC_CTYPE .
  256. Thus, care should be taken when using bracketed filename patterns, as
  257. collation and typing rules may vary from one system to another. Also
  258. be aware that certain types of expression (that is, equivalence
  259. classes, character classes, and collating symbols) need not be
  260. supported on non-internationalized systems.
  261. .SH EXAMPLES
  262. .IP " 1." 4
  263. The following command gets
  264. .BR file1
  265. from system
  266. .BR a
  267. and
  268. .BR file2
  269. from system
  270. .BR b ,
  271. executes
  272. .IR diff
  273. on the local system, and puts the results in
  274. .BR file.diff
  275. in the local
  276. .IR PUBDIR
  277. directory. (\c
  278. .IR PUBDIR
  279. is the
  280. .IR uucp
  281. public directory on the local system.)
  282. .RS 4
  283. .sp
  284. .RS 4
  285. .nf
  286. uux "!diff a!/usr/file1 b!/a4/file2 >!\(ti/file.diff"
  287. .fi
  288. .P
  289. .RE
  290. .RE
  291. .IP " 2." 4
  292. The following command fails because
  293. .IR uux
  294. places all files copied to a system in the same working directory.
  295. Although the files
  296. .BR xyz
  297. are from two different systems, their filenames are the same and
  298. conflict.
  299. .RS 4
  300. .sp
  301. .RS 4
  302. .nf
  303. uux "!diff a!/usr1/xyz b!/usr2/xyz >!\(ti/xyz.diff"
  304. .fi
  305. .P
  306. .RE
  307. .RE
  308. .IP " 3." 4
  309. The following command succeeds (assuming
  310. .IR diff
  311. is permitted on system
  312. .BR a )
  313. because the file local to system
  314. .BR a
  315. is not copied to the working directory, and hence does not conflict with
  316. the file from system
  317. .BR c .
  318. .RS 4
  319. .sp
  320. .RS 4
  321. .nf
  322. uux "a!diff a!/usr/xyz c!/usr/xyz >!\(ti/xyz.diff"
  323. .fi
  324. .P
  325. .RE
  326. .RE
  327. .SH RATIONALE
  328. None.
  329. .SH "FUTURE DIRECTIONS"
  330. None.
  331. .SH "SEE ALSO"
  332. .IR "Chapter 2" ", " "Shell Command Language",
  333. .IR "\fIuucp\fR\^",
  334. .IR "\fIuuencode\fR\^",
  335. .IR "\fIuustat\fR\^"
  336. .P
  337. The Base Definitions volume of POSIX.1\(hy2017,
  338. .IR "Chapter 8" ", " "Environment Variables",
  339. .IR "Chapter 11" ", " "General Terminal Interface",
  340. .IR "Section 12.2" ", " "Utility Syntax Guidelines"
  341. .\"
  342. .SH COPYRIGHT
  343. Portions of this text are reprinted and reproduced in electronic form
  344. from IEEE Std 1003.1-2017, Standard for Information Technology
  345. -- Portable Operating System Interface (POSIX), The Open Group Base
  346. Specifications Issue 7, 2018 Edition,
  347. Copyright (C) 2018 by the Institute of
  348. Electrical and Electronics Engineers, Inc and The Open Group.
  349. In the event of any discrepancy between this version and the original IEEE and
  350. The Open Group Standard, the original IEEE and The Open Group Standard
  351. is the referee document. The original Standard can be obtained online at
  352. http://www.opengroup.org/unix/online.html .
  353. .PP
  354. Any typographical or formatting errors that appear
  355. in this page are most likely
  356. to have been introduced during the conversion of the source files to
  357. man page format. To report such errors, see
  358. https://www.kernel.org/doc/man-pages/reporting_bugs.html .