![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to uucp CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [MW Coherent from dump] / coherent / a / usr / man / COHERENT|
Return to uucp CVS log | Up to [MW Coherent from dump] / coherent / a / usr / man / COHERENT |
1.1 root 1:
2:
3: UUCP Overview UUCP
4:
5:
6:
7:
8: Unattended communication with remote systems
9:
10:
11: _U_U_C_P stands for ``UNIX to UNIX copy''. It is a system of
12: commands that allows you to exchange files with other COHERENT or
13: UNIX systems, in an unattended manner. With UUCP, you can send
14: mail to other systems, upload files, and execute commands. When
15: configured correctly, UUCP also lets other users upload files to
16: your system, copy files from it, and execute commands. All this
17: can be done without your having to sit at your console and type
18: commands; thus, files can be transferred in the small hours, when
19: telephone rates are lower and computers are relative free.
20:
21: UUCP gives you access to the Usenet, a nation-wide network of
22: UNIX and COHERENT users. Access to the Usenet will let you
23: exchange mail with any of the thousands of Usenet users, receive
24: mail from them, download source code for many useful programs,
25: and read the latest news on a host of subjects. For details on
26: contacting UUNET, a commercially accessible Usenet site, enter
27: the command:
28:
29:
30: phone uunet
31:
32:
33: The UUCP protocol is implemented through a suite of commands and
34: files. The following Lexicon entries relate to UUCP:
35:
36:
37: LL-ddeevv File that describes devices used by UUCP
38: LL.ssyyss File that describes systems contacted by UUCP
39: PPeerrmmiissssiioonnss FIle that sets remote system permissions
40: uuuucciiccoo Transmit data to a remote site
41: uuuuccpp Prepare files for transmission
42: uuuuccppnnaammee File that sets your system's UUCP name
43: uuuuddeeccooddee Decode a binary file sent from a remote system
44: uuuueennccooddee Encode a binary file for sending to a remote system
45: uuuuiinnssttaallll Help install UUCP on your system
46: uuuulloogg Read UUCP log files
47: uuuummvvlloogg Move UUCP log files to backup archive
48: uuuunnaammee List UUCP names of known systems
49: uuuurrmmlloocckk Remote UUCP lock files
50: uuuuttoouucchh Touch a file to trigger uuuucciiccoo poll
51: uuuuxx Execute command on a remote system
52: uuuuxxqq Execute commands requested by a remote system
53:
54:
55: The following sections discuss problems that can arise when using
56: UUCP, as diagnosed by the Mark Williams Technical Support Staff.
57:
58: ***** Using Trailblazer Modems With UUCP *****
59:
60: The Trailblazer modem has been designed to be used with UUCP. It
61: is extremely fast and extremely accurate; however, some users
62:
63:
64: COHERENT Lexicon Page 1
65:
66:
67:
68:
69: UUCP Overview UUCP
70:
71:
72:
73: reported problems in using COHERENT UUCP with a Trailblazer
74: modem. The following describes how Mark Williams Company has
75: configured the Trailblazer modem that it uses under COHERENT at
76: 9600 baud.
77:
78: To begin, the following gives the permissions in /uussrr/lliibb/uuuuccpp
79: for selected files:
80:
81:
82: -rw-r--r-- 1 uucp uucp 196 Wed May 23 10:16 L-devices
83: -rw-r--r-- 1 uucp uucp 740 Tue May 22 15:40 L.sys
84: -rw-r--r-- 1 uucp uucp 2151 Wed Jul 11 10:44 Permissions
85:
86:
87: The following gives partial contents of file /uussrr/lliibb/uuuuccpp/LL-
88: ddeevviicceess:
89:
90:
91: #type line remote baud brand
92: #----- ------ ------ ---- -----
93: ACU com3l com3r 2400 tb2400
94: ACU com3l com3r 9600 tbfast
95:
96:
97: The following gives partial contents of file /uussrr/lliibb/uuuuccpp/LL.ssyyss
98: (note that # should be replaced by the actual phone number):
99:
100:
101: uunet Any ACU 9600 # FAST \d\r\c in:-\r-in: \dmwc\r\c rd: PASSWORD\r
102:
103:
104: The following gives partial contents of
105: /uussrr/lliibb/uuuuccpp/PPeerrmmiissssiioonnss:
106:
107:
108: MACHINE=uunet LOGNAME=uuunet \
109: COMMANDS=rmail:rnews: \
110: READ=/usr/spool/uucppublic:/tmp \
111: WRITE=/usr/spool/uucppublic:/tmp \
112: SENDFILES=yes REQUEST=no
113:
114:
115: The following gives permissions and partial contents of file
116: /eettcc/ttttyyss:
117:
118:
119: -rw-r--r-- 1 root root 163 Wed Jul 11 11:36 /etc/ttys
120:
121: 1lPconsole
122: 1rPcom3r
123:
124:
125: Finally, the following gives permissions on /ddeevv/ccoomm33rr (while
126: enabled):
127:
128:
129:
130: COHERENT Lexicon Page 2
131:
132:
133:
134:
135: UUCP Overview UUCP
136:
137:
138:
139:
140: c--s------ 1 root root 21 38 Wed Jul 11 11:50 /dev/com3r
141:
142:
143: To use the Trailblazer, log in as rroooott, and type the following
144: commands:
145:
146:
147: disable com3r
148: kermit cbl 9600 /dev/com3l > /tmp/modem_dump
149:
150:
151: Note that we disabled the ``remote'' device but used the
152: ``local'' modem device when using kkeerrmmiitt. This allows us to
153: access the modem registers without having to wait for the modem
154: to assert the carrier detect signal.
155:
156: While talking to the Trailblazer, we sent it AATTNN? followed by the
157: <EEnntteerr> key. We then entered ^ (the circumflex) followed by the
158: letter CC in order to exit from kkeerrmmiitt. The following gives the
159: results contained in file /ttmmpp/mmooddeemm_dduummpp:
160:
161:
162: kermit: connected...
163:
164: E0 F1 M1 Q9 T V0 W0 X3 Y0 &P0 &T4 Version BA5.01
165: S00=001 S01=000 S02=043 S03=013 S04=010 S05=008 S06=002 S07:060 \
166: S08=002 S09=006
167: S10=007 S11=070 S12=050 S18=000 S25=005 S38=000
168: S41=000 S45=000 S47=004 S48:001 S49=000
169: S50=000 S51:252 S52=000 S54:003 S55=000 S56=017 S57=019 \
170: S58:000 S59=000
171: S60=000 S61:230 S62=003 S63=001 S64=000 S65=000 S66=000 S67=000 \
172: S68=255 S69=000
173: S90=000 S91=000 S92=000 S94=001 S95=000 S96=001
174: S100=000 S101=000 S102=000 S104=000 S105=001
175: S110=255 S111=255 S112=001
176: S121=000 S130=002 S131:001 S255=000
177: N0:
178: N1:
179: N2:
180: N3:
181: N4:
182: N5:
183: N6:
184: N7:
185: N8:
186: N9:
187: 0
188: kermit: disconnected.
189:
190:
191: ***** /etc/ttys Problems *****
192:
193: Sometimes, UUCP problems will arise because the entry in file
194:
195:
196: COHERENT Lexicon Page 3
197:
198:
199:
200:
201: UUCP Overview UUCP
202:
203:
204:
205: /eettcc/ttttyyss for the serial port your modem is using, is either
206: missing or is incorrect.
207:
208: To discover which port UUCP thinks your modem is using, invoke
209: the command uuuuiinnssttaallll. Then, under its DDeevviicceess option, look at
210: the _r_e_m_o_t_e line. The remote device you specified on this line
211: must be described in file /eettcc/ttttyyss. If it is not, then you will
212: find statements in the log file for the site you are calling
213: stating that a device was not found.
214:
215: If you see errors in the log files that state that a device is
216: not found, and you have checked the ``remote'' entry in uuuuiinnssttaallll
217: against the contents of /eettcc/ttttyyss, the next possible cause may be
218: the /eettcc/ttttyyss entry for the port. Look for trailing spaces at
219: the end of the line that describes the ccoomm port. If you find a
220: space at the end of a line, delete it.
221:
222: ***** com Port Driver Permissions *****
223:
224: By far, the most common problem deals with permissions associated
225: with the ccoomm port devices. If you are trying to get UUCP to call
226: out on a port, and keep seeing errors of the form
227:
228:
229: Dial failed, Line Problem
230:
231:
232: in the output of uuuulloogg, you may need to fix permissions on the
233: port in question.
234:
235: If you are using one ccoomm port both for remote logins and to call
236: out using UUCP, note the following: When a port is enabled for
237: remote access via a modem, the permissions for the port are
238: changed so that only the superuser rroooott can access the port.
239: This prevents someone from inadvertently trying to send data out
240: the port. When the port is later disabled so that UUCP can dial
241: out, the permissions for that ccoomm port _a_r_e _n_o_t changed to give
242: everyone access to the port. Remember, when UUCP is executing,
243: it is just another user with the name ``uucp'' and does not have
244: rroooott privileges.
245:
246: To set the permissions properly, use the command cchhmmoodd to reset
247: the permission of the ccoomm port device in directory /ddeevv. For
248: example, if your UUCP connection is via ccoomm11rr, log in as the
249: superuser rroooott and enter the command:
250:
251:
252: chmod 666 /dev/com1*
253:
254:
255: Usually, serial ports should have read and write permissions
256: turned on for all users. The main exception to this rule is that
257: a port enabled for logins becomes readable and writeable only by
258: rroooott. This not a problem for UUCP as the port is disabled (and
259: permissions expanded) temporarily when uuuucciiccoo runs.
260:
261:
262: COHERENT Lexicon Page 4
263:
264:
265:
266:
267: UUCP Overview UUCP
268:
269:
270:
271:
272: ***** Lock Files and Temporary Files *****
273:
274: UUCP controls access to the modem and to various directories and
275: sites via a set of ``lock files''. This is to prevent UUCP from
276: tripping over its own feet by attempting to write more than one
277: file to the same site at the same site.
278:
279: When a UUCP session fails, it may fail to remove all of its lock
280: files before it exits, depending upon the seriousness of the
281: failure. ``Stale'' lock files and temporary files in directory
282: will prevent UUCP from accessing a given site or even from
283: working altogether. Symptoms of this problem are messages in the
284: log files that state:
285:
286:
287: Site locked
288:
289:
290: This, of course, is not indicative of a problem unless no UUCP
291: connection has been made recently (within the last minute or so).
292: To cure this problem, log in as the superuser rroooott and then enter
293: the command:
294:
295:
296: uurmlock
297:
298:
299: This will remove all ``stale'' lock or temporary files.
300:
301: ***** UUCP Configuration Files *****
302:
303: By far the most common cause of problems are mistakes in one or
304: another UUCP configuration file. If problems persist, check all
305: UUCP configuration files against the descriptions found in
306: correspondingly named Lexicon articles. The files in question
307: are ttttyyss, LL-ddeevviicceess, LL.ssyyss, and PPeerrmmiissssiioonnss.
308:
309: ***** UUCP Executable File Permissions *****
310:
311: UUCP commands can invoke each other from time to time. If a UUCP
312: executable file's permissions are set incorrectly, that command
313: may be prevented from being executed under certain conditions, or
314: from reading or writing certain key files.
315:
316: Key UUCP executable files are /uussrr/lliibb/uuuuccpp/uuuucciiccoo,
317: /uussrr/lliibb/uuuuccpp/uuuuxxqqtt, /uussrr/bbiinn/uuuuccpp, and /uussrr/bbiinn/uuuuxx. These files
318: must belong to user and group uuuuccpp. Permissions on these files
319: must be 6511 (-r-s--s--x). See the Lexicon article for the
320: command cchhmmoodd for further details on how to reset permissions for
321: files.
322:
323: ***** UUCP Connects, but ... *****
324:
325: Once UUCP is dialing out, it is extremely difficult to diagnose
326:
327:
328: COHERENT Lexicon Page 5
329:
330:
331:
332:
333: UUCP Overview UUCP
334:
335:
336:
337: problems, as they can occur at either end of the connection. In
338: most cases, one must know both systems to diagnose problems
339: related to communication problems. Check the following:
340:
341: -> Check your chat scripts. Contact the other system's system
342: administrator to be sure that you are expecting the correct
343: prompts in the chat script for the system you are calling.
344:
345: -> Use the debugging mode of uuuucciiccoo to watch communications.
346: Debugging mode is accessed using the uuuucciiccoo command suffixed
347: by a -xx#, where # is 1 to 9 which determines the debugging
348: level. For example
349:
350: /usr/lib/uucp/uucico -Smwcbbs -x1
351:
352: Please note, the uuuucciiccoo debugging option is incompatible with
353: certain non-COHERENT versions of uuuucciiccoo.
354:
355: -> Note also that the COHERENT default mailer does not yet
356: support domains. If domain information is being sent to your
357: system, an error may result and possibly cause unexpected
358: results or errors from uuuucciiccoo. The error will usually state
359: that a log file could not be written to. Alternate mailers
360: are available from the various COHERENT archive sites, as well
361: as the MWC UUCP bulletin board system.
362:
363: ***** Remote Won't Accept Files ... Where'd My Mail Go? *****
364:
365: If you see messages in your log files that a site would not
366: accept a file from your site, the other site may not have its
367: permissions set to allow you to send files to it, or to write the
368: files you are sending to a directory that you specified.
369:
370: When sending files across systems, check the length of the site
371: name. Currently, COHERENT can only work with a seven-character
372: or shorter site name. If you are using an eight-character or
373: longer site name, COHERENT will not properly distribute files
374: transferred from your site. To change the name of your system,
375: edit the contents of file /eettcc/uuuuccppnnaammee.
376:
377: ***** See Also *****
378:
379: ccoomm, ccoommmmaannddss, LL-ddeevv, LL.ssyyss, PPeerrmmiissssiioonnss, tteerrmmiinnaall, uuuucciiccoo, uuuuccpp,
380: uuuuccppnnaammee, uuuuddeeccooddee, uuuueennccooddee, uuuuiinnssttaallll, uuuulloogg, uuuummvvlloogg, uuuunnaammee,
381: uuuurrmmlloocckk, uuuuttoouucchh, uuuuxx, uuuuxxqqtt
382: _U_U_C_P, _R_e_m_o_t_e _C_o_m_m_u_n_i_c_a_t_i_o_n_s _U_t_i_l_i_t_y, tutorial
383:
384:
385:
386:
387:
388:
389:
390:
391:
392:
393:
394: COHERENT Lexicon Page 6
395:
396:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.