X-Git-Url: http://git.i-scream.org/?a=blobdiff_plain;f=www%2Fcontents.inc;h=f35b244114a3e18855b2db4061571bf50756ca3a;hb=a5515849053f82757f19704c16d29537e306e1bb;hp=81559b9574a48801d40a556371f40b4b7501876e;hpb=85875d83f53389e59b9075b6e0f83eec3e76d03a;p=www.i-scream.org.git diff --git a/www/contents.inc b/www/contents.inc index 81559b9..f35b244 100644 --- a/www/contents.inc +++ b/www/contents.inc @@ -16,18 +16,19 @@ All i-scream components now function to initial design parameters and our system is regarded to be complete. - Documentation is available to assist third party programmers + Documentation is available to assist third party programmers in producing Hosts for use with the i-scream server. Our progress during the project can be found in the meeting minutes. - Code is viewable via CVS to local users users only. + Code is viewable via CVS to local users only.

- The i-scream Distributed Central Monitoring System Reports + The i-scream Distributed Central Monitoring System Reports are now visible on the web. If you are not a local user, then you may - view some of the output in the screenshots section. + view some of the output in the screen shots section or you may view some + static example content on the Reports Demo pages. You may view the latest information about each machine, historical 24-hour reports and alerts for each machine. Our own i-scream server is running constantly, along with several hosts to enable plenty of data harvesting. If you would @@ -77,7 +78,7 @@

- As can be seen in our "problem domain" document, the project + As can be seen in our "problem domain" document, the project was aimed at the UKC Computer Science department, and as such we believed that a demonstration to the "customer" was important. The feedback from our demonstation was more positive than we had