The operating system supports name resolution from five different maps:
With the Dynamic Load Application Programming Interface (API), you can load your own modules to provide routines that supplement the maps provided by the operating system. The Dynamic Load API enables you to create dynamically loading APIs in any of the following map classes:
You can build your own user modules containing APIs for any or all of the map classes. The following sections define an API's function names and prototypes for each of the five classes. To instantiate each map accesssor, the operating system requires that a user-provided module use the specified function names and function prototypes for each map class.
For information about configuring a dynamically loading API, see Configuring a Dynamic API.
The following is the required prototype for a user-defined services map class:
void *sv_pvtinit(); void sv_close(void *private); struct servent * sv_byname(void *private, const char *name, const char *proto); struct servent * sv_byport(void *private, int port, const char *proto); struct servent * sv_next(void *private); void sv_rewind(void *private); void sv_minimize(void *private);
Function sv_pvtinit must exist. It is not required to return anything more than NULL. For example, the function can return NULL if the calling routine does not need private data.
Functions other than sv_pvtinit are optional for this class. The module can provide none or only part of the optional functions in its definition.
The following is the required prototype for a user-defined protocols map class:
void * pr_pvtinit(); void pr_close(void *private); struct protoent * pr_byname(void *private, const char *name); struct protoent * pr_bynumber(void *private, int num); struct protoent * pr_next(void *private); void pr_rewind(void *private); void pr_minimize(void *private);
Function pr_pvtinit must exist. It is not required to return anything more than NULL. For example, the function can return NULL if the calling routine does not need private data.
Functions other than pr_pvtinit are optional for this class. The module can provide none or only part of the optional functions in its definition.
The following is the required prototype for a user-defined hosts map class:
void * ho_pvtinit(); void ho_close(void *private); struct hostent * ho_byname(void *private, const char *name); struct hostent * ho_byname2(void *private, const char *name, int af); struct hostent * ho_byaddr(void *private, const void *addr, size_t len, int af); struct hostent * ho_next(void *private); void ho_rewind(void *private); void ho_minimize(void *private);
Function ho_pvtinit must exist. It is not required to return anything more than NULL. For example, the function can return NULL if the calling routine does not need private data.
Functions other than ho_pvtinit are optional for this class. The module can provide none or only part of the optional functions in its definition.
The following is the required prototype for a user-defined networks map class:
void * nw_pvtinit(); void nw_close(void *private); struct nwent * nw_byname(void *private, const char *name, int addrtype); struct nwent * nw_byaddr(void *private, void *net, int length, int addrtype); struct nwent * nw_next(void *private); void nw_rewind(void *private); void nw_minimize(void *private);
Function nw_pvtinit must exist. It is not required to return anything more than NULL. For example, the function can return NULL if the calling routine does not need private data.
Functions other than nw_pvtinit are optional for this class. The module can provide none or only part of the optional functions in its definition.
The operating system provides a data structure required to implement the networks map class, which uses this structure to communicate with the operating system.
struct nwent {
char *name; /* official name of net */
char **n_aliases; /* alias list */
int n_addrtype; /* net address type */
void *n_addr; /* network address */
int n_length; /* address length, in bits */
};
The following is the required prototype for a user-defined netgroup map class:
void * ng_pvtinit(); void ng_rewind(void *private, const char *group); void ng_close(void *private); int ng_next(void *private, char **host, char **user, char **domain); int ng_test(void *private, const char *name, const char *host, const char *user, const char *domain); void ng_minimize(void *private);
Function ng_pvtinit must exist. It is not required to return anything more than NULL. For example, the function can return NULL if the calling routine does not need private data.
Functions other than ng_pvtinit are optional for this class. The module can provide none or only part of the optional functions in its definition.
You must name your user-defined module according to a pre-established convention. Also, you must configure it into the operating system before it will work. The following sections explain API module naming and configuration.
The names of modules containing user-defined APIs follow this general form:
NameAddressfamily
Where:
There are three ways to specify user-provided, dynamically loading resolver routines. You can use the NSORDER environment variable, the /etc/netsvc.conf configuration file, or the /etc/irs.conf configuration file. With any of these sources, you are not restricted in the number of options that you can enter, nor in the sequence in which they are entered. You are, however, restricted to a maximum number of 16 user modules that a user can specify from any of these sources.
The NSORDER environemnt variable is given the highest priority. Next is the /etc/netsvc.conf configuration file, then the /etc/irs.conf configuration file. A user option specified in a higher priority source (for example, NSORDER) causes any user options specified in the lower priority sources to be ignored.
export NSORDER=local, bind, bob, nis, david4, jason6
In this example, the operating system invokes the listed name resolution modules, left to right, until the name is resolved. The modules named local, bind, and nis are reserved by the operating system, but bob, david4, and jason6 are user-provided modules.
hosts=nis, jason4, david, local, bob6, bind
hosts dns continue hosts jason6 merge hosts david4
To create and install a module containing a dynamically loading API, use the following procedure. The operating system provides a sample Makefile, sample export file, and sample user module file, which are located in the /usr/samples/tcpip/dynload directory.