2 .\" David L. Nugent. 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.
13 .\" THIS SOFTWARE IS PROVIDED BY DAVID L. NUGENT AND CONTRIBUTORS ``AS IS'' AND
14 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
15 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
16 .\" ARE DISCLAIMED. IN NO EVENT SHALL DAVID L. NUGENT OR CONTRIBUTORS BE LIABLE
17 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
18 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
19 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
20 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
21 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
22 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32 .Nd format of the pw.conf configuration file
36 contains configuration data for the
41 utility is used for maintenance of the system password and group
42 files, allowing users and groups to be added, deleted and changed.
43 This file may be modified via the
49 option, or by editing it directly with a text editor.
53 is treated either a comment or as configuration data;
54 blank lines and lines commencing with a
56 character are considered comments, and any remaining lines are
57 examined for a leading keyword, followed by corresponding data.
59 Keywords recognized by
62 .Bl -tag -width password_days -offset indent -compact
64 affect passwords generated for new users
66 reuse gaps in uid sequences
68 reuse gaps in gid sequences
74 where to obtain default home contents
76 mail to send to new users
78 log user/group modifications to this file
80 root directory for home directories
82 paths in which to locate shell programs
84 list of valid shells (without path)
86 default shell (without path)
90 add new users to this groups
92 place new users in this login class
95 range of valid default user ids
98 range of valid default group ids
100 days after which account expires
102 days after which password expires
108 .Bl -tag -width password_days -offset indent -compact
110 disable login on newly created accounts
112 force the password to be the account name
114 force a blank password
116 generate a random password
119 The second and third options are insecure and should be avoided if
120 possible on a publicly accessible system.
121 The first option requires that the superuser run
123 to set a password before the account may be used.
124 This may also be useful for creating administrative accounts.
125 The final option causes
127 to respond by printing a randomly generated password on stdout.
128 This is the preferred and most secure option.
131 utility also provides a method of setting a specific password for the new
132 user via a filehandle (command lines are not secure).
138 determine the method by which new user and group id numbers are
142 in this field will cause
144 to search for the first unused user or group id within the allowed
147 will ensure that no other existing user or group id within the range
148 is numerically lower than the new one generated, and therefore avoids
149 reusing gaps in the user or group id sequence that are caused by
150 previous user or group deletions.
151 Note that if the default group is not specified using the
155 will create a new group for the user and attempt to keep the new
156 user's uid and gid the same.
157 If the new user's uid is currently in use as a group id, then the next
158 available group id is chosen instead.
162 servers which maintain a separate passwd database to
163 .Pa /etc/master.passwd ,
164 this option allows the additional file to be concurrently updated
165 as user records are added, modified or removed.
166 If blank or set to 'no', no additional database is updated.
167 An absolute pathname must be used.
171 keyword nominates a directory from which the contents of a user's
172 new home directory is constructed.
179 option causes the user's home directory to be created and populated
180 using the files contained in the
184 To send an initial email to new users, the
186 keyword may be used to specify a path name to a file containing
187 the message body of the message to be sent.
188 To avoid sending mail when accounts are created, leave this entry
194 option allows logging of password file modifications into the
196 To avoid creating or adding to such a logfile, then leave this
197 field blank or specify
202 keyword is mandatory.
203 This specifies the location of the directory in which all new user
204 home directories are created.
208 keyword specifies a list of directories - separated by colons
210 - which contain the programs used by the login shells.
214 keyword specifies a list of programs available for use as login
216 This list is a comma-separated list of shell names which should
218 These shells must exist in one of the directories nominated by
223 keyword nominates which shell program to use for new users when
224 none is specified on the
230 keyword defines the primary group (the group id number in the
231 password file) used for new accounts.
232 If left blank, or the word
234 is used, then each new user will have a corresponding group of
235 their own created automatically.
236 This is the recommended procedure for new users as it best secures each
237 user's files against interference by other users of the system
240 normally used by the user.
244 keyword provides an automatic means of placing new users into groups within
248 This is useful where all users share some resources, and is preferable
249 to placing users into the same primary group.
250 The effect of this keyword can be overridden using the
258 field determines the login class (See
260 that new users will be allocated unless overwritten by
268 keywords determine the allowed ranges of automatically allocated user
269 and group id numbers.
270 The default values for both user and group ids are 1000 and 32000 as
271 minimum and maximum respectively.
272 The user and group id's actually used when creating an account with
274 may be overridden using the
278 command line options.
284 are used to automatically calculate the number of days from the date
285 on which an account is created when the account will expire or the
286 user will be forced to change the account's password.
289 in either field will disable the corresponding (account or password)
292 The maximum line length of
295 Longer lines will be skipped and treated
298 .Bl -tag -width /etc/master.passwd -compact
301 .It Pa /etc/master.passwd