$Id: TODO,v 1.20 1998/07/13 12:03:22 trockij Exp $

-add a zephyr alert.

-re-vamp the host disabling. 1) store them in a table with a timeout
 on each so that they can automatically re-enable themselves so
 people don't forget to re-enable them manually. 2) don't do
 the disabling by "commenting" them out of the host groups.
 We still want them to be tested for failure, but just disable
 alerts that have to do with the disabled hosts.
 When a host is commented out, accept a "reason" field that
 is later accessible so that you can tell why someone disabled
 the host.

-Support general asynchronous traps from any other programs

-allow checking a service at a particular time of day, maybe using
 inPeriod.

-service templates in the config file would be nice. Maybe this can
 be done with M4 macros or something. Maybe it doesn't belong in
 mon itself.

-add a "time first noticed" to each service, which is the time
 of the first failure. When a monitor succeeds, reset "time first
 noticed" to zero. Add a new argument to alert programs passing this
 variable.

-implement some sort of "worsening-condition" rule on a per-service
 basis, triggering different alerts when things are really bad.

-make Wietse's tcp_scan.c multiplex hosts in addition to ports

-make a name for this silly program other than mon (well, mon *is*
 easy to type!)

-maybe make a command that will disable an alert for a certain amount
 of time (maybe implement this as an at(1) job??)

-make it possible to disable just one of multiple alarms in a service

-handle client timeouts by adding a command I/O sub that calls select(2)
 on the client's filehandle, and closes the connection when it times out

-Add better grammar checking to the config file. Don't allow watch
 records for groups that haven't been defined, etc.

-Do something to control rampant alerts because of a lot of
 inter-dependent test fail. E.g, you're testing if a hub is down,
 and another test depends on a machine plugged into that hub. The hub
 burns up or some goon trips over the power cord, and you get pages
 because the hub is down, and because you can't get to the service
 from

-change $watch{$group}[$service] to be $watch{$group}{$service}, because
 services are now required to have a tag

-Handle alert processes like monitor processes, meaning only allow
 one running at a time

-What happens to stderr from monitors and alerts???
