|
|
1.1 root 1: .\" Copyright (c) 1980 The Regents of the University of California.
2: .\" All rights reserved.
3: .\"
4: .\" Redistribution and use in source and binary forms are permitted provided
5: .\" that: (1) source distributions retain this entire copyright notice and
6: .\" comment, and (2) distributions including binaries display the following
7: .\" acknowledgement: ``This product includes software developed by the
8: .\" University of California, Berkeley and its contributors'' in the
9: .\" documentation or other materials provided with the distribution and in
10: .\" all advertising materials mentioning features or use of this software.
11: .\" Neither the name of the University nor the names of its contributors may
12: .\" be used to endorse or promote products derived from this software without
13: .\" specific prior written permission.
14: .\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED
15: .\" WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
16: .\" MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
17: .\"
18: .\" @(#)adduser.8 6.7 (Berkeley) 6/24/90
19: .\"
20: .TH ADDUSER 8 "June 24, 1990"
21: .UC 4
22: .SH NAME
23: adduser \- procedure for adding new users
24: .SH DESCRIPTION
25: A new user must choose a login name, which must not already appear in
26: .IR /etc/passwd or
27: .IR /etc/aliases .
28: It must also not begin with the hyphen (``-'') character.
29: It is strongly recommended that it be all lower-case, and not contain
30: the dot (``.'') character, as that tends to confuse mailers.
31: An account can be added by editing a line into the passwd file; this
32: must be done with the password file locked e.g. by using
33: .IR chpass (1)
34: or
35: .IR vipw (8).
36: .PP
37: A new user is given a group and user id.
38: Login's and user id's should be unique across the system, and often across
39: a group of systems, since they are used to control file access.
40: Typically, users working on similar projects will be put in the same groups.
41: At the University of California, Berkeley, we have groups for system staff,
42: faculty, graduate students, and special groups for large projects.
43: .PP
44: A skeletal account for a new user \*(lqernie\*(rq might look like:
45: .IP
46: ernie::25:30::0:0:Ernie Kovacs,508 Evans Hall,x7925,642-8202:/a/users/ernie:/bin/csh
47: .PP
48: For a description of each of these fields, see
49: .IR passwd (5).
50: .PP
51: It is useful to give new users some help in getting started, supplying
52: them with a few skeletal files such as
53: .I \&.profile
54: if they use \*(lq/bin/sh\*(rq, or
55: .I \&.cshrc
56: and
57: .I \&.login
58: if they use \*(lq/bin/csh\*(rq.
59: The directory
60: \*(lq/usr/share/skel\*(rq contains skeletal definitions of such files.
61: New users should be given copies of these files which, for instance,
62: use
63: .IR tset (1)
64: automatically at each login.
65: .SH FILES
66: .ta 2i
67: /etc/master.passwd user database
68: .br
69: /usr/share/skel skeletal login directory
70: .SH SEE ALSO
71: chpass(1), finger(1), passwd(1), aliases(5), passwd(5), mkpasswd(8), vipw(8)
72: .SH BUGS
73: User information should (and eventually will) be stored elsewhere.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.