![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to uux.1 CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [MW Coherent from dump] / coherent / g / usr / lib / uucp / tay104|
Return to uux.1 CVS log | Up to [MW Coherent from dump] / coherent / g / usr / lib / uucp / tay104 |
1.1 root 1: ''' $Id: uux.1,v 1.1 93/07/30 08:00:07 bin Exp Locker: bin $
2: .TH uux 1 "Taylor UUCP 1.04"
3: .SH NAME
4: uux \- Remote command execution over UUCP
5: .SH SYNOPSIS
6: .B uux
7: [ options ] command
8: .SH DESCRIPTION
9: The
10: .I uux
11: command is used to execute a command on a remote system, or to execute
12: a command on the local system using files from remote systems.
13: The command
14: is not executed immediately; the request is queued until the
15: .I uucico
16: (8) daemon calls the system and executes it. The daemon is
17: started automatically unless the
18: .B \-r
19: switch is given.
20:
21: The actual command execution is done by the
22: .I uuxqt
23: (8) daemon.
24:
25: File arguments can be gathered from remote systems to the execution
26: system, as can standard input. Standard output may be directed to a
27: file on a remote system.
28:
29: The command name may be preceded by a system name followed by an
30: exclamation point if it is to be executed on a remote system. An
31: empty system name is taken as the local system.
32:
33: Each argument that contains an exclamation point is treated as naming
34: a file. The system which the file is on is before the exclamation
35: point, and the pathname on that system follows it. An empty system
36: name is taken as the local system; this must be used to transfer a
37: file to a command being executed on a remote system. If the path is
38: not absolute, it will be appended to the current working directory on
39: the local system; the result may not be meaningful on the remote
40: system. A pathname may begin with ~/, in which case it is relative to
41: the UUCP public directory (usually /usr/spool/uucppublic) on the
42: appropriate system. A pathname may begin with ~name/, in which case
43: it is relative to the home directory of the named user on the
44: appropriate system.
45:
46: Standard input and output may be redirected as usual; the pathnames
47: used may contain exclamation points to indicate that they are on
48: remote systems. Note that the redirection characters must be quoted
49: so that they are passed to
50: .I uux
51: rather than interpreted by the shell. Append redirection (>>) does
52: not work.
53:
54: All specified files are gathered together into a single directory
55: before execution of the command begins. This means that each file
56: must have a distinct base name. For example,
57: .EX
58: uux 'sys1!diff sys2!~user1/foo sys3!~user2/foo >!foo.diff'
59: .EE
60: will fail because both files will be copied to sys1 and stored under
61: the name foo.
62:
63: Arguments may be quoted by parentheses to avoid interpretation of
64: exclamation points. This is useful when executing the
65: .I uucp
66: command on a remote system.
67: .SH OPTIONS
68: The following options may be given to
69: .I uux.
70: .TP 5
71: .B \-,\-p
72: Read standard input and use it as the standard input for the command
73: to be executed.
74: .TP 5
75: .B \-c
76: Do not copy local files to the spool directory. This is the default.
77: If they are
78: removed before being processed by the
79: .I uucico
80: (8) daemon, the copy will fail. The files must be readable by the
81: .I uucico
82: (8) daemon,
83: as well as the by the invoker of
84: .I uux.
85: .TP 5
86: .B \-C
87: Copy local files to the spool directory.
88: .TP 5
89: .B \-l
90: Link local files into the spool directory. If a file can not be
91: linked because it is on a different device, it will be copied unless
92: the
93: .B \-c
94: option also appears (in other words, use of
95: .B \-l
96: switches the default from
97: .B \-c
98: to
99: .B \-C).
100: If the files are changed before being processed by the
101: .I uucico
102: (8) daemon, the changed versions will be used. The files must be
103: readable by the
104: .I uucico
105: (8) daemon, as well as by the invoker of
106: .I uux.
107: .TP 5
108: .B \-g grade
109: Set the grade of the file transfer command. Jobs of a higher grade
110: are executed first. Grades run 0 ... 9 A ... Z a ... z from high to
111: low.
112: .TP 5
113: .B \-n
114: Do not send mail about the status of the job, even if it fails.
115: .TP 5
116: .B \-z
117: Send mail about the status of the job if an error occurs. For many
118: .I uuxqt
119: daemons, including the Taylor UUCP
120: .I uuxqt,
121: this is the default action; for those,
122: .B \-z
123: will have no effect. However, some
124: .I uuxqt
125: daemons will send mail if the job succeeds unless the
126: .B \-z
127: option is used, and some other
128: .I uuxqt
129: daemons will not send mail if the job fails unless the
130: .B \-z
131: option is used.
132: .TP 5
133: .B \-r
134: Do not start the
135: .I uucico
136: (8) daemon immediately; merely queue up the execution request for later
137: processing.
138: .TP 5
139: .B \-j
140: Print jobids on standard output. A jobid will be generated for each
141: file copy operation required to perform the operation. These file
142: copies may be cancelled by
143: passing the jobid to the
144: .B \-k
145: switch of
146: .I uustat
147: (1), which will make the execution impossible to complete.
148: .TP 5
149: .B \-a address
150: Report job status to the specified e-mail address.
151: .TP 5
152: .B \-x type
153: Turn on particular debugging types. The following types are
154: recognized: abnormal, chat, handshake, uucp-proto, proto, port,
155: config, spooldir, execute, incoming, outgoing. Only abnormal, config,
156: spooldir and execute are meaningful for
157: .I uux.
158:
159: Multiple types may be given, separated by commas, and the
160: .B \-x
161: option may appear multiple times. A number may also be given, which
162: will turn on that many types from the foregoing list; for example,
163: .B \-x 2
164: is equivalent to
165: .B \-x abnormal,chat.
166: .TP 5
167: .B \-I file
168: Set configuration file to use. This option may not be available,
169: depending upon how
170: .I uux
171: was compiled.
172: .SH EXAMPLES
173: .EX
174: uux -z - sys1!rmail user1
175: .EE
176: Execute the command ``rmail user1'' on the system sys1, giving it as
177: standard input whatever is given to
178: .I uux
179: as standard input. If a failure occurs, send a message using
180: .I mail
181: (1).
182: .EX
183: uux 'diff -c sys1!~user1/file1 sys2!~user2/file2 >!file.diff'
184: .EE
185: Fetch the two named files from system sys1 and system sys2 and execute
186: .I diff
187: putting the result in file.diff in the current directory. The current
188: directory must be writable by the
189: .I uuxqt
190: (8) daemon for this to work.
191: .EX
192: uux 'sys1!uucp ~user1/file1 (sys2!~user2/file2)'
193: .EE
194: Execute
195: .I uucp
196: on the system sys1 copying file1 (on system sys1) to sys2. This
197: illustrates the use of parentheses for quoting.
198: .SH RESTRICTIONS
199: The remote system may not permit you to execute certain commands.
200: Many remote systems only permit the execution of
201: .I rmail
202: and
203: .I rnews.
204:
205: Some of the options are dependent on the capabilities of the
206: .I uuxqt
207: (8) daemon on the remote system.
208: .SH FILES
209: The file names may be changed at compilation time or by the
210: configuration file, so these are only approximations.
211:
212: .br
213: /usr/lib/uucp/config - Configuration file.
214: .br
215: /usr/spool/uucp -
216: UUCP spool directory.
217: .br
218: /usr/spool/uucp/Log -
219: UUCP log file.
220: .br
221: /usr/spool/uucppublic -
222: Default UUCP public directory.
223: .SH SEE ALSO
224: mail(1), uustat(1), uucp(1), uucico(8), uuxqt(8)
225: .SH BUGS
226: Files can not be referenced across multiple systems.
227:
228: Too many jobids are output by
229: .B \-j,
230: and there is no good way to cancel a local execution requiring remote
231: files.
232: .SH AUTHOR
233: Ian Lance Taylor
234: ([email protected] or uunet!airs!ian)
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.