YPBIND(8) | System Manager's Manual | YPBIND(8) |
ypbind
—
ypbind |
[-broadcast ] [-insecure ]
[-ypset ] [-ypsetme ] |
ypbind
finds the server for a particular NIS domain and
stores information about it in a “binding file”. This binding
information includes the IP address of the server associated with that
particular domain and which port the server is using. This information is
stored in the directory /var/yp/binding in a file
named with the convention <domain>.version,
where ⟨domain⟩ is the relevant domain. The NIS system only
supplies information on version 2.
If ypbind
is started without the
-broadcast
option, ypbind
steps through the list of NIS servers specified in
/var/yp/binding/<domain>.ypservers and
contacts each in turn attempting to bind to that server. It is strongly
recommended that these hosts are in the local hosts file, and that hosts are
looked up in local files before the NIS hosts map.
If ypbind
is started with the
-broadcast
option, or if
/var/yp/binding/<domain>.ypservers does not
exist, ypbind
broadcasts to find a process willing
to serve maps for the client's domain.
Once a binding is established, ypbind
maintains this binding by periodically communicating with the server to
which it is bound. If the binding is somehow lost, e.g by server reboot,
ypbind
marks the domain as unbound and attempts to
re-establish the binding. If a binding cannot be re-established within 60
seconds, ypbind
backs off exponentially to trying
only once per hour.
The options are as follows:
-broadcast
-insecure
-ypset
-ypsetme
The -broadcast
,
-ypset
, and -ypsetme
options
are inherently insecure and should be avoided.
ypbind
responds to the following signals:
HUP
ypbind
to immediately retry any unbound
domains that are currently in exponential backoff. Use this to resume
immediately after a long network outage is resolved.LOG_DAEMON
facility.
ypbind
was originally implemented by
Theo de Raadt. The ypservers support was implemented
by Luke Mewburn.
June 14, 2014 | NetBSD 9.4 |