


UUX(1)		    UNIX Programmer's Manual		   UUX(1)



NAME
     uux - unix to unix command execution

SYNOPSIS
     uux [ - ] [ -cClLnprz ] [ -a_n_a_m_e ] [ -g_g_r_a_d_e ] [ -x_d_e_b_u_g ]
     command-string

DESCRIPTION
     _U_u_x will gather zero or more files from various systems,
     execute a command on a specified system and then send stan-
     dard 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 command 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
	  /usr/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 file1 and file2 files from the ``usg'' and
     ``pwba'' machines, execute a _d_i_f_f(1) command and put the
     results in file.diff in the local /usr/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 \)




Printed 11/26/99	October 22, 1996			1






UUX(1)		    UNIX Programmer's Manual		   UUX(1)



     get /usr/file1 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 -n 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.

     -a_n_a_m_e
	  Use _n_a_m_e as the user identification replacing the ini-
	  tiator user-id.

     -c   Do not copy local file to the spool directory for
	  transfer to the remote machine (this is the default).

     -C   Force the copy of local files to the spool directory
	  for transfer.

     -g_g_r_a_d_e
	  _G_r_a_d_e is a single letter/number, from 0 to 9, A to Z,
	  or a to z; 0 is the highest, and z is the lowest grade.
	  The default is A; by comparison _u_u_c_p(1) defaults to n
	  and mail is usually sent at grade C.	Lower grades
	  should be specified for high-volume jobs, such as news.

     -l   Try and make a link from the original file to the spool
	  directory.  If the link cannot be made, copy the file.

     -n   Do not notify the user when the command completes.

     -p   Same as -: The standard input to _u_u_x is made the stan-
	  dard input to the _c_o_m_m_a_n_d-_s_t_r_i_n_g.

     -r   Do not start the file transfer, just queue the job.

     -x_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).

     -z   Notify the user only if the command fails.

     -L   Start up _u_u_c_i_c_o with the -L flag. This will force calls
	  to be made to local sites only (see _u_u_c_i_c_o(8C)).




Printed 11/26/99	October 22, 1996			2






UUX(1)		    UNIX Programmer's Manual		   UUX(1)



FILES
     /usr/spool/uucp	   spool directories
     /etc/uucp/*	   UUCP configuration data.

SEE ALSO
     uucp(1), uucico(8), uuxqt(8).

WARNING
     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.

BUGS
     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 mechan-
     ism. (Quotes are not sufficient.)





























Printed 11/26/99	October 22, 1996			3



