| 1 | quick help for administrators of the new lert program... |
|---|
| 2 | |
|---|
| 3 | 1. to put someone in the database for lert to notify |
|---|
| 4 | pick a letter that is not in use (a-z, A-Z, etc.) |
|---|
| 5 | |
|---|
| 6 | 2. in the lert directory, edit a file lerta. |
|---|
| 7 | (make the last letter match your lertload) |
|---|
| 8 | |
|---|
| 9 | 3. use an editor to make a list of names (one name to a line!) |
|---|
| 10 | run lertload like this |
|---|
| 11 | lertload a < yourfile |
|---|
| 12 | |
|---|
| 13 | good luck. |
|---|
| 14 | |
|---|
| 15 | let me know if you have any suggestions about this. |
|---|
| 16 | |
|---|
| 17 | more notes... |
|---|
| 18 | |
|---|
| 19 | where does lert keep database and files? |
|---|
| 20 | /afs/athena.mit.edu/system/config/lert |
|---|
| 21 | |
|---|
| 22 | lertdata is the database. |
|---|
| 23 | |
|---|
| 24 | lertlog is the log of users who have done "lert -n" |
|---|
| 25 | |
|---|
| 26 | lert0 is the standard "first notification" message which will always |
|---|
| 27 | precede any other messages. it is intended to let you tell the user |
|---|
| 28 | how to quit being notified. |
|---|
| 29 | |
|---|
| 30 | lerta, lertb, etc. are the notifications for group a, group b, etc. |
|---|
| 31 | you should probably include an explanation of what the notification is |
|---|
| 32 | for and what response (if any) the user is expected to provide. |
|---|
| 33 | |
|---|
| 34 | (sample lert0 and lerta files are included in the release package) |
|---|
| 35 | |
|---|
| 36 | administrators have to manage two things: |
|---|
| 37 | grouping users |
|---|
| 38 | messages for those groups |
|---|
| 39 | |
|---|
| 40 | the utility programs are: |
|---|
| 41 | |
|---|
| 42 | lertload -- to add categories and users to the database. |
|---|
| 43 | |
|---|
| 44 | lertdump -- show all the names in the database and the categories... |
|---|
| 45 | |
|---|
| 46 | note: users can be in more than one group. to see what groups are in |
|---|
| 47 | use and what users are in which groups, use lertdump. |
|---|
| 48 | |
|---|
| 49 | lertused user -- remove user from database |
|---|
| 50 | |
|---|
| 51 | lertstop type -- remove category from database |
|---|
| 52 | |
|---|
| 53 | users who are only in the removed category also will be removed from |
|---|
| 54 | the database. |
|---|
| 55 | |
|---|
| 56 | lertsaid -- see the log of users who did "lert -n" |
|---|
| 57 | |
|---|
| 58 | when users use "lert -n" to stop getting notifications, lert puts them |
|---|
| 59 | in lertlog (a second database). lertsaid dumps this second database |
|---|
| 60 | for you, allowing you to see who has read the messages and |
|---|
| 61 | acknowledged them. |
|---|
| 62 | |
|---|
