Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ rfmaster(4) — sysv — mips UMIPS RISC/os 4.52

Media Vault

Software Library

Restoration Projects

Artifacts Sought



RFMASTER(4-SysV)    RISC/os Reference Manual     RFMASTER(4-SysV)



NAME
     rfmaster - Remote File Sharing name server master file

DESCRIPTION
     The rfmaster file is an ASCII file that identifies the hosts
     that are responsible for providing primary and secondary
     domain name service for Remote File Sharing domains.  This
     file contains a series of records, each terminated by a new-
     line; a record may be extended over more than one line by
     escaping the newline character with a backslash ("\").  The
     fields in each record are separated by one or more tabs or
     spaces.  Each record has three fields:

          name type data

     The type field, which defines the meaning of the name and
     data fields, has three possible values:

     p     The p type defines the primary domain name server.
           For this type, name is the domain name and data is the
           full host name of the machine that is the primary name
           server.  The full host name is specified as
           domain.nodename.  There can be only one primary name
           server per domain.

     s     The s type defines a secondary name server for a
           domain.  Name and data are the same as for the p type.
           The order of the s entries in the rfmaster file deter-
           mines the order in which secondary name servers take
           over when the current domain name server fails.

     a     The a type defines a network address for a machine.
           Name is the full domain name for the machine and data
           is the network address of the machine. The network
           address can be in plain ASCII text or it can be pre-
           ceded by a \x to be interpreted as hexadecimal nota-
           tion.  (See the documentation for the particular net-
           work you are using to determine the network addresses
           you need.)

     There are at least two lines in the rfmaster file per domain
     name server:  one p and one a line, to define the primary
     and its network address.  There should also be at least one
     secondary name server in each domain.

     This file is created and maintained on the primary domain
     name server.  When a machine other than the primary tries to
     start Remote File Sharing, this file is read to determine
     the address of the primary.

     Domains not served by the primary can also be listed in the
     rfmaster file.  By adding primary, secondary, and address



                         Printed 1/15/91                   Page 1





RFMASTER(4-SysV)    RISC/os Reference Manual     RFMASTER(4-SysV)



     information for other domains on a network, machines served
     by the primary will be able to share resources with machines
     in other domains.

     A primary name server may be a primary for more than one
     domain.  However, the secondaries must then also be the same
     for each domain served by the primary.

Example
     An example of an rfmaster file is shown below.  (The network
     address examples, comp1.serve and comp2.serve, are STARLAN
     network addresses.)

          ccs       p    ccs.comp1
          ccs       s    ccs.comp2
          ccs.comp2 a    comp2.serve
          ccs.comp1 a    comp1.serve

     NOTE:  If a line in the rfmaster file begins with a # char-
     acter, the entire line will be treated as a comment.

FILES
     /usr/nserve/rfmaster
































 Page 2                  Printed 1/15/91



Typewritten Software • bear@typewritten.org • Edmonds, WA 98026