1 '\" te
2 .\" Copyright (C) 1999, Sun Microsystems, Inc. All Rights Reserved
3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
6 .TH GETENT 1M "Mar 26, 2007"
7 .SH NAME
8 getent \- get entries from administrative database
9 .SH SYNOPSIS
10 .LP
11 .nf
12 \fBgetent\fR \fIdatabase\fR [\fIkey\fR]...
13 .fi
14
15 .SH DESCRIPTION
16 .sp
17 .LP
18 \fBgetent\fR gets a list of entries from the administrative database specified
19 by \fIdatabase\fR. The information generally comes from one or more of the
20 sources that are specified for the \fIdatabase\fR in \fB/etc/nsswitch.conf\fR.
21 .sp
22 .LP
23 \fIdatabase\fR is the name of the database to be examined. This can be
24 \fBpasswd\fR, \fBgroup\fR, \fBhosts\fR, \fBipnodes\fR, \fBservices\fR,
25 \fBprotocols\fR, \fBethers\fR, \fBproject\fR, \fBnetworks\fR, or
26 \fBnetmasks\fR. For each of these databases, \fBgetent\fR uses the appropriate
27 library routines described in \fBgetpwnam\fR(3C), \fBgetgrnam\fR(3C),
28 \fBgethostbyaddr\fR(3NSL), \fBgethostbyname\fR(3NSL),
29 \fBgetipnodebyaddr\fR(3SOCKET), \fBgetipnodebyname\fR(3SOCKET),
30 \fBgetservbyname\fR(3SOCKET), \fBgetprotobyname\fR(3SOCKET),
31 \fBethers\fR(3SOCKET), \fBgetprojbyname\fR(3PROJECT) and
32 \fBgetnetbyname\fR(3SOCKET), respectively.
33 .sp
34 .LP
35 Each \fIkey\fR must be in a format appropriate for searching on the respective
36 database. For example, it can be a \fIusername\fR or \fInumeric-uid\fR for
37 \fBpasswd\fR; \fIhostname\fR or \fIIP\fR \fIaddress\fR for \fBhosts\fR; or
38 \fIservice\fR, \fIservice/protocol\fR, \fIport\fR, or \fIport/proto\fR for
39 \fBservices\fR.
40 .sp
41 .LP
42 \fBgetent\fR prints out the database entries that match each of the supplied
43 keys, one per line, in the format of the matching administrative file:
44 \fBpasswd\fR(4), \fBgroup\fR(4), \fBproject\fR(4), \fBhosts\fR(4),
45 \fBservices\fR(4), \fBprotocols\fR(4), \fBethers\fR(3SOCKET),
46 \fBnetworks\fR(4), or \fBnetmasks\fR(4). If no key is given, all entries
47 returned by the corresponding enumeration library routine, for example,
48 \fBgetpwent()\fR or \fBgethostent()\fR, are printed. Enumeration is not
49 supported on \fBipnodes\fR.
50 .SS "Key Interpretation for \fBpasswd\fR and \fBgroup\fR Databases"
51 .sp
52 .LP
53 When \fBgetent\fR is invoked with database set to \fBpasswd\fR, each key value
54 is processed as follows:
55 .RS +4
56 .TP
57 .ie t \(bu
58 .el o
59 If the key value consists only of numeric characters, \fBgetent\fR assumes that
60 the key value is a numeric user ID and searches the user database for a
61 matching user ID.
62 .RE
63 .RS +4
64 .TP
131
132 .SH FILES
133 .sp
134 .ne 2
135 .na
136 \fB\fB/etc/nsswitch.conf\fR\fR
137 .ad
138 .RS 22n
139 name service switch configuration file
140 .RE
141
142 .sp
143 .ne 2
144 .na
145 \fB\fB/etc/passwd\fR\fR
146 .ad
147 .RS 22n
148 password file
149 .RE
150
151 .sp
152 .ne 2
153 .na
154 \fB\fB/etc/group\fR\fR
155 .ad
156 .RS 22n
157 group file
158 .RE
159
160 .sp
161 .ne 2
162 .na
163 \fB\fB/etc/inet/hosts\fR\fR
164 .ad
165 .RS 22n
166 IPv4 and IPv6 host name database
167 .RE
168
169 .sp
170 .ne 2
|
1 '\" te
2 .\" Copyright (c) 2014 Gary Mills
3 .\" Copyright (C) 1999, Sun Microsystems, Inc. All Rights Reserved
4 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
5 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
6 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
7 .TH GETENT 1M "Mar 14, 2014"
8 .SH NAME
9 getent \- get entries from administrative database
10 .SH SYNOPSIS
11 .LP
12 .nf
13 \fBgetent\fR \fIdatabase\fR [\fIkey\fR]...
14 .fi
15
16 .SH DESCRIPTION
17 .sp
18 .LP
19 \fBgetent\fR gets a list of entries from the administrative database specified
20 by \fIdatabase\fR. The information generally comes from one or more of the
21 sources that are specified for the \fIdatabase\fR in \fB/etc/nsswitch.conf\fR.
22 .sp
23 .LP
24 \fIdatabase\fR is the name of the database to be examined. This can be
25 \fBpasswd\fR, \fBshadow\fR, \fBgroup\fR, \fBhosts\fR, \fBipnodes\fR, \fBservices\fR,
26 \fBprotocols\fR, \fBethers\fR, \fBproject\fR, \fBnetworks\fR, or
27 \fBnetmasks\fR. For each of these databases, \fBgetent\fR uses the appropriate
28 library routines described in \fBgetpwnam\fR(3C), \fBgetspnam\fR(3C), \fBgetgrnam\fR(3C),
29 \fBgethostbyaddr\fR(3NSL), \fBgethostbyname\fR(3NSL),
30 \fBgetipnodebyaddr\fR(3SOCKET), \fBgetipnodebyname\fR(3SOCKET),
31 \fBgetservbyname\fR(3SOCKET), \fBgetprotobyname\fR(3SOCKET),
32 \fBethers\fR(3SOCKET), \fBgetprojbyname\fR(3PROJECT) and
33 \fBgetnetbyname\fR(3SOCKET), respectively.
34 .sp
35 .LP
36 Each \fIkey\fR must be in a format appropriate for searching on the respective
37 database. For example, it can be a \fIusername\fR or \fInumeric-uid\fR for
38 \fBpasswd\fR; \fIhostname\fR or \fIIP\fR \fIaddress\fR for \fBhosts\fR; or
39 \fIservice\fR, \fIservice/protocol\fR, \fIport\fR, or \fIport/proto\fR for
40 \fBservices\fR.
41 .sp
42 .LP
43 \fBgetent\fR prints out the database entries that match each of the supplied
44 keys, one per line, in the format of the matching administrative file:
45 \fBpasswd\fR(4), \fBshadow\fR(4), \fBgroup\fR(4), \fBproject\fR(4), \fBhosts\fR(4),
46 \fBservices\fR(4), \fBprotocols\fR(4), \fBethers\fR(3SOCKET),
47 \fBnetworks\fR(4), or \fBnetmasks\fR(4). If no key is given, all entries
48 returned by the corresponding enumeration library routine, for example,
49 \fBgetpwent()\fR or \fBgethostent()\fR, are printed. Enumeration is not
50 supported on \fBipnodes\fR.
51 .SS "Key Interpretation for \fBpasswd\fR and \fBgroup\fR Databases"
52 .sp
53 .LP
54 When \fBgetent\fR is invoked with database set to \fBpasswd\fR, each key value
55 is processed as follows:
56 .RS +4
57 .TP
58 .ie t \(bu
59 .el o
60 If the key value consists only of numeric characters, \fBgetent\fR assumes that
61 the key value is a numeric user ID and searches the user database for a
62 matching user ID.
63 .RE
64 .RS +4
65 .TP
132
133 .SH FILES
134 .sp
135 .ne 2
136 .na
137 \fB\fB/etc/nsswitch.conf\fR\fR
138 .ad
139 .RS 22n
140 name service switch configuration file
141 .RE
142
143 .sp
144 .ne 2
145 .na
146 \fB\fB/etc/passwd\fR\fR
147 .ad
148 .RS 22n
149 password file
150 .RE
151
152 .sp
153 .ne 2
154 .na
155 \fB\fB/etc/shadow\fR\fR
156 .ad
157 .RS 22n
158 shadowed password file
159 .RE
160
161 .sp
162 .ne 2
163 .na
164 \fB\fB/etc/group\fR\fR
165 .ad
166 .RS 22n
167 group file
168 .RE
169
170 .sp
171 .ne 2
172 .na
173 \fB\fB/etc/inet/hosts\fR\fR
174 .ad
175 .RS 22n
176 IPv4 and IPv6 host name database
177 .RE
178
179 .sp
180 .ne 2
|