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 program 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
70 path to the NIS passwd database
72 where to obtain default home contents
74 mail to send to new users
76 log user/group modifications to this file
78 root directory for home directories
80 paths in which to locate shell programs
82 list of valid shells (without path)
84 default shell (without path)
88 add new users to this groups
90 place new users in this login class
93 range of valid default user ids
96 range of valid default group ids
98 days after which account expires
100 days after which password expires
106 .Bl -tag -width password_days -offset indent -compact
108 disable login on newly created accounts
110 force the password to be the account name
112 force a blank password
114 generate a random password
117 The second and third options are insecure and should be avoided if
118 possible on a publicly accessible system.
119 The first option requires that the superuser run
121 to set a password before the account may be used.
122 This may also be useful for creating administrative accounts.
123 The final option causes
125 to respond by printing a randomly generated password on stdout.
126 This is the preferred and most secure option.
128 also provides a method of setting a specific password for the new
129 user via a filehandle (command lines are not secure).
135 determine the method by which new user and group id numbers are
139 in this field will cause
141 to search for the first unused user or group id within the allowed
144 will ensure that no other existing user or group id within the range
145 is numerically lower than the new one generated, and therefore avoids
146 reusing gaps in the user or group id sequence that are caused by
147 previous user or group deletions.
148 Note that if the default group is not specified using the
152 will create a new group for the user and attempt to keep the new
153 user's uid and gid the same.
154 If the new user's uid is currently in use as a group id, then the next
155 available group id is chosen instead.
157 On NIS servers which maintain a separate passwd database to
158 .Pa /etc/master.passwd ,
159 this option allows the additional file to be concurrently updated
160 as user records are added, modified or removed.
161 If blank or set to 'no', no additional database is updated.
162 An absolute pathname must be used.
166 keyword nominates a directory from which the contents of a user's
167 new home directory is constructed.
173 option causes the user's home directory to be created and populated
174 using the files contained in the
178 To send an initial email to new users, the
180 keyword may be used to specify a path name to a file containing
181 the message body of the message to be sent.
182 To avoid sending mail when accounts are created, leave this entry
188 option allows logging of password file modifications into the
190 To avoid creating or adding to such a logfile, then leave this
191 field blank or specify
196 keyword is mandatory.
197 This specifies the location of the directory in which all new user
198 home directories are created.
201 specifies a list of directories - separated by colons
203 - which contain the programs used by the login shells.
207 keyword specifies a list of programs available for use as login
209 This list is a comma-separated list of shell names which should
211 These shells must exist in one of the directories nominated by
216 keyword nominates which shell program to use for new users when
217 none is specified on the
223 keyword defines the primary group (the group id number in the
224 password file) used for new accounts.
225 If left blank, or the word
227 is used, then each new user will have a corresponding group of
228 their own created automatically.
229 This is the recommended procedure for new users as it best secures each
230 user's files against interference by other users of the system
233 normally used by the user.
236 provides an automatic means of placing new users into groups within
240 This is useful where all users share some resources, and is preferable
241 to placing users into the same primary group.
242 The effect of this keyword can be overridden using the
250 field determines the login class (See
252 that new users will be allocated unless overwritten by
260 keywords determines the allowed ranges of automatically allocated user
261 and group id numbers.
262 The default values for both user and group ids are 1000 and 32000 as
263 minimum and maximum respectively.
264 The user and group id's actually used when creating an account with
266 may be overridden using the
270 command line options.
276 are used to automatically calculate the number of days from the date
277 on which an account is created when the account will expire or the
278 user will be forced to change the account's password.
281 in either field will disable the corresponding (account or password)
284 The maximum line length of
287 Longer lines will be skipped and treated
290 .Bl -tag -width /etc/master.passwd -compact
293 .It Pa /etc/master.passwd