1uux(1) General Commands Manual uux(1)
2
6 uux - Remote command execution over UUCP
7
9 uux [ options ] command
10
12 The uux command is used to execute a command on a remote system, or to
13 execute a command on the local system using files from remote systems.
14 The command is not executed immediately; the request is queued until
15 the uucico (8) daemon calls the system and executes it. The daemon is
16 started automatically unless one of the -r or --nouucico options is
17 given.
18 The actual command execution is done by the uuxqt (8) daemon.
20 File arguments can be gathered from remote systems to the execution
22 system, as can standard input. Standard output may be directed to a
23 file on a remote system.
24 The command name may be preceded by a system name followed by an excla‐
26 mation point if it is to be executed on a remote system. An empty sys‐
27 tem name is taken as the local system.
28 Each argument that contains an exclamation point is treated as naming a
30 file. The system which the file is on is before the exclamation point,
31 and the pathname on that system follows it. An empty system name is
32 taken as the local system; this must be used to transfer a file to a
33 command being executed on a remote system. If the path is not abso‐
34 lute, it will be appended to the current working directory on the local
35 system; the result may not be meaningful on the remote system. A path‐
36 name may begin with ~/, in which case it is relative to the UUCP public
37 directory (usually /usr/spool/uucppublic or /var/spool/uucppublic) on
38 the appropriate system. A pathname may begin with ~name/, in which
39 case it is relative to the home directory of the named user on the
40 appropriate system.
41 Standard input and output may be redirected as usual; the pathnames
43 used may contain exclamation points to indicate that they are on remote
44 systems. Note that the redirection characters must be quoted so that
45 they are passed to uux rather than interpreted by the shell. Append
46 redirection (>>) does not work.
47 All specified files are gathered together into a single directory
49 before execution of the command begins. This means that each file must
50 have a distinct base name. For example,
51 uux 'sys1!diff sys2!~user1/foo sys3!~user2/foo >!foo.diff'
52 will fail because both files will be copied to sys1 and stored under
53 the name foo.
54 Arguments may be quoted by parentheses to avoid interpretation of
56 exclamation points. This is useful when executing the uucp command on
57 a remote system.
58 A request to execute an empty command (e.g., uux sys!) will create a
60 poll file for the specified system.
61 The exit status of uux is one of the codes found in the header file
63 sysexits.h. In particular, EX_OK ( 0 ) indicates success, and EX_TEMP‐
64 FAIL ( 75 ) indicates a temporary failure.
65
67 The following options may be given to uux.
68 -, -p, --stdin
70 Read standard input and use it as the standard input for the com‐
71 mand to be executed.
72 -c, --nocopy
74 Do not copy local files to the spool directory. This is the
75 default. If they are removed before being processed by the uucico
76 (8) daemon, the copy will fail. The files must be readable by the
77 uucico (8) daemon, as well as the by the invoker of uux.
78 -C, --copy
80 Copy local files to the spool directory.
81 -l, --link
83 Link local files into the spool directory. If a file can not be
84 linked because it is on a different device, it will be copied
85 unless one of the -c or --nocopy options also appears (in other
86 words, use of --link switches the default from --nocopy to
87 --copy). If the files are changed before being processed by the
88 uucico (8) daemon, the changed versions will be used. The files
89 must be readable by the uucico (8) daemon, as well as by the
90 invoker of uux.
91 -g grade, --grade grade
93 Set the grade of the file transfer command. Jobs of a higher
94 grade are executed first. Grades run 0 ... 9 A ... Z a ... z from
95 high to low.
96 -n, --notification=no
98 Do not send mail about the status of the job, even if it fails.
99 -z, --notification=error
101 Send mail about the status of the job if an error occurs. For
102 many uuxqt daemons, including the Taylor UUCP uuxqt, this is the
103 default action; for those, --notification=error will have no
104 effect. However, some uuxqt daemons will send mail if the job
105 succeeds unless the --notification=error option is used, and some
106 other uuxqt daemons will not send mail if the job fails unless the
107 --notification=error option is used.
108 -r, --nouucico
110 Do not start the uucico (8) daemon immediately; merely queue up
111 the execution request for later processing.
112 -j, --jobid
114 Print jobids on standard output. A jobid will be generated for
115 each file copy operation required to perform the operation. These
116 file copies may be cancelled by passing the jobid to the --kill
117 switch of uustat (1), which will make the execution impossible to
118 complete.
119 -a address, --requestor address
121 Report job status to the specified e-mail address.
122 -x type, --debug type
124 Turn on particular debugging types. The following types are rec‐
125 ognized: abnormal, chat, handshake, uucp-proto, proto, port, con‐
126 fig, spooldir, execute, incoming, outgoing. Only abnormal, con‐
127 fig, spooldir and execute are meaningful for uux.
128 Multiple types may be given, separated by commas, and the --debug
130 option may appear multiple times. A number may also be given,
131 which will turn on that many types from the foregoing list; for
132 example, --debug 2 is equivalent to --debug abnormal,chat.
133 -I file, --config file
135 Set configuration file to use. This option may not be available,
136 depending upon how uux was compiled.
137 -v, --version
139 Report version information and exit.
140 --help
142 Print a help message and exit.
143
145 uux -z - sys1!rmail user1
146 Execute the command ``rmail user1'' on the system sys1, giving it as
147 standard input whatever is given to uux as standard input. If a fail‐
148 ure occurs, send a message using mail (1).
149 uux 'diff -c sys1!~user1/file1 sys2!~user2/file2 >!file.diff'
151 Fetch the two named files from system sys1 and system sys2 and execute
152 diff putting the result in file.diff in the current directory. The
153 current directory must be writable by the uuxqt (8) daemon for this to
154 work.
155 uux 'sys1!uucp ~user1/file1 (sys2!~user2/file2)'
157 Execute uucp on the system sys1 copying file1 (on system sys1) to sys2.
158 This illustrates the use of parentheses for quoting.
159
161 The remote system may not permit you to execute certain commands. Many
162 remote systems only permit the execution of rmail and rnews.
163 Some of the options are dependent on the capabilities of the uuxqt (8)
165 daemon on the remote system.
166
168 mail(1), uustat(1), uucp(1), uucico(8), uuxqt(8)
169
171 Files can not be referenced across multiple systems.
172 Too many jobids are output by --jobid, and there is no good way to can‐
174 cel a local execution requiring remote files.
175
177 Ian Lance Taylor (ian@airs.com)
178 Taylor UUCP 1.07 uux(1)