Using the Sysfiles file, you can define several files to be used as Systems files. See "The Sysfiles File" for details.
Each entry in the Systems file has the following format:
These fields are defined in the following sections.System-name Time Type Class Phone Login
The day portion is a list of one or more day specifiers. These specifiers are listed below.day[time][;retry]
This example allows calls from 5:00 p.m. to 8:00 a.m., Monday through Friday, and any time Saturday and Sunday. The example would be an effective way to call only when phone rates are low, if immediate transfer is not critical.Wk1700-0800,Sa,Su
The time portion should be a range of times such as 0800-1230. If no time portion is specified, any time of day is assumed to be allowed for the call. A time range that spans 0000 is permitted. For example, 0800-0600
means all times are allowed other than at times between 6 a.m. and 8 a.m.
An optional subfield, retry, is available to specify the minimum time (in minutes) before a retry, following a failed attempt. The default wait is 5 minutes after the first failure, 10 after the second, and so on until a delay of about 24 hours. If the retry subfield is present, that wait is used after every failure. The subfield separator is a semicolon (;). For example, "Any;9" is interpreted as "call any time, but wait at least 9 minutes before retrying after a failure occurs."
You can define the protocol used to contact the station by adding it on to the Type field. The example just given shows how to attach the protocol g to the device type ACU. For direct connects, use the name of the station to which you are connecting. See "Device Protocols".Systems: eagle Any ACU,g D1200 3251 login:nuucp password: Oakgrass
Devices: ACU ttym2 - D1200 penril
If information is not required for this field, use a hyphen as a place holder for the field.Systems: eagle Any ACU D1200 NY3251 login:nuucp password:Oakgrass
Devices: ACU ttym2 - D1200 penril
In this string, an equal sign (=) tells the ACU to wait for a secondary dial tone before dialing the remaining digits. A hyphen (-) in the string instructs the ACU to pause four seconds before dialing the next digit.Systems: eagle Any ACU D1200 NY3251 login:nuucp password: Oakgrass
Dialcodes: NY 9=1212555
If your computer is connected to a modem switch, you may access other computers that are connected to that switch. The Systems file entries for these computers does not have a phone number in the Phone field. Instead, this field contains the token that must be passed on to the switch so it will know which computer your computer wishes to communicate with. This token is usually just the station name. The associated Devices file entry should have a \D at the end of the entry to ensure that this field is not translated by means of the Dialcodes file.
The send string is sent when the expect string is received. The expect field may be made up of subfields of the form:expect send
The send field is sent if the prior expect is not successfully read and the expect following the send is the next expected string. For example, with "login--login," UUCP expects the string "login." If UUCP receives that string, it goes on to the next field. If it does not receive the string, it sends nothing, followed by a new line, then looks for "login" again. If no characters are initially expected from the remote computer, the characters " " (null string) should be used in the first expect field. Note that all send fields are sent followed by a newline unless the send string is terminated with a \c.expect[-send-expect]...
Here is an example of a Systems file entry that uses an expect-send string:
This example means causes UUCP to send a carriage return and wait for the string "login:" If it doesn't receive the string, it sends a break character and waits for "login:" again. When it does receive the string "login," it sends the login name uucpx; waits to receive the string "word:" (the last part of "Password:"); and sends the password xyzzy.
owl Any ACU 1200 NY6013 "" \r login:-BREAK-login: uucpx word: xyzzy
Several escape sequences cause specific actions when they are a part of a string sent during the login sequence. These are the same escape sequences used in the Dialers file, listed in Table 7-2.