32v 1m uux

From Computer History Wiki
Revision as of 17:51, 26 October 2009 by Neozeed (talk | contribs) (New page: UUX(1C) UNIX Programmer's Manual UUX(1C) == NAME == uux - unix to unix command execution == SYNOPSIS == uux [ - ] command-string == DESCRIPTION == ...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

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


NAME

    uux - unix to unix command execution

SYNOPSIS

    uux [ - ] command-string

DESCRIPTION

    _U_u_x will gather 0 or more files from various systems, exe-
    cute a command on a specified system and send standard out-
    put to a file on a specified system.
    The command-string 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 system-name!.  A null system-
    name is interpreted as the local system.
    File names may be one of
         (1) a full pathname;
         (2) a pathname preceded by ~_x_x_x; where _x_x_x is a userid
         on the specified system and is replaced by that user's
         login directory;
         (3) anything else is prefixed by the current directory.
    The `-' option will cause the standard input to the _u_u_x com-
    mand to be the standard input to the command-string.
    For example, the command
         uux "!diff usg!/usr/dan/f1 pwba!/a4/dan/f1 > !fi.diff"
    will get the f1 files from the usg and pwba machines, exe-
    cute a _d_i_f_f command and put the results in f1.diff in the
    local directory.
    Any special shell characters such as <>;| should be quoted
    either by quoting the entire command-string, or quoting the
    special characters as individual arguments.

FILES

    /usr/uucp/spool - spool directory
    /usr/uucp/* - other data and programs

SEE ALSO

    uucp(1)
    D. A. Nowitz, _U_u_c_p _i_m_p_l_e_m_e_n_t_a_t_i_o_n _d_e_s_c_r_i_p_t_i_o_n

WARNING

    An installation may, and for security reasons generally
    will, limit the list of commands executable on behalf of an
    incoming request from _u_u_x. Typically, a restricted site will
    permit little other than the receipt of mail via _u_u_x.

BUGS

    Only the first command of a shell pipeline may have a
    system-name!.  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.
    There is no notification of denial of execution on the
    remote machine.