Catch a lot of old URL's and update them. Also remove a couple of old files that aren't used.
OK - I can still program Java, I just can't remember how this works :-)
Assuming I can still program in Java, these changes allow monitoring to be disabled at a per-host level or a per-host-per-monitor level.
Build system showed up a couple of compile errors :-) Opps.
This brings the Swap monitor up-to-date with the Memory monitor.
Changed the server to use the external util package. Quite a minor change, but does affect a lot of files.
Added URL to GPL headers.
i-scream is now licensed under the GPL. I've added the GPL headers to every source file, and put a full copy of the license in the appropriate places. I think I've covered everything. This is going to be a mad commit ;)
Minor change to log message.
Major change in the java package naming. This has been held off for some time now, but it really needed doing. The future packaging of all i-scream products will be; uk.org.iscream.<product>.<subpart>.* In the case of the central monitoring system server this will be; uk.org.iscream.cms.server.* The whole server has been changed to follow this structure, and tested to a smallish extent. Further changes in other parts of the CMS will follow.
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
The whole server package structure has been changed. Old Package: uk.ac.ukc.iscream.* New Package: uk.org.iscream.*
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.
Bug Fix: Made the mistake of comparing % of swap *free*, not the % of swap being *used*. This made the alerts all fire when they shouldn't. Also noticed that some "Infinity" items appeared, probably due to a divide by zero whilst working out the percentage. It seems that Double.parseDouble() wasn't throwing NumberFormatException.. maybe :/ Finally, the numbers were appearing like 95.238172732123, which looks silly. Now the NumberFormat class is used to set it to two decimal places.
Two new monitors for Memory and Swap.
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, select a symbolic revision name using the selection box, or choose 'Use Text Field' and enter a numeric revision.