Return to paths CVS log

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

Annotation of coherent/a/usr/man/COHERENT/paths, revision 1.1.1.1

1.1       root        1: 
                      2: 
                      3: paths                 Technical Information                 paths
                      4: 
                      5: 
                      6: 
                      7: 
                      8: Routing data base for mail
                      9: 
                     10: /uussrr/lliibb/mmaaiill/ppaatthhss
                     11: 
                     12: File /uussrr/lliibb/mmaaiill/ppaatthhss holds the data base used by the COHERENT
                     13: mail system  to route mail.  Each  line gives routing information
                     14: to a host, and has the following format:
                     15: 
                     16: 
                     17:         host    route   [cost]
                     18: 
                     19: 
                     20: _h_o_s_t  names a  UUCP  host.  Because  ssmmaaiill  uses a  binary-search
                     21: algorithm when searching the data base for a given host name, the
                     22: lines in  ppaatthhss must  be sorted  into ascending order.   (See the
                     23: Lexicon entry for  bbsseeaarrcchh for details on binary searches.) ssmmaaiill
                     24: ignores case  when it searches ppaatthhss, so  you should convert each
                     25: host name to lower case before you sort ppaatthhss.
                     26: 
                     27: The _r_o_u_t_e  field details the route by which  mail can travel from
                     28: your system to _h_o_s_t.  Note that it includes a pprriinnttff-style format
                     29: string.
                     30: 
                     31: The optional  field _c_o_s_t is  used by the COHERENT  mail system to
                     32: decide whether  to queue outbound UUCP mail,  or to invoke uuuucciiccoo
                     33: to  deliver the  mail immediately.   If the _c_o_s_t  is at  or below
                     34: ssmmaaiill's  ``queueing  threshold'',  then  ssmmaaiill  will  attempt  to
                     35: deliver it immediately.   This speeds mail delivery between hosts
                     36: that enjoy  an inexpensive UUCP link, such  as a hard-wired line,
                     37: and batches mail that must  be sent over expensive media, such as
                     38: long-distance  telephone.  If  the  _c_o_s_t field  is absent,  ssmmaaiill
                     39: gives  this  host  a  cost  value  above  that  of  its  queueing
                     40: threshold.
                     41: 
                     42: ***** Example *****
                     43: 
                     44: The following  gives a  sample ppaatthhss  file for a  COHERENT system
                     45: that its owner has named lleeppaannttoo.
                     46: 
                     47: 
                     48: friend  friend!%s       300
                     49: hubsys  hubsys!%s       95
                     50: lepanto %s      0
                     51: lepanto.ampr.org        %s      0
                     52: smart-host      hubsys!%s       95
                     53: widget  hubsys!widget!%s        95
                     54: 
                     55: 
                     56: As  this file  shows,  lleeppaannttoo is  linked to  systems hhuubbssyyss  and
                     57: ffrriieenndd.  The cost  of 95  associated with hhuubbssyyss  is low,  and is
                     58: appropriate to a low-cost link, such as a hard-wired link; On the
                     59: other hand, the cost of 300 associated with ffrriieenndd is high, which
                     60: indicates that the connection with ffrriieenndd is high-cost, such as a
                     61: long-distance telephone  connection.  If cost is  100 or greater,
                     62: 
                     63: 
                     64: COHERENT Lexicon                                           Page 1
                     65: 
                     66: 
                     67: 
                     68: 
                     69: paths                 Technical Information                 paths
                     70: 
                     71: 
                     72: 
                     73: mail will be queued for latter delivery.  A cost below 100 causes
                     74: ssmmaaiill to attempt immediate delivery.
                     75: 
                     76: In this  example, machine lleeppaannttoo  is registered in  the aammpprr.oorrgg
                     77: Amateur  Packet Radio  domain.   Note that  machine name  lleeppaannttoo
                     78: appears in  both conventional and  domain forms in  order to help
                     79: resolve addressing.
                     80: 
                     81: In order to avoid having to  maintain a huge data base, the owner
                     82: of  lleeppaannttoo   uses  hhuubbssyyss  as  a   _s_m_a_r_t  _h_o_s_t.  The  ssmmaarrtt-hhoosstt
                     83: designation in  the ppaatthhss data base signals  ssmmaaiill to forward any
                     84: mail that it doesn't know how to deliver onto site hhuubbssyyss.
                     85: 
                     86: Finally, lleeppaannttoo can use hhuubbssyyss  to pass mail on to wwiiddggeett. Thus,
                     87: when rrmmaaiill  receives mail for system wwiiddggeett,  it will transmit it
                     88: to hhuubbssyyss for  forwarding.  Note that hhuubbssyyss's administrator must
                     89: have given lleeppaannttoo permission to use  it as a mail relay, or this
                     90: would not work.
                     91: 
                     92: ***** See Also *****
                     93: 
                     94: mmaaiill, tteecchhnniiccaall iinnffoorrmmaattiioonn
                     95: 
                     96: 
                     97: 
                     98: 
                     99: 
                    100: 
                    101: 
                    102: 
                    103: 
                    104: 
                    105: 
                    106: 
                    107: 
                    108: 
                    109: 
                    110: 
                    111: 
                    112: 
                    113: 
                    114: 
                    115: 
                    116: 
                    117: 
                    118: 
                    119: 
                    120: 
                    121: 
                    122: 
                    123: 
                    124: 
                    125: 
                    126: 
                    127: 
                    128: 
                    129: 
                    130: COHERENT Lexicon                                           Page 2
                    131: 
                    132: 

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