Annotated edit history of
chpasswd(8) version 1, including all changes.
View license author blame.
| Rev |
Author |
# |
Line |
| 1 |
perry |
1 |
CHPASSWD |
| |
|
2 |
!!!CHPASSWD |
| |
|
3 |
NAME |
| |
|
4 |
SYNOPSIS |
| |
|
5 |
DESCRIPTION |
| |
|
6 |
CAVEATS |
| |
|
7 |
SEE ALSO |
| |
|
8 |
AUTHOR |
| |
|
9 |
---- |
| |
|
10 |
!!NAME |
| |
|
11 |
|
| |
|
12 |
|
| |
|
13 |
__chpasswd__ - update password file in batch |
| |
|
14 |
!!SYNOPSIS |
| |
|
15 |
|
| |
|
16 |
|
| |
|
17 |
__chpasswd [[-e]__ |
| |
|
18 |
!!DESCRIPTION |
| |
|
19 |
|
| |
|
20 |
|
| |
|
21 |
__chpasswd__ reads a file of user name and password pairs |
| |
|
22 |
from standard input and uses this information to update a |
| |
|
23 |
group of existing users. Without the -e switch, the |
| |
|
24 |
passwords are expected to be cleartext. With the -e switch, |
| |
|
25 |
the passwords are expected to be in encrypted form. Each |
| |
|
26 |
line is of the format |
| |
|
27 |
|
| |
|
28 |
|
| |
|
29 |
''user_name'':''password'' |
| |
|
30 |
|
| |
|
31 |
|
| |
|
32 |
The named user must exist. The supplied password will be |
| |
|
33 |
encrypted as necessary, and the password age updated, if |
| |
|
34 |
present. |
| |
|
35 |
|
| |
|
36 |
|
| |
|
37 |
This command is intended to be used in a large system |
| |
|
38 |
environment where many accounts are created at a single |
| |
|
39 |
time. |
| |
|
40 |
!!CAVEATS |
| |
|
41 |
|
| |
|
42 |
|
| |
|
43 |
The input file must be protected if it contains unencrypted |
| |
|
44 |
passwords. |
| |
|
45 |
!!SEE ALSO |
| |
|
46 |
|
| |
|
47 |
|
| |
|
48 |
passwd(1), useradd(8), |
| |
|
49 |
newusers(8) |
| |
|
50 |
!!AUTHOR |
| |
|
51 |
|
| |
|
52 |
|
| |
|
53 |
Julianne Frances Haugh (jfh@austin.ibm.com) |
| |
|
54 |
---- |
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.
