icon Top 9 categories map      RocketAware >


Tips: Browse or Search all pages for efficient awareness of more than 6000 of the most popular reusable and open source applications, functions, libraries, and FAQs.

The "RKT couplings" below include links to source code, updates, additional information, advice, FAQs, and overviews.


Search all pages


By activity
Professions, Sciences, Humanities, Business, ...

User Interface
Text-based, GUI, Audio, Video, Keyboards, Mouse, Images,...

Text Strings
Conversions, tests, processing, manipulation,...

Integer, Floating point, Matrix, Statistics, Boolean, ...

Algorithms, Memory, Process control, Debugging, ...

Stored Data
Data storage, Integrity, Encryption, Compression, ...

Networks, protocols, Interprocess, Remote, Client Server, ...

Hard World
Timing, Calendar and Clock, Audio, Video, Printer, Controls...

File System
Management, Filtering, File & Directory access, Viewers, ...


RocketLink!--> Man page versions: OpenBSD FreeBSD NetBSD Others

CHPASS(1)                  OpenBSD Reference Manual                  CHPASS(1)

     chpass - add or change user database information

     chpass [-ly] [-a list] [-s newshell] [user]

     chpass allows editing of the user database information associated with
     user, or, by default, the current user.  The information is formatted and
     supplied to an editor for changes.

     Only the information that the user is allowed to change is displayed.

     If YP in enabled change requests are first tried in the local database,
     and then in the YP database, if there was no entry to change locally.

     The options are as follows:

     -a list
             The super-user is allowed to directly supply a user database en-
             try, in the format specified by passwd(5),  as an argument.  This
             argument must be a colon (`:') separated list of all the user
             database fields, although they may be empty.  In YP environments
             this operation is not supported, only local additions can be done
             and that requires use of the -l flag.

     -l      In environments where YP is enabled, always alter local informa-
             tion as opposed to information in YP.

     -s newshell
             Attempts to change the user's shell to newshell.

     -y      In environments where YP is enabled, always change the YP entry,
             even if this is a modification request and there is a local entry
             for the specified user.

     Possible display items are as follows:

           Login:           user's login name
           Password:        user's encrypted password
           Uid:             user's login
           Gid:             user's login group
           Change:          password change time
           Expire:          account expiration time
           Class:           user's general classification
           Home Directory:  user's home directory
           Shell:           user's login shell
           Full Name:       user's real name
           Location:        user's normal location
           Home Phone:      user's home phone
           Office Phone:    user's office phone

     The login field is the user name used to access the computer account.

     The password field contains the encrypted form of the user's password.

     The uid field is the number associated with the login field.  Both of
     these fields should be unique across the system (and often across a group
     of systems) as they control file access.

     While it is possible to have multiple entries with identical login names
     and/or identical user IDs, it is usually a mistake to do so.  Routines
     that manipulate these files will often return only one of the multiple
     entries, and that one by random selection.

     The group field is the group that the user will be placed in at login.
     Since BSD supports multiple groups (see groups(1)),  this field currently
     has little special meaning.  This field may be filled in with either a
     number or a group name (see group(5)).

     The change field is the date by which the password must be changed.

     The expire field is the date on which the account expires.

     Both the change and expire fields should be entered in the form ``month
     day year'' where month is the month name (the first three characters are
     sufficient), day is the day of the month, and year is the year.

     The class field is currently unused.  In the near future it will be a key
     to a termcap(5) style database of user attributes.

     The user's home directory is the full UNIX path name where the user will
     be placed at login.

     The shell field is the command interpreter the user prefers.  If the
     shell field is empty, the Bourne shell (/bin/sh) is assumed.  When alter-
     ing a login shell, and not the super-user, the user may not change from a
     non-standard shell or to a non-standard shell.  Non-standard is defined
     as a shell not found in /etc/shells.

     The last four fields are for storing the user's full name, office
     location, and work and home telephone numbers.

     Once the information has been verified, chpass uses pwd_mkdb(8) to update
     the user database.

     The vi(1) editor will be used unless the environment variable EDITOR is
     set to an alternate editor.  When the editor terminates, the information
     is re-read and used to update the user database itself.  Only the user,
     or the super-user, may edit the information associated with the user.

     /etc/master.passwd    user database
     /etc/passwd           a Version 7 format password file
     /etc/ptmp             lock file for the passwd database
     /var/tmp/pw.XXXXXXXX  temporary copy of the user passwd information
     /etc/shells           list of approved shells

     finger(1),  login(1),  passwd(1),  getusershell(3),  passwd(5),
     pwd_mkdb(8),  vipw(8)

     Robert Morris, and Ken Thompson, UNIX Password Security.

     User information should (and eventually will) be stored elsewhere.

     The chpass command appeared in 4.3BSD-Reno.

OpenBSD 2.6                    December 30, 1993                             2

Source: OpenBSD 2.6 man pages. Copyright: Portions are copyrighted by BERKELEY
SOFTWARE DESIGN, INC., The Regents of the University of California, Massachusetts
Institute of Technology, Free Software Foundation, FreeBSD Inc., and others.

(Corrections, notes, and links courtesy of RocketAware.com)

[Detailed Topics]
FreeBSD Sources for chpass(1)
OpenBSD sources for chpass(1)

[Overview Topics]

Up to: Process Limits: Identity - Process ownership and Identity

RocketLink!--> Man page versions: OpenBSD FreeBSD NetBSD Others

Rapid-Links: Search | About | Comments | Submit Path: RocketAware > chpass.1/
RocketAware.com is a service of Mib Software
Copyright 1999, Forrest J. Cavalier III. All Rights Reserved.
We welcome submissions and comments