style secure and insecure databases for the specified file.
These databases are then installed into
argument is installed into
must be in the correct format (see
It is important to note that the format used in this system is
different from the historic 6th Edition-style format.
The options are as follows:
Check if the password file is in the correct format.
Do not change, add, or remove any files.
Operate in a base directory other than the default of
All absolute paths (including
will be made relative to
Any directories specified as a part of
will be stripped off.
This option is used to create password databases in directories
for instance in a
Create a 6th Edition-style password file and install it into
Only update the secure version of the database.
This is most commonly used in conjunction with the
flag during a password change.
Because the insecure database doesn't contain the password there
is no reason to update it if the only change is in the password field.
Cannot be used in conjunction with the
Only update the record for the specified user.
Utilities that operate on a single user can use this option to avoid the
overhead of rebuilding the entire database.
This option must never be used if the line number of the user's record in
The absolute path to a file in
format, as described in
The two databases differ in that the secure version contains the user's
encrypted password and the insecure version has an asterisk
The databases are used by the C library password routines (see
exits zero on success, non-zero on failure.
Previous versions of the system had a program similar to
style databases for the password file but depended on the calling programs
to install them.
The program was renamed in order that previous users of the program
not be surprised by the changes in functionality.
Because of the necessity for atomic update of the password files,
to install them.
This, however, requires that the file specified on the command line live
on the same file system as the
There are the obvious races with multiple people running
on different password files at the same time.
The front-ends to
handle the locking necessary to avoid this problem.