1 GETENT(1M) Maintenance Commands GETENT(1M)
2
3
4
5 NAME
6 getent - get entries from administrative database
7
8 SYNOPSIS
9 getent database [key]...
10
11
12 DESCRIPTION
13 getent gets a list of entries from the administrative database
14 specified by database. The information generally comes from one or more
15 of the sources that are specified for the database in
16 /etc/nsswitch.conf.
17
18
19 database is the name of the database to be examined. This can be
20 passwd, shadow, group, hosts, ipnodes, services, protocols, ethers,
21 project, networks, or netmasks. For each of these databases, getent
22 uses the appropriate library routines described in getpwnam(3C),
23 getspnam(3C), getgrnam(3C), gethostbyaddr(3NSL), gethostbyname(3NSL),
24 getipnodebyaddr(3SOCKET), getipnodebyname(3SOCKET),
25 getservbyname(3SOCKET), getprotobyname(3SOCKET), ethers(3SOCKET),
26 getprojbyname(3PROJECT) and getnetbyname(3SOCKET), respectively.
27
28
29 Each key must be in a format appropriate for searching on the
30 respective database. For example, it can be a username or numeric-uid
31 for passwd; hostname or IP address for hosts; or service,
32 service/protocol, port, or port/proto for services.
33
34
35 getent prints out the database entries that match each of the supplied
36 keys, one per line, in the format of the matching administrative file:
37 passwd(4), shadow(4), group(4), project(4), hosts(4), services(4),
38 protocols(4), ethers(3SOCKET), networks(4), or netmasks(4). If no key
39 is given, all entries returned by the corresponding enumeration library
40 routine, for example, getpwent() or gethostent(), are printed.
41 Enumeration is not supported on ipnodes.
42
43 Key Interpretation for passwd and group Databases
44 When getent is invoked with database set to passwd, each key value is
45 processed as follows:
46
|
1 GETENT(1M) Maintenance Commands GETENT(1M)
2
3
4
5 NAME
6 getent - get entries from administrative database
7
8 SYNOPSIS
9 getent database [key]...
10
11
12 DESCRIPTION
13 getent gets a list of entries from the administrative database
14 specified by database. The information generally comes from one or more
15 of the sources that are specified for the database in
16 /etc/nsswitch.conf.
17
18
19 database is the name of the database to be examined. This can be
20 passwd, shadow, group, hosts, ipnodes, services, protocols, ethers,
21 project, networks, netmasks, or netgroup. For each of these databases,
22 getent uses the appropriate library routines described in getpwnam(3C),
23 getspnam(3C), getgrnam(3C), gethostbyaddr(3NSL), gethostbyname(3NSL),
24 getipnodebyaddr(3SOCKET), getipnodebyname(3SOCKET),
25 getservbyname(3SOCKET), getprotobyname(3SOCKET), ethers(3SOCKET),
26 getprojbyname(3PROJECT), getnetbyname(3SOCKET), or getnetgrent(3C)
27 respectively.
28
29
30 Each key must be in a format appropriate for searching on the
31 respective database. For example, it can be a username or numeric-uid
32 for passwd; hostname or IP address for hosts; or service,
33 service/protocol, port, or port/proto for services.
34
35
36 getent prints out the database entries that match each of the supplied
37 keys, one per line, in the format of the matching administrative file:
38 passwd(4), shadow(4), group(4), project(4), hosts(4), services(4),
39 protocols(4), ethers(3SOCKET), networks(4), or netmasks(4). If no key
40 is given, all entries returned by the corresponding enumeration library
41 routine, for example, getpwent() or gethostent(), are printed.
42 Enumeration is not supported on ipnodes.
43
44 Key Interpretation for passwd and group Databases
45 When getent is invoked with database set to passwd, each key value is
46 processed as follows:
47
|