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. Neither the name of the University nor the names of its contributors
13 .\" may be used to endorse or promote products derived from this software
14 .\" without specific prior written permission.
16 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
28 .\" @(#)cap_mkdb.1 8.1 (Berkeley) 6/6/93
29 .\" $FreeBSD: src/usr.bin/cap_mkdb/cap_mkdb.1,v 1.15 2005/02/22 23:29:53 ru Exp $
30 .\" $DragonFly: src/usr.bin/cap_mkdb/cap_mkdb.1,v 1.3 2007/09/25 04:53:48 pavalos Exp $
37 .Nd create capability database
47 utility builds a hashed database out of the
49 logical database constructed by the concatenation of the specified
52 The database is named by the basename of the first file argument and
57 routines can access the database in this form much more quickly
58 than they can the original text file(s).
60 The ``tc'' capabilities of the records are expanded before the
61 record is stored into the database.
63 The following options are available:
64 .Bl -tag -width indent
66 Use big-endian byte order for database metadata.
68 Specify a different database basename.
70 Use little-endian byte order for database metadata.
72 Print out the number of capability records in the database.
79 flags are mutually exclusive.
80 The default byte ordering is the current host order.
82 Each record is stored in the database using two different types of keys.
84 The first type is a key which consists of the first capability of
85 the record (not including the trailing colon (``:'')) with a data
86 field consisting of a special byte followed by the rest of the record.
87 The special byte is either a 0 or 1, where a 0 means that the record
88 is okay, and a 1 means that there was a ``tc'' capability in the record
89 that could not be expanded.
91 The second type is a key which consists of one of the names from the
92 first capability of the record with a data field consisting a special
93 byte followed by the first capability of the record.
94 The special byte is a 2.
96 In normal operation names are looked up in the database, resulting
97 in a key/data pair of the second type.
98 The data field of this key/data pair is used to look up a key/data
99 pair of the first type which has the real data associated with the