1UUX(P) POSIX Programmer's Manual UUX(P)
2
6 uux - remote command execution
7
9 uux [-np] command-string
10 uux [-jnp] command-string
12
15 The uux utility shall gather zero or more files from various systems,
16 execute a shell pipeline (see Shell Commands ) on a specified system,
17 and then send the standard output of the command to a file on a speci‐
18 fied system. Only the first command of a pipeline can have a system-
19 name! prefix. All other commands in the pipeline shall be executed on
20 the system of the first command.
21 The following restrictions are applicable to the shell pipeline pro‐
23 cessed by uux:
24 * In gathering files from different systems, pathname expansion shall
26 not be performed by uux. Thus, a request such as:
27 uux "c99 remsys!~/*.c"
30 would attempt to copy the file named literally *.c to the local system.
32 * The redirection operators ">>" , "<<" , ">|" , and ">&" shall not be
34 accepted. Any use of these redirection operators shall cause this
35 utility to write an error message describing the problem and exit
36 with a non-zero exit status.
37 * The reserved word ! cannot be used at the head of the pipeline to
39 modify the exit status. (See the command-string operand description
40 below.)
41 * Alias substitution shall not be performed.
43 A filename can be specified as for uucp; it can be an absolute path‐
45 name, a pathname preceded by ~ name (which is replaced by the corre‐
46 sponding login directory), a pathname specified as ~/ dest ( dest is
47 prefixed by the public directory called PUBDIR; the actual location of
48 PUBDIR is implementation-defined), or a simple filename (which is pre‐
49 fixed by uux with the current directory). See uucp for the details.
50 The execution of commands on remote systems shall take place in an exe‐
52 cution directory known to the uucp system. All files required for the
53 execution shall be put into this directory unless they already reside
54 on that machine. Therefore, the application shall ensure that non-local
55 filenames (without path or machine reference) are unique within the uux
56 request.
57 The uux utility shall attempt to get all files to the execution system.
59 For files that are output files, the application shall ensure that the
60 filename is escaped using parentheses.
61 The remote system shall notify the user by mail if the requested com‐
63 mand on the remote system was disallowed or the files were not accessi‐
64 ble. This notification can be turned off by the -n option.
65 Typical implementations of this utility require a communications line
67 configured to use the Base Definitions volume of IEEE Std 1003.1-2001,
68 Chapter 11, General Terminal Interface, but other communications means
69 may be used. On systems where there are no available communications
70 means (either temporarily or permanently), this utility shall write an
71 error message describing the problem and exit with a non-zero exit sta‐
72 tus.
73 The uux utility cannot guarantee support for all character encodings in
75 all circumstances. For example, transmission data may be restricted to
76 7 bits by the underlying network, 8-bit data and filenames need not be
77 portable to non-internationalized systems, and so on. Under these cir‐
78 cumstances, it is recommended that only characters defined in the
79 ISO/IEC 646:1991 standard International Reference Version (equivalent
80 to ASCII) 7-bit range of characters be used and that only characters
81 defined in the portable filename character set be used for naming
82 files.
83
85 The uux utility shall conform to the Base Definitions volume of
86 IEEE Std 1003.1-2001, Section 12.2, Utility Syntax Guidelines.
87 The following options shall be supported:
89 -p Make the standard input to uux the standard input to the com‐
91 mand-string.
92 -j Write the job identification string to standard output. This job
94 identification can be used by uustat to obtain the status or
95 terminate a job.
96 -n Do not notify the user if the command fails.
98
101 The following operand shall be supported:
102 command-string
104 A string made up of one or more arguments that are similar to
106 normal command arguments, except that the command and any file‐
107 names can be prefixed by system-name!. A null system-name shall
108 be interpreted as the local system.
109
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 variables
124 that are unset or null. (See the Base Definitions volume of
125 IEEE Std 1003.1-2001, Section 8.2, Internationalization Vari‐
126 ables for the precedence of internationalization variables used
127 to determine the values of locale categories.)
128 LC_ALL If set to a non-empty string value, override the values of all
130 the other internationalization variables.
131 LC_CTYPE
133 Determine the locale for the interpretation of sequences of
134 bytes of text data as characters (for example, single-byte as
135 opposed to multi-byte characters in arguments).
136 LC_MESSAGES
138 Determine the locale that should be used to affect the format
139 and contents of diagnostic messages written to standard error.
140 NLSPATH
142 Determine the location of message catalogs for the processing of
143 LC_MESSAGES .
144
147 Default.
148
150 The standard output shall not be used unless the -j option is speci‐
151 fied; in that case, the job identification string shall be written to
152 standard output in the following format:
153 "%s\n", <jobid>
156
158 The standard error shall be used only for diagnostic messages.
159
161 Output files shall be created or written, or both, according to the
162 contents of command-string.
163 If -n is not used, mail files shall be modified following any command
165 or file-access failures on the remote system.
166
168 None.
169
171 The following exit values shall be returned:
172 0 Successful completion.
174 >0 An error occurred.
176
179 Default.
180 The following sections are informative.
182
184 Note that, for security reasons, many installations limit the list of
185 commands executable on behalf of an incoming request from uux. Many
186 sites permit little more than the receipt of mail via uux.
187 Any characters special to the command interpreter should be quoted
189 either by quoting the entire command-string or quoting the special
190 characters as individual arguments.
191 As noted in uucp, shell pattern matching notation characters appearing
193 in pathnames are expanded on the appropriate local system. This is done
194 under the control of local settings of LC_COLLATE and LC_CTYPE . Thus,
195 care should be taken when using bracketed filename patterns, as colla‐
196 tion and typing rules may vary from one system to another. Also be
197 aware that certain types of expression (that is, equivalence classes,
198 character classes, and collating symbols) need not be supported on non-
199 internationalized systems.
200
202 1. The following command gets file1 from system a and file2 from sys‐
203 tem b, executes diff on the local system, and puts the results in
204 file.diff in the local PUBDIR directory. ( PUBDIR is the uucp pub‐
205 lic directory on the local system.)
206 uux "!diff a!/usr/file1 b!/a4/file2 >!~/file.diff"
209 2. The following command fails because uux places all files copied to
211 a system in the same working directory. Although the files xyz are
212 from two different systems, their filenames are the same and con‐
213 flict.
214 uux "!diff a!/usr1/xyz b!/usr2/xyz >!~/xyz.diff"
217 3. The following command succeeds (assuming diff is permitted on sys‐
219 tem a) because the file local to system a is not copied to the
220 working directory, and hence does not conflict with the file from
221 system c.
222 uux "a!diff a!/usr/xyz c!/usr/xyz >!~/xyz.diff"
225
227 None.
228
230 None.
231
233 Shell Command Language , uucp , uuencode , uustat
234
236 Portions of this text are reprinted and reproduced in electronic form
237 from IEEE Std 1003.1, 2003 Edition, Standard for Information Technology
238 -- Portable Operating System Interface (POSIX), The Open Group Base
239 Specifications Issue 6, Copyright (C) 2001-2003 by the Institute of
240 Electrical and Electronics Engineers, Inc and The Open Group. In the
241 event of any discrepancy between this version and the original IEEE and
242 The Open Group Standard, the original IEEE and The Open Group Standard
243 is the referee document. The original Standard can be obtained online
244 at http://www.opengroup.org/unix/online.html .
245IEEE/The Open Group 2003 UUX(P)