NAME

L.sys − information needed to connect to a system

SYNTAX

/usr/lib/uucp/L.sys

DESCRIPTION

The uucp utility uses the L.sys file.  The file contains entries for each remote system that the local system can call, and for each remote system for which the local system accepts calls but does not call.  More than one line can be used for a particular remote system.  In this case, the additional lines represent alternative communication paths that are tried in sequential order.

The format of each entry, with each field separated by blanks or tabs, is:

system-name time device class phone login

system-nameThe name of the remote system. 

timeA string that indicates the days of the week and the times of day when the system can be called (for example, MoTuTh0800-1740). 

The day portion may be a list containing:

Su Mo Tu We Th Fr Sa

The day may also be Wk for any weekday or Any for any day. 

You can indicate hours in a range (for example, 0800-1230).  If you do not specify a time calls will be allowed at any time. 

Note that a time range that spans 0000 is permitted.  For example, 0800-0600 means that all times are allowed except times between 6 AM and 8 AM. 

Multiple date specifications that are separated by a vertical (|) are allowed.  For example, Any0100-0600|Sa|Su means that the system can be called any day between 1 AM and y AM, or any time on Saturday and Sunday. 

An optional subfield is available to indicate the minimum time, in minutes, before retrying a failed connection.  A failed connection attempt is a login failure, as opposed to a dialing connection failure.  The subfield separator is a comma (,).  For example, Any,9 means call any time, but wait at least 9 minutes after a failure has occurred. 

deviceEither the ACU or the hard-wired device used for the call.  For the hard-wired device, use the last part of the special file name (for example, tty2). 

classThe line speed for the call (for example, 1200).  The exception is when the BC library routine dialout is available, in which case this is the dialout class. 

phoneThe telephone number, made up of an optional alphabetic abbreviation and a numeric part.  The abbreviation should be one that appears in the L-dialcodes(5) file (for example, ct5900, nh6511).  If a numeric number is used, it should be given in full.  For the hard-wired devices, this field contains the same string as used for the device field. 

loginThe login information, given as a series of fields and subfields in this format:

expect1[−[sendspecial]−expect2] send ... 

The expect1 argument is the string the local system expects to read when logging in to the remote system, and the send argument is the string the local system is to send when the expect string is received.  If two double quotes ("") are specified instead of the expect1 argument, nothing is expected from the remote system. 

The sendspecial argument specifies a special character to be sent to the remote system if the expect1 argument is not received.  If sendspecial is omitted, and two dashes (−−) follow the expect1 argument, the local system sends a carriage return to the remote system. 

Other special characters are:

EOTSend an EOT character

BREAK# Send # break sequences (default is 3)

PAUSE#Pause # seconds (default is 5)

\dPause 1 second before sending next character

\sSend a blank character

\rSend a carriage return

\bSend a break character

\#Send the character represented by the octal number
#.  For example, \05 is CTRL-e. 

P_ZERO  Change parity from even (default) to zero

P_EVEN Change parity to even

P_ODDChange parity to odd

P_ONEChange parity to one parity

The expect2 argument defines another string expected to be read after transmission of the sendspecial argument to the remote system. 

EXAMPLES

login: xuucp ssword: smiley

In the preceding example, the remote system is expected to send the string “login:”, to which the local system replies “xuucp”.  Then the word “ssword:” is expected from the remote system.  (The first letter of the password prompt varies from system to system, so it is safer to look for the ending characters.)  When “ssword:” is received, the local system sends “smiley”.  If the login is successful, the conversation between the peer transfer processes (uucico) begins.  If the login fails, the connection attempt fails.

login:--login xuucp ssword: smiley

In the preceding example, “login:” is expected.  If it is received, “xuucp” is sent to the remote system.  If “login:” is not received, a carriage return is sent to the remote system, and “login” is expected.  If it is received “xuucp” is sent to the remote system.  The example then proceeds the same as the previous example.

login:-BREAK1-login: xuucp ssword: smiley

In the above example, “login:” is expected.  If it is not received, one break sequence is sent, to change the baud rate of the remote process.  Then “login:” is again expected, and the example proceeds the same as the previous examples.

SEE ALSO

System Management Guide