The type field, which defines the meaning of the name and data fields, has three possible values:
There can be only one primary name server per domain.
There are at least two lines in the rfmaster file per domain name server: one p line and one a line. Together, they 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. If this file is missing, the -p option 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.
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.
An example of an rfmaster file is shown below. The network addresses given in the example are IP addresses; for more information on their format and how to generate them, see hostrfs.8
sunrfs p sunrfs.estale sunrfs s sunrfs.ivy sunrfs.estale a \x000214508190320d sunrfs.ivy a \x0002145081903246
Note: If a line in the
file begins with a
(pound sign) character,
the entire line will be treated as a comment.
[a manual with the abbreviation ADMIN]
Created by unroff & hp-tools. © by Hans-Peter Bischof. All Rights Reserved (1997).
Last modified 21/April/97