Revision 1.8 - (view) (annotate) - [select for diffs]
Fri Mar 23 02:32:49 2001 UTC (23 years, 1 month ago) by tdb
Branch: MAIN
CVS Tags: PROJECT_COMPLETION
Changes since 1.7: +48 -17 lines
Diff to previous 1.7

Fully javadoc'd all the monitors. Also made a few little changes here and there,
removing code that had been duplicated by copying other monitors, and tidying
up any silly little things (such has hardcoded integer values).

Modified to use the new style queuing in the local client

Revision 1.6 - (view) (annotate) - [select for diffs]
Thu Mar 22 01:51:27 2001 UTC (23 years, 1 month ago) by ajm
Branch: MAIN
Changes since 1.5: +3 -3 lines
Diff to previous 1.5

modified old comment

Now has support for giving separate mount points

Revision 1.4 - (view) (annotate) - [select for diffs]
Sun Mar 18 00:54:04 2001 UTC (23 years, 2 months ago) by ajm
Branch: MAIN
Changes since 1.3: +27 -6 lines
Diff to previous 1.3

added the option:

Monitor.Disk.thresholdMeasure=VALUE/PERCENTAGE
Monitor.Memory.thresholdMeasure=VALUE/PERCENTAGE

to allow the choosing of what is used to measure the crossing of a threshold.

The whole server package structure has been changed.
Old Package: uk.ac.ukc.iscream.*
New Package: uk.org.iscream.*

Revision 1.2 - (view) (annotate) - [select for diffs]
Fri Mar 9 03:30:55 2001 UTC (23 years, 2 months ago) by ajm
Branch: MAIN
Changes since 1.1: +15 -6 lines
Diff to previous 1.1

TOTALLY re-wrote the Register class and made appropriate changes thoughout.  It
is now much more obvious what is going on in many places.

The problem was probably caused by doing CPU as a first monitor and hard coding
the number of attributes a Register stores.  Now if a monitor wants to store
multiple attributes, it has to do that itself.  This makes alot of things
much more readable and inteligable as a result.

The new Disk monitor, allows the monitoring of all disks on a host.