1 .\" Copyright (c) 1992, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. All advertising materials mentioning features or use of this software
13 .\" must display the following acknowledgement:
14 .\" This product includes software developed by the University of
15 .\" California, Berkeley and its contributors.
16 .\" 4. Neither the name of the University nor the names of its contributors
17 .\" may be used to endorse or promote products derived from this software
18 .\" without specific prior written permission.
20 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32 .\" @(#)cap_mkdb.1 8.1 (Berkeley) 6/6/93
33 .\" $Id: cap_mkdb.1,v 1.4 1997/02/22 19:54:19 peter Exp $
40 .Nd create capability database
51 builds a hashed database out of the
53 logical database constructed by the concatenation of the specified
56 The database is named by the basename of the first file argument and
61 routines can access the database in this form much more quickly
62 than they can the original text file(s).
64 The ``tc'' capabilities of the records are expanded before the
65 record is stored into the database.
67 The options as follows:
68 .Bl -tag -width XXXXXX -indent
70 Specify a different database basename.
72 Print out the number of capability records in the database.
76 Each record is stored in the database using two different types of keys.
78 The first type is a key which consists of the first capability of
79 the record (not including the trailing colon (``:'')) with a data
80 field consisting of a special byte followed by the rest of the record.
81 The special byte is either a 0 or 1, where a 0 means that the record
82 is okay, and a 1 means that there was a ``tc'' capability in the record
83 that couldn't be expanded.
85 The second type is a key which consists of one of the names from the
86 first capability of the record with a data field consisting a special
87 byte followed by the first capability of the record.
88 The special byte is a 2.
90 In normal operation names are looked up in the database, resulting
91 in a key/data pair of the second type.
92 The data field of this key/data pair is used to look up a key/data
93 pair of the first type which has the real data associated with the
98 utility exits 0 on success and >0 if an error occurs.