1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
|
.\" $OpenBSD: revnetgroup.8,v 1.10 2007/05/31 19:20:31 jmc Exp $
.\"
.\" Copyright (c) 1995
.\" Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\" must display the following acknowledgement:
.\" This product includes software developed by Bill Paul.
.\" 4. Neither the name of the University nor the names of its contributors
.\" may be used to endorse or promote products derived from this software
.\" without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
.\" $FreeBSD: revnetgroup.8,v 1.4 1997/02/22 14:22:03 peter Exp $
.\"
.Dd $Mdocdate: May 31 2007 $
.Dt REVNETGROUP 8
.Os
.Sh NAME
.Nm revnetgroup
.Nd "generate reverse netgroup data"
.Sh SYNOPSIS
.Nm revnetgroup
.Fl u
.Fl h
.Op Fl f Ar netgroup_file
.Sh DESCRIPTION
.Nm
processes the contents of a file in
.Xr netgroup 5
format into what is called
.Pa reverse netgroup
form.
That is, where the original file shows
netgroup memberships in terms of which members reside in a particular
group, the reverse netgroup format specifies what groups are associated
with a particular member.
This information is used to generate the
.Pa netgroup.byuser
and
.Pa netgroup.byhosts
YP maps.
These reverse netgroup maps are used to help speed up
netgroup lookups, particularly for the
.Fn innetgr
library function.
.Pp
For example, the standard
.Pa /etc/netgroup
file may list a netgroup and a list of its members.
Here, the netgroup is considered the
.Pa key
and the member names are the
.Pa data .
By contrast, the reverse
.Pa netgroup.byusers
database lists each unique
member as the key and the netgroups to which the members belong become
the data.
Separate databases are created to hold information pertaining
to users and hosts; this allows netgroup username lookups
and netgroup hostname lookups to be performed using independent keyspaces.
.Pp
By constructing these reverse netgroup databases (and the corresponding
YP maps) in advance, the
.Xr getnetgrent 3
library functions are spared from having to work out the dependencies
themselves on the fly.
This is important on networks with large numbers
of users and hosts, since it can take a considerable amount of time
to process very large netgroup databases.
.Pp
The
.Nm
command prints its results on the standard output.
It is usually called only by
.Pa /var/yp/\<domain\>/Makefile
when rebuilding the YP netgroup maps.
.Pp
The options are as follows:
.Bl -tag -width Ds
.It Fl u
Generate netgroup.byuser output; only username information in the
original netgroup file is processed.
.It Fl h
Generate netgroup.byhost output; only hostname information in the
original netgroup file is processed. (Note at least one of the
.Fl u
or
.Fl h
flags must be specified.)
.It Op Fl f Ar netgroup_file
The
.Nm
command uses
.Pa /etc/netgroup
as its default input file.
The
.Fl f
flag allows the user to specify an alternate input file.
Specifying
.Dq -
as the input file causes
.Nm
to read from the standard input.
.El
.Sh FILES
.Bl -tag -width xxxxxxxxxxxxxxxxxxxxxxxx -compact
.It Pa /var/yp/\<domain\>Makefile
The Makefile that calls
.Xr makedbm 8
and
.Nm
to build the YP databases.
.It Pa /etc/netgroup
The default netgroup database file.
This file is most often found only on the YP master server.
.El
.Sh SEE ALSO
.Xr getnetgrent 3 ,
.Xr netgroup 5 ,
.Xr makedbm 8 ,
.Xr yp 8
.Sh AUTHORS
.An Bill Paul Aq wpaul@ctr.columbia.edu
|
