02.07.2013 Views

A/UX® System Administrator's Reference Sections 1M, 7, and 8

A/UX® System Administrator's Reference Sections 1M, 7, and 8

A/UX® System Administrator's Reference Sections 1M, 7, and 8

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

ypserv(lM) ypserv(lM)<br />

Two other functions supply information about the map, rather than<br />

map entries: Get order number, <strong>and</strong> Get master name.<br />

In fact, both order number-<strong>and</strong> master name eXist in the -map as<br />

key-value pairs, but the server will not return either through the<br />

normal lookup functions. (If you examine the map with<br />

makedbm(lM), however, they will be visible.)<br />

Other functions are used within the yP subsystem itself, <strong>and</strong> are<br />

not of general interest to yP clients. They include<br />

Do-you_serve_this_domain?, Transfer_map, <strong>and</strong><br />

Reinitialize internal state.<br />

- -<br />

The function of ypbind is to remember information that allows<br />

client processes on a single node communicate with some ypserv<br />

process. ypbind must run on every machine which has<br />

yP client processes; ypserv mayor may not be running on the<br />

same node, but must be running somewhere on the network.<br />

The information ypbind remembers is called a binding: the association<br />

of a domain name with the internet address of the yP<br />

server, <strong>and</strong> the port on that host at which the ypserv process is<br />

listening for service requests. The process of binding is driven by<br />

client requests. As a request for an unbound domain is received,<br />

the ypbind process broadcasts on the net. trying to find a ypserv<br />

process that serves maps within that domain. Since the<br />

binding is established by broadcasting, there must be at least one<br />

ypserv process on every net Once a domain is bound by a particular<br />

ypbind, that same binding is given to every client process<br />

on the node. The ypbind process on the local or on a remote<br />

node may be queried for the binding of a particular domain by using<br />

the ypwhich(l) comm<strong>and</strong>.<br />

Bindings are verified before they are given out to a client process.<br />

If ypbind is unable to speak to the ypserv process to which it's<br />

bound, it marks the domain as unbound, tells the client process<br />

that the domain is unbound. <strong>and</strong> tries to bind the domain once<br />

again. Requests received for an unbound domain will fail immediately.<br />

In general, a bound domain is marked as unbound<br />

when the node running ypserv crashes or gets overloaded. In<br />

such a case, ypbind will to bind any yP server (typically one<br />

that is less-heavily loaded) available on the net<br />

ypbind also accepts requests to set its binding for a particular<br />

domain. The request is usually generated by the yP subsystem itself.<br />

ypset(<strong>1M</strong>) is a comm<strong>and</strong> to access the Set_domain fa-<br />

February. 1990<br />

Revision C<br />

2

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!