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



PPRROOLLOOGG
       This manual page is part of the POSIX Programmer's Manual.  The OS
       implementation of this interface may differ (consult the corresponding
       OS manual page for details of OS behavior), or the interface may not be
       implemented on OS.

NNAAMMEE
       uux -- remote command execution

SSYYNNOOPPSSIISS
       uux [[-jnp]] _c_o_m_m_a_n_d_-_s_t_r_i_n_g

DDEESSCCRRIIPPTTIIOONN
       The _u_u_x utility shall gather zero or more files from various systems,
       execute a shell pipeline (see _S_e_c_t_i_o_n _2_._9, _S_h_e_l_l _C_o_m_m_a_n_d_s) on a
       specified system, and then send the standard output of the command to a
       file on a specified system. Only the first command of a pipeline can
       have a _s_y_s_t_e_m_-_n_a_m_e!  prefix. All other commands in the pipeline shall
       be executed on the system of the first command.

       The following restrictions are applicable to the shell pipeline
       processed by _u_u_x:

        *  In gathering files from different systems, pathname expansion shall
           not be performed by _u_u_x.  Thus, a request such as:


               uux "c99 remsys!~/*.c"

           would attempt to copy the file named literally **..cc to the local
           system.

        *  The redirection operators "">>>>"", ""<<<<"", "">>||"", and "">>&&"" shall not be
           accepted. Any use of these redirection operators shall cause this
           utility to write an error message describing the problem and exit
           with a non-zero exit status.

        *  The reserved word !!  cannot be used at the head of the pipeline to
           modify the exit status.  (See the _c_o_m_m_a_n_d_-_s_t_r_i_n_g operand
           description below.)

        *  Alias substitution shall not be performed.

       A filename can be specified as for _u_u_c_p; it can be an absolute
       pathname, a pathname preceded by ~_n_a_m_e (which is replaced by the
       corresponding login directory), a pathname specified as ~/_d_e_s_t (_d_e_s_t is
       prefixed by the public directory called _P_U_B_D_I_R; the actual location of
       _P_U_B_D_I_R is implementation-defined), or a simple filename (which is
       prefixed by _u_u_x with the current directory). See _u_u_c_p for the details.

       The execution of commands on remote systems shall take place in an
       execution directory known to the _u_u_c_p system. All files required for
       the execution shall be put into this directory unless they already
       reside on that machine. Therefore, the application shall ensure that
       non-local filenames (without path or machine reference) are unique
       within the _u_u_x request.

       The _u_u_x utility shall attempt to get all files to the execution system.
       For files that are output files, the application shall ensure that the
       filename is escaped using parentheses.

       The remote system shall notify the user by mail if the requested
       command on the remote system was disallowed or the files were not
       accessible. This notification can be turned off by the --nn option.

       Typical implementations of this utility require a communications line
       configured to use the Base Definitions volume of POSIX.1-2017, _C_h_a_p_t_e_r
       _1_1, _G_e_n_e_r_a_l _T_e_r_m_i_n_a_l _I_n_t_e_r_f_a_c_e, but other communications means may be
       used. On systems where there are no available communications means
       (either temporarily or permanently), this utility shall write an error
       message describing the problem and exit with a non-zero exit status.

       The _u_u_x utility cannot guarantee support for all character encodings in
       all circumstances. For example, transmission data may be restricted to
       7 bits by the underlying network, 8-bit data and filenames need not be
       portable to non-internationalized systems, and so on. Under these
       circumstances, it is recommended that only characters defined in the
       ISO/IEC 646:1991 standard International Reference Version (equivalent
       to ASCII) 7-bit range of characters be used and that only characters
       defined in the portable filename character set be used for naming
       files.

OOPPTTIIOONNSS
       The _u_u_x utility shall conform to the Base Definitions volume of
       POSIX.1-2017, _S_e_c_t_i_o_n _1_2_._2, _U_t_i_l_i_t_y _S_y_n_t_a_x _G_u_i_d_e_l_i_n_e_s.

       The following options shall be supported:

       --jj        Write the job identification string to standard output. This
                 job identification can be used by _u_u_s_t_a_t to obtain the status
                 or terminate a job.

       --nn        Do not notify the user if the command fails.

       --pp        Make the standard input to _u_u_x the standard input to the
                 _c_o_m_m_a_n_d_-_s_t_r_i_n_g.

OOPPEERRAANNDDSS
       The following operand shall be supported:

       _c_o_m_m_a_n_d_-_s_t_r_i_n_g
                 A string made up of one or more arguments that are similar to
                 normal command arguments, except that the command and any
                 filenames can 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 shall be interpreted as the local system.

SSTTDDIINN
       The standard input shall not be used unless the ''--'' or --pp option is
       specified; in those cases, the standard input shall be made the
       standard input of the _c_o_m_m_a_n_d_-_s_t_r_i_n_g.

IINNPPUUTT FFIILLEESS
       Input files shall be selected according to the contents of _c_o_m_m_a_n_d_-
       _s_t_r_i_n_g.

EENNVVIIRROONNMMEENNTT VVAARRIIAABBLLEESS
       The following environment variables shall affect the execution of _u_u_x:

       _L_A_N_G      Provide a default value for the internationalization
                 variables that are unset or null. (See the Base Definitions
                 volume of POSIX.1-2017, _S_e_c_t_i_o_n _8_._2, _I_n_t_e_r_n_a_t_i_o_n_a_l_i_z_a_t_i_o_n
                 _V_a_r_i_a_b_l_e_s for the precedence of internationalization
                 variables used to determine the values of locale categories.)

       _L_C___A_L_L    If set to a non-empty string value, override the values of
                 all the other internationalization variables.

       _L_C___C_T_Y_P_E  Determine the locale for the interpretation of sequences of
                 bytes of text data as characters (for example, single-byte as
                 opposed to multi-byte characters in arguments).

       _L_C___M_E_S_S_A_G_E_S
                 Determine the locale that should be used to affect the format
                 and contents of diagnostic messages written to standard
                 error.

       _N_L_S_P_A_T_H   Determine the location of message catalogs for the processing
                 of _L_C___M_E_S_S_A_G_E_S.

AASSYYNNCCHHRROONNOOUUSS EEVVEENNTTSS
       Default.

SSTTDDOOUUTT
       The standard output shall not be used unless the --jj option is
       specified; in that case, the job identification string shall be written
       to standard output in the following format:


           "%s\n", <_j_o_b_i_d>

SSTTDDEERRRR
       The standard error shall be used only for diagnostic messages.

OOUUTTPPUUTT FFIILLEESS
       Output files shall be created or written, or both, according to the
       contents of _c_o_m_m_a_n_d_-_s_t_r_i_n_g.

       If --nn is not used, mail files shall be modified following any command
       or file-access failures on the remote system.

EEXXTTEENNDDEEDD DDEESSCCRRIIPPTTIIOONN
       None.

EEXXIITT SSTTAATTUUSS
       The following exit values shall be returned:

        0    Successful completion.

       >0    An error occurred.

CCOONNSSEEQQUUEENNCCEESS OOFF EERRRROORRSS
       Default.

       _T_h_e _f_o_l_l_o_w_i_n_g _s_e_c_t_i_o_n_s _a_r_e _i_n_f_o_r_m_a_t_i_v_e_.

AAPPPPLLIICCAATTIIOONN UUSSAAGGEE
       This utility is part of the UUCP Utilities option and need not be
       supported by all implementations.

       Note that, for security reasons, many installations limit the list of
       commands executable on behalf of an incoming request from _u_u_x.  Many
       sites permit little more than the receipt of mail via _u_u_x.

       Any characters special to the command interpreter 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.

       As noted in _u_u_c_p, shell pattern matching notation characters appearing
       in pathnames are expanded on the appropriate local system. This is done
       under the control of local settings of _L_C___C_O_L_L_A_T_E and _L_C___C_T_Y_P_E.  Thus,
       care should be taken when using bracketed filename patterns, as
       collation and typing rules may vary from one system to another. Also be
       aware that certain types of expression (that is, equivalence classes,
       character classes, and collating symbols) need not be supported on non-
       internationalized systems.

EEXXAAMMPPLLEESS
        1. The following command gets ffiillee11 from system aa and ffiillee22 from
           system bb, executes _d_i_f_f on the local system, and puts the results
           in ffiillee..ddiiffff in the local _P_U_B_D_I_R directory. (_P_U_B_D_I_R is the _u_u_c_p
           public directory on the local system.)


               uux "!diff a!/usr/file1 b!/a4/file2 >!~/file.diff"

        2. The following command fails because _u_u_x places all files copied to
           a system in the same working directory.  Although the files xxyyzz are
           from two different systems, their filenames are the same and
           conflict.


               uux "!diff a!/usr1/xyz b!/usr2/xyz >!~/xyz.diff"

        3. The following command succeeds (assuming _d_i_f_f is permitted on
           system aa) because the file local to system aa is not copied to the
           working directory, and hence does not conflict with the file from
           system cc.


               uux "a!diff a!/usr/xyz c!/usr/xyz >!~/xyz.diff"

RRAATTIIOONNAALLEE
       None.

FFUUTTUURREE DDIIRREECCTTIIOONNSS
       None.

SSEEEE AALLSSOO
       _C_h_a_p_t_e_r _2, _S_h_e_l_l _C_o_m_m_a_n_d _L_a_n_g_u_a_g_e, _u_u_c_p, _u_u_e_n_c_o_d_e, _u_u_s_t_a_t

       The Base Definitions volume of POSIX.1-2017, _C_h_a_p_t_e_r _8, _E_n_v_i_r_o_n_m_e_n_t
       _V_a_r_i_a_b_l_e_s, _C_h_a_p_t_e_r _1_1, _G_e_n_e_r_a_l _T_e_r_m_i_n_a_l _I_n_t_e_r_f_a_c_e, _S_e_c_t_i_o_n _1_2_._2,
       _U_t_i_l_i_t_y _S_y_n_t_a_x _G_u_i_d_e_l_i_n_e_s

CCOOPPYYRRIIGGHHTT
       Portions of this text are reprinted and reproduced in electronic form
       from IEEE Std 1003.1-2017, Standard for Information Technology --
       Portable Operating System Interface (POSIX), The Open Group Base
       Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the
       Institute of Electrical and Electronics Engineers, Inc and The Open
       Group.  In the event of any discrepancy between this version and the
       original IEEE and The Open Group Standard, the original IEEE and The
       Open Group Standard is the referee document. The original Standard can
       be obtained online at http://www.opengroup.org/unix/online.html .

       Any typographical or formatting errors that appear in this page are
       most likely to have been introduced during the conversion of the source
       files to man page format. To report such errors, see
       https://www.kernel.org/doc/man-pages/reporting_bugs.html .



IEEE/The Open Group                  2017                               UUX(1)
