rfmaster(4) CLIX rfmaster(4)
NAME
rfmaster - Remote File Sharing name server master file
DESCRIPTION
The /usr/nserve/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 (RFS) domains. The rfmaster file contains
a series of records, each terminated 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:
p The p type defines the primary domain_name server. For this type,
name is the domain_name and data is the full hostname of the machine
that is the primary name server. The full hostname 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. The name and
data arguments 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. The name argument
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 to be interpreted as hexadecimal
notation. (See the documentation for the particular network 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.
The rfmaster file is created and maintained on the primary domain_name
server. When a machine other than the primary tries to start RFS, this
file is read to determine the address of the primary. If rfmaster is
missing, the -p flag of rfstart must be used to identify the primary.
After that, a copy of the primary's rfmaster file is automatically placed
on the machine.
The domain(s) not served by the primary can also be listed in the rfmaster
file. By adding primary, secondary, and address information for other
domain(s) on a network, machines served by the primary will be able to
2/94 - Intergraph Corporation 1
rfmaster(4) CLIX rfmaster(4)
share resources with machines in other domain(s).
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.
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
NOTE: If a line in the rfmaster file begins with a # character, the
entire line will be treated as a comment.
FILES
/usr/nserve/rfmaster
RELATED INFORMATION
Commands: rfstart(8)
2 Intergraph Corporation - 2/94