Lines Matching refs:not
152 @code{db}, @code{dns}, @code{nis}, and @code{nisplus}. This does not
166 at the end is the currently used version of the interface which will not
167 change frequently. Normally the user should not have to be cognizant of
205 The lookup process works ok but the needed value was not found. The
211 file is not available, or, for DNS, the server is not available or does
212 not allow queries. The default action is @code{continue}.
299 complete; i.e., if an entry is not available in the NIS+ tables it is
300 not available anywhere else. This is what is expressed by this action
301 item: it is useless to examine further services since they will not give
306 The situation would be different if the NIS+ service is not available
308 lookup function is not @code{notfound} but instead @code{unavail}. And
311 system administrator need not pay special care for the time the system
312 is not completely ready to work (while booting or shutdown or
319 Finally a few more hints. The NSS implementation is not completely
320 helpless if @file{/etc/nsswitch.conf} does not exist. For
400 is used. You see, what is explained above in not the whole truth. In
412 access them. If a function is not available it is simply treated as if
422 libraries themselves. This is @emph{not} true at the moment, though.
423 However, the organization of the name space in the modules does not make it
427 not starting with @file{lib} but don't tell this to anybody.}
495 resources or a service is currently not available.
498 @code{ERANGE} @tab The provided buffer is not large enough.
505 @code{ENOENT} @tab The requested entry is not available.
511 be enabled at a later time. This is not the same as the service
522 not share the same thread-local variable @code{errno}, which is the
529 linked programs, the thread-local variable @code{h_errno} is not shared
562 value is not @code{NSS_STATUS_SUCCESS}, @code{*@var{errnop}} needs to be
570 name lookup functions. If the return value is not
590 independent from adding another service because a service need not
606 The sources for a new service need not (and should not) be part of @theglibc{}
612 For now the version is 2 (the interface in version 1 was not adequate)
638 But this is not always possible since some programs (those which run
639 under IDs which do not belong to the user) ignore this variable.
644 careful: this should only be done if it is clear the module does not
652 the NSS module. In fact there is not much more we can say since the
685 also means the functions are not really reentrant. They are reentrant
686 only in that simultaneous calls to this function will not try to
694 for storing some additional data for the result. It is @emph{not}
696 function. Therefore one must not misuse this buffer to save some state
702 working in statically linked programs. The stored value must not be
713 returned. When the service was not formerly initialized by a call to
727 @var{buffer} of length @var{buflen}. There must not be any references