HP-UX Reference (11i v2 03/08) - 3 Library Functions N-Z (vol 7)

n
nis_tables(3N) nis_tables(3N)
NIS_NOMEMORY Generally a fatal result. It means that the service ran out of heap space.
NIS_NOSUCHNAME
This hard error indicates that the named directory of the table object does not exist.
This occurs when the server that should be the parent of the server that serves the
table, does not know about the directory in which the table resides.
NIS_NOSUCHTABLE
The named table does not exist.
NIS_NOT_ME A request was made to a server that does not serve the given name. Normally this
will not occur, however if you are not using the built in location mechanism for
servers, you may see this if your mechanism is broken.
NIS_NOTFOUND No entries in the table matched the search criteria. If the search criteria was null
(return all entries) then this result means that the table is empty and may safely be
removed by calling the
nis_remove().
If the
FOLLOW_PATH flag was set, this error indicates that none of the tables in the
path contain entries that match the search criteria.
NIS_NOTMASTER
A change request was made to a server that serves the name, but it is not the mas-
ter server. This can occur when a directory object changes and it specifies a new
master server. Clients that have cached copies of the directory object in the
/var/nis/NIS_SHARED_DIRCACHE
file will need to have their cache managers
restarted (use
nis_cachemgr -i) to flush this cache.
NIS_NOTSAMEOBJ An attempt to remove an object from the namespace was aborted because the object
that would have been removed was not the same object that was passed in the
request.
NIS_NOTSEARCHABLE
The table name resolved to a NIS+ object that was not searchable.
NIS_PARTIAL This result is similar to NIS_NOTFOUND except that it means the request suc-
ceeded but resolved to zero entries. When this occurs, the server returns a copy of
the table object instead of an entry so that the client may then process the path or
implement some other local policy.
NIS_RPCERROR This fatal error indicates the RPC subsystem failed in some way. Generally there
will be a syslog(3C) message indicating why the RPC request failed.
NIS_S_NOTFOUND The named entry does not exist in the table, however not all tables in the path could
be searched, so the entry may exist in one of those tables.
NIS_S_SUCCESS Even though the request was successful, a table in the search path was not able to
be searched, so the result may not be the same as the one you would have received
if that table had been accessible.
NIS_SUCCESS The request was successful.
NIS_SYSTEMERROR
Some form of generic system error occurred while attempting the request. Check
the syslog(3C) record for error messages from the server.
NIS_TOOMANYATTRS
The search criteria passed to the server had more attributes than the table had
searchable columns.
NIS_TRYAGAIN The server connected to was too busy to handle your request. add_entry(),
remove_entry(), and modify_entry() return this error when the master
server is currently updating its internal state. It can be returned to nis_list()
when the function specifies a callback and the server does not have the resources to
handle callbacks.
NIS_TYPEMISMATCH
An attempt was made to add or modify an entry in a table, and the entry passed
was of a different type than the table.
EXTERNAL INFLUENCES
HP-UX 11i Version 2: August 2003 − 5 − Hewlett-Packard Company Section 3−−667