|-, -p, --stdin|
|Read standard input and use it as the standard input for the command to be executed.|
|Do not copy local files to the spool directory. This is the default. If they are removed before being processed by the uucico (8) daemon, the copy will fail. The files must be readable by the uucico (8) daemon, as well as the by the invoker of uux.|
|Copy local files to the spool directory.|
|Link local files into the spool directory. If a file can not be linked because it is on a different device, it will be copied unless one of the -c or --nocopy options also appears (in other words, use of --link switches the default from --nocopy to --copy). If the files are changed before being processed by the uucico (8) daemon, the changed versions will be used. The files must be readable by the uucico (8) daemon, as well as by the invoker of uux.|
|-g grade, --grade grade|
|Set the grade of the file transfer command. Jobs of a higher grade are executed first. Grades run 0 ... 9 A ... Z a ... z from high to low.|
|Do not send mail about the status of the job, even if it fails.|
|Send mail about the status of the job if an error occurs. For many uuxqt daemons, including the Taylor UUCP uuxqt, this is the default action; for those, --notification=error will have no effect. However, some uuxqt daemons will send mail if the job succeeds unless the --notification=error option is used, and some other uuxqt daemons will not send mail if the job fails unless the --notification=error option is used.|
|Do not start the uucico (8) daemon immediately; merely queue up the execution request for later processing.|
|Print jobids on standard output. A jobid will be generated for each file copy operation required to perform the operation. These file copies may be cancelled by passing the jobid to the --kill switch of uustat (1), which will make the execution impossible to complete.|
|-a address, --requestor address|
|Report job status to the specified e-mail address.|
|-x type, --debug type|
Turn on particular debugging types. The following types are
recognized: abnormal, chat, handshake, uucp-proto, proto, port,
config, spooldir, execute, incoming, outgoing. Only abnormal, config,
spooldir and execute are meaningful for
Multiple types may be given, separated by commas, and the --debug option may appear multiple times. A number may also be given, which will turn on that many types from the foregoing list; for example, --debug 2 is equivalent to --debug abnormal,chat.
|-I file, --config file|
|Set configuration file to use. This option may not be available, depending upon how uux was compiled.|
|Report version information and exit.|
|--help||Print a help message and exit.|
uux -z - sys1!rmail user1Execute the command rmail user1 on the system sys1, giving it as standard input whatever is given to uux as standard input. If a failure occurs, send a message using mail (1).
uux diff -c sys1!~user1/file1 sys2!~user2/file2 >!file.diffFetch the two named files from system sys1 and system sys2 and execute diff putting the result in file.diff in the current directory. The current directory must be writable by the uuxqt (8) daemon for this to work.
uux sys1!uucp ~user1/file1 (sys2!~user2/file2)Execute uucp on the system sys1 copying file1 (on system sys1) to sys2. This illustrates the use of parentheses for quoting.
The remote system may not permit you to execute certain commands. Many remote systems only permit the execution of rmail and rnews.
Some of the options are dependent on the capabilities of the uuxqt (8) daemon on the remote system.
Files can not be referenced across multiple systems.
Too many jobids are output by --jobid, and there is no good way to cancel a local execution requiring remote files.
Ian Lance Taylor (email@example.com)
|-->||UUX (1)||Taylor UUCP 1.07|