NAME

rfmaster - Remote File Sharing name server master file

DESCRIPTION

Each transport provider used by Remote File Sharing  has  an
associated  rfmaster  file  that  identifies the primary and
secondary name servers for  that  transport  provider.   The
rfmaster  file ASCII contains a series of records, each ter-
minated by a newline; 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.  These values can
appear in upper case or lower case:

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 determines 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 preceded by a \x or \X to be interpreted as hexadecimal notation. (See the documentation for the particular network you are using to determine the network addresses you need.) If a line in the rfmaster file begins with a # character, the entire line is treated as a comment. 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. 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. If the associated rfmaster for a transport provider is missing, use rfstart -p to identify the primary for that transport provider. After that, a copy of the primary's rfmaster file is automatically placed on the machine. Domains not served by the primary can also be listed in the rfmaster file. By adding primary, secondary, and address 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. There is an rfmaster file for each transport provider.

EXAMPLES

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

FILES

/etc/rfs/<transport>/rfmaster

SEE ALSO

rfstart(1M) in the System Administrator's Reference Manual.