1UUX(1P) POSIX Programmer's Manual UUX(1P)
2
6 This manual page is part of the POSIX Programmer's Manual. The Linux
7 implementation of this interface may differ (consult the corresponding
8 Linux manual page for details of Linux behavior), or the interface may
9 not be implemented on Linux.
10
13 uux — remote command execution
14
16 uux [−jnp] command−string
17
19 The uux utility shall gather zero or more files from various systems,
20 execute a shell pipeline (see Section 2.9, Shell Commands) on a speci‐
21 fied system, and then send the standard output of the command to a file
22 on a specified system. Only the first command of a pipeline can have a
23 system-name! prefix. All other commands in the pipeline shall be exe‐
24 cuted on the system of the first command.
25 The following restrictions are applicable to the shell pipeline pro‐
27 cessed by uux:
28 * In gathering files from different systems, pathname expansion shall
30 not be performed by uux. Thus, a request such as:
31 uux "c99 remsys!~/*.c"
33 would attempt to copy the file named literally *.c to the local
35 system.
36 * The redirection operators ">>", "<<", ">|", and ">&" shall not be
38 accepted. Any use of these redirection operators shall cause this
39 utility to write an error message describing the problem and exit
40 with a non-zero exit status.
41 * The reserved word ! cannot be used at the head of the pipeline to
43 modify the exit status. (See the command-string operand descrip‐
44 tion below.)
45 * Alias substitution shall not be performed.
47 A filename can be specified as for uucp; it can be an absolute path‐
49 name, a pathname preceded by ~name (which is replaced by the corre‐
50 sponding login directory), a pathname specified as ~/dest (dest is pre‐
51 fixed by the public directory called PUBDIR; the actual location of
52 PUBDIR is implementation-defined), or a simple filename (which is pre‐
53 fixed by uux with the current directory). See uucp for the details.
54 The execution of commands on remote systems shall take place in an exe‐
56 cution directory known to the uucp system. All files required for the
57 execution shall be put into this directory unless they already reside
58 on that machine. Therefore, the application shall ensure that non-local
59 filenames (without path or machine reference) are unique within the uux
60 request.
61 The uux utility shall attempt to get all files to the execution system.
63 For files that are output files, the application shall ensure that the
64 filename is escaped using parentheses.
65 The remote system shall notify the user by mail if the requested com‐
67 mand on the remote system was disallowed or the files were not accessi‐
68 ble. This notification can be turned off by the −n option.
69 Typical implementations of this utility require a communications line
71 configured to use the Base Definitions volume of POSIX.1‐2008, Chapter
72 11, General Terminal Interface, but other communications means may be
73 used. On systems where there are no available communications means
74 (either temporarily or permanently), this utility shall write an error
75 message describing the problem and exit with a non-zero exit status.
76 The uux utility cannot guarantee support for all character encodings in
78 all circumstances. For example, transmission data may be restricted to
79 7 bits by the underlying network, 8-bit data and filenames need not be
80 portable to non-internationalized systems, and so on. Under these cir‐
81 cumstances, it is recommended that only characters defined in the
82 ISO/IEC 646:1991 standard International Reference Version (equivalent
83 to ASCII) 7-bit range of characters be used and that only characters
84 defined in the portable filename character set be used for naming
85 files.
86
88 The uux utility shall conform to the Base Definitions volume of
89 POSIX.1‐2008, Section 12.2, Utility Syntax Guidelines.
90 The following options shall be supported:
92 −j Write the job identification string to standard output. This
94 job identification can be used by uustat to obtain the status
95 or terminate a job.
96 −n Do not notify the user if the command fails.
98 −p Make the standard input to uux the standard input to the com‐
100 mand-string.
101
103 The following operand shall be supported:
104 command-string
106 A string made up of one or more arguments that are similar to
107 normal command arguments, except that the command and any
108 filenames can be prefixed by system-name!. A null system-
109 name shall be interpreted as the local system.
110
112 The standard input shall not be used unless the '−' or −p option is
113 specified; in those cases, the standard input shall be made the stan‐
114 dard input of the command-string.
115
117 Input files shall be selected according to the contents of command-
118 string.
119
121 The following environment variables shall affect the execution of uux:
122 LANG Provide a default value for the internationalization vari‐
124 ables that are unset or null. (See the Base Definitions vol‐
125 ume of POSIX.1‐2008, Section 8.2, Internationalization Vari‐
126 ables for the precedence of internationalization variables
127 used to determine the values of locale categories.)
128 LC_ALL If set to a non-empty string value, override the values of
130 all the other internationalization variables.
131 LC_CTYPE Determine the locale for the interpretation of sequences of
133 bytes of text data as characters (for example, single-byte as
134 opposed to multi-byte characters in arguments).
135 LC_MESSAGES
137 Determine the locale that should be used to affect the format
138 and contents of diagnostic messages written to standard
139 error.
140 NLSPATH Determine the location of message catalogs for the processing
142 of LC_MESSAGES.
143
145 Default.
146
148 The standard output shall not be used unless the −j option is speci‐
149 fied; in that case, the job identification string shall be written to
150 standard output in the following format:
151 "%s\n", <jobid>
153
155 The standard error shall be used only for diagnostic messages.
156
158 Output files shall be created or written, or both, according to the
159 contents of command-string.
160 If −n is not used, mail files shall be modified following any command
162 or file-access failures on the remote system.
163
165 None.
166
168 The following exit values shall be returned:
169 0 Successful completion.
171 >0 An error occurred.
173
175 Default.
176 The following sections are informative.
178
180 This utility is part of the UUCP Utilities option and need not be sup‐
181 ported by all implementations.
182 Note that, for security reasons, many installations limit the list of
184 commands executable on behalf of an incoming request from uux. Many
185 sites permit little more than the receipt of mail via uux.
186 Any characters special to the command interpreter should be quoted
188 either by quoting the entire command-string or quoting the special
189 characters as individual arguments.
190 As noted in uucp, shell pattern matching notation characters appearing
192 in pathnames are expanded on the appropriate local system. This is done
193 under the control of local settings of LC_COLLATE and LC_CTYPE. Thus,
194 care should be taken when using bracketed filename patterns, as colla‐
195 tion and typing rules may vary from one system to another. Also be
196 aware that certain types of expression (that is, equivalence classes,
197 character classes, and collating symbols) need not be supported on non-
198 internationalized systems.
199
201 1. The following command gets file1 from system a and file2 from sys‐
202 tem b, executes diff on the local system, and puts the results in
203 file.diff in the local PUBDIR directory. (PUBDIR is the uucp public
204 directory on the local system.)
205 uux "!diff a!/usr/file1 b!/a4/file2 >!~/file.diff"
207 2. The following command fails because uux places all files copied to
209 a system in the same working directory. Although the files xyz are
210 from two different systems, their filenames are the same and con‐
211 flict.
212 uux "!diff a!/usr1/xyz b!/usr2/xyz >!~/xyz.diff"
214 3. The following command succeeds (assuming diff is permitted on sys‐
216 tem a) because the file local to system a is not copied to the
217 working directory, and hence does not conflict with the file from
218 system c.
219 uux "a!diff a!/usr/xyz c!/usr/xyz >!~/xyz.diff"
221
223 None.
224
226 None.
227
229 Chapter 2, Shell Command Language, uucp, uuencode, uustat
230 The Base Definitions volume of POSIX.1‐2008, Chapter 8, Environment
232 Variables, Chapter 11, General Terminal Interface, Section 12.2, Util‐
233 ity Syntax Guidelines
234
236 Portions of this text are reprinted and reproduced in electronic form
237 from IEEE Std 1003.1, 2013 Edition, Standard for Information Technology
238 -- Portable Operating System Interface (POSIX), The Open Group Base
239 Specifications Issue 7, Copyright (C) 2013 by the Institute of Electri‐
240 cal and Electronics Engineers, Inc and The Open Group. (This is
241 POSIX.1-2008 with the 2013 Technical Corrigendum 1 applied.) In the
242 event of any discrepancy between this version and the original IEEE and
243 The Open Group Standard, the original IEEE and The Open Group Standard
244 is the referee document. The original Standard can be obtained online
245 at http://www.unix.org/online.html .
246 Any typographical or formatting errors that appear in this page are
248 most likely to have been introduced during the conversion of the source
249 files to man page format. To report such errors, see https://www.ker‐
250 nel.org/doc/man-pages/reporting_bugs.html .
251IEEE/The Open Group 2013 UUX(1P)