]>
Commit | Line | Data |
---|---|---|
967b62f5 | 1 | .TH ADDUSR 1 "12 Jan 1996" "Project Athena" |
93d0b3bf | 2 | \" RCSID: $Header$ |
3 | .SH NAME | |
4 | addusr \- add and/or register users in Moira | |
5 | .SH SYNOPSIS | |
00988715 | 6 | .B addusr [-cCdfhrRsSv6] |
93d0b3bf | 7 | .SH DESCRIPTION |
8 | .I Addusr | |
9 | is a tool for adding users in bulk to the moira database and | |
10 | registering them for accounts. It reads the users from a file (or | |
11 | stdin) rather than the menu-oriented regular moira client. | |
12 | ||
13 | The users are entered in one of two formats, depending on whether or | |
14 | not they will be registered. When users are only being added to the | |
15 | database, the format is: | |
16 | .nf | |
17 | lastname, firstname middlename idnumber | |
18 | .fi | |
19 | The lastname may have spaces in it, as it will continue up until the | |
20 | first comma on the line. The firstname also may have spaces, as it | |
21 | will take up everything but the last two tokens on the line. If only | |
22 | 3 tokens are on the line, the middlename will be assumed to be the | |
23 | empty string. The middlename cannot have spaces in it. The idnumber | |
24 | also cannot have spaces, although it may have hyphens in it. The | |
25 | capitalization of the names is not important as it will be corrected | |
26 | before entering into the database. If the operation specified for | |
27 | .B addusr | |
38018b28 | 28 | includes registering users, then there is one additional token on |
93d0b3bf | 29 | the end of the line: |
30 | .nf | |
38018b28 | 31 | lastname, firstname middlename idnumber loginname |
93d0b3bf | 32 | .fi |
93d0b3bf | 33 | .SH OPTIONS |
34 | .IP \fB-file\ \fIfilename\ \fRor\ \fB-f\ \fIfilename\fR: | |
35 | This specifies the file that will be read for the list of users to | |
36 | operate on. If not specifed, standard input will be used. The file | |
37 | format is described above. | |
38 | .IP \fB-class\ \fIclass\ \fRor\ \fB-c\ \fIclass\fR: | |
39 | This specifies the account class that will be used for all users added | |
40 | in this invocation. If not specified, \fITEMP\fR will be used. | |
41 | .IP \fB-comment\ \fI"comment"\ \fRor\ \fB-C\ \fI"comment"\fR: | |
42 | This specifies the comment that will be stored for all users added | |
43 | in this invocation. If not specified, the comment field will be left | |
44 | blank. Note that the double-quotes are not required by \fBaddusr\fR, | |
45 | but will be parsed out by the shell and are only needed to specify | |
46 | comments with spaces in them. | |
47 | .IP \fB-status\ \fIstatus\ \fRor\ \fB-s\ \fIstatus\fR: | |
48 | This specifies the account status that will be used for all users added | |
49 | in this invocation. If not specified, \fI0 (registerable)\fR will be used. | |
50 | .IP \fB-shell\ \fIshell\ \fRor\ \fB-h\ \fIshell\fR: | |
51 | This specifies the login shell that will be stored for all users added | |
967b62f5 | 52 | in this invocation. If not specified, a default will be used. At MIT |
53 | Athena the default is \fI/bin/athena/tcsh\fR, elsewhere it is likely to be | |
54 | \fI/bin/csh\fR. | |
93d0b3bf | 55 | .IP \fB-register\ \fRor\ \fB-R\fR: |
56 | This instructs \fBaddusr\fR to both add the users to the database and | |
38018b28 | 57 | then to immediately register them. The users will be left |
58 | "half-registered", meaning that they have everything but a Kerberos | |
59 | principal. | |
93d0b3bf | 60 | .IP \fB-reg_only\ \fRor\ \fB-r\fR: |
38018b28 | 61 | This instructs \fBaddusr\fR to (half-) register the users without |
62 | attempting to add them to the database. They must already exist in the | |
63 | database. | |
93d0b3bf | 64 | .IP \fB-verbose\ \fRor\ \fB-v\fR: |
65 | This causes \fBaddusr\fR to print messages about each operation as it | |
66 | performs it. | |
67 | .IP \fB-nodupcheck\ \fRor\ \fB-d\fR: | |
68 | Do not attempt to check the database for duplicates before adding | |
69 | users. Normally \fBaddusr\fR will check the database for users with | |
70 | the same name. If it finds any who match in both name and ID number, | |
71 | the user will not be added. If it finds a name match with a different | |
72 | ID number, it will print a warning and add the user anyway. | |
bbf9216c | 73 | .IP \fB-database\ \fIhost:port\ \fRor\ \fB-db\ \fIhost:port\fR: |
93d0b3bf | 74 | Use the specified host and port to contact the Moira server instead of |
75 | the default server. Both may be symbolic names or numbers. If the | |
76 | port is left off, the default Moira server port will be assumed. The | |
77 | server chosen will be the one specified on the command line, specified | |
78 | in the MOIRASERVER environment variable, the hesiod "moira" sloc entry, | |
79 | or the compiled in default, in that order or preference. | |
00988715 | 80 | .IP \fB-secure\ \fRor\ \fB-6\fR: |
81 | This specifies that users added in this invocation will need a secure | |
82 | "Account Coupon" containing additional verification information beyond | |
83 | name and ID number to be allowed to register. | |
93d0b3bf | 84 | |
85 | .SH AUTHOR | |
86 | Mark Rosenstein | |
87 | .SH SEE ALSO | |
88 | moira(1), userreg(1) |