.\" based on glibc infopages
.\" polished - aeb
.\"
-.TH SETNETGRENT 3 2016-03-15 "GNU" "Linux Programmer's Manual"
+.TH SETNETGRENT 3 2017-09-15 "GNU" "Linux Programmer's Manual"
.SH NAME
setnetgrent, endnetgrent, getnetgrent, getnetgrent_r, innetgr \-
handle network group entries
.SH SYNOPSIS
.nf
.B #include <netdb.h>
-
+.PP
.BI "int setnetgrent(const char *" netgroup );
-
+.PP
.B "void endnetgrent(void);"
-
+.PP
.BI "int getnetgrent(char **" host ", char **" user ", char **" domain );
-
+.PP
.BI "int getnetgrent_r(char **" host ", char **" user ","
.BI " char **" domain ", char *" buf ", size_t " buflen );
-
+.PP
.BI "int innetgr(const char *" netgroup ", const char *" host ","
.BI " const char *" user ", const char *" domain );
.fi
-.sp
+.PP
.in -4n
Feature Test Macro Requirements for glibc (see
.BR feature_test_macros (7)):
.in
-.sp
+.PP
.ad l
.BR setnetgrent (),
.BR endnetgrent (),
race:netgrentbuf locale
T}
.TE
-
+.sp 1
In the above table,
.I netgrent
in
.I race:netgrent
signifies that if any of the functions
-.BR setnetgrent (3),
-.BR getnetgrent_r (3),
-.BR innetgr (3),
-.BR getnetgrent (3),
+.BR setnetgrent (),
+.BR getnetgrent_r (),
+.BR innetgr (),
+.BR getnetgrent (),
or
-.BR endnetgrent (3)
+.BR endnetgrent ()
are used in parallel in different threads of a program,
then data races could occur.
.SH CONFORMING TO