Commit | Line | Data |
---|---|---|
e1db696c KB |
1 | .\" Copyright (c) 1988 The Regents of the University of California. |
2 | .\" All rights reserved. | |
3 | .\" | |
4 | .\" Redistribution and use in source and binary forms are permitted | |
5 | .\" provided that the above copyright notice and this paragraph are | |
6 | .\" duplicated in all such forms and that any documentation, | |
7 | .\" advertising materials, and other materials related to such | |
8 | .\" distribution and use acknowledge that the software was developed | |
9 | .\" by the University of California, Berkeley. The name of the | |
10 | .\" University may not be used to endorse or promote products derived | |
11 | .\" from this software without specific prior written permission. | |
12 | .\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR | |
13 | .\" IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED | |
14 | .\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. | |
15 | .\" | |
0982b854 | 16 | .\" @(#)passwd.5 6.4 (Berkeley) %G% |
a343bbd7 | 17 | .\" |
0b6955e2 | 18 | .TH PASSWD 5 "" |
a343bbd7 KM |
19 | .AT 3 |
20 | .SH NAME | |
e1db696c | 21 | passwd \- password files |
a343bbd7 KM |
22 | .SH DESCRIPTION |
23 | .I Passwd | |
e1db696c KB |
24 | files are files consisting of newline separated records, one per user, |
25 | containing ten colon (``:'') separated fields. These fields are as | |
26 | follows: | |
a343bbd7 | 27 | .PP |
e1db696c KB |
28 | .RS |
29 | name user's login name | |
30 | password user's \fIencrypted\fP password | |
31 | uid user's id | |
32 | gid user's login group id | |
33 | class user's general classification (unused) | |
34 | change password change time | |
35 | expire account expiration time | |
36 | gecos general information about the user | |
37 | home_dir user's home directory | |
38 | shell user's login shell | |
39 | .RE | |
40 | .PP | |
41 | The | |
42 | .I name | |
43 | field is the login used to access the computer account, and the | |
44 | .I uid | |
45 | field is the number associated with it. They should both be unique | |
46 | across the system (and often across a group of systems) since they | |
47 | control file access. | |
48 | .PP | |
49 | While it is possible to have multiple entries with identical login names | |
50 | and/or identical user id's, it is usually a mistake to do so. Routines | |
51 | that manipulate these files will often return only one of the multiple | |
52 | entries, and that one by random selection. | |
53 | .PP | |
0982b854 KB |
54 | The login name must never begin with a hyphen (``-''); also, it is strongly |
55 | suggested that neither upper-case characters or dots (``.'') be part | |
56 | of the name, as this tends to confuse mailers. No field may contain a | |
57 | colon (``:'') as this has been used historically to separate the fields | |
58 | in the user database. | |
59 | .PP | |
e1db696c KB |
60 | The password field is the |
61 | .I encrypted | |
62 | form of the password. | |
63 | If the | |
64 | .I password | |
65 | field is empty, no password will be required to gain access to the | |
66 | machine. This is almost invariably a mistake. | |
67 | Because these files contain the encrypted user passwords, they should | |
68 | not be readable by anyone without appropriate privileges. | |
69 | .PP | |
70 | The group field is the group that the user will be placed in upon login. | |
71 | Since this system supports multiple groups (see | |
72 | .IR groups (1)) | |
73 | this field currently has little special meaning. | |
a343bbd7 | 74 | .PP |
e1db696c KB |
75 | The |
76 | .I class | |
77 | field is currently unused. In the near future it will be a key to | |
78 | a | |
79 | .IR termcap (5) | |
80 | style database of user attributes. | |
81 | .PP | |
82 | The | |
83 | .I change | |
84 | field is the number in seconds, GMT, from the epoch, until the | |
85 | password for the account must be changed. | |
86 | .PP | |
87 | The | |
88 | .I expire | |
89 | field is the number in seconds, GMT, from the epoch, until the | |
90 | account expires. | |
91 | .PP | |
92 | The | |
93 | .I gecos | |
94 | field normally contains comma (``,'') separated subfields as follows: | |
95 | .PP | |
96 | .RS | |
97 | name user's full name | |
98 | office user's office number | |
99 | wphone user's work phone number | |
100 | hphone user's home phone number | |
101 | .RE | |
102 | .PP | |
103 | This information is used by the | |
104 | .IR finger (1) | |
105 | program. | |
a343bbd7 | 106 | .PP |
e1db696c KB |
107 | The user's home directory is the full UNIX path name where the user |
108 | will be placed on login. | |
a343bbd7 | 109 | .PP |
e1db696c KB |
110 | The shell field is the command interpreter the user prefers. |
111 | If the | |
112 | .I shell | |
113 | field is empty, the Bourne shell (\fI/bin/sh\fP) is assumed. | |
a343bbd7 | 114 | .SH "SEE ALSO" |
e1db696c | 115 | chpass(1), login(1), passwd(1), getpwent(3), mkpasswd(8), vipw(8) adduser(8) |
a343bbd7 | 116 | .SH BUGS |
e1db696c | 117 | User information should (and eventually will) be stored elsewhere. |