ypupdate.3c (2010 09)

y
ypupdate(3C) ypupdate(3C)
NAME
ypupdate: yp_update() - changes NIS information
SYNOPSIS
cc [flag]... file...
-lnsl [library ]...
#include <rpcsvc/ypclnt.h>
yp_update (domain, map, ypop, key, keylen, data, datalen)
char *domain;
char *map;
unsigned ypop;
char *key;
int keylen;
char *data;
int datalen;
Remarks
The Network Information Service (NIS) was formerly known as Yellow Pages (YP). Although the name
has changed, the functionality of the service remains the same.
DESCRIPTION
The
yp_update() routine is used to make changes to the Network Information Service (NIS) database.
The syntax is the same as that of yp_match() (see ypclnt (3C)) except for the extra parameter
ypop
which can be one of these four values:
YPOP_CHANGE The data associated with the key will be changed to the new value. If the key
is not found in the database, then yp_update() returns [YPERR_KEY].
YPOP_INSERT The key-value pair will be inserted into the database. The error
[YPERR_KEY] is returned if the key already exists in the database.
YPOP_STORE The key-value pair will be stored into the database without concern for
whether it already exists or not.
YPOP_DELETE The key-value pair will be deleted from the database.
This routine depends upon secure RPC and will not work unless the network is running secure RPC.
MULTITHREAD USAGE
Thread Safe: No
Cancel Safe: No
Fork Safe: No
Async-cancel Safe: No
Async-signal Safe: No
These functions cannot be called safely in a multithreaded environment. They may be cancellation points
in that they call functions that are cancel points.
In a multithreaded environment, these functions are not safe to be called by a child process after
fork()
and before exec(). These functions should not be called by a multithreaded application that support
asynchronous cancellation or asynchronous signals.
AUTHOR
The
yp_update() routine was developed by Sun Microsystems, Inc.
SEE ALSO
ypclnt(3C).
HP-UX 11i Version 3: September 2010 1 Hewlett-Packard Company 1

Summary of content (2 pages)