Document YP support.

2 files changed, 51 insertions, 29 deletions

diff --git a/lib/libc/gen/getgrent.3 b/lib/libc/gen/getgrent.3
index e0e2782..132ba6b 100644
--- a/lib/libc/gen/getgrent.3
+++ b/lib/libc/gen/getgrent.3
@@ -29,9 +29,10 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.\"     @(#)getgrent.3	8.2 (Berkeley) 4/19/94
+.\"     From: @(#)getgrent.3	8.2 (Berkeley) 4/19/94
+.\"	$Id$
 .\"
-.Dd April 19, 1994
+.Dd September 29, 1994
 .Dt GETGRENT 3
 .Os
 .Sh NAME
@@ -121,6 +122,25 @@ The
 .Fn endgrent
 function
 closes any open files.
+.Sh YP/NIS INTERACTION
+When the
+.Xr yp 4
+group database is enabled, the
+.Fn getgrnam
+and
+.Fn getgrgid
+functions use the YP maps
+.Dq Li group.byname
+and
+.Dq Li group.bygid ,
+respectively, if the requested group is not found in the local
+.Pa /etc/group
+file.  The
+.Fn getgrent
+function will step through the YP map
+.Dq Li group.byname
+if the entire map is enabled as described in
+.Xr group 5 .
 .Sh RETURN VALUES
 The functions
 .Fn getgrent ,
@@ -147,7 +167,8 @@ group database file
 .El
 .Sh SEE ALSO
 .Fn getpwent 3 ,
-.Fn group 5
+.Fn group 5 ,
+.Fn yp 4
 .Sh HISTORY
 The functions
 .Fn endgrent ,
@@ -181,12 +202,3 @@ leave their results in an internal static object and return
 a pointer to that object. Subsequent calls to
 the same function
 will modify the same object.
-.Pp
-The functions
-.Fn getgrent ,
-.Fn endgrent ,
-.Fn setgroupent ,
-and
-.Fn setgrent
-are fairly useless in a networked environment and should be
-avoided, if possible.
diff --git a/lib/libc/gen/getpwent.3 b/lib/libc/gen/getpwent.3
index 1208f53..6c23f49 100644
--- a/lib/libc/gen/getpwent.3
+++ b/lib/libc/gen/getpwent.3
@@ -29,9 +29,9 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\"
-.\"     @(#)getpwent.3	8.2 (Berkeley) 12/11/93
+.\"     From: @(#)getpwent.3	8.2 (Berkeley) 12/11/93
 .\"
-.Dd December 11, 1993
+.Dd September 20, 1994
 .Dt GETPWENT 3
 .Os
 .Sh NAME
@@ -133,6 +133,24 @@ If the process which calls them has an effective uid of 0, the encrypted
 password will be returned, otherwise, the password field of the returned
 structure will point to the string
 .Ql * .
+.Sh YP/NIS INTERACTION
+When the
+.Xr yp 4
+password database is enabled, the
+.Fn getpwnam
+and
+.Fn getpwuid
+functions use the YP maps
+.Dq Li passwd.byname
+and
+.Dq Li passwd.byuid ,
+respectively, if the requested password entry is not found in the 
+local database.  The
+.Fn getpwent
+function will step through the YP map
+.Dq Li passwd.byname
+if the entire map is enabled as described in
+.Xr passwd 5 .
 .Sh RETURN VALUES
 The functions
 .Fn getpwent ,
@@ -166,7 +184,8 @@ A Version 7 format password file
 .Xr getgrent 3 ,
 .Xr passwd 5 ,
 .Xr pwd_mkdb 8 ,
-.Xr vipw 8
+.Xr vipw 8 ,
+.Xr yp 4
 .Sh HISTORY
 The
 .Nm getpwent ,
@@ -181,6 +200,11 @@ The
 .Nm setpassent
 function appeared in
 .Bx 4.3 Reno .
+.Sh COMPATIBILITY
+The historic function
+.Xr setpwfile 3 ,
+which allowed the specification of alternate password databases,
+has been deprecated and is no longer available.
 .Sh BUGS
 The functions
 .Fn getpwent ,
@@ -191,17 +215,3 @@ leave their results in an internal static object and return
 a pointer to that object. Subsequent calls to
 the same function
 will modify the same object.
-.Pp
-The routines
-.Fn getpwent ,
-.Fn endpwent ,
-.Fn setpassent ,
-and
-.Fn setpwent
-are fairly useless in a networked environment and should be
-avoided, if possible.
-.Sh COMPATIBILITY
-The historic function
-.Xr setpwfile 3 ,
-which allowed the specification of alternate password databases,
-has been deprecated and is no longer available.