UUX(1) — HP-UX

NAME

uux − UNIX system to UNIX system command execution

SYNOPSIS

uux [ options ] command-string

DESCRIPTION

Uux 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. Note that, for security reasons, many installations will limit the list of commands executable on behalf of an incoming request from uux. Many sites will permit little more than the receipt of mail (see mail(1)) via uux.

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 path name;

(2) a path name preceded by ~xxx where xxx is a login name on the specified system and is replaced by that user’s login directory;

(3) anything else 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 diff(1) command and put the results in file.diff in the local /usr/spool/uucppublic 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.

Uux will attempt to get all files to the execution system. For files which are output files, the file name must be escaped using parentheses. For example, the command

uux a!cut -f1 b!/usr/file \(c!/usr/file\)

gets /usr/file from system “b” and sends it to system “a”, performs a cut command on the file and sends the result of the cut command to system “c”.

Uux will notify you if the requested command on the remote system was disallowed. The list of commands allowed is specified in the Permissions file in /usr/lib/uucp. The response comes by remote mail from the remote machine.

The following options are interpreted by uux:

− The standard input to uux is made the standard input to the command-string.

−aname Use name as the user identification replacing the initiator user-id. (Notification is returned to the user.)

−b Return whatever standard input was provided to the uux command if the exit status is non-zero.

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

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

−ggrade Grade is a single letter/number; lower ASCII sequence characters will cause the job to be transmitted earlier during a particular conversation.

−j Output the jobid, which is the job identification ASCII string on the standard output. This job identification can be used by uustat(1) to obtain the status or terminate a job.

−n Do not notify the user if the command fails.

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

−sfile Report status of the transfer in file.

−xdebug_level Produce debugging output on standard output. The debug_level is a number between 0 and 9. The higher the numbers, the more detailed information returned.

−z Send success notification to user.

WARNINGS

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.

The execution of commands on remote systems takes places in an execution directory known to the uucp system. All files required for the execution will be put into this directory unless they already reside on that machine. Therefore, the simple file name (without path or machine reference) must be unique within the uux request. The following command will NOT work:

uux "a!diff b!/usr/dan/xyz c!/usr/dan/xyz > !xyz.diff"

but the command:

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

will work (if diff(1) is a permitted command).

Protected file and files that are in protected directories that are owned by the requester can be sent in commands using uux. However, if the requester is root, and the directory is not searchable by "other", the request will fail.

DEPENDENCIES

Series 300 Diskless
In a clustered environment, all UUCP activity is handled through devices attached to the rootserver as if the cluster were a single system.

FILES

/usr/spool/uucp spool directory

/usr/spool/uucppublic public directory

/usr/lib/uucp/* other data and programs

Museum

Related Articles