|
1767
|
1 # Systems file - UUCPbb v2.1
|
|
|
2 #
|
|
|
3 # Format:
|
|
|
4 # <system_name> <schedule> <device> <baud> <phone> <chat_script>
|
|
|
5 #
|
|
|
6 # Notes:
|
|
|
7 # - Lines starting with a #, <space>, <tab> or <cr> character are considered
|
|
|
8 # comment lines and ignored.
|
|
|
9 #
|
|
|
10 # - At least one whitespace (<space> or <tab>) must separate each field.
|
|
|
11 #
|
|
|
12 # - Each system entry must contain only one <cr> at its end.
|
|
|
13 #
|
|
|
14 # - UUCICO uses <system_name> to identify the host to call or let call us.
|
|
|
15 #
|
|
|
16 # - <system_name> MUST start in the first column. System names cannot be
|
|
|
17 # more than 8 alphanumeric characters. Punctation is not allowed in the
|
|
|
18 # system name.
|
|
|
19 #
|
|
|
20 # - <schedule> is the day(s)/time(s) we are allowed to call the system.
|
|
|
21 # This field consists of two subfields DAY and TIME. These have no
|
|
|
22 # spaces between them. The DAY subfield is specified using the
|
|
|
23 # following keywords (case is unimportant);
|
|
|
24 #
|
|
|
25 # Any -we can call at any time
|
|
|
26 # Never -we should never call but wait to be called
|
|
|
27 # Wk -call any weekday (Monday-Friday)
|
|
|
28 # Su,Mo,Tu,We, -call on individual days
|
|
|
29 # Th,Fr,Sa
|
|
|
30 #
|
|
|
31 # The TIME subfield is specified by two 24-hour clock times separated by
|
|
|
32 # a dash (-) representing the span of allowed time. For example,
|
|
|
33 # 0930-1100, call only between 9:30 and 11:00 in the morning. More than
|
|
|
34 # one DAY/TIME can be included by separating them with commas.
|
|
|
35 # Examples:
|
|
|
36 #
|
|
|
37 # Wk1230-1545,Su,Sa -call Monday-Friday from 12:30 to 3:45 in the
|
|
|
38 # afternoon and any time on Saturday and Sunday.
|
|
|
39 # Any1800-2000 -call any day from 6:00 to 8:00 at night
|
|
|
40 # Any -call any day, any time
|
|
|
41 # Th -call any time on Thursday
|
|
|
42 #
|
|
|
43 # - <device> field is refers to entry in the 'Devices' file.
|
|
|
44 #
|
|
|
45 # - <baud> is the maximum speed we will use to talk to the remote.
|
|
|
46 #
|
|
|
47 # - <phone> is the full number we need to call the remote
|
|
|
48 #
|
|
|
49 # - <chat_script> are alternating pairs of strings starting with the
|
|
|
50 # expected response from the remote and what we send. A space separates
|
|
|
51 # each expect or send string. Normally, a newline character is sent at
|
|
|
52 # the end of every send string. This can be overridden with the \c
|
|
|
53 # character. If we to indicate not to expect or wait for a response a
|
|
|
54 # pair of double quotes ("") can be used.
|
|
|
55 #
|
|
|
56 # - Special chat script characters are:
|
|
|
57 # "" -send or expect nothing
|
|
|
58 # EOT -send end-of-transmission character (hex 04)
|
|
|
59 # BREAK -send a line break
|
|
|
60 # \b -send a backspace character (hex 08)
|
|
|
61 # \c -suppress sending a newline character at the end of SEND string
|
|
|
62 # \d -delay 1 second
|
|
|
63 # \K -send a line break
|
|
|
64 # \n -send a newline character, i.e. linefeed (hex 0A)
|
|
|
65 # \N -send a NUL character (hex 00)
|
|
|
66 # \p -pause a fraction of a second
|
|
|
67 # \r -send a carriage return (hex 0D)
|
|
|
68 # \s -send a space (hex 20)
|
|
|
69 # \\ -send a backslash (\) character
|
|
|
70 # \t -send a tab character (hex 09)
|
|
|
71 # \xxx -collapse the octal digits xxx into a single ASCII character
|
|
|
72 # and send that character
|
|
|
73 # \[ -send escape character (hex 1B)
|
|
|
74 # \^? -send a control character where ? is replaced with appropriate
|
|
|
75 # character, e.g. \^A sends control-A
|
|
|
76
|
|
|
77 # Boisy's RedHat Linux Box
|
|
|
78 redhat Any T2 9600 none "" \d\n in: nuucp word: itsme
|
|
|
79
|
|
|
80 # some remotes
|
|
|
81 phoenix Any T4 9600 none "" \n name?: uucp
|
|
|
82 seabass Any ViVa24 1200 555-1212 "" \r ogin: nuucp word: abcdefg
|
