4.4BSD/usr/share/man/cat1/uux.0
UUX(1) BSD Reference Manual UUX(1)
NNAAMMEE
uux - unix to unix command execution
SSYYNNOOPPSSIISS
uuuuxx [ -- ] [ --ccCCllLLnnpprrzz ] [ --aa_n_a_m_e ] [ --gg_g_r_a_d_e ] [ --xx_d_e_b_u_g ]
command-string
DDEESSCCRRIIPPTTIIOONN
_U_u_x will gather zero or more files from various systems,
execute a command on a specified system and then send
standard output to a file on a specified system.
The _c_o_m_m_a_n_d_-_s_t_r_i_n_g is made up of one or more arguments
that look like a Shell command line, except that the com-
mand and file names may be prefixed by _s_y_s_t_e_m_-_n_a_m_e!!. A
null _s_y_s_t_e_m_-_n_a_m_e is interpreted as the local system.
File names may be one of
(1) a full path name;
(2) a path name preceded by ~~_u_s_e_r where _u_s_e_r is a
login name on the specified system and is replaced
by that user's login directory;
(3) a path name prefixed by ~~;; where ~~ is expanded
to the system's public directory (usually
/var/spool/uucppublic);
(4) a partial pathname, which is prefixed by the
current directory.
As an example, the command
uux "!diff usg!/usr/dan/file1 pwba!/a4/dan/file2 >
!~/dan/file.diff"
will get the ffiillee11 and ffiillee22 files from the ``usg'' and
``pwba'' machines, execute a _d_i_f_f(1) command and put the
results in ffiillee..ddiiffff in the local
/var/spool/uucppublic/dan/ directory.
Any special shell characters, such as <<>>;;||, should be
quoted either by quoting the entire _c_o_m_m_a_n_d_-_s_t_r_i_n_g, or
quoting the special characters as individual arguments.
_U_u_x will attempt to get all files to the execution system.
For files that are output files, the file name must be
escaped using parentheses. For example, the command
uux a!wc b!/usr/file1 \(c!/usr/file2 \)
7th Edition October 24, 1988 1
UUX(1) BSD Reference Manual UUX(1)
get //uussrr//ffiillee11 from system ``b'' and send it to system
``a'', perform a _w_c command on that file and send the
result of the _w_c command to system ``c''.
_U_u_x will notify you by mail if the requested command on
the remote system was disallowed. This notification can
be turned off by the --nn option.
The following _o_p_t_i_o_n_s are interpreted by _u_u_x:
-- The standard input to _u_u_x is made the standard input
to the _c_o_m_m_a_n_d_-_s_t_r_i_n_g.
--aa_n_a_m_e
Use _n_a_m_e as the user identification replacing the
initiator user-id.
--cc Do not copy local file to the spool directory for
transfer to the remote machine (this is the default).
--CC Force the copy of local files to the spool directory
for transfer.
--gg_g_r_a_d_e
_G_r_a_d_e is a single letter/number, from 00 to 99, AA to ZZ,
or aa to zz; 00 is the highest, and zz is the lowest
grade. The default is AA; by comparison _u_u_c_p(1)
defaults to nn and mail is usually sent at grade CC.
Lower grades should be specified for high-volume
jobs, such as news.
--ll Try and make a link from the original file to the
spool directory. If the link cannot be made, copy
the file.
--nn Do not notify the user when the command completes.
--pp Same as -: The standard input to _u_u_x is made the
standard input to the _c_o_m_m_a_n_d_-_s_t_r_i_n_g.
--rr Do not start the file transfer, just queue the job.
--xx_d_e_b_u_g
Produce debugging output on stdout. The debug is a
number between 0 and 9; higher numbers give more
detailed information. Debugging is permitted only for
privileged users (specifically, those with read
access to _L_._s_y_s(5)_.
--zz Notify the user only if the command fails.
7th Edition October 24, 1988 2
UUX(1) BSD Reference Manual UUX(1)
--LL Start up _u_u_c_i_c_o with the --LL flag. This will force
calls to be made to local sites only (see _u_u_c_i_c_o(8)).
FFIILLEESS
/var/spool/uucp spool directories
/usr/lib/uucp/* UUCP configuration data and daemons
SSEEEE AALLSSOO
uucp(1), uucico(8), uuxqt(8).
WWAARRNNIINNGG
For security reasons, many installations will limit the
list of commands executable on behalf of an incoming
request from _u_u_x. Many sites will permit little more than
the receipt of mail (see _m_a_i_l(1)) via _u_u_x.
BBUUGGSS
Only the first command of a shell pipeline may have a _s_y_s_-
_t_e_m_-_n_a_m_e!!. All other commands are executed on the system
of the first command.
The use of the shell metacharacter ** will probably not do
what you want it to do.
The shell tokens <<<< and >>>> are not implemented.
When invoking _u_u_x from _c_s_h(1), the `!' character must be
prefixed by the `\' escape to inhibit _c_s_h's history mecha-
nism. (Quotes are not sufficient.)
7th Edition October 24, 1988 3