BSD 4_3_Reno development

[unix-history] / usr / share / man / cat1 / chpass.0

CHPASS(1)		    UNIX Reference Manual		     CHPASS(1)

N\bNA\bAM\bME\bE
     c\bch\bhp\bpa\bas\bss\bs - add or change user database information

S\bSY\bYN\bNO\bOP\bPS\bSI\bIS\bS
     chpass [-\b-a\ba _\bl_\bi_\bs_\bt] [-\b-s\bs _\bs_\bh_\be_\bl_\bl] [user]

D\bDE\bES\bSC\bCR\bRI\bIP\bPT\bTI\bIO\bON\bN
     C\bCh\bhp\bpa\bas\bss\bs allows editing of the user database information associated with
     _\bu_\bs_\be_\br 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.

     The options are as follows:

     -\b-a\ba    The super-user is allowed to directly supply a user database entry,
	   in the format specified by passwd(5), as an argument.  This argu-
	   ment must be a colon (``:'') separated list of all the user data-
	   base fields, although they may be empty.

     -\b-s\bs    The -\b-s\bs option attempts to change the user's shell to _\bn_\be_\bw_\bs_\bh.

     Possible display items are as follows:

	   Login:	     user's login name
	   Password:	     user's encrypted password
	   Uid:              user's id
	   Gid:              user's login group id
	   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 _\bl_\bo_\bg_\bi_\bn field is the user name used to access the computer account.

     The _\bp_\ba_\bs_\bs_\bw_\bo_\br_\bd field contains the encrypted form of the user's password.

     The _\bu_\bi_\bd field is the number associated with the _\bl_\bo_\bg_\bi_\bn 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 id's, 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 _\bg_\br_\bo_\bu_\bp field is the group that the user will be placed in at login.
     Since this system 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 _\bc_\bh_\ba_\bn_\bg_\be field is the date by which the password must be changed.

     The _\be_\bx_\bp_\bi_\br_\be field is the date on which the account expires.

     Both the _\bc_\bh_\ba_\bn_\bg_\be and _\be_\bx_\bp_\bi_\br_\be fields should be entered in the form ``month
     day year'' where _\bm_\bo_\bn_\bt_\bh is the month name (the first three characters are
     sufficient), _\bd_\ba_\by is the day of the month, and _\by_\be_\ba_\br is the year.
     The _\bc_\bl_\ba_\bs_\bs 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 _\bh_\bo_\bm_\be _\bd_\bi_\br_\be_\bc_\bt_\bo_\br_\by is the full UNIX path name where the user will
     be placed at login.

     The _\bs_\bh_\be_\bl_\bl field is the command interpreter the user prefers.  If the
     _\bs_\bh_\be_\bl_\bl field is empty, the Bourne shell, /_\bb_\bi_\bn/_\bs_\bh, 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 /_\be_\bt_\bc/_\bs_\bh_\be_\bl_\bl_\bs.

     The last four fields are for storing the user's _\bf_\bu_\bl_\bl _\bn_\ba_\bm_\be, _\bo_\bf_\bf_\bi_\bc_\be
     _\bl_\bo_\bc_\ba_\bt_\bi_\bo_\bn, and _\bh_\bo_\bm_\be and _\bw_\bo_\br_\bk _\bt_\be_\bl_\be_\bp_\bh_\bo_\bn_\be numbers.

     Once the information has been verified, c\bch\bhp\bpa\bas\bss\bs uses mkpasswd(8) to update
     the user database.  This is run in the background, and, at very large
     sites could take several minutes.	Until this update is completed, the
     password file is unavailable for other updates and the new information
     will not be available to programs.

E\bEN\bNV\bVI\bIR\bRO\bON\bNM\bME\bEN\bNT\bT
     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.

F\bFI\bIL\bLE\bES\bS
     /_\be_\bt_\bc/_\bm_\ba_\bs_\bt_\be_\br._\bp_\ba_\bs_\bs_\bw_\bd   The user database
     /_\be_\bt_\bc/_\bs_\bh_\be_\bl_\bl_\bs	  The list of approved shells


S\bSE\bEE\bE A\bAL\bLS\bSO\bO
     login(1), finger(1), getusershell(3), passwd(5), mkpasswd(8), vipw(8)

     Robert Morris and Ken Thompson, _\bU_\bN_\bI_\bX _\bP_\ba_\bs_\bs_\bw_\bo_\br_\bd _\bs_\be_\bc_\bu_\br_\bi_\bt_\by

H\bHI\bIS\bST\bTO\bOR\bRY\bY
     First release 4.3 Reno BSD.

B\bBU\bUG\bGS\bS
     User information should (and eventually will) be stored elsewhere.