source: trunk/athena/bin/lert/admin.help @ 7779

Revision 7779, 1.8 KB checked in by cfields, 29 years ago (diff)
Initial revision
RevLine 
[7779]1quick help for administrators of the new lert program...
2
31.  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
62.  in the lert directory, edit a file lerta.
7(make the last letter match your lertload)
8
93.  use an editor to make a list of names (one name to a line!)
10    run lertload like this
11      lertload a < yourfile
12
13good luck.
14
15let me know if you have any suggestions about this.
16
17more notes...
18
19where does lert keep database and files?
20 /afs/athena.mit.edu/system/config/lert
21
22lertdata is the database.
23
24lertlog is the log of users who have done "lert -n"
25
26lert0 is the standard "first notification" message which will always
27precede any other messages.  it is intended to let you tell the user
28how to quit being notified.
29
30lerta, lertb, etc. are the notifications for group a, group b, etc.
31you should probably include an explanation of what the notification is
32for 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
36administrators have to manage two things:
37  grouping users
38  messages for those groups
39
40the utility programs are:
41
42lertload -- to add categories and users to the database.
43
44lertdump -- show all the names in the database and the categories...
45
46note: users can be in more than one group.  to see what groups are in
47use and what users are in which groups, use lertdump.
48
49lertused user -- remove user from database
50
51lertstop type -- remove category from database
52
53users who are only in the removed category also will be removed from
54the database.
55
56lertsaid -- see the log of users who did "lert -n"
57
58when users use "lert -n" to stop getting notifications, lert puts them
59in lertlog (a second database).  lertsaid dumps this second database
60for you, allowing you to see who has read the messages and
61acknowledged them.
62
Note: See TracBrowser for help on using the repository browser.