ypserv(8yp) ypserv(8yp)
Name
ypserv, ypbind - yellow pages (YP) server and binder processes
Syntax
/usr/etc/ypserv
/etc/ypbind [ -S domainname, servername1,servername2... ][ -X ]
Description
The yellow pages (YP) service provides a network lookup service consisting of databases and processes. The databases are files stored in
the directory. These files are described in The processes are the YP database lookup server, and the YP binder. The software interface to
the YP service is described in Administrative tools are described in and Tools to see the contents of YP maps are described in and Database
generation and maintenance tools are described in and
Both and are daemon processes activated at system startup time from The command runs only on a YP server machine with a complete YP data-
base. The command runs on all machines using YP services, both YP servers and clients.
The daemon's primary function is to look up information in its local database of YP maps. The operations performed by are defined for the
programmer in the header file
Communication with is by means of RPC calls. Lookup functions are described in and are supplied as C-callable functions in
There are four lookup functions, all of which are performed on a specified map within a YP domain: and The operation takes a key, and
returns the associated value. The operation returns the first key-value pair from the map, and the operation returns the remaining key-
value pairs. The operation ships the entire map to the requester.
Two other functions supply information about the map, rather than the map entries: and Both the order number and the master name exist in
the map as key-value pairs, but the server will not return either through the usual lookup functions. If the map is examined with however,
they are visible.
Other functions are used within the YP subsystem itself, and are not of general interest to YP clients. They include the the and the func-
tions.
The purpose of the function is to remember information that lets client processes on a single node communicate with a process. The func-
tion must run on every machine that has YP client service requirements. The function must be started through an entry in the file.
The information remembers is called a binding, the association of a domain name with the internet address of the YP server, and the port on
that host at which the process is listening for service requests. The process of binding is driven by client requests. As a request for
an unbound domain comes in, the process broadcasts on the net trying to find a process that serves maps within that domain. Since the
binding is established by broadcasting, there must be at least one process on every net. Once a domain is bound by a particular that same
binding is given to every client process on the node. The process on the local node or a remote node may be queried for the binding of a
particular domain by using the command.
Bindings are verified before they are given out to a client process. If is unable to speak to the process it is bound to, it marks the
domain as unbound, tells the client process that the domain is unbound, and tries to bind the domain once again. Requests received for an
unbound domain will fail immediately. In general, a bound domain is marked as unbound when the node running crashes or gets overloaded.
When the node gets overloaded, will try to bind any YP server (typically one that is less-heavily loaded) available on the net.
The process also accepts requests to set its binding for a particular domain. The request is usually generated by the YP subsystem itself.
Options
-S Allows the system administrator to lock to a particular domain and set of servers. Up to four servers can be specified as fol-
lows:
/etc/ypbind -S domainname,server1,server2,server3,server4
Note that there can not be any spaces around the commas in the command line. The option ensures that this system only binds to
the specified domain and to one of the specified servers. The servers used with the option must have entries in the local file.
-X The initial bind ( option forces to bind to a YP server at the time that the command is executed, instead of waiting until YP is
used. If no server is available at this time, will try for several minutes and then exit. Normally, is executed at boot time.
The option enables a system that does not exclusively depend on YP to boot and to allow logins when there are no YP servers
available. Without this option, such a system hangs.
Files
If the file exists when starts up, log information is written to when error conditions occur.
See Also
ypcat(1yp), ypmatch(1yp), ypwhich(1yp), ypclnt(3yp), ypfiles(5yp), yppush(8yp), ypxfr(8yp)
Guide to the Yellow Pages Service
ypserv(8yp)