| 1 | .\" |
|---|
| 2 | .\" |
|---|
| 3 | .\" |
|---|
| 4 | .\" |
|---|
| 5 | .\" |
|---|
| 6 | .\" |
|---|
| 7 | .TH MKDS 8 "16 October 2009" "MIT SIPB" |
|---|
| 8 | .SH NAME |
|---|
| 9 | mkds \- Create a discuss meeting |
|---|
| 10 | .SH SYNOPSIS |
|---|
| 11 | .B mkds |
|---|
| 12 | .SH DESCRIPTION |
|---|
| 13 | .I mkds |
|---|
| 14 | creates a discuss meeting on a specified discuss server, |
|---|
| 15 | provided the user has permission to do so. |
|---|
| 16 | |
|---|
| 17 | .I mkds |
|---|
| 18 | will prompt for the server name, a directory where the meeting should |
|---|
| 19 | be stored, the long and short names of the meeting, and whether or not |
|---|
| 20 | the meeting should be public. |
|---|
| 21 | At this point, it attempts to contact the discuss daemon running on the |
|---|
| 22 | discuss server, and an access checked is performed for meeting creation |
|---|
| 23 | (the ``cacl'' file on the server lists authorized users). |
|---|
| 24 | If the meeting can be successfully created and is not a public meeting, |
|---|
| 25 | .I mkds |
|---|
| 26 | will then prompt for a list of users who should have |
|---|
| 27 | permission to create new transactions in the meeting. |
|---|
| 28 | (The user who created the meeting will automatically be given |
|---|
| 29 | chairman permissions.) |
|---|
| 30 | .I mkds |
|---|
| 31 | will then open an editor for |
|---|
| 32 | the creator to enter the initial meeting transaction. Finally, |
|---|
| 33 | .I mkds |
|---|
| 34 | will ask whether or not the meeting should be announced |
|---|
| 35 | (in the new_meetings meeting). |
|---|
| 36 | |
|---|
| 37 | .I mkds |
|---|
| 38 | accepts no arguments. |
|---|
| 39 | |
|---|
| 40 | The meeting created by |
|---|
| 41 | .I mkds |
|---|
| 42 | is a pure discuss meeting in its original form. If it is intended |
|---|
| 43 | to be used as a mail archive, a server maintainer will need to perform |
|---|
| 44 | additional configuration to accept mail for the meeting's alias and |
|---|
| 45 | run |
|---|
| 46 | .I dsmail |
|---|
| 47 | as appropriate. |
|---|
| 48 | |
|---|
| 49 | A meeting created with |
|---|
| 50 | .I mkds |
|---|
| 51 | can be removed with |
|---|
| 52 | \fIrmds\fR. |
|---|
| 53 | |
|---|
| 54 | The cacl file has a similar format to that of a discuss meeting acl; |
|---|
| 55 | the first line contains a number which is the number of entries on the |
|---|
| 56 | acl. |
|---|
| 57 | The subsequent lines contain a list of access bits, a colon, |
|---|
| 58 | and the user they correspond to. |
|---|
| 59 | However, unlike meeting acls, only the 'a' bit is relevant for |
|---|
| 60 | meeting creation. |
|---|
| 61 | |
|---|
| 62 | .SH FILES |
|---|
| 63 | .ta \w'/var/spool/discuss/cacl 'u |
|---|
| 64 | .br |
|---|
| 65 | ~/.meetings Data file listing meetings that you attend. |
|---|
| 66 | .br |
|---|
| 67 | /var/spool/discuss/cacl The list of users (Kerberos principals) who |
|---|
| 68 | can create meetings on the server. |
|---|
| 69 | |
|---|
| 70 | .SH AUTHORS |
|---|
| 71 | Robert French and Ken Raeburn, MIT Student Information Processing Board |
|---|
| 72 | |
|---|
| 73 | .SH "SEE ALSO" |
|---|
| 74 | discuss(1), dsmail(1), rmds(8) |
|---|
| 75 | |
|---|
| 76 | |
|---|
| 77 | |
|---|
| 78 | |
|---|
| 79 | |
|---|
| 80 | |
|---|
