1 .\" Copyright (c) 1991, 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 .\" 4. 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 .\" @(#)pwd_mkdb.8 8.1 (Berkeley) 6/6/93
36 .Nd "generate the password databases"
52 style secure and insecure databases for the specified file.
53 These databases are then installed into
58 The file is installed into
59 .Pa /etc/master.passwd .
60 The file must be in the correct format (see
62 It is important to note that the format used in this system is
63 different from the historic Version 7 style format.
65 The options are as follows:
68 Check if the password file is in the correct format.
70 change, add, or remove any files.
74 to exit with an error if it cannot obtain a lock on the file.
76 we block waiting for a lock on the source file.
77 The lock is held through
78 the rebuilding of the database.
80 Create a Version 7 style password file and install it into
83 Ignore locking failure of the
86 This option is intended to be used to build password files in
87 the release process over NFS where no contention can happen.
88 A non-default directory must also be specified with the
90 option for locking to be ignored.
91 Other use of this option is strongly discouraged.
93 Store databases into specified destination directory instead of
96 Only update the record for the specified user.
98 operate on a single user can use this option to avoid the
99 overhead of rebuilding the entire database.
100 .It Fl s Ar cachesize
101 Specify in megabytes the size of the memory cache used by the
103 On systems with a large user base, a small cache
104 size can lead to prohibitively long database file rebuild times.
105 As a rough guide, the memory usage of
107 in megabytes will be a little bit more than twice the figure
109 The default is 2 megabytes.
112 The two databases differ in that the secure version contains the user's
113 encrypted password and the insecure version has an asterisk (``*'')
115 The databases are used by the C library password routines (see
120 utility exits zero on success, non-zero on failure.
124 environment variable is set,
126 will suppress the warning messages that are
127 normally generated for large user and group IDs.
128 Such IDs can cause serious problems with software
129 that makes assumptions about the values of IDs.
131 .Bl -tag -width Pa -compact
133 The insecure password database file.
134 .It Pa /etc/pwd.db.tmp
137 The secure password database file.
138 .It Pa /etc/spwd.db.tmp
140 .It Pa /etc/master.passwd
141 The current password file.
143 A Version 7 format password file.
146 Because of the necessity for atomic update of the password files,
151 This, however, requires that the file specified on the command line live
152 on the same file system as the
156 There are the obvious races with multiple people running
158 on different password files at the same time.
165 handle the locking necessary to avoid this problem.
167 Previous versions of the system had a program similar to
172 style databases for the password file but depended on the calling programs
174 The program was renamed in order that previous users of the program
175 not be surprised by the changes in functionality.