![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to L.sys.0 CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 43BSDReno / usr.bin / uucp|
Return to L.sys.0 CVS log | Up to [CSRG BSD Unix] / 43BSDReno / usr.bin / uucp |
1.1 root 1:
2:
3:
4: L.SYS(5) 1986 L.SYS(5)
5:
6:
7:
8: NNAAMMEE
9: L.sys - UUCP remote host description file
10:
11: DDEESSCCRRIIPPTTIIOONN
12: The _L._s_y_s file is consulted by the UUCP daemon _u_u_c_i_c_o(8C)
13: for information on remote systems. _L._s_y_s includes the sys-
14: tem name, appropriate times to call, phone numbers, and a
15: login and password for the remote system. _L._s_y_s is thus a
16: privileged file, owned by the UUCP Administrator; it is
17: accessible only to the Administrator and to the superuser.
18:
19: Each line in _L._s_y_s describes one connection to one remote
20: host, and has the form:
21:
22: System Times Caller Class Device/Phone_Number [Expect Send]....
23:
24: Fields can be separated by any number of blanks or tabs.
25: Lines beginning with a `#' character are comments; long
26: lines can be continued by appending a `\' character to the
27: end of the line.
28:
29: The first five fields (_S_y_s_t_e_m through _D_e_v_i_c_e/_P_h_o_n_e__N_u_m_b_e_r)
30: specify the hardware mechanism that is necessary to make a
31: connection to a remote host, such as a modem or network.
32: _U_u_c_i_c_o searches from the top down through _L._s_y_s to find the
33: desired _S_y_s_t_e_m; it then opens the _L-_d_e_v_i_c_e_s(5) file and
34: searches for the first available device with the same
35: _C_a_l_l_e_r, _C_l_a_s_s, and (possibly) _D_e_v_i_c_e. (``Available'' means
36: that the device is ready and not being used for something
37: else.) _U_u_c_i_c_o attempts a connection using that device; if
38: the connection cannot be made (for example, a dialer gets a
39: busy signal), _u_u_c_i_c_o tries the next available device. If
40: this also fails, it returns to _L._s_y_s to look for another
41: line for the same _S_y_s_t_e_m. If none is found, _u_u_c_i_c_o gives
42: up.
43:
44: _S_y_s_t_e_m is the hostname of the remote system. Every machine
45: with which this system communicates via UUCP should be
46: listed, regardless of who calls whom. Systems not listed in
47: _L._s_y_s will not be permitted a connection. The local host-
48: name should nnoott appear here for security reasons.
49:
50: _T_i_m_e_s is a comma-separated list of the times of the day and
51: week that calls are permitted to this _S_y_s_t_e_m. _T_i_m_e_s is most
52: commonly used to restrict long distance telephone calls to
53: those times when rates are lower. List items are con-
54: structed as:
55:
56: _k_e_y_w_o_r_dhhmm--hhmm//_g_r_a_d_e;;_r_e_t_r_y__t_i_m_e
57:
58: _K_e_y_w_o_r_d is required, and must be one of:
59:
60:
61:
62:
63: Printed 7/4/90 April 1
64:
65:
66:
67:
68:
69:
70: L.SYS(5) 1986 L.SYS(5)
71:
72:
73:
74: AAnnyy Any time, any day of the week.
75:
76: WWkk Any weekday. In addition, MMoo, TTuu, WWee, TThh, FFrr, SSaa,
77: and SSuu can be used for Monday through Sunday,
78: respectively.
79:
80: EEvveenniinngg When evening telephone rates are in effect, from
81: 1700 to 0800 Monday through Friday, and all day
82: Saturday and Sunday. EEvveenniinngg is the same as
83: WWkk11770000--00880000,,SSaa,,SSuu.
84:
85: NNiigghhtt When nighttime telephone rates are in effect, from
86: 2300 to 0800 Monday through Friday, all day Satur-
87: day, and from 2300 to 1700 Sunday. NNiigghhtt is the
88: same as AAnnyy22330000--00880000,,SSaa,,SSuu00880000--11770000.
89:
90: NNoonnPPeeaakk This is a slight modification of EEvveenniinngg. It
91: matches when the USA X.25 carriers have their lower
92: rate period. This is 1800 to 0700 Monday through
93: Friday, and all day Saturday and Sunday. NNoonnPPeeaakk is
94: the same as AAnnyy11880000--00770000,,SSaa,,SSuu.
95:
96: NNeevveerr Never call; calling into this _S_y_s_t_e_m is forbidden or
97: impossible. This is intended for polled connec-
98: tions, where the remote system calls into the local
99: machine periodically. This is necessary when one of
100: the machines is lacking either dial-in or dial-out
101: modems.
102:
103: The optional _h_h_m_m-_h_h_m_m subfield provides a time range that
104: modifies the keyword. _h_h_m_m refers to _h_o_u_r_s and _m_i_n_u_t_e_s in
105: 24-hour time (from 0000 to 2359). The time range is permit-
106: ted to "wrap" around midnight, and will behave in the obvi-
107: ous way. It is invalid to follow the EEvveenniinngg, NNoonnPPeeaakk, and
108: NNiigghhtt keywords with a time range.
109:
110: The _g_r_a_d_e subfield is optional; if present, it is composed
111: of a `/' (slash) and single character denoting the _g_r_a_d_e of
112: the connection, from 00 to 99, AA to ZZ, or aa to zz. This speci-
113: fies that only requests of grade _g_r_a_d_e or better will be
114: transferred during this time. (The grade of a request or
115: job is specified when it is queued by _u_u_c_p or _u_u_x.) By con-
116: vention, mail is sent at grade CC, news is sent at grade dd,
117: and uucp copies are sent at grade nn. Unfortunately, some
118: sites do not follow these conventions, so it is not 100%
119: reliable.
120:
121: The _r_e_t_r_y__t_i_m_e subfield is optional; it must be preceded by
122: a `;' (semicolon) and specifies the time, in minutes, before
123: a failed connection may be tried again. (This restriction
124: is in addition to any constraints imposed by the rest of the
125: _T_i_m_e field.) By default, the retry time starts at 10 minutes
126:
127:
128:
129: Printed 7/4/90 April 2
130:
131:
132:
133:
134:
135:
136: L.SYS(5) 1986 L.SYS(5)
137:
138:
139:
140: and gradually increases at each failure, until after 26
141: tries _u_u_c_i_c_o gives up completely (MAX RETRIES). If the retry
142: time is too small, _u_u_c_i_c_o may run into MAX RETRIES too soon.
143:
144: _C_a_l_l_e_r is the type of device used:
145:
146: AACCUU Automatic call unit or auto-dialing modem such as
147: the Hayes Smartmodem 1200 or Novation ``Smart Cat''.
148: See _L-_d_e_v_i_c_e_s for a list of supported modems.
149:
150: DDIIRR Direct connect; hardwired line (usually RS-232) to a
151: remote system.
152:
153: MMIICCOOMM Micom Terminal Switch.
154:
155: PPAADD X.25 PAD connection.
156:
157: PPCCPP GTE Telenet PC Pursuit. See _L-_d_e_v_i_c_e_s for configura-
158: tion details.
159:
160: SSYYTTEEKK Sytek high-speed dedicated modem port connection.
161:
162: TTCCPP Berkeley TCP/IP or 3Com UNET connection. These are
163: mutually exclusive. TCP ports do nnoott need entries
164: in _L-_d_e_v_i_c_e_s since all the necessary information is
165: contained in _L._s_y_s. If several alternate ports or
166: network connections should be tried, use multiple
167: _L._s_y_s entries.
168:
169: _C_l_a_s_s is usually the speed (baud) of the device, typically
170: 300, 1200, or 2400 for ACU devices and 9600 for direct
171: lines. Valid values are device dependent, and are specified
172: in the _L-_d_e_v_i_c_e_s file.
173:
174: On some devices, the baud may be preceded by a non-numeric
175: prefix. This is used in _L-_d_e_v_i_c_e_s to distinguish among dev-
176: ices that have identical _C_a_l_l_e_r and baud, but yet are dis-
177: tinctly different. For example, 1200 could refer to all Bell
178: 212-compatible modems, V1200 to Racal-Vadic modems, and
179: C1200 to CCITT modems, all at 1200 baud.
180:
181: On TCP connections, _C_l_a_s_s is the port number (an integer
182: number) or a port name from /_e_t_c/_s_e_r_v_i_c_e_s that is used to
183: make the connection. For standard Berkeley TCP/IP, UUCP nor-
184: mally uses port number 540.
185:
186: _D_e_v_i_c_e/_P_h_o_n_e__N_u_m_b_e_r varies based on the _C_a_l_l_e_r field. For
187: ACU devices, this is the phone number to dial. The number
188: may include: digits 00 through 99; ## and ** for dialing those
189: symbols on tone telephone lines; -- (hyphen) to pause for a
190: moment, typically two to four seconds; == (equal sign) to
191: wait for a second dial tone (implemented as a pause on many
192:
193:
194:
195: Printed 7/4/90 April 3
196:
197:
198:
199:
200:
201:
202: L.SYS(5) 1986 L.SYS(5)
203:
204:
205:
206: modems). Other characters are modem dependent; generally
207: standard telephone punctuation characters (such as the slash
208: and parentheses) are ignored, although _u_u_c_i_c_o does not
209: guarantee this.
210:
211: The phone number can be preceded by an alphabetic string;
212: the string is indexed and converted through the
213: _L-_d_i_a_l_c_o_d_e_s(5) file.
214:
215: For DIR devices, the _D_e_v_i_c_e/_P_h_o_n_e__N_u_m_b_e_r field contains the
216: name of the device in /_d_e_v that is used to make the connec-
217: tion. There must be a corresponding line in _L-_d_e_v_i_c_e_s with
218: identical _C_a_l_l_e_r, _C_l_a_s_s, and _D_e_v_i_c_e fields.
219:
220: For TCP and other network devices, _D_e_v_i_c_e/_P_h_o_n_e__N_u_m_b_e_r holds
221: the true network name of the remote system, which may be
222: different from its UUCP name (although one would hope not).
223:
224: _E_x_p_e_c_t and _S_e_n_d refer to an arbitrarily long set of strings
225: that alternately specify what to _e_x_p_e_c_t and what to _s_e_n_d to
226: login to the remote system once a physical connection has
227: been established. A complete set of expect/send strings is
228: referred to as an _e_x_p_e_c_t/_s_e_n_d _s_c_r_i_p_t. The same syntax is
229: used in the _L-_d_e_v_i_c_e_s file to interact with the dialer prior
230: to making a connection; there it is referred to as a _c_h_a_t
231: _s_c_r_i_p_t. The complete format for one _e_x_p_e_c_t/_s_e_n_d pair is:
232:
233: _e_x_p_e_c_t--_t_i_m_e_o_u_t--_s_e_n_d--_e_x_p_e_c_t--_t_i_m_e_o_u_t _s_e_n_d
234:
235: _E_x_p_e_c_t and _S_e_n_d are character strings. _E_x_p_e_c_t is compared
236: against incoming text from the remote host; _s_e_n_d is sent
237: back when _e_x_p_e_c_t is matched. By default, the _s_e_n_d is fol-
238: lowed by a `\r' (carriage return). If the _e_x_p_e_c_t string is
239: not matched within _t_i_m_e_o_u_t seconds (default 45), then it is
240: assumed that the match failed. The `_e_x_p_e_c_t--_s_e_n_d--_e_x_p_e_c_t'
241: notation provides a limited loop mechanism; if the first
242: _e_x_p_e_c_t string fails to match, then the _s_e_n_d string between
243: the hyphens is transmitted, and _u_u_c_i_c_o waits for the second
244: _e_x_p_e_c_t string. This can be repeated indefinitely. When the
245: last _e_x_p_e_c_t string fails, _u_u_c_i_c_o hangs up and logs that the
246: connection failed.
247:
248: The timeout can (optionally) be specified by appending the
249: parameter `~~_n_n' to the expect string, when _n_n is the timeout
250: time in seconds.
251:
252: Backslash escapes that may be imbedded in the _e_x_p_e_c_t or _s_e_n_d
253: strings include:
254:
255: \b Generate a 3/10 second BREAK.
256: \b_n Where _n is a single-digit number;
257: generate an _n/10 second BREAK.
258:
259:
260:
261: Printed 7/4/90 April 4
262:
263:
264:
265:
266:
267:
268: L.SYS(5) 1986 L.SYS(5)
269:
270:
271:
272: \c Suppress the \r at the end of a _s_e_n_d string.
273: \d Delay; pause for 1 second. (_S_e_n_d only.)
274: \r Carriage Return.
275: \s Space.
276: \n Newline.
277: \xxx Where _x_x_x is an octal constant;
278: denotes the corresponding ASCII character.
279:
280: As a special case, an empty pair of double-quotes """" in the
281: _e_x_p_e_c_t string is interpreted as ``expect nothing''; that is,
282: transmit the _s_e_n_d string regardless of what is received.
283: Empty double-quotes in the _s_e_n_d string cause a lone `\r'
284: (carriage return) to be sent.
285:
286: One of the following keywords may be substituted for the
287: _s_e_n_d string:
288:
289: BREAK Generate a 3/10 second BREAK
290: BREAK_n Generate an _n/10 second BREAK
291: CR Send a Carriage Return (same as "").
292: EOT Send an End-Of-Transmission character, ASCII \004.
293: Note that this will cause most hosts to hang up.
294: NL Send a Newline.
295: PAUSE Pause for 3 seconds.
296: PAUSE_n Pause for _n seconds.
297: P_ODD Use odd parity on future send strings.
298: P_ONE Use parity one on future send strings.
299: P_EVEN Use even parity on future send strings. (Default)
300: P_ZERO Use parity zero on future send strings.
301:
302: Finally, if the _e_x_p_e_c_t string consists of the keyword AABBOORRTT,
303: then the string following is used to arm an abort trap. If
304: that string is subsequently received any time prior to the
305: completion of the entire _e_x_p_e_c_t/_s_e_n_d script, then _u_u_c_i_c_o
306: will abort, just as if the script had timed out. This is
307: useful for trapping error messages from port selectors or
308: front-end processors such as ``Host Unavailable'' or ``Sys-
309: tem is Down.''
310:
311: For example:
312:
313: "" "" ogin:--ogin: nuucp ssword: ufeedme
314:
315: This is executed as, ``When the remote system answers,
316: _e_x_p_e_c_t nothing. _S_e_n_d a carriage return. _E_x_p_e_c_t the remote
317: to transmit the string `ogin:'. If it doesn't within 45
318: seconds, send another carriage return. When it finally
319: does, _s_e_n_d it the string `nuucp'. Then _e_x_p_e_c_t the string
320: `ssword:'; when that is received, _s_e_n_d `ufeedme'.''
321:
322: FFIILLEESS
323: /usr/lib/uucp/L.sys
324:
325:
326:
327: Printed 7/4/90 April 5
328:
329:
330:
331:
332:
333:
334: L.SYS(5) 1986 L.SYS(5)
335:
336:
337:
338: /usr/lib/uucp/UUAIDS/L.sysL.sys example
339:
340: SSEEEE AALLSSOO
341: uucp(1C), uux(1C), L-devices(5), services(5), uucico(8C)
342:
343: BBUUGGSS
344: ``ABORT'' in the send/expect script is expressed ``back-
345: wards,'' that is, it should be written `` _e_x_p_e_c_t AABBOORRTT'' but
346: instead it is `` AABBOORRTT _e_x_p_e_c_t''.
347:
348: Several of the backslash escapes in the send/expect strings
349: are confusing and/or different from those used by AT&T and
350: Honey-Danber UUCP. For example, `\b' requests a BREAK,
351: while practically everywhere else `\b' means backspace.
352: `\t' for tab and `\f' for formfeed are not implemented.
353: `\s' is a kludge; it would be more sensible to be able to
354: delimit strings with quotation marks.
355:
356:
357:
358:
359:
360:
361:
362:
363:
364:
365:
366:
367:
368:
369:
370:
371:
372:
373:
374:
375:
376:
377:
378:
379:
380:
381:
382:
383:
384:
385:
386:
387:
388:
389:
390:
391:
392:
393: Printed 7/4/90 April 6
394:
395:
396:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.