OpenE2K
/
glibc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Document best practice for disconnected NSS modules. 

NSS modules which can run in disconnected modes should
return NSS_STATUS_NOTFOUND and SUCCESS in order to follow
best practice for such modules and ensure user applications
can have these modules configured without causing problems
if the data sources are not connected.
This commit is contained in:
Carlos O'Donell 2015-12-10 00:48:15 -05:00
parent 23256f5ed8
commit d4e301c5c6
2 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ChangeLog
View File

@ -1,3 +1,8 @@
2015-12-10 Carlos O'Donell <carlos@redhat.com>
* manual/nss.texi (NSS Modules Interface): Document
NSS_STATUS_NOTFOUND and SUCCESS.
2015-12-09 Mike FABIAN <mfabian@redhat.com>
[BZ 18568]

7
manual/nss.texi
View File

@ -448,6 +448,13 @@ The function should be called again with a larger buffer.
@item
@code{NSS_STATUS_NOTFOUND} @tab
@code{ENOENT} @tab The requested entry is not available.
@item
@code{NSS_STATUS_NOTFOUND} @tab
@code{SUCCESS} @tab There are no entries.
Use this to avoid returning errors for inactive services which may
be enabled at a later time. This is not the same as the service
being temporarily unavailable.
@end multitable
These are proposed values. There can be other error codes and the