Return to l.sys CVS log

Up to [MW Coherent from dump] / coherent / a / usr / man / COHERENT

coherent

L.sys                      File Format                      L.sys




Format for UUCP site descriptions

/uussrr/lliibb/uuuuccpp/LL.ssyyss

The  file  LL.ssyyss  holds descriptions  of  remote  sites that  are
accessed  via  UUCP.   UUCP utilities  read  from  this file  the
description  of any  system  that you  ask them  to access.   The
superuser rroooott can read and  edit the contents of this file, both
to update its contents and to add new descriptions.

Each line in LL.ssyyss is either  a comment or a site descriptor.  If
a  line  begins  with  a  pound  sign (`#'),  it  is  a  comment;
otherwise,  it  is  treated  as  a  site descriptor.   Each  site
description  consists of  five or more  fields, each  field being
demarcated by one or more white-space characters.

***** Site Description *****

The first five fields of a site description identify the site and
how to contact it.  These fields are as follows:

11. RReemmoottee ssyysstteemm nnaammee
     This names  the remote  system.  In COHERENT  versions 3.0.0
     and 3.1.0, only the first seven characters are significant.

22. LLeeggaall ccaallll ttiimmeess
     This  entry specifies  when the remote  site may  be called.
     There are several possible formats:

             NNeevveerr
             _d_a_y__l_i_s_t
             _d_a_y__a_n_d__t_i_m_e__l_i_s_t

     NNeevveerr  means never  call the  remote site;  use it  only for
     sites that will only be calling you.  _d_a_y__l_i_s_t may be any of
     the  following: AAnnyy  (that is,  call  as soon  as a  file is
     queued for sending),  WWkk (for Monday through Friday), or one
     or  more of  SSuu, MMoo,  TTuu, WWee,  TThh, FFrr,  or SSaa,  separated by
     commas   (be   sure    not   to   use   spaces   here).    A
     _d_a_y__a_n_d__t_i_m_e__l_i_s_t is  identical to a _d_a_y__l_i_s_t  but appends a
     _t_i_m_e field  to one or more of the  days specified.  The _t_i_m_e
     field consists of  two four-digit 24-hour times separated by
     a hyphen.  The  legal call time is any time  at or after the
     first time  and at or before the second  time.  If the first
     time is greater than the second time, then the valid calling
     times will be from midnight  to the second time and from the
     first  time  through  midnight.   Omitting  the  _t_i_m_e  field
     permits  calling at  any  time on  the  specified day.   For
     example:

             # never dial the site
             Never
             # dial the site whenever a file is queued
             Any


COHERENT Lexicon                                           Page 1




L.sys                      File Format                      L.sys



             # dial on Sunday, Monday and Tuesday, 2-5 AM
             SuMoTu0200-0500
             # Weekdays between 1-7 PM and all day on Saturday
             Wk1300-1900,Sa
             # Midnight Sunday through 2 AM and 11 PM through midnight
             Su2300-0200


33. DDeevviiccee
     This indicates the device on your computer via which UUCP is
     to contact the remote site.  For sites accessed via a modem,
     use the entry AACCUU. For sites directly connected via a serial
     port, use the name of the port, e.g.,  ccoomm33ll.

4. SSppeeeedd
     This gives  the the baud rate  at which UUCP is  to call the
     remote system,  e.g., 1200, 2400, or  9600.  This speed must
     be valid  according to the  file /eettcc/mmooddeemmccaapp for  at least
     one modem described in the file LL-ddeevviicceess.

55. TTeelleepphhoonnee nnuummbbeerr
     This gives the  string that UUCP is to send  to the modem in
     order  to call  the remote  site.   This string  may include
     special characters for  your modem (e.g., some modems accept
     a  comma if  a  pause is  needed during  dialing), but  will
     usually be simply the number to dial, e.g.  ``17085590412''.
     The string  that is actually  sent to the  modem consists of
     the   ccss  and   ddss  strings  from   the  modem's   entry  in
     /eettcc/mmooddeemmccaapp, the telephone  number, and finally the ddee and
     ccee strings from /eettcc/mmooddeemmccaapp.

***** Chat Script *****

The remaining  fields in a  descriptor form the  ``chat script'',
that is, the dialogue that your UUCP system must perform in order
to log  on to the  remote computer.  The chat  script consists of
strings of characters to be exchanged between the remote computer
and your  UUCP system; first  comes an _e_x_p_e_c_t__s_t_r_i_n_g  (the string
that your system  expects), followed by a _s_e_n_d__s_t_r_i_n_g (the string
to send in response to the _e_x_p_e_c_t__s_t_r_i_n_g).  When calling a remote
site, your  computer waits for  a carrier from  the remote modem,
then waits for the  first _e_x_p_e_c_t__s_t_r_i_n_g, after which it sends the
first _s_e_n_d__s_t_r_i_n_g, etc.

Consider,  for example,  the remote system  bbaazzooookkaa, which  has a
login  prompt  of  CCoohheerreenntt llooggiinn:;  assume  that  your login  is
hhoowwaarrdd, the  remote system prompts for  passwords with ppaasssswwoorrdd:,
and your  password is rr5566dd9922.   The chat script  for bbaazzooookkaa will
read as follows:








COHERENT Lexicon                                           Page 2




L.sys                      File Format                      L.sys



        ogin: howard word: r56d92


As  you can  see from  the above  example, an  _e_x_p_e_c_t__s_t_r_i_n_g need
contain only  the last five characters of  what the remote system
sends.

An   _e_x_p_e_c_t__s_t_r_i_n_g  may   be  compound   or  simple.    A  simple
_e_x_p_e_c_t__s_t_r_i_n_g is  either a sequence of  characters (not including
spaces, tabs,  or hyphens) or  a pair of quotation  marks "".  An
empty  pair of  quotation marks  tells UUCP not  to wait  for any
incoming  prompt, but  go  ahead and  send  the next  _s_e_n_d__s_t_r_i_n_g
(i.e.,  expect a  null string).   A  compound _e_x_p_e_c_t__s_t_r_i_n_g  is a
sequence of fields separated by hyphens, in the format:


        _s_i_m_p_l_e__e_x_p_e_c_t__s_t_r_i_n_g-_s_e_n_d__s_t_r_i_n_g-_s_i_m_p_l_e__e_x_p_e_c_t__s_t_r_i_n_g-_s_e_n_d__s_t_r_i_n_g...


A compound  _e_x_p_e_c_t__s_t_r_i_n_g has  no spaces  or tabs.  If  the first
simple _e_x_p_e_c_t__s_t_r_i_n_g is not received within 25 seconds, the first
_s_e_n_d__s_t_r_i_n_g after the hyphen is sent and the system waits for the
second simple  _e_x_p_e_c_t__s_t_r_i_n_g; if the  second simple _e_x_p_e_c_t__s_t_r_i_n_g
is not received after 25 seconds, the second _s_e_n_d__s_t_r_i_n_g is sent,
and  so  on.   This syntax  allows  UUCP  to  use  any number  of
alternate expect/send  exchanges, rather than failing  if it does
not receive the first _e_x_p_e_c_t__s_t_r_i_n_g.

A _s_e_n_d__s_t_r_i_n_g  is the character  sequence that UUCP  sents to the
remote site.  Unless otherwise specified, UUCP sends a newline at
the end of any _s_e_n_d__s_t_r_i_n_g.  As  a special case of this, an empty
alternate _s_e_n_d__s_t_r_i_n_g tells UUCP  to send a single newline to the
remote site if  the preceding _e_x_p_e_c_t__s_t_r_i_n_g is not received.  For
example


        ogin:--ogin:


is  a compound  _e_x_p_e_c_t__s_t_r_i_n_g  that tells  UUCP to  wait for  the
string ooggiinn: from the remote site.  If UUCP does not receive this
string within  the specified time  limit, it sends  a newline and
again waits for ooggiinn: from the remote site.

You  can  also   use  escape  sequences  to  embed  non-printable
characters in a _s_e_n_d__s_t_r_i_n_g.  The following table lists all legal
escape sequences and their meaning:


      _N_o_t_a_t_i_o_n      _M_e_a_n_i_n_g

         \b         Send backspace
         \c         Suppress newline after _s_e_n_d__s_t_r_i_n_g
                    (Must appear at end of string)
         \d         Delay one second while sending


COHERENT Lexicon                                           Page 3




L.sys                      File Format                      L.sys



         \n         Send newline
         \r         Send carriage return
         \s         Send a space
         \t         Send tab


***** Limitations *****

LL.ssyyss has the following limitations:

->   Site descriptors may not continue beyond one line.

->   Line length cannot exceed 511 characters.

->   No line may have more than 27 composite-expect/send pairs.

->   In the COHERENT versions 3.0.0 and 3.1.0, there is no way to
     send a break signal  to the remote modem.  This feature will
     be added in a future release.

***** Example *****


The following  LL.ssyyss entries are  used to dial into  the MWC UUCP
BBS.  The  first entry corresponds to 2400  b.p.s. access and the
second  to 9600  b.p.s via a  Telebit Trailblazer  modem.  Please
note  that  in  the example  below,  entries  are continued  over
multiple  lines; in  the actual  file,  each entry  must be  on a
single line, but the line may exceed 80 characters in length.


       mwcbbs       Any ACU 2400 17085590412 \
                    "" \r\d\r in:--in: nuucp word: public word: SERIALNUM
       #mwcbbs      Any ACU 9600 17085590445 \
                    FAST \r\d\r in:--in: nuucp word: public word: SERIALNUM


For  further  details on  accessing  the MWC  BBS,  refer to  the
COHERENT Release Notes.

***** See Also *****

ffiillee ffoorrmmaattss, LL-ddeevviicceess, mmooddeemmccaapp, PPeerrmmiissssiioonnss, UUUUCCPP














COHERENT Lexicon                                           Page 4

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.