• Keine Ergebnisse gefunden

IDstalling a Uucp System

Im Dokument The Chapter (Seite 91-94)

9.S Uuxqt - Uucp Commagd Execution

9.9 IDstalling a Uucp System

The uucp system provided with the XENIX Software Development System is already configured for cperation on yourcomputa'. ToinstaU the system. you must edit a few files to provide information about your local site. The following sections provide

an

overview of the files 10 beeditedaodthe information required.

During execution of the uucp programs. the uucp system uses files from the following three directories:

spool

(/wrllibluucp) This is the dRctory used for the executabJe system programs and the systemfiJc ..

(/wrlspoollUIICp) 1bia it the spool directory used during UllCp execution.

(/usr/ spoolhalcpl.XQTDIR)1bisdin:ctory is used duringexccutionof execute file ..

The names given in parenJheses above are the default values for the directories. The names lib. program. xqtdir. and spool wiU be used in the following text to represent the appropriate directory names.

9.9.1 Modl'yi . . abe leldSYSlemid File

You must choose a unique site name for each computer to be directly connected 10 a uucp line and add the site name tothelelclsysrmrid file oflhecorrespondingcomputer by using aXENlX text editor. Theletcl SYSlemidfilc canadually cOlllaintwo names: the uucp site name. which must appear on the first line of the file. and a Micnet machine name. which must appear 00 the DeXlIine. However. you may decide tobave both the uucp site name andMicnet machine name 10 be the same. in wbichcase. only one name is required. For a dcacripdon of the iJe.1Ce systemid(M) in the XEN1X Reference MaIfIlQJ.

9-10

9.9.2 Creating the Requln:cl Fila

There are four files which are required for execution, aU of which ~hruld reside in the program directory. To prepare tbeuucp system for eXeaJtion, you must add your own site specific information to these files by editing the files with a XENIX text editor. The field separator for all filesisa space unlessothcrwise specified.

L-devka

This file contains entries for the call-unit devices and hardwired connections which are to be used by uucp. The spc:ciaJdevice files are assumed to be in the ldev directoIy . The format forcach entry is

line caJI-1UIiI speed

where line is the device for the line (e.g. culO). call-unit is the automatic c:aJ1 unit associated with Ii tie (e.g. cuaO). Hardwired lincsha YC a number' '0" in this field, and

&peed is the line speed.

The line

a1l0

cuaO

300

defines a system which has device '"cuIO" wired to a caD -unit "cuaO" for use at 300 baud.

L-cIlakodes

This file contains entries with 1ocationabbrcviations used in the L . .sy.s fiJc (e.g. PY. mho boston). The entry fmnal is

abb dial-seq

where abb is the abbreviation. and dUJI-uq is the dial sequeoce to caU that location.

The line py

J6S-causestheerlrypy7777tobeexpandedtoJ6S-7777.

USERFILE

This file contains useraccessibil~y informatim. It specifies

The files that can be accessed by a oormal user of the local machine The files that can be accessed from a remote computer

The login name used by a particular remote computer

Whether a remote computer should be caUed back in ordel" to confirm its identity

Each line inthe file has the foUowing format Iogin.sys

r

c

1

pathname

r

palluwne

1 ...

where login is the login name for a user or the remote computer. sys is the system name for a remote computer. c is the optional calJ- back required flag. and palhnome is a pathname prefix that is acceptable for

use, .

9-11

It is assumed that the login name used by a remote computer 10 call Into a local computer IS not the same: as the login name of a normal user of that local machine.

Howe ver. several remote computers may employ the same login name.

Each computer is given a unique system name which is transmitted at the SlaJ'l of each call. This name identifies the calling machine to tbe called machine.

When the program is obeying a ccmmand stcn:d on the local machine. MASTER mode. the pathnames allowed are those given f~the first line inthe USERFILE that has a login name that matches the login name of the user whoeDlered the command. If DO

such line is found. the first line wilh a nuliloginname is used.

When the program is responding to a command from arem~emachine, SLA VEmode.

the pathnames allowed are those given for the first line in the file that has the system name that matches the system name of the I'CIIlOU machmc. lfnosuch line is found. the first one with a null system name is used.

When a mncte ccmputc:r logs in. the login name that it uses must appear in the USERFILE. There may be several lines with the same login name but one of them must either have the name of the remotesystemormustcontaina null system name.

If a line is found that bat the appropriale login and mnOle system naJDea and also contains a "c", the remote machine iscaUed back before any transactions take place.

The line u.m lug/xyz

allows machine "m" to login with name "u" and request the transfer offiJcs whose names start with "'/Ug/xyz" .••

Theline

dan, lug/dan

allows the ordinary user "'dan" to issue coounands for files whose name starts wi1b

"'usr/dan".

The lines

u,m lug/xyz lug/spool u, lug/spool

allow any mnote machine to login with name "u", but ifils system name boot "m".

it can only ask totransfer files whose names start wilh "/usr/spooI··.

The lines root, I

• lug

allow any user to transfer files beginning with ulu." but the UICI' with login "root"

can transfer any file.

Lays

Each entry in this file represents one system which can be called by the local uucp program •. The fields are described below.

system namcTbe nameofthereDlOtC syataa.

9-12

device speed phone

login

This is a string which indicates the days-of-week and times-of-day when the system should be called (e.g. MoTuThOSOO-1730). The day portionmay be a list containing some of

Su Mo Tu We Th Fr Sa

01" it may be "Wk." for any week-day or· 'Any" for any day. The time should bt' a range of times (e.g. 0800- J230). If no time portion is specified. any time of day is assumed to be ok for the call.

This is either" ACU" or the hardwired device to be used for the call. For the hardwired case. the last part of the special file name is used (c. g. ttyO).

This isthe line spcedforthe caD (e.g. 3(0).

The phone number is made up of anQltional alphabetic abbreviation and a numeric part. The abbreviation is one which appears in the L-dWcodes file (e.g. mhS900. boston99S-9980). For the hardwired devices. this fieldcODlains the same string as used ford1edevice field.

The login information is given as a series of field. and subfields in the format

expect send

r

expect send

1 ...

where expect is the string expcct.ed to be read and send is the string to ~ ICD1 when the expected string is received. The expect field may be made up of sub fields of the form

expecd -send-expect]

1 ...

where send is sent if the prior expect is DOl successfuUy read and expect]

is the next expected string.

There are two special names available to be sera during the login sequence. The string "EaT" sends an Ear character and the string .. BREAK" tries to send a BREAK character. (The BREAK character is simulated using line speed changes and mall c:haraClen and may not wort on aD devices andlor systc:ms. )

A typical erary inthe L. sysfiie is

.ya Any ACU 300 mh76S4login uucp ssword: word

The expect algorithm looks at lhe last pan of lhe string as illuSlraled in the password field.

Im Dokument The Chapter (Seite 91-94)