ViewVC Help
View File | Revision Log | Show Annotations | Revision Graph | Root Listing
root/i-scream/web/www/contents.inc
(Generate patch)

Comparing web/www/contents.inc (file contents):
Revision 1.24 by tdb, Tue Jul 10 08:54:30 2001 UTC vs.
Revision 1.27 by tdb, Sun Dec 9 18:06:07 2001 UTC

# Line 14 | Line 14
14  
15         <p align="justify">
16          <a href="screenshots/"><img border="0" src="screenshots/thumbnail-reports-raptor-load15.gif" width="100" height="107" align="left"></a>
17 <        All i-scream components now function to initial
18 <        design parameters and our system is regarded to be complete.
19 <        <b><a href="documentation/">Documentation</a></b> is available to assist third party programmers
20 <        in producing Hosts for use with the i-scream server.
17 >        The "project" stage of i-scream has finished, leaving the
18 >        system in a completed state. Since then the goals have
19 >        changed from completing a project to producing a useful
20 >        and functional product.
21 >        <b><a href="documentation/">Documentation</a></b> is
22 >        available for people wanting to try out the i-scream
23 >        system, and our code is availabel via <a href="cvs.shtml">CVS</a>.
24          Our progress during the project can be found in the meeting minutes.
25 <        Code is viewable via <a href="http://raptor.ukc.ac.uk/~tdb1/cgi-bin/viewcvs.cgi">CVS</a> to local users only.
25 >        Work is still continuing to adapt and improve the i-scream central
26 >        monitoring system as a product for use in networked environments.
27         </p>
28  
29         <p align="justify">
30          <a href="screenshots/"><img border="0" src="screenshots/thumbnail-winhost-main.gif" width="100" height="62" align="right"></a>
27        
31          The i-scream Distributed Central Monitoring System Reports
32 <        are now visible on the web.  If you are <b>not</b> a local user, then you may
33 <        view some of the output in the <b><a href="screenshots/">screen shots</a></b> section or you may view some
34 <        static example content on the <a href="reports/"><b>Reports Demo</b></a> pages.
35 <        You may view the latest information about each machine, historical 24-hour
36 <        reports and alerts for each machine.  Our own i-scream server is running constantly,
37 <        along with several hosts to enable plenty of data harvesting.  If you would
38 <        like your i-scream web reports to be linked from this site, then please email us
39 <        at <a href="mailto:dev@i-scream.org.uk">dev@i-scream.org.uk</a>
32 >        are no longer visible on the web.  You may view some of the
33 >        output in the <b><a href="screenshots/">screen shots</a></b>
34 >        section or you can sample some static example content on the
35 >        <a href="reports/"><b>Reports Demo</b></a> pages.
36 >        You may view the latest information about each machine,
37 >        historical 24-hour reports and alerts for each machine. If
38 >        you would like your i-scream web reports to be linked from this
39 >        site, then please email us at
40 >        <a href="mailto:dev@i-scream.org.uk">dev@i-scream.org.uk</a>
41         </p>
42  
43         <p align="justify">
# Line 49 | Line 53
53        
54         <p align="justify">
55          <a href="screenshots/"><img border="0" src="screenshots/thumbnail-alerter-email.gif" width="100" height="107" align="right"></a>
56 <        The latest builds of the i-scream Distributed Central Monitoring System
56 >        Builds of the i-scream Distributed Central Monitoring System
57          are now available for <b><a href="/downloads/">download</a></b> from this
58          website.  To assist in our addition of features to the system, we
59          would be extremely grateful to receive feedback from anybody who has
# Line 82 | Line 86
86          was aimed at the UKC Computer Science department, and as such
87          we believed that a demonstration to the &quot;customer&quot; was important. The
88          feedback from our demonstation was more positive than we had
89 <        anticipated. We believe that the system may now be of great
90 <        interest to anybody who wishes to monitor a number of machines
91 <        on their network using a central configuration.
89 >        anticipated. We believe that the system may now be of interest
90 >        to anybody who wishes to monitor a number of machines on their
91 >        network using a central configuration. The i-scream central
92 >        monitoring system is now being used by the UKC Computer Science
93 >        department, and their feedback is being used to further improve
94 >        the product.
95         </p>
96  
97         <p>&nbsp;</p>
# Line 100 | Line 107
107          Copyright issues immediately ruled out anything involving Mr Whippy,
108          so we had to settle for <i>i-scream</i>. And thus, we were left with a cunning
109          play on words - it still sounded like <i>ice cream</i>, yet also
110 <        served as a functional decription of our system - namely, one which
110 >        served as a functional description of our system - namely, one which
111          screams at somebody if something has gone wrong...
112         </p>
113         <p align="justify">

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines