Used in programs to call the ypbind daemon directly for processes that use backup strategies when Network Information Services (NIS) is not available.
#include <rpcsvc/ypclnt.h> #include <rpcsvc/yp_prot.h>
yp_bind (indomain) char *indomain;
In order to use NIS, the client process must be bound to an NIS server that serves the appropriate domain. That is, the client must be associated with a specific NIS server that services the client's requests for NIS information. The NIS lookup processes automatically use the ypbind daemon to bind the client, but the yp_bind subroutine can be used in programs to call the daemon directly for processes that use backup strategies (for example, a local file) when NIS is not available.
Each NIS binding allocates, or uses up, one client process socket descriptor, and each bound domain uses one socket descriptor. Multiple requests to the same domain use the same descriptor.
Note: If a Remote Procedure Call (RPC) failure status returns from the use of the yp_bind subroutine, the domain is unbound automatically. When this occurs, the NIS client tries to complete the operation if the ypbind daemon is running and either of the following is true:
| indomain | Points to the name of the domain for which to attempt the bind. |
The NIS client returns control to the user with either an error or a success code if any of the following occurs:
This subroutine is part of Base Operating System (BOS) Runtime.
The ypbind daemon, ypserv daemon.
Network Information Service (NIS) Overview for System Management in AIX Version 4.3 System Management Guide: Communications and Networks.
List of NIS Programming References and Remote Procedure Call (RPC) Overview for Programming in AIX Version 4.3 Communications Programming Concepts.