1UUX(1P)                    POSIX Programmer's Manual                   UUX(1P)
2
3
4

PROLOG

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

NAME

12       uux — remote command execution
13

SYNOPSIS

15       uux [-jnp] command-string
16

DESCRIPTION

18       The uux utility shall gather zero or more files from  various  systems,
19       execute  a shell pipeline (see Section 2.9, Shell Commands) on a speci‐
20       fied system, and then send the standard output of the command to a file
21       on  a specified system. Only the first command of a pipeline can have a
22       system-name!  prefix. All other commands in the pipeline shall be  exe‐
23       cuted on the system of the first command.
24
25       The  following  restrictions  are applicable to the shell pipeline pro‐
26       cessed by uux:
27
28        *  In gathering files from different systems, pathname expansion shall
29           not be performed by uux.  Thus, a request such as:
30
31
32               uux "c99 remsys!~/*.c"
33
34           would  attempt  to  copy  the file named literally *.c to the local
35           system.
36
37        *  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
42        *  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
46        *  Alias substitution shall not be performed.
47
48       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
55       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
62       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
66       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
70       Typical  implementations  of this utility require a communications line
71       configured to use the Base Definitions volume of POSIX.1‐2017,  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
77       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

OPTIONS

88       The uux utility  shall  conform  to  the  Base  Definitions  volume  of
89       POSIX.1‐2017, Section 12.2, Utility Syntax Guidelines.
90
91       The following options shall be supported:
92
93       -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
97       -n        Do not notify the user if the command fails.
98
99       -p        Make the standard input to uux the standard input to the com‐
100                 mand-string.
101

OPERANDS

103       The following operand shall be supported:
104
105       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

STDIN

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

INPUT FILES

117       Input  files  shall  be  selected according to the contents of command-
118       string.
119

ENVIRONMENT VARIABLES

121       The following environment variables shall affect the execution of uux:
122
123       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‐2017, Section 8.2, Internationalization  Vari‐
126                 ables  for  the  precedence of internationalization variables
127                 used to determine the values of locale categories.)
128
129       LC_ALL    If set to a non-empty string value, override  the  values  of
130                 all the other internationalization variables.
131
132       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
136       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
141       NLSPATH   Determine the location of message catalogs for the processing
142                 of LC_MESSAGES.
143

ASYNCHRONOUS EVENTS

145       Default.
146

STDOUT

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
152
153           "%s\n", <jobid>
154

STDERR

156       The standard error shall be used only for diagnostic messages.
157

OUTPUT FILES

159       Output files shall be created or written, or  both,  according  to  the
160       contents of command-string.
161
162       If  -n  is not used, mail files shall be modified following any command
163       or file-access failures on the remote system.
164

EXTENDED DESCRIPTION

166       None.
167

EXIT STATUS

169       The following exit values shall be returned:
170
171        0    Successful completion.
172
173       >0    An error occurred.
174

CONSEQUENCES OF ERRORS

176       Default.
177
178       The following sections are informative.
179

APPLICATION USAGE

181       This utility is part of the UUCP Utilities option and need not be  sup‐
182       ported by all implementations.
183
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
188       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
192       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

EXAMPLES

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 public
205           directory on the local system.)
206
207
208               uux "!diff a!/usr/file1 b!/a4/file2 >!~/file.diff"
209
210        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
215
216               uux "!diff a!/usr1/xyz b!/usr2/xyz >!~/xyz.diff"
217
218        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
223
224               uux "a!diff a!/usr/xyz c!/usr/xyz >!~/xyz.diff"
225

RATIONALE

227       None.
228

FUTURE DIRECTIONS

230       None.
231

SEE ALSO

233       Chapter 2, Shell Command Language, uucp, uuencode, uustat
234
235       The  Base  Definitions  volume  of POSIX.1‐2017, Chapter 8, Environment
236       Variables, Chapter 11, General Terminal Interface, Section 12.2,  Util‐
237       ity Syntax Guidelines
238
240       Portions  of  this text are reprinted and reproduced in electronic form
241       from IEEE Std 1003.1-2017, Standard for Information Technology --  Por‐
242       table  Operating System Interface (POSIX), The Open Group Base Specifi‐
243       cations Issue 7, 2018 Edition, Copyright (C) 2018 by the  Institute  of
244       Electrical  and  Electronics Engineers, Inc and The Open Group.  In the
245       event of any discrepancy between this version and the original IEEE and
246       The  Open Group Standard, the original IEEE and The Open Group Standard
247       is the referee document. The original Standard can be  obtained  online
248       at http://www.opengroup.org/unix/online.html .
249
250       Any  typographical  or  formatting  errors that appear in this page are
251       most likely to have been introduced during the conversion of the source
252       files  to  man page format. To report such errors, see https://www.ker
253       nel.org/doc/man-pages/reporting_bugs.html .
254
255
256
257IEEE/The Open Group                  2017                              UUX(1P)
Impressum